If browser plugins were a future we would be worrying quite a bit about releasing Flex 4.7 or Flex 5. The problem is, the most popular plugin in the world seems to have a hazy future, which is probably the reason for all the discussion about moving away from Flash.
On Mon, Feb 20, 2012 at 9:09 AM, jude <flexcapaci...@gmail.com> wrote: > The ease of making HTML pages was partly what hooked me so long ago. I > could type something in a text editor and it would show up rendered in the > browser. > > What about a browser plug in that would handle .mxml files? Then you'd just > drag and drop an MXML file to the browser and it would render? > > Judah > > On Sun, Feb 12, 2012 at 11:19 AM, Martin Heidegger <m...@leichtgewicht.at > >wrote: > > > The differences to languages like Python is that AS3 requires a compiler, > > and unlike - for example - haXe the compiler for AS3 is not written in > AS3. > > > > One option is to implement that nice functionality would be a compiler in > > AS3. There is rudimentary ActionScript 3 evaluator called "Eval" > available > > [1]. > > The other option would be to "call" the Compiler using a Java > executable. > > [2] That will work "perfectly" but requires the java plugin to be > installed. > > The third option would be to compile it on a server which well ... would > > require a server. Wonderfl is nice but highly proprietary. And we could > not > > use > > those examples offline. > > > > A completely different approach would be to implement a "IDE" tutorial. > To > > be used with all AS3 ide's out there. You download the IDE and there you > > have access to documentation from Apache. This way all the IDE's could > > provide the same Flex documentation that "interacts" with their editor. > > > > Just thoughts. > > > > yours > > Martin. > > > > [1] http://eval.hurlant.com/ > > [2] http://www.victordramba.com/?p=31 > > > -- Regards, Ganaraj P R
