>@see >https://github.com/apache/flex-examples/tree/develop/showcase/4.11/components/mobilegrid/index.html >I think it might be better to only include paths to released code and that >will work once it's released. Means we should think about publishing showcase >under the website just like we do >with ASDocs. >Under Apache a release can only contain voted on released code/documentation, >so this may be a grey area where we need some caution.
Actually, the final link would point to release branch, something like: >@see >https://github.com/apache/flex-examples/tree/release/showcase/4.11/components/mobilegrid/index.html I am not sure if the flex-examples repo is meant to have a release branch eventually, or would stay forever as "develop" code. If it will have a release branch, will it be considered as "released code" ? Otherwise, putting the showcase code under the website is fine. Will the code be structured the same way (kind of git repo embedded in the apache ?). Maurice -----Message d'origine----- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : vendredi 4 octobre 2013 02:46 À : dev@flex.apache.org Objet : Re: Thoughts about ApacheFlex ASDOC Hi, > 2) Using flex-examples in the ASDOC > Since I included a sample application of MobileGrid in flex-exemples > repo, I thought it could be nice to have a link to it from the ASDOC, So I > added the following : > > @see > https://github.com/apache/flex-examples/tree/develop/showcase/4.11/com > ponents/mobilegrid/index.html Examples of MobileGrid usage on > ApacheFlex github I think it might be better to only include paths to released code and that will work once it's released. Means we should think about publishing showcase under the website just like we do with ASDocs. Under Apache a release can only contain voted on released code/documentation, so this may be a grey area where we need some caution. > 3) Experimental components > > Someone has raised the issue that experimental components could be marked as > such, maybe using a specific metadata (eg [Experimental]). That's a good idea, can you raise a JIRA for it. > I thought that ASDOC compiler could use this metadata to display a > disclaimer, much like the disclaimer for Deprecated components, or for > discouraging the use of component on mobile platforms. I've looked into ASDOCs code before it's a bit of a mess that that shouldn't be too hard to do, but looks like you looked into this already. Thanks, Justin
