Re: [ASJS] AS to HTML5 in action: announcing the ASJS Publisher and the VanillaSDK JS framework.
Om, I've committed a new build.xml, build.properties and README for the ASJS Publisher. I also added mxmlc.bat to the compiler.jx bin directory. Please update your working copies and try again. Thanks, EdB On Sun, Jan 27, 2013 at 9:59 AM, Erik de Bruin e...@ixsoftware.nl wrote: Always troublesome, you Windows folk :-) I'll fix the script and add the mxmlc.bat file on Monday. Thanks for testing. EdB On Sunday, January 27, 2013, Om wrote: Erik, This sounds very exciting. I cant wait to play around with your prototype! I am looking at the README files and I dont seem to be able to locate anything regarding how to build and use your prototype. The falcon\trunk\compiler.jx\README does not seem to have anything significant. Any advice? BTW, UIComponent.js? Sweet! Thanks, Om Never mind, got it: asjs\branches\develop\publisher\README. Okay, I read the README and created the appropriate build.properties file. When I run the ant script, The falconjx ant task is bumming out: === snip ... falconJx: [echo] Compiling the AS project into intermediate JS BUILD FAILED C:\p\flex_os\workspace\flexroot\asjs\branches\develop\publisher\build.xml:93: Ex ecute failed: java.io.IOException: Cannot run program C:\p\flex_os\workspace\fl exroot\falcon\trunk\compiler.jx\bin\mxmlc: CreateProcess error=193, %1 is not a valid Win32 application at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) at java.lang.Runtime.exec(Runtime.java:593) at org.apache.tools.ant.taskdefs.Execute$Java13CommandLauncher.exec(Exec ute.java:862) at org.apache.tools.ant.taskdefs.Execute.launch(Execute.java:481) at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:495) at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:631) at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:672) at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:498) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.jav a:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:390) at org.apache.tools.ant.Target.performTasks(Target.java:411) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399) at org.apache.tools.ant.Project.executeTarget(Project.java:1368) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExe cutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1251) at org.apache.tools.ant.Main.runBuild(Main.java:809) at org.apache.tools.ant.Main.startAnt(Main.java:217) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109) Caused by: java.io.IOException: CreateProcess error=193, %1 is not a valid Win32 application at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.init(ProcessImpl.java:81) at java.lang.ProcessImpl.start(ProcessImpl.java:30) at java.lang.ProcessBuilder.start(ProcessBuilder.java:453) ... 23 more Total time: 7 seconds === It looks like the falcon.jx/mxmlc is a Mac version file. I am guessing something needs to change with the ant scripts in the falcon or falcon.jx projects? Thanks, Om -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: [ASJS] AS to HTML5 in action: announcing the ASJS Publisher and the VanillaSDK JS framework.
Erik, This sounds very exciting. I cant wait to play around with your prototype! I am looking at the README files and I dont seem to be able to locate anything regarding how to build and use your prototype. The falcon\trunk\compiler.jx\README does not seem to have anything significant. Any advice? BTW, UIComponent.js? Sweet! Thanks, Om Never mind, got it: asjs\branches\develop\publisher\README. Okay, I read the README and created the appropriate build.properties file. When I run the ant script, The falconjx ant task is bumming out: === snip ... falconJx: [echo] Compiling the AS project into intermediate JS BUILD FAILED C:\p\flex_os\workspace\flexroot\asjs\branches\develop\publisher\build.xml:93: Ex ecute failed: java.io.IOException: Cannot run program C:\p\flex_os\workspace\fl exroot\falcon\trunk\compiler.jx\bin\mxmlc: CreateProcess error=193, %1 is not a valid Win32 application at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) at java.lang.Runtime.exec(Runtime.java:593) at org.apache.tools.ant.taskdefs.Execute$Java13CommandLauncher.exec(Exec ute.java:862) at org.apache.tools.ant.taskdefs.Execute.launch(Execute.java:481) at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:495) at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:631) at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:672) at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:498) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.jav a:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:390) at org.apache.tools.ant.Target.performTasks(Target.java:411) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399) at org.apache.tools.ant.Project.executeTarget(Project.java:1368) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExe cutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1251) at org.apache.tools.ant.Main.runBuild(Main.java:809) at org.apache.tools.ant.Main.startAnt(Main.java:217) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109) Caused by: java.io.IOException: CreateProcess error=193, %1 is not a valid Win32 application at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.init(ProcessImpl.java:81) at java.lang.ProcessImpl.start(ProcessImpl.java:30) at java.lang.ProcessBuilder.start(ProcessBuilder.java:453) ... 23 more Total time: 7 seconds === It looks like the falcon.jx/mxmlc is a Mac version file. I am guessing something needs to change with the ant scripts in the falcon or falcon.jx projects? Thanks, Om
Re: [ASJS] AS to HTML5 in action: announcing the ASJS Publisher and the VanillaSDK JS framework.
Well not necessarily, Either via DOM emulation or swapping the PlayerGlobal with a DOM API, you could technically build full AS components that get converted into JS. Given the second choice, then you'd still need to be aware of the HTML quirks as if you would handcraft JS components. The first solution would obfuscate the platform specific API to something similar to today's Flash display list. (less Flash specific, more generic) Speaking for the current Flex, we love the fact that anything is virtually possible, and the framework is very extendable to whatever the client demands. Would hate to lose that flexibility on the UI side of things, but great things come at a price :) We mainly focus on HTML/JS now, but falcon can go much broader, true write once, run everywhere is utopia... But we could try to draw that line as low as we can? A VanillaSDK-API would have to be extensive to suit most (enterprise) needs, as you mentioned some kind of Ext-JS plug will get you quite far in the UI requirements section, then again a more generic Apache Flex sdk to target UI could be better ported in the future, if you plan to not just target JS, but anything else, as native Android for example. Tough choices! And to be honest I know too little of the whole current web-ecology to keep blabbering on about this :) In the end, we need enough traction to this new Flex framework from the outside world, we need to fill a gap and be successful at how it plays its role compared to the other HTML (or other platform target) solutions. -Original Message- From: Roland Zwaga Sent: Saturday, January 26, 2013 2:51 PM To: dev@flex.apache.org Subject: Re: [ASJS] AS to HTML5 in action: announcing the ASJS Publisher and the VanillaSDK JS framework. On 26 January 2013 01:40, Hans Van den Keybus h...@dotdotcommadot.comwrote: But if I understand it correctly, wouldn't it mean in Erik's model that when I create my own custom datagrid component for instance, I would also have to write a JS version for this? (For me personally this is what I would want to avoid -- writing JS myself :) ) I hate to be a party-pooper here :) But I think if you're going to be building HTML/JS applications there is no way around having to learn at least a measure of JS and do some JS coding manually. When creating an HTML component I think JS is actually exactly the language you need to add the UI logic, since the UI logic is very platform specific (in this case the browser) it is probably easier to have those pieces of code done in JS than it is to cross-compile them. From where I sit I think having all of your business logic (which in most applications will be the brunt of your code) will make much more sense being cross-compiled. That's why I was suggesting the integration options with existing HTML components, there's a wealth of them out there ready to be taken advantage of. If you want to build components from the ground up, IMHO, going native is the best choice. But feel free to disagree and prove me wrong of course :) cheers, Roland
Re: [ASJS] AS to HTML5 in action: announcing the ASJS Publisher and the VanillaSDK JS framework.
On Sat, Jan 26, 2013 at 11:02 PM, Om bigosma...@gmail.com wrote: On Fri, Jan 25, 2013 at 7:03 AM, Erik de Bruin e...@ixsoftware.nl wrote: Hi, I'm proud to announce the availability of a 'proof of concept' for a Actionscript to HTML5/Javascript work flow. Standing on the shoulders of giants (Gordon, Mike, Alex et al., I'm looking at you!) I was able to piece together a working prototype of a full Flash Builder - Browser application development tool chain. The tools are: - the Flex SDK. Most importantly, the goal is to allow developers to use the tools they know while giving them the ability to publish their work to a www-friendly format. - the FalconJx browser, which can as of today output a pretty descent approximation of AS in JS, the 'goog' way. - the ASJS Publisher, an ant script that takes the JS that FalconJx produces and puts it through the Google Closure Tools to create both intermediate and release versions of the web native application. - the VanillaSDK, my attempt at an AS compatible JS framework. I have plan for a different type of framework, even better integrated with the current Flex SDK, but more on that later ;-) With these new tools, you are now able (albeit in a very limited way) to use the regular Flex SDK for application development in your favorite development tool. Using the new ASJS Publisher script, you can compile your project into a highly optimized HTML5 application that will run in any modern browser. It's that simple... well, almost :-) As this is a prototype, there are some (ha!) limitations: - the VanillaSDK (the Javascript counterpart to the Flex SDK) is very basic indeed, with only 2 UI components: Button and Label. Both these components currently support only 1 or 2 properties (position and label or text). It does show, however, how easy it is to create these Flex SDK compatible UI elements. - not all AS language features are fully supported on the JS side yet. - there isn't (yet) support for MXML, but that's coming soon. - since this is only a proof of concept, there is almost certainly a lot that doesn't work -- to be honest, I'd be suprised if anything works at all :-) If you want to try this out, please get the latest version of the tool set from SVN, starting with here: https://svn.apache.org/repos/asf/flex/asjs/branches/develop Begin with the README you'll find there. After an initially non-trivial setup (SDK, Falcon, FalconJx and the new tools), the everyday use is really simple: just one command in a terminal, calling one ant script with one argument: this will publish your Flash Builder application to the 'js-intermediate' and 'js-release' directories in your FB project folder. Simply double click on the HTML files in either of these will run your application in your default browser, no Flash plugin needed! Please let me know if this works for you and what issues you encounter. Should you feel inspired, feel free to contribute, this part of the project can use all the help it can get! Have fun, EdB Erik, This sounds very exciting. I cant wait to play around with your prototype! I am looking at the README files and I dont seem to be able to locate anything regarding how to build and use your prototype. The falcon\trunk\compiler.jx\README does not seem to have anything significant. Any advice? BTW, UIComponent.js? Sweet! Thanks, Om Never mind, got it: asjs\branches\develop\publisher\README.
Re: [ASJS] AS to HTML5 in action: announcing the ASJS Publisher and the VanillaSDK JS framework.
Firstly, WELL DONE TO ALL cause this sounds epic! I haven't tried it yet but it's already in my todo list. I'll go slightly off topic here and ask you if you can share your vision about the VanillaSDK Erik. I'm reading the hundreds of emails but its kinda hard to keep up with you guys. You do a great job and you do it fast. I plan on investing some time to our beloved project and spending some time with VanillaSDK made the click for me. That's why I ask. Also, any hints on what I should read or check to understand how I can contribute would be really appreciated. Please keep in mind that I never had any experience with compilers. I'm more of a 'components and apps' developer. Again, congratulations guys. I hope I'll be able to join in soon. At least I'll try. :) On Fri, Jan 25, 2013 at 5:03 PM, Erik de Bruin e...@ixsoftware.nl wrote: Hi, I'm proud to announce the availability of a 'proof of concept' for a Actionscript to HTML5/Javascript work flow. Standing on the shoulders of giants (Gordon, Mike, Alex et al., I'm looking at you!) I was able to piece together a working prototype of a full Flash Builder - Browser application development tool chain. The tools are: - the Flex SDK. Most importantly, the goal is to allow developers to use the tools they know while giving them the ability to publish their work to a www-friendly format. - the FalconJx browser, which can as of today output a pretty descent approximation of AS in JS, the 'goog' way. - the ASJS Publisher, an ant script that takes the JS that FalconJx produces and puts it through the Google Closure Tools to create both intermediate and release versions of the web native application. - the VanillaSDK, my attempt at an AS compatible JS framework. I have plan for a different type of framework, even better integrated with the current Flex SDK, but more on that later ;-) With these new tools, you are now able (albeit in a very limited way) to use the regular Flex SDK for application development in your favorite development tool. Using the new ASJS Publisher script, you can compile your project into a highly optimized HTML5 application that will run in any modern browser. It's that simple... well, almost :-) As this is a prototype, there are some (ha!) limitations: - the VanillaSDK (the Javascript counterpart to the Flex SDK) is very basic indeed, with only 2 UI components: Button and Label. Both these components currently support only 1 or 2 properties (position and label or text). It does show, however, how easy it is to create these Flex SDK compatible UI elements. - not all AS language features are fully supported on the JS side yet. - there isn't (yet) support for MXML, but that's coming soon. - since this is only a proof of concept, there is almost certainly a lot that doesn't work -- to be honest, I'd be suprised if anything works at all :-) If you want to try this out, please get the latest version of the tool set from SVN, starting with here: https://svn.apache.org/repos/asf/flex/asjs/branches/develop Begin with the README you'll find there. After an initially non-trivial setup (SDK, Falcon, FalconJx and the new tools), the everyday use is really simple: just one command in a terminal, calling one ant script with one argument: this will publish your Flash Builder application to the 'js-intermediate' and 'js-release' directories in your FB project folder. Simply double click on the HTML files in either of these will run your application in your default browser, no Flash plugin needed! Please let me know if this works for you and what issues you encounter. Should you feel inspired, feel free to contribute, this part of the project can use all the help it can get! Have fun, EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Nick Tsitlakidis, CEO and Software Architect at Perfect Edge LTD. www.perfectedz.com
Re: [ASJS] AS to HTML5 in action: announcing the ASJS Publisher and the VanillaSDK JS framework.
Hi, The idea behind the Vanilla SDK is that there is already a pretty good AS side UI toolkit: the Flex SDK. That means there is no need to do any work on the AS side creating a new framework. The only thing we need to build is the JS side of the equation. The Vanilla SDK philosophy is to create a JS framework that has the same public API as the Flex SDK, but with a different, platform (web native/'goog') implementation behind the scenes. This would allow for development in exactly the same way as you are now used to in Flash Builder, but would add the option to publish the project to HTML5. And I'm working on something that might actually facilitate this 'inside' the Flex SDK, which means the main objection to this approach -- developers not knowing which components and which properties are supported -- will be taken away. EdB On Fri, Jan 25, 2013 at 7:11 PM, Frank Pepermans frankp...@hotmail.com wrote: I concur, this is huge news for the future of Flex! Congrats to making this possible! About the vanilla sdk, I have some Jangaroo experience, there you can build a full AS Button component, which compiles to JS without the need of a vanilla SDK. I assume technically you can do the same, if the basic Flash API stuff is 'emulated' for JS and included with the compilation? -Original Message- From: Nick Tsitlakidis Sent: Friday, January 25, 2013 6:58 PM To: dev@flex.apache.org Subject: Re: [ASJS] AS to HTML5 in action: announcing the ASJS Publisher and the VanillaSDK JS framework. Firstly, WELL DONE TO ALL cause this sounds epic! I haven't tried it yet but it's already in my todo list. I'll go slightly off topic here and ask you if you can share your vision about the VanillaSDK Erik. I'm reading the hundreds of emails but its kinda hard to keep up with you guys. You do a great job and you do it fast. I plan on investing some time to our beloved project and spending some time with VanillaSDK made the click for me. That's why I ask. Also, any hints on what I should read or check to understand how I can contribute would be really appreciated. Please keep in mind that I never had any experience with compilers. I'm more of a 'components and apps' developer. Again, congratulations guys. I hope I'll be able to join in soon. At least I'll try. :) On Fri, Jan 25, 2013 at 5:03 PM, Erik de Bruin e...@ixsoftware.nl wrote: Hi, I'm proud to announce the availability of a 'proof of concept' for a Actionscript to HTML5/Javascript work flow. Standing on the shoulders of giants (Gordon, Mike, Alex et al., I'm looking at you!) I was able to piece together a working prototype of a full Flash Builder - Browser application development tool chain. The tools are: - the Flex SDK. Most importantly, the goal is to allow developers to use the tools they know while giving them the ability to publish their work to a www-friendly format. - the FalconJx browser, which can as of today output a pretty descent approximation of AS in JS, the 'goog' way. - the ASJS Publisher, an ant script that takes the JS that FalconJx produces and puts it through the Google Closure Tools to create both intermediate and release versions of the web native application. - the VanillaSDK, my attempt at an AS compatible JS framework. I have plan for a different type of framework, even better integrated with the current Flex SDK, but more on that later ;-) With these new tools, you are now able (albeit in a very limited way) to use the regular Flex SDK for application development in your favorite development tool. Using the new ASJS Publisher script, you can compile your project into a highly optimized HTML5 application that will run in any modern browser. It's that simple... well, almost :-) As this is a prototype, there are some (ha!) limitations: - the VanillaSDK (the Javascript counterpart to the Flex SDK) is very basic indeed, with only 2 UI components: Button and Label. Both these components currently support only 1 or 2 properties (position and label or text). It does show, however, how easy it is to create these Flex SDK compatible UI elements. - not all AS language features are fully supported on the JS side yet. - there isn't (yet) support for MXML, but that's coming soon. - since this is only a proof of concept, there is almost certainly a lot that doesn't work -- to be honest, I'd be suprised if anything works at all :-) If you want to try this out, please get the latest version of the tool set from SVN, starting with here: https://svn.apache.org/repos/asf/flex/asjs/branches/develop Begin with the README you'll find there. After an initially non-trivial setup (SDK, Falcon, FalconJx and the new tools), the everyday use is really simple: just one command in a terminal, calling one ant script with one argument: this will publish your Flash Builder application to the 'js-intermediate' and 'js-release' directories in your FB project folder. Simply double
Re: [ASJS] AS to HTML5 in action: announcing the ASJS Publisher and the VanillaSDK JS framework.
On 1/25/13 10:11 AM, Frank Pepermans frankp...@hotmail.com wrote: I concur, this is huge news for the future of Flex! Congrats to making this possible! About the vanilla sdk, I have some Jangaroo experience, there you can build a full AS Button component, which compiles to JS without the need of a vanilla SDK. I assume technically you can do the same, if the basic Flash API stuff is 'emulated' for JS and included with the compilation? Yes, it is great to see other approaches being investigated. I think there three approaches right now. 1) Jangaroo: Actually a product. Uses Flash API emulation 2) Eriks' VanillaSDK: Still a proof of concept. My main concerns are that it will be a lot of work to finish, and that it will drag with it all of the unused code the Flex SDK does with its intertwined dependencies. 3) My approach: Still a proof of concept. Brand new SDK designed to be optimally implemented in both JS and AS. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [ASJS] AS to HTML5 in action: announcing the ASJS Publisher and the VanillaSDK JS framework.
Hello Alex, To be honest, your approach sounds like the proper way to move forward (at least to me), but I still think that using what we already have in the AS side is going to take less time and as you have already said in some emails, this year will be a crucial one for Flex. Anyway, having choices is always good. Time will show which one will be adopted by the community. Regarding the VanillaSDK, I can't understand how it's possible without some kind of Flash API emulation (like in Jangaroo) but I haven't looked at the code yet so I think I'll get it when I do. On Fri, Jan 25, 2013 at 8:30 PM, Alex Harui aha...@adobe.com wrote: On 1/25/13 10:11 AM, Frank Pepermans frankp...@hotmail.com wrote: I concur, this is huge news for the future of Flex! Congrats to making this possible! About the vanilla sdk, I have some Jangaroo experience, there you can build a full AS Button component, which compiles to JS without the need of a vanilla SDK. I assume technically you can do the same, if the basic Flash API stuff is 'emulated' for JS and included with the compilation? Yes, it is great to see other approaches being investigated. I think there three approaches right now. 1) Jangaroo: Actually a product. Uses Flash API emulation 2) Eriks' VanillaSDK: Still a proof of concept. My main concerns are that it will be a lot of work to finish, and that it will drag with it all of the unused code the Flex SDK does with its intertwined dependencies. 3) My approach: Still a proof of concept. Brand new SDK designed to be optimally implemented in both JS and AS. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Nick Tsitlakidis, CEO and Software Architect at Perfect Edge LTD. www.perfectedz.com
Re: [ASJS] AS to HTML5 in action: announcing the ASJS Publisher and the VanillaSDK JS framework.
On 1/25/13 11:00 AM, Erik de Bruin e...@ixsoftware.nl wrote: 2) Actually, I have the AS implementation completely finished... it's the Flex SDK (hence the 'vanilla' in the name). On the browser side I'll have to create a JS framework that has the same public API as the Flex SDK, but I never said that behind that API would be a translation of any unused code from the Flex SDK (would be silly, wouldn't it?), nor will it necessarily use the same intertwined dependencies. OK, I'll believe you, but one of the problems in the current Flex SDK is interwined dependencies caused by the use of complex classes in the API surface itself. I'm not clear how you can fix that without changing the API surface. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [ASJS] AS to HTML5 in action: announcing the ASJS Publisher and the VanillaSDK JS framework.
On 1/25/13 10:57 AM, Nick Tsitlakidis ni...@perfectedz.com wrote: Hello Alex, To be honest, your approach sounds like the proper way to move forward (at least to me), but I still think that using what we already have in the AS side is going to take less time and as you have already said in some emails, this year will be a crucial one for Flex. Anyway, having choices is always good. Time will show which one will be adopted by the community. I'm not sure which one will take less time. I'm taking my approach because I can set a low bar (the first one being using a simple form to get JSON data, and view it in a list) and build up from there without setting expectations that it is the same Flex SDK you know. The other approach will probably be incomplete for a long time and have performance and fidelity issues dealing with the APIs that relied on Dictionary and weak references and other impedance mismatches between AS and JS. Over time, the approach I'm taking can grow to match a significant portion of the existing Flex SDK, but I would not want to promise 100% for the above stated reasons. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [ASJS] AS to HTML5 in action: announcing the ASJS Publisher and the VanillaSDK JS framework.
Over time, the approach I'm taking can grow to match a significant portion of the existing Flex SDK, but I would not want to promise 100% for the above stated reasons. Ditto for me. :-) EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: [ASJS] AS to HTML5 in action: announcing the ASJS Publisher and the VanillaSDK JS framework.
Well done guys. This is really brilliant news. Many many thanks a On Jan 25, 2013 6:11 PM, Frank Pepermans frankp...@hotmail.com wrote: I concur, this is huge news for the future of Flex! Congrats to making this possible! About the vanilla sdk, I have some Jangaroo experience, there you can build a full AS Button component, which compiles to JS without the need of a vanilla SDK. I assume technically you can do the same, if the basic Flash API stuff is 'emulated' for JS and included with the compilation? -Original Message- From: Nick Tsitlakidis Sent: Friday, January 25, 2013 6:58 PM To: dev@flex.apache.org Subject: Re: [ASJS] AS to HTML5 in action: announcing the ASJS Publisher and the VanillaSDK JS framework. Firstly, WELL DONE TO ALL cause this sounds epic! I haven't tried it yet but it's already in my todo list. I'll go slightly off topic here and ask you if you can share your vision about the VanillaSDK Erik. I'm reading the hundreds of emails but its kinda hard to keep up with you guys. You do a great job and you do it fast. I plan on investing some time to our beloved project and spending some time with VanillaSDK made the click for me. That's why I ask. Also, any hints on what I should read or check to understand how I can contribute would be really appreciated. Please keep in mind that I never had any experience with compilers. I'm more of a 'components and apps' developer. Again, congratulations guys. I hope I'll be able to join in soon. At least I'll try. :) On Fri, Jan 25, 2013 at 5:03 PM, Erik de Bruin e...@ixsoftware.nl wrote: Hi, I'm proud to announce the availability of a 'proof of concept' for a Actionscript to HTML5/Javascript work flow. Standing on the shoulders of giants (Gordon, Mike, Alex et al., I'm looking at you!) I was able to piece together a working prototype of a full Flash Builder - Browser application development tool chain. The tools are: - the Flex SDK. Most importantly, the goal is to allow developers to use the tools they know while giving them the ability to publish their work to a www-friendly format. - the FalconJx browser, which can as of today output a pretty descent approximation of AS in JS, the 'goog' way. - the ASJS Publisher, an ant script that takes the JS that FalconJx produces and puts it through the Google Closure Tools to create both intermediate and release versions of the web native application. - the VanillaSDK, my attempt at an AS compatible JS framework. I have plan for a different type of framework, even better integrated with the current Flex SDK, but more on that later ;-) With these new tools, you are now able (albeit in a very limited way) to use the regular Flex SDK for application development in your favorite development tool. Using the new ASJS Publisher script, you can compile your project into a highly optimized HTML5 application that will run in any modern browser. It's that simple... well, almost :-) As this is a prototype, there are some (ha!) limitations: - the VanillaSDK (the Javascript counterpart to the Flex SDK) is very basic indeed, with only 2 UI components: Button and Label. Both these components currently support only 1 or 2 properties (position and label or text). It does show, however, how easy it is to create these Flex SDK compatible UI elements. - not all AS language features are fully supported on the JS side yet. - there isn't (yet) support for MXML, but that's coming soon. - since this is only a proof of concept, there is almost certainly a lot that doesn't work -- to be honest, I'd be suprised if anything works at all :-) If you want to try this out, please get the latest version of the tool set from SVN, starting with here: https://svn.apache.org/repos/**asf/flex/asjs/branches/develophttps://svn.apache.org/repos/asf/flex/asjs/branches/develop Begin with the README you'll find there. After an initially non-trivial setup (SDK, Falcon, FalconJx and the new tools), the everyday use is really simple: just one command in a terminal, calling one ant script with one argument: this will publish your Flash Builder application to the 'js-intermediate' and 'js-release' directories in your FB project folder. Simply double click on the HTML files in either of these will run your application in your default browser, no Flash plugin needed! Please let me know if this works for you and what issues you encounter. Should you feel inspired, feel free to contribute, this part of the project can use all the help it can get! Have fun, EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Nick Tsitlakidis, CEO and Software Architect at Perfect Edge LTD. www.perfectedz.com
Re: [ASJS] AS to HTML5 in action: announcing the ASJS Publisher and the VanillaSDK JS framework.
Erik, its really amazing to witness your progress! On Fri, Jan 25, 2013 at 7:30 PM, Alex Harui aha...@adobe.com wrote: On 1/25/13 10:11 AM, Frank Pepermans frankp...@hotmail.com wrote: I concur, this is huge news for the future of Flex! Congrats to making this possible! About the vanilla sdk, I have some Jangaroo experience, there you can build a full AS Button component, which compiles to JS without the need of a vanilla SDK. I assume technically you can do the same, if the basic Flash API stuff is 'emulated' for JS and included with the compilation? Yes, it is great to see other approaches being investigated. I think there three approaches right now. 1) Jangaroo: Actually a product. Uses Flash API emulation It is important to note that the way we use Jangaroo at CoreMedia, we do *not* use JooFlash (the Flash API emulation). Instead, we build UIs in ActionScript and EXML (an MXML dialect), using Ext JS through a (generated) ActionScript API. We call this approach Ext AS: https://github.com/CoreMedia/jangaroo-tools/wiki/Ext-AS I have just recently successfully experimented with using original MXML instead of EXML and will soon post a demo application. This means you can build full-scale Ext JS applications in AS3 and MXML! So actually our solutions are all quite similar in that they do not use the standard Flex component implementation code (Erik uses only the API) nor the Flash API. My Vision is that Apache Flex can be used to fully compile AS3 + MXML to JavaScript and allows using the component library of your choice (Flex-API re-implemented, completely new one, or and Ext JS or other JS UI library bridge). After all, Flex has a tradition of changing the component library ;-) What I like about Ext JS is that this is not a newly invented component framework, but you can find lots of information and experience about Ext JS on the web. It already has a declarative notation, namely a JSON format, that can straight-forwardly be transformed to/from MXML. Greetings -Frank- J8)
Re: [ASJS] AS to HTML5 in action: announcing the ASJS Publisher and the VanillaSDK JS framework.
It is important to note that the way we use Jangaroo at CoreMedia, we do *not* use JooFlash (the Flash API emulation). Instead, we build UIs in ActionScript and EXML (an MXML dialect), using Ext JS through a (generated) ActionScript API. We call this approach Ext AS: https://github.com/CoreMedia/jangaroo-tools/wiki/Ext-AS I have just recently successfully experimented with using original MXML instead of EXML and will soon post a demo application. This means you can build full-scale Ext JS applications in AS3 and MXML! Hi Frank, I'm really glad to read about this, if you read the [ASJS] Integration with existing JS libraries and components you will see that I was actually talking about exactly what you're describing. So I'm pretty happy that we actually already have a proven implementation of my idea, haha. So actually our solutions are all quite similar in that they do not use the standard Flex component implementation code (Erik uses only the API) nor the Flash API. My Vision is that Apache Flex can be used to fully compile AS3 + MXML to JavaScript and allows using the component library of your choice (Flex-API re-implemented, completely new one, or and Ext JS or other JS UI library bridge). After all, Flex has a tradition of changing the component library ;-) Haha, these were EXACTLY my thoughts too :) What I like about Ext JS is that this is not a newly invented component framework, but you can find lots of information and experience about Ext JS on the web. It already has a declarative notation, namely a JSON format, that can straight-forwardly be transformed to/from MXML. Plus. Sencha/ExtJS is the most popular framework for enterprise JS apps out there at the moment. So if Apache Flex offers great support and integration with it we'll probably earn a lot of fans right out the door. cheers, Roland
Re: [ASJS] AS to HTML5 in action: announcing the ASJS Publisher and the VanillaSDK JS framework.
On Fri, Jan 25, 2013 at 10:13 PM, Roland Zwaga rol...@stackandheap.comwrote: I'm really glad to read about this, if you read the [ASJS] Integration with existing JS libraries and components you will see that I was actually talking about exactly what you're describing. Yeah, you sure saw that I also answered in that thread! So I'm pretty happy that we actually already have a proven implementation of my idea, haha. Haha, well, it was not my idea, either, but rather proven practice from HaXe and others. Plus. Sencha/ExtJS is the most popular framework for enterprise JS apps out there at the moment. So if Apache Flex offers great support and integration with it we'll probably earn a lot of fans right out the door. Not to forget that there is also Sencha Touch, which works according to the same foundation as Ext JS, but with a mobile-/touch-specific component set. I am sure Sencha Touch applications can be built via AS3/MXML, too, so we'd have an alternative to AIR to target mobile devices with Flex! Greetings, -Frank-
Re: [ASJS] AS to HTML5 in action: announcing the ASJS Publisher and the VanillaSDK JS framework.
But if I understand it correctly, wouldn't it mean in Erik's model that when I create my own custom datagrid component for instance, I would also have to write a JS version for this? (For me personally this is what I would want to avoid -- writing JS myself :) ) Does anybody know what GWT is doing excactly and how the current paths we (the flexers) have choosen compare to that? To me it seems pretty nice in GWT to be writing your own HTML, and just plug in your java (which then cross compiles). Do you guys think this a good model? (I'm not saying we should this or that, and that i think somebody is choosing the wrong path right now. I think all of you guys are doing an amazing job, and I wouldn't be able to do anything similar myself. Just trying to make some discussion and gather info, because I think that is healthy, at all times) And nice Job Erik, looking forward to experiment with it!! On 25 Jan 2013, at 20:13, Alex Harui aha...@adobe.com wrote: On 1/25/13 11:00 AM, Erik de Bruin e...@ixsoftware.nl wrote: 2) Actually, I have the AS implementation completely finished... it's the Flex SDK (hence the 'vanilla' in the name). On the browser side I'll have to create a JS framework that has the same public API as the Flex SDK, but I never said that behind that API would be a translation of any unused code from the Flex SDK (would be silly, wouldn't it?), nor will it necessarily use the same intertwined dependencies. OK, I'll believe you, but one of the problems in the current Flex SDK is interwined dependencies caused by the use of complex classes in the API surface itself. I'm not clear how you can fix that without changing the API surface. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
