So should I add the [Experimental] processing to the other parts as well ?
I won't hurt anyway.
Maurice
-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : lundi 7 octobre 2013 09:47
À : dev@flex.apache.org
Objet : Re: Thoughts about ApacheFlex
Hi,
Not looked in detail but would guess that that other paths refer to attaching
meta data to properties and methods not classes - that might be useful.
Thanks,
Justin
SDOC and is not in the call chain above.
Note: I didn't run the compiler in debug which would be the best way to be
sure.
What do you think ?
Maurice
-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : lundi 7 octobre 2013 02:51
À : dev@flex.ap
Hi,
> There is a misspelling in DocCommentNode "Experimantal" instead of
> "Experimental".
I've not applied the patch. It was just an easy way to point out where the
changes perhaps need to be made. What do you think?
Thanks,
Justin
.org
Objet : Re: Thoughts about ApacheFlex ASDOC
HI,
> I have committed https://issues.apache.org/jira/browse/FLEX-33800 to develop
> branch.
Looked over it and it looks good you may of missed a few places that a similar
change is required not 100% sure.
diff --git a/modules/asc
HI,
> I have committed https://issues.apache.org/jira/browse/FLEX-33800 to develop
> branch.
Looked over it and it looks good you may of missed a few places that a similar
change is required not 100% sure.
diff --git a/modules/asc/src/java/macromedia/asc/parser/DocCommentNode.java
b/modules/a
I have committed https://issues.apache.org/jira/browse/FLEX-33800 to develop
branch.
Someone to review the changes ?
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : samedi 5 octobre 2013 16:28
À : dev@flex.apache.org
Objet : Re: Thoughts
Ok, thanks
-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : samedi 5 octobre 2013 16:21
À : dev@flex.apache.org
Objet : Re: Thoughts about ApacheFlex ASDOC
Hi,
I'd go with commit then review, no need for a vote on something minor like this
IMO
Justin
Agreed. Plus, the concept was discussed without objections, and we have
time to make adjustments before the release if needed.
On 10/5/13 7:20 AM, "Justin Mclean" wrote:
>Hi,
>
>I'd go with commit then review, no need for a vote on something minor
>like this IMO
>
>Justin
Hi,
I'd go with commit then review, no need for a vote on something minor like this
IMO
Justin
Hi Team,
I have created https://issues.apache.org/jira/browse/FLEX-33800 to support the
changes for ASDOC.
Current implementation is the following:
If class has [Experimental] metadata, then a disclaimer is added to the ASDOC
(thanks to Om for proposing this).
I have attached to the JIRA tick
13
À : dev@flex.apache.org
Objet : Re: Thoughts about ApacheFlex ASDOC
On 10/4/13 12:46 AM, "Maurice Amsellem"
wrote:
>Hi Alex,
>
>> 1) The Falcon compiler code base may be easier to work with.
>
>I don't know anything about the Falcon compiler, so excuse if
On 10/4/13 12:46 AM, "Maurice Amsellem"
wrote:
>Hi Alex,
>
>> 1) The Falcon compiler code base may be easier to work with.
>
>I don't know anything about the Falcon compiler, so excuse if my
>questions are dumb:
>- Does the Falcon compiler include ASDOC compiler ? or is it limited to
>AS/MMXL c
verything 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 :
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
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
Apac
Hi,
> PS: sorry for the "lesson" on how ASDOC generation works.
> Of course you guys know it by heart...
IMO there would only be a few people who looked at the ASDocs code and even
fewer who have modified it.
Thanks,
Justin
: Re: Thoughts about ApacheFlex ASDOC
Hi,
> It's just a matter on changing the ASDOC XLSTs.
It's a mix of Java and XLST, if you want to give it a go go for it. If you get
stuck ask I might be able to point in the right direction having also modified
it before.
Thanks,
Justin
Ok understood.
-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : vendredi 4 octobre 2013 09:08
À : dev@flex.apache.org
Objet : Re: Thoughts about ApacheFlex ASDOC
Hi,
> I am not sure if the flex-examples repo is meant to have a releas
;tweaking" the existing tools, than rewriting
everything...
So if someone else is interested in doing it, "pourquoi pas ?" :-)
Regards,
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : vendredi 4 octobre 2013 06:02
À : dev@flex.a
Hi,
> 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" ?
It needs to be checked, tagged and voted on by the PMC to be release (or part
of
Hi,
> It's just a matter on changing the ASDOC XLSTs.
It's a mix of Java and XLST, if you want to give it a go go for it. If you get
stuck ask I might be able to point in the right direction having also modified
it before.
Thanks,
Justin
herwise, 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@fle
>I was the one who suggested this (maybe someone else also did) I think this
>is a much better way to handle 'experimental' components. When it goes to
>'maintream', all >we would have to do is remove the [Experimental] metadata.
>Saves time for us and for end users this way.
I knew it was s
another project in the past.
Maurice
-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : vendredi 4 octobre 2013 05:23
À : dev@flex.apache.org
Objet : Re: Thoughts about ApacheFlex ASDOC
On Thu, Oct 3, 2013 at 8:22 PM, Justin Mclean wrote:
> Hi,
>
> > Refactoring efforts on our side and end users' side.
>
> I assume you mean changing the MML namespace/prefixes and the moving out
> of the experimental namespace/manifest files to where it finally goes.
>
>
Yes, that is what I meant.
Hi Maurice,
If you've got the time and energy, go for it. A couple of things to
consider:
1) The Falcon compiler code base may be easier to work with
2) I've been wondering if an AIR app would easier to maintain as the ASDoc
generator. I don't know how XSLT at all.
3) And I've been wondering wh
Hi,
> Refactoring efforts on our side and end users' side.
I assume you mean changing the MML namespace/prefixes and the moving out of the
experimental namespace/manifest files to where it finally goes.
The useful think about namespaces is that we can have 2 components with the
same package na
On Thu, Oct 3, 2013 at 7:27 PM, Justin Mclean wrote:
> Hi,
>
> > I was the one who suggested this (maybe someone else also did) I think
> > this is a much better way to handle 'experimental' components. When it
> > goes to 'maintream', all we would have to do is remove the [Experimental]
> > met
Hi,
> I was the one who suggested this (maybe someone else also did) I think
> this is a much better way to handle 'experimental' components. When it
> goes to 'maintream', all we would have to do is remove the [Experimental]
> metadata. Saves time for us and for end users this way.
Not sure h
On Thu, Oct 3, 2013 at 5:11 PM, Maurice Amsellem <
maurice.amsel...@systar.com> wrote:
> Hi team,
>
> ** **
>
> While working on the asdoc for MobileGrid, I came to the following
> thoughts and propositions that I would like to share with you:
>
> ** **
>
> **1) **Include-examples in
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/
Hi team,
While working on the asdoc for MobileGrid, I came to the following thoughts and
propositions that I would like to share with you:
1) Include-examples in the ASDOC:
As I said in a previous thread (09/28/2013 13:25 CET "RE: Mobile datagrid
component integration (ASDOC)"), the cur
33 matches
Mail list logo
