I think this is a noble goal in theory, but note that all our efforts to keep the various kernel's in "native" syntax have really just led to the kernel code being more complex and unmaintainable (e.g., all the hand-written boilerplate to fake inheritance of the various dhtml sprite pseudo-classes, which could have been written so much more simply just using our extensions to JS).
I think I would write the code in whatever fashion is the easiest for us to maintain, while soliciting interest. If someone shows up who is really serious about reusing and extending the code outside of OL, you can easily create them a "plain" version at that time. I would not invest the effort until there is such interest. On 2010-08-11, at 23:09, Henry Minsky wrote: > Max and I were thinking making our bidi-TextField workalike class use plain > as3 syntax, so it can be compiled directly with the flex compiler , and > then trying to drum up some interest from the flex developers community in > helping improving and maintaining it. > > The only problem there is that it won't just compile like an ordinary LFC > file. Either we come up with some more "file at a time" passthrough > syntax, or else I am thinking that when someone needs to modify it, > there's an ant target to compile it as a flex .swc library, using compc, and > put > it in our WEB-INF/flexlib directory. Then it gets linked against > automatically when the LFC is compiled. > > I am not sure if it's worth the extra hack to make this work, in the > somewhat optimistic hope of getting some free help in maintaining this code. > > > -- > Henry Minsky > Software Architect > [email protected]
