On Fri, Mar 15, 2013 at 8:22 AM, Alex Harui <aha...@adobe.com> wrote:
> FWIW, Peter and I are pretty much done with the basic set of unstyleable, > unskinnable HTML4 components. Peter and I were going to work on styleable > HTML4 components next then tackle HTML5 and bitmap skinning, but maybe we > should jump to wrapping the HTML5 components so you can try getting your > skinning model to work on them. > > Sounds exciting. I am in! I can help as much as I can. Thanks, Om > > On 3/15/13 4:16 AM, "Om" <bigosma...@gmail.com> wrote: > > > On Fri, Mar 15, 2013 at 4:11 AM, Michael Schmalle > > <apa...@teotigraphix.com>wrote: > > > >> Om, > >> > >> At this point and time, I am not worried about rendering. I am more > >> concerned about straight business logic getting cross compiled. > >> > >> > > I am worried about it and hence scratching my itch :-) I have not seen > any > > proposal better than mine so far. > > > > > >> This is probably why you have heard anything, I talk a lot on this forum > >> and haven't said anything about it. :) > >> > >> I don't even own up to date Adobe programs that even export FXG, I > think I > >> have CS3, and love it. I think giving the View to web developers using > HTML > >> and CSS should be explored by this group as well, instead of relying on > >> cross compiling views. > >> > > > > My goal is to have a solution that does not make the user touch HTML, JS > or > > CSS. The current workflow we have with Flex + FXG is far superior than > > anything out there. I am just trying to see how to keep these workflows > > going forward but still support cross compilation. > > > > > >> > >> Mike > >> > >> > >> > >> Quoting Om <bigosma...@gmail.com>: > >> > >> I quickly whipped up a proof of concept proving the FXG to SVG > >>> interoperability. > >>> > >>> The working demo can be found here: > >>> http://people.apache.org/~**bigosmallm/fxg2svg/svg.html< > http://people.apache > >>> .org/~bigosmallm/fxg2svg/svg.html>(Tested to be working > >>> fine on Chrome 25, Firefox 19 and IE 10 on Windows) > >>> > >>> I did not have time to write a stylesheet, so I hand created a simple > SVG > >>> element based on an FXG element. I chose the most basic element: > "Rect" > >>> which is available as "rect" in SVG. Once I had the basic set up > working, > >>> all I had to do was modify the svg's attributes using Javascript. This > >>> happens during runtime, but we could totally move this to the > compilation > >>> stage. > >>> > >>> As you can see, I have proven that rendering fidelity can be achieved > >>> using > >>> this route. At the same time, this can be plugged into the AS to JS > >>> translation piece that Mike, Erik, et al. are working on. From what I > see > >>> in that project, there is no faithful rendering solution (yet) You > >>> probably discussed about rendering that I might have missed. > >>> > >>> When I get some more time, I will start fiddling with more and more FXG > >>> elements and see how SVG handles them. At some point, writing a > >>> stylesheet > >>> would be more efficient. > >>> > >>> Just right click either the Flex app or the HTML content to view the > >>> source > >>> of both. Comments and suggestions for improvement highly appreciated. > >>> This is a very basic demo, dealing mostly about rendering fidelity. But > >>> IMHO, this unleashes a ton of possibilities. > >>> > >>> (And no, FXG is not dead - yet. ;-) ) > >>> > >>> Thanks, > >>> Om > >>> > >>> > >> -- > >> Michael Schmalle - Teoti Graphix, LLC > >> http://www.teotigraphix.com > >> http://blog.teotigraphix.com > >> > >> > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > >
