Alex Harui wrote > Depending on how you look at it, each class is a component, or maybe only > classes listed in manifest.xml files are components. > You might get a directory listing or parse the manifest files. > I've been tempted to find a way to mark or annotate classes as being > intended for application developers as opposed to framework developers.
I've just browsed through the asjs repo and it seems to me that it is already a challenge to get list of the relevant classes/components. I've found e.g. [1] wich is probably a summary of the core components. Would that be the way to search for this file inside each "component set" to get an overview of all components? Alex Harui wrote > I'm still hoping we can be more efficient about the doc. If we know there > is going to be a Tour de FlexJS, we should put the examples in there as > opposed to having examples in both places, and link back and forth between > the doc and Tour de FlexJS, and probably the ASDoc as well. Maybe the wiki is not the best place to start with the docs... What do you think of using github? We could start with a repo that contains examples for the particular components and maybe this could be consumend by an "Tour de FlexJS" app using the github API? Thanks, Olaf [1] https://github.com/apache/flex-asjs/blob/develop/frameworks/projects/Core/src/main/resources/basic-manifest.xml -- View this message in context: http://apache-flex-development.2333347.n4.nabble.com/FlexJS-Starting-with-the-Docs-tp55005p55012.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
