On Mon, Mar 25, 2013 at 12:09 PM, Alex Harui <aha...@adobe.com> wrote:
> My answers in-line > > > On 3/25/13 11:55 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: > > > Om, > > > > 1) the wiki is mostly current, but as a work in progress: if it > > doesn't work, ask and we will fix ;-) > > > > 2) CSS resulting from...? I'm not familiar with FXG etc., so my > > questions are bound to be naive as well, as you'll notice. Basically > > we have access to whatever the compiler (Falcon-main, if you will) has > > access to, but some thing might be easier than others. Mike S. is our > > wizard, he'll know what to do if we can't figure it out. > For FlexJS, I haven't decided on what to do. Currently, CSS is compiled > into a datastream much like MXML is, but nothing on the JS side of FlexJS > has required CSS yet, so essentially the problem is unsolved. I'm pretty > sure we'll decide that we want one .css file that gets loaded in by the > HTML > wrapper. The compiler currently has the smarts that determines the right > subset of the source CSS files (by culling out type-selectors that aren't > used, for example). But knowing what your output will look like can > certainly guide what we end up with. > With my approach, to get the rendering fidelity to match that of Flex's skins, inline CSS makes it easy (because of the XSLT approach) BTW, we still need to deal with the 'cascading' part of CSS, right? One big .css file probably will not solve all questions. > > > > 3) Ah, there is the CSS, I guess (fxg -> svg + css). The AS code will > > be cross-compiled to AS (weird, I know) or any form of JS we chose, > > most likely 'goog' JS, as it will have to be compatible with FlexJS > > and the VanillaSDK. Due to the way FalconJx is set up, it will be easy > > to add FXG specific JS parsing, if needed. > > > > 4) Sounds like and excellent starting point... however, you'll > > probably have to tweak your local SDK 'a bit' to get both the Flex and > > JS side working. Or should be start one of those much rumored > > 'shared' feature branches of the SDK? > Peter and/or I plan to get started on the HTML5 set for FlexJS this week. > You are welcome to wait or write that first Button yourself. BTW, what > browser or runtime environment are you going to be working with? > The button component is what I am using as my first use case. If things go well, I will have an independently working skinned HTML5 button component that can be plugged in anywhere. So far, everything I have done seems to be working with the latest versions of all major browsers. This means: Firefox 19.0.2 (Mac and Windows) Chrome 25.0.1 (Mac and Windows) IE 9 Safari (version unknown) Android Browser (Android version 4.1.2) iOS (version unknown) I prefer to not concentrate on older browsers because the Flash/Flex version of the same app should just work fine there. > > > > I love how everything seems to be converging and it really feels like > > Flex -> HTML5/JS is doable! > I finally got eclipse to build FalconJX from the Git sources. I'll be > testing it out today. FalconJS had a few bugs that needed fixing and I'm > hoping that you already fixed them in FalconJX. If not I'll fix them in > FalconJX to help me learn that code. Hopefully there won't be any more > code > changes in compiler.js going forward. > Are you saying that you are planning to switch to FalconJX soon? > > > > EdB > > > > > > > > On Mon, Mar 25, 2013 at 7:21 PM, Om <bigosma...@gmail.com> wrote: > >> Erik, > >> > >> I am planning to get FalconJX working on my machine soon. Before I > start > >> digging into it, > >> > >> 1. Are these wiki pages current? > >> > >> > > https://cwiki.apache.org/confluence/display/FLEX/AS+to+JS+-+the+%27goog%27+Wa > >> > y > >> > >> https://cwiki.apache.org/confluence/display/FLEX/FalconJx+Prototype > >> > >> 2. Do you have any thoughts on how we want to handle the resulting CSS? > >> Inlining everything or have it as separate files? > >> > >> 3. My approach would take in a spark skin file and convert the fxg > >> elements into svg+css. There is going to some AS code that needs to be > >> converted JS. I believe your approach already handles this right? > >> > >> 4. I see that the VanillaSDK supports the Button component in HTML5. > >> Maybe that is where I should start and get my code working there? > >> > >> Sorry if I am asking naive questions, but I am looking for some > guidance on > >> how to get my work integrated into FalconJx (or FalconJS) > >> > >> Thanks, > >> Om > >> > >> On Mon, Mar 25, 2013 at 8:45 AM, Erik de Bruin <e...@ixsoftware.nl> > wrote: > >> > >>> Hi, > >>> > >>> Just 'checking in': FalconJx can now compile the FlexJSTest_again > >>> example from the command line, using these arguments: > >>> > >>> > >>> > +env.PLAYERGLOBAL_HOME=/Users/erik/Documents/ApacheFlex/dependencies/PlayerG > >>> lobal/player > >>> +playerglobal.version=11.1 > >>> -load-config="/Applications/Adobe Flash Builder > >>> 4.7/sdks/4.9.1/frameworks/flex-config.xml" > >>> > >>> > -library-path+=/Users/erik/Documents/ApacheFlex/git/flex-asjs/frameworks/as/ > >>> libs/FlexJSUI.swc > >>> -js-output-type=FLEXJS > >>> -output=/Users/erik/Desktop/FlexJS/fromEclipse/FlexJSTest.js > >>> > >>> > /Users/erik/Documents/ApacheFlex/git/flex-asjs/examples/FlexJSTest_again/src > >>> /FlexJSTest.mxml > >>> > >>> Well, not exactly those, please change the paths to fit your local > >>> environment ;-) > >>> > >>> Next up: > >>> - support for publishing with the GCC and associated tricks (SourceMap > >>> etc.) > >>> - full FlexJS type AS -> JS support (the current implementation is > >>> custom tailored to the FlexJSTest_Again example code) > >>> > >>> Have fun! > >>> > >>> EdB > >>> > >>> > >>> > >>> -- > >>> Ix Multimedia Software > >>> > >>> Jan Luykenstraat 27 > >>> 3521 VB Utrecht > >>> > >>> T. 06-51952295 > >>> I. www.ixsoftware.nl > >>> > > > > > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > >
