OemCompiler

[velo]

On flex 3, adobe release the flex-compiler-oem.jar.

Any planning to stop using mxmlc/compc in console and start to use the
oem compiler?

Need an extra hand? I wanna to help in this question.


VELO

[Christian Edward Gruber]

It's been on the long-term radar since we first were told about it
(Adobe offered to give an early -access version, since I was working
on a common client, but we rejected it because we couldn't ship
it.). It's definitely the next generation of the plugin, for sure,
but at that point, flex2 won't really be supported, so I think we're
probably going to clean up some things about this information before
tackling the re-write. There are some outstanding issues people will
need solved for long-term flex 2 usage.

Christian.

> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google
> Groups "Israfil Mojo User Discussions" group.
> To post to this group, send email to israfil-m...@googlegroups.com
> To unsubscribe from this group, send email to israfil-mojo-us...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/israfil-mojo-u

[VELO]

OemCompiler is not compatible with 2.0.1?

Can't do something like:
mxmlc -compatibility-version=2.0.1
../samples/explorer/controls/ButtonExample.mxml

VELO

[Christian Edward Gruber]

It might be, but it's oriented around Flex 3. I haven't looked at it
enough to determine if it's suitable for compiling flex 2 apps, or
what would be involved.

Christian.

[VELO]

So, no planning for Israfil-oem-mojo.

Right?

VELO

On Fri, Mar 7, 2008 at 4:33 PM, Christian Edward Gruber

[Christian Edward Gruber]

Nah, it would be israfil-flex-mojo 2.x, probably.

Christian.