Hi, >> I spent some time going through your new framework. First off, I think it >> deserves to be called something else. The "JS" in "ASJS" implies that it >> is a JS specific implementation of the framework. In reality it is not. > Well, I called that to show that it is a parallel framework. That we build > both AS and JS beads. But I don't care to much about what we end up calling > it.
Well, I do care. There are 2 naming conventions I think are working well right now: the intended use of a framework decides the first: ASJS stands for Actionscript to JavaScript, exactly what the frameworks and tools in there do. The second is the approach taken when going from AS to JS: first there is FlexJS, Alex's set of bottom up, start from scratch frameworks (one for AS and one for JS), and then there is VanillaSDK, my attempt at a top down, use the Flex SDK and write a complimentary JS framework approach. ASJS is also the home of the Publisher I'm writing, which will take either framework (FlexJS and VanillaSDK) and use it and it's dependencies to build an AS/MXML project into a HTML/JS project, again AS -> JS. I don't mind renaming/rebranding things, especially is something is gained by doing so (even if it's only better marketing), but we should take care not to end up with a too generic naming convention just trying to fit too many projects under one roof. EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
