Not sure I followed, but sounds like work ;-) Would it be sufficient if someone were to write up a class called CompilerElements.as and put it in the framework?
-Alex On 3/29/14 9:46 PM, "Joseph Balderson" <n...@joeflash.ca> wrote: >It would be useful to see all metadata, compiler directives (like >conditinoal >compilation), MXML compiler pseudo-properties (like itemCreationPolicy), >have a >mention in the ASDOCs, somewhere. So that if you're searching them, you >don't >have to wade through the wiki. > >The Adobe ASDOCs has two sections in the top left side menu: >- Packages >- Language Elements >- Appendices > >(The Appendices in the Adobe asdocs have one Flex-specific section: "MXML >Only >Tags" -- we could migrate this information to the Apache Flex ASDOCs >and/or Wiki.) > >I would recommend something similar for Apache Flex, only in the following >categories: >- Packages >- Compiler Elements > >In "Compiler Elements", you could have: > - Namespaces > - MXML language specifications > - Compiler Directives > - Metadata tags > - MXML-only properties > - etc. > >Basically anything that would be found in code not in the class packages, >and >not a part of the AS3 spec, would be in the second section. You could >mention >compiler-driven MXML language elements, without getting into lengthy >descriptions and examples more suited to a wiki. These pages might lead >to wiki >pages, much as how the Adobe ASDOCs would lead to "help" pages with >examples >elsewhere in the Flex documentation. > >This would make more sense, since coding in Flex covers not just the class >framework, but MXML compiler conventions. Right now the ASDOCs only cover >the >framework, not the compiler. > >_______________________________________________________________________ > >Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca >Author, Professional Flex 3 :: http://tinyurl.com/proflex3book > >Alex Harui wrote: >> >> On 3/27/14 7:07 PM, "Joseph Balderson" <n...@joeflash.ca> wrote: >>> But it raises the question -- how do we get MXML coding conventions >>>which >>> are >>> not a part of actual classes, but are compiler-interpreted, into the >>> asdocs? >> Do you want to see it on the classes or is another doc chapter good >>enough? >> >> -Alex >> >>
