Nice work. I really like this approach. It reminds me of the Label, RichText, RichEditableText, TextArea.
A couple of things about this to whoever may work on the visual side of things including myself in the future. I would NOT try to support all the features in HTML or CSS. I can see it leading down the path of 100s of other HTML tools before it. All of a sudden it becomes unyielding. I think it's tempting to want to adopt the CSS features that Flex doesn't have but I think we should keep feature parity and not get caught up in CSS and HTML way of doing things. I mean really examine what is going on there and prevent some of the mistakes that have been made in the past. I mention this because we are having this discussion in other threads. FXG -> SVG, HTML5, etc One mess I would avoid is CSS stylesheets. It's basically one declaration clobbering the next one where the last one declared wins. Then there's this important tag that veto's everyone else and even that can be overruled by another important flag set later on. Even in Flex you can have multiple type declarations for the same component from all different locations. Later, when it comes time to determine why your component doesn't look the way you want you have to untangle the fun ball of twine called CSS to find out. I spent a lot of time dealing with this CSS issue in multiple Flex projects over the years and there are a couple of things that could be done that would help. There are HTML tools that can take an element and show it's style inheritance. Firebug is one of them. Flex doesn't have any tools like this. I don't know if Adobe had ever thought of working on one at one point but if they did maybe it could get donated? Another helpful solution would be to use the compiler to show warnings or errors when types have been declared previously. Another would be to keep track of where styles have been declared in the SDK. There is a document property on UIComponent. That same concept could apply to styles as they are created and applied. Setup a breadcrumb trail back to the declarations. I worked on a style inheritance lookup a while back. You can see it here, http://goo.gl/mD7xK in the getStyleDetails and getStyleInheritence methods. You could give it a IStyleClient element and it would list it styles by broadest to narrowest in how they were applied. It was modeled after some of the CSS tools out there. It was a lot of work to do something that should have been easy. It isn't finished though. It doesn't take into account style names declared inline and has a few other unsolved problems as well. I'm mentioning this again for myself and for discussion. On Sun, Mar 24, 2013 at 1:10 AM, Alex Harui <aha...@adobe.com> wrote: > > > > On 3/22/13 8:41 PM, "jude" <flexcapaci...@gmail.com> wrote: > > > Alex, > > > > Do you have a link to the demo that runs in the browser? I couldn't get > it > > to render via the SVN whiteboard link. It would always show the contents > of > > the file. > > > > > I posted a recent version here: http://people.apache.org/~aharui/FlexJS/ > > There are four folders: > bin-debug - Flash debug SWF > bin-release - Flash release SWF (yes, MXML apps in as little as 25K) > binjs-debug - Html/JS debug (separate source files) > binjs-release - Html/JS release (minified file) > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > >
