Mike, > I got a snow ball full of ice hitting my face directly. If we would have > talked a bit first at least I could have ducked (prepared to refactor my
Yes, mea culpa on the communication. > My project is kind of NDA at the moment but completely uses the compiler.jx > platform. This is what I have been talking about "I am working on other > projects". I actually mean, I am working on other projects that plug into > THIS framework. As a mental exercise, purely out of curiosity - as I just promised "it won't happen again" - would you try to veto changes to an Apache Flex project when those changes negatively affect a private, non-open source project? In light of our newly re-found communication (:-)), which parts of this framework do your private projects rely on? Can I hack away at the MXML stuff without bothering you too much? And, maybe more importantly, will you be donating improvements you make to your local copy of the framework back to Apache and if so, how might those improvements influence the code that's based upon the current version of the framework? > BTW, did you mean to commit the SWC in the repository? I meant to commit all the FlexJS files and dependencies for the moment, until I have broken it down into their separate pieces and written test for all of them. I didn't however realize that the swc was a binary, thanks for pointing that out. I'll remove it from the repo on my next commit. Now, moving forward: I'll be doing a lot of work on any file that has MXML in it's name. Do you foresee any problems with that? I might also need to make minor modifications to some of the supporting files. When do you consider a change worthy of discussion? EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
