Hi Igor, >IMHO We have to keep ASDOCS simple as possible with the aggregation only for a >comment system already available on market for free like Adobe does on >>help.adobe.com
The examples that come with the Adobe ASDOC are very valuable and useful. First Problem it's not very convenient for downloading and trying the code, and it's very limited (one or two files max, no assets). Second problem it's not currently implemented in the ApacheFlex asdoc page (http://flex.apache.org/asdoc/) I propose to fix the build file so that existing asdoc examples are included, to be at the same level than classic Adobe ASDOCs (without the "running examples" though). I think this can be done anyway. On the other hand, I also proposed to provide a link to the flex-examples "hub" , so that we could provide "full running" examples as well, that can be downloaded and compiled, and not only single files. It's rather simple to achieve by slightly extending the existing asdoc compiler and xlst templates. I proposed to do it, but it didn't seem to get approval , so wait and see. About the idea of rewriting everything using a different technology and / or organization ( AIR, devdocs.io, etc.), all I can say is that it's a LOT of work... Regards, Maurice -----Message d'origine----- De : Igor Costa [mailto:igorco...@gmail.com] Envoyé : vendredi 4 octobre 2013 17:19 À : dev@flex.apache.org Objet : Re: Thoughts about ApacheFlex ASDOC I guess we're misspelling asdocs with a hub for samples or tutorials. IMHO We have to keep ASDOCS simple as possible with the aggregation only for a comment system already available on market for free like Adobe does on help.adobe.com which community can increase comments with links for samples or sort of it. In the other hand, more detailed explanation on topics that takes a little bit more time to understand like skins, component life cycle and bytearray manipulation theses are more relevant topic on google search that we could enhance the current version. There's something inspiration outthere like http://devdocs.io<http://devdocs.io/html/data> which translate that simplicity and act on the focus point of problem, the understand of behavior os specific topic. Those are good suggestions and I personally appreciate all, but I see more as a dev hub rather than asdocs. Best Regards Igor ---------------------------- Igor Costa www.igorcosta.com www.igorcosta.org On Fri, Oct 4, 2013 at 11:49 AM, Kessler CTR Mark J < mark.kessler....@usmc.mil> wrote: > I've thumbed through it... /shudder > > It felt like there should be some other way to create the ASDOCs. > > > Random thoughts from ASDOCs as a whole. > > * Doesn't contain properties/methods/events inherited from Adobe AS > (DisplayObject, EventDispatcher, InteractiveObject) that are not part > of the Apache Flex SDK . This makes you reference both our ASDOCs and > Adobe's. > > * Would be nice to include lists of enumerated values without having > to directly add static comments. E.g. VGroup.verticalAlign can use > "bottom", "middle", or "top" as it's values listed. There is an > inspectable tag, but it doesn't show up in the ASDOCs, just the comments. > > * Easier to implement examples. > > I'm sure I had more at some point but those were on the top of my head. > > > > -Mark > > -----Original Message----- > From: Justin Mclean [mailto:jus...@classsoftware.com] > > IMO there would only be a few people who looked at the ASDocs code and > even fewer who have modified it. >
