Hi just responding some few things I saw: "Metadata is possible, but metadata is expensive at runtime."
Depend if is a Metadata to use at compile time or at run time. In this case we're talking about a compile time metadata. Even at runtime, a metadata can be or not expensive depending on the scope (running some code inside a class is as efficient as run a method but apply a behavior that cross all instances of same type can be expensive." "One option is to fully qualify the *compiled* class selector so it’s named “.org_apache_royale_html_RadioButton”. I’m pretty sure this is what you are proposing. The primary objection to that is that it’s a rather long string and kind of “ugly”." One more important technical thing about that way is "verbosity" since each time you reference that kind of class you are introducing a name that use to be 2-3 time longer, each time. "My suggestion with meta-data was a way to enable the second option. It does not need to be specifically meta-tags. It could be something like this as well: /** * royaleclassselector RadioButton * royaleclassprefix basic * royaleinheritsbaseselector */ " I still prefers the [] format since is more concise and I think is more suited for this particular purpose. In General, I think we should get something that will be the "default" way, and then if we have a metadata, that should override the default way. That will make possible the most flexible way of handling this an a solution that since to fit all visions. Thanks -- Carlos Rovira http://about.me/carlosrovira
