Well the output format is created from a tree of objects(traversing). :)
What I mean is, the convertor traverses the object model based on page
structure so it doesn't do what you are asking right now. But sure, XML
could be emitted then say Velocity could be written, but that is two passes
and th
I don’t know all of the pieces that go into ASDoc. Is there some output
format like XML that then goes into Velocity or are you sticking in some
non-standard format? Having some canonical data format would be good so
that folks can write other transformations but not necessarily know
Velocity or
Hi,
Not checked but fairly certain this is not a regression, ASdocs has allways
been very picky about it's content.
Thanks,
Justin
;-)
Chris
Von: Maurice Amsellem [maurice.amsel...@systar.com]
Gesendet: Mittwoch, 23. Oktober 2013 16:26
An: dev@flex.apache.org
Betreff: RE: ASDoc
I would rather call that a "bug fix" as the previous versions of ASDoc allowed
invalid html in the asdoc
ce Amsellem [maurice.amsel...@systar.com]
Gesendet: Mittwoch, 23. Oktober 2013 15:47
An: dev@flex.apache.org
Betreff: RE: ASDoc
Ok, I understand.
/**
* along with this program. If not, see <http://www.gnu.org/licenses/>.
*/
package net.flexmojos.oss.it
What I don't understand, is why y
, I can't really see if it's still a
Problem.
Chris
Von: Maurice Amsellem [maurice.amsel...@systar.com]
Gesendet: Mittwoch, 23. Oktober 2013 15:20
An: dev@flex.apache.org
Betreff: RE: ASDoc
Are you sure this is a regression?
Can you give an exa
Are you sure this is a regression?
Can you give an example of ASDOC comment that causes this problem, so that I
can run it on older version of ASDOC tool.
Thanks
Maurice
-Message d'origine-
De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Envoyé : mercredi 23 octo
Yes, they are.
Thanks
-Message d'origine-
De : Nicholas Kwiatkowski [mailto:nicho...@spoon.as]
Envoyé : mercredi 23 octobre 2013 14:07
À : dev@flex.apache.org
Objet : Re: ASDoc missing parts / broken links
Should be all there now -- can you check again?
It looks like my ori
ted to be sure...
>
> Maurice
>
> -Message d'origine-
> De : Nicholas Kwiatkowski [mailto:nicho...@spoon.as]
> Envoyé : mercredi 23 octobre 2013 00:41
> À : dev@flex.apache.org
> Objet : Re: ASDoc missing parts / broken links
>
> I just uploaded the new ASDocs..
Ok. That's what I thought, but wanted to be sure...
Maurice
-Message d'origine-
De : Nicholas Kwiatkowski [mailto:nicho...@spoon.as]
Envoyé : mercredi 23 octobre 2013 00:41
À : dev@flex.apache.org
Objet : Re: ASDoc missing parts / broken links
I just uploaded the new AS
I just uploaded the new ASDocs... It will take a few hours for them to be
fully populated and processed.
On Tue, Oct 22, 2013 at 6:25 PM, Maurice Amsellem <
maurice.amsel...@systar.com> wrote:
> Hi,
> AsDoc on ApacheFlex site has missing parts / broken links
>
> http://flex.staging.apache.org/as
Fine for me
-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : mardi 15 octobre 2013 03:25
À : dev@flex.apache.org
Objet : Re: ASDoc test
Hi,
> Are we releasing the asdoc\test folder?
It's in the release source. I think it probably should b
Hi,
> Are we releasing the asdoc\test folder?
It's in the release source. I think it probably should be removed for now - any
opposing view?
Thanks,
Justin
Alex,
Are we allowed to copy the text from [1] the ASDoc pages of Adobe?
[1]
http://help.adobe.com/en_US/flex/using/WSd0ded3821e0d52fe1e63e3d11c2f44bb7b-7fe7.html
-Mark
On Mon, Oct 14, 2013 at 1:35 PM, Mark Kessler
wrote:
> I'm not apposed to it if other people could use it. But it sounds
I'm not apposed to it if other people could use it. But it sounds like
it's going to change a lot. No worries I guess.
BTW do we have any assembled ASDoc information? I mean besides a blurb in
our README...
To build the ASDoc package
ant asdoc-package
We put together more infor
The purpose of asdoc/test was for me to provide a simple structure and build
file to test changes in ASDOC compiler or templates, without having to run
through the whole SDK ASDOC generation.
I wrote them while I was working on the "experimental" metadata changes.
I thought these could be useful
I love that 'or you can be brave'
On 21 May 2013 19:09, "Alex Harui" wrote:
> Ok, now I see what the issue is. WindowedApplication is in the
> spark.components package along with the experimental
> spark.components.Alert, so an attempt to use mx.controls.Alert needs to be
> fully qualified.
>
>
Ok, now I see what the issue is. WindowedApplication is in the
spark.components package along with the experimental
spark.components.Alert, so an attempt to use mx.controls.Alert needs to be
fully qualified.
So, yes, changing to fully qualified is correct (or you can be brave,
remove the import f
I don't see this error during a normal build, only when I specifically
run 'ant asdoc'.
EdB
On Tue, May 21, 2013 at 7:27 PM, Erik de Bruin wrote:
> Here is the actual output for that issue:
>
> [asdoc]
> /Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/airspark/src/spark/comp
Here is the actual output for that issue:
[asdoc]
/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/airspark/src/spark/components/WindowedApplication.as:
Error: Can not resolve a multiname reference unambiguously.
spark.components:Alert (from
/Users/erik/Documents/ApacheFlex/git/f
On 5/21/13 9:55 AM, "Erik de Bruin" wrote:
>>>
>>>2) the build fails because it sees 2 versions of the Alert class (in
>>>experimental and in MX): prefixing the only call to Alert on line 1939
>>>of airspark::spark.components.WindowedApplication with 'mx.controls.'
>>>seems to fix this. Does th
>>1) the build complains there is a property 'tlf.branch' that is not
>>set; setting this property to '${basedir}/../flex-tlf/textLayout' in
>>'build.properties' seems to fix this. Shouldn't this be a default
>>setting (the property is presently commented out)?
> Actually, I wanted to get rid of tl
On 5/21/13 3:41 AM, "Erik de Bruin" wrote:
>Hi,
>
>When working through the release procedure I noticed some issues with
>the ASDoc build:
>
>1) the build complains there is a property 'tlf.branch' that is not
>set; setting this property to '${basedir}/../flex-tlf/textLayout' in
>'build.propert
Justin,
That was a bit too cryptic. Which of the 4 points does your "it" refer
to? And, in order to prevent someone else mentioning all of the above
points again in a few months, what action do you suggest/prefer?
EdB
On Tue, May 21, 2013 at 2:05 PM, Justin Mclean wrote:
> Hi,
>
> Tell me abo
Hi,
Tell me about it - mentioned it a few months ago.
Justin
If that target is not called from release target then it needs updating.
Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
Mark Kessler wrote:
My "ant asdoc-package" is giving me the following error. Are we still
changing around the tlf properties?
[asdoc] command line: Error:
and delete the 3.0.33 link if you have it too.
-Fred
-Message d'origine-
From: Frédéric THOMAS
Sent: Thursday, March 28, 2013 6:31 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
It has been fixed in the build.xml, how did you
It has been fixed in the build.xml, how did you call your flex-tlf repo ?
It should be ${FLEX_HOME}/../flex-tlf or ${FLEX_HOME}/../tlf
-Fred
-Message d'origine-
From: Justin Mclean
Sent: Thursday, March 28, 2013 6:23 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release
Hi
Also doesn't look like the TLF issue is fixed in that branch:
git branch
* FLEX-33451
develop
master
ompile:
[compc] Loading configuration file
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/projects/textLayout/compile-config.xml
[compc] Apache Flex compc (Compone
From: Frédéric THOMAS
Sent: Thursday, March 28, 2013 5:42 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
You right, I had to do that but didn't do it, feel free to open other
tickets.
There're no needs to open a new branch, the mother one
t the new issue ids.
-Fred
-Message d'origine-
From: Justin Mclean
Sent: Thursday, March 28, 2013 5:37 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
Hi,
You right, I just filled the jira accordingly.
Thanks that's a lot clea
Hi,
> You right, I just filled the jira accordingly.
Thanks that's a lot clearer.
There still a minor workflow issue here in that unless we make each of those
sub tasks real JIRA subtasks how do I know who's working on each one (or if
anyone is). I can't assign the entire bug to myself as I wou
7;origine-
From: Justin Mclean
Sent: Thursday, March 28, 2013 5:20 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
Hi,
It's not a silly question, the answer is because, I opened a jira ticket
[1] in which there are few sub-issues/tasks
Hi,
> It's not a silly question, the answer is because, I opened a jira ticket [1]
> in which there are few sub-issues/tasks.
I guess that one way of doing it - but IMO would be better if they were either
merged into develop as each sub task was fixed. As that JIRA issue is
unassigned I'd assum
ssage d'origine-
From: Justin Mclean
Sent: Thursday, March 28, 2013 4:48 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
Hi,
You can see the fix in the branch I did
Perhaps a silly question but if you have a fix in a branch why hasn&#x
Hi,
> You can see the fix in the branch I did
Perhaps a silly question but if you have a fix in a branch why hasn't it been
merged into develop? Especially if it fixes an issue. Other people may have
this issue but they wouldn't know that your branch fixes it.
Thanks,
Justin
You can see the fix in the branch I did
-Fred
-Message d'origine-
From: Justin Mclean
Sent: Thursday, March 28, 2013 2:33 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
Hi,
Ok files the compiler issue but still getting an error
Hi,
Ok files the compiler issue but still getting an error to do with TLF. Assume
this is to do with the recent TLF changes.
Can you remind me how the SDK build files now knows where TLF is? There
nothing in the README that I can see.
compile:
[compc] Loading configuration file
/Users/j
On 3/27/13 12:43 AM, "Justin Mclean" wrote:
> Hi,
>
>> For me, it is using the one in lib, not in ant/lib.
>
> Mine was using the one in ant/lib and issue was fixed my moving the lib one to
> this location. However I'd still like to know why it was using the one in
> ant/lib and not lib - an
humm... weird, I'ld like to see the others result then.
Thanks Erik,
-Fred
-Message d'origine-
From: Erik de Bruin
Sent: Wednesday, March 27, 2013 10:51 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
I ran 'ant
>
> Thanks,
> -Fred
>
> -Message d'origine- From: Erik de Bruin
> Sent: Wednesday, March 27, 2013 10:29 AM
>
> To: dev@flex.apache.org
> Subject: Re: asdoc - Release build broken (was: Release build broken)
>
> Running 'ant asdoc' gives me:
>
Well, sorry, I meant 'ant doc' from the experimental lib.
Thanks,
-Fred
-Message d'origine-
From: Erik de Bruin
Sent: Wednesday, March 27, 2013 10:29 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
Running '
ed
>
> -Message d'origine- From: Erik de Bruin
> Sent: Wednesday, March 27, 2013 10:06 AM
>
> To: dev@flex.apache.org
> Subject: Re: asdoc - Release build broken (was: Release build broken)
>
> I just did this (OS X) and the build was successful both times (on
>
27;origine-
From: Erik de Bruin
Sent: Wednesday, March 27, 2013 10:06 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
I just did this (OS X) and the build was successful both times (on
develop with 'main', on FLEX-33451 with 'relea
branch,
> checkout the 'FLEX-33451' and build release on it ?
>
> -Fred
>
> -Message d'origine- From: Justin Mclean
> Sent: Wednesday, March 27, 2013 8:11 AM
> To: dev@flex.apache.org
> Subject: Re: asdoc - Release build broken (was: Release build broke
Ok, so I'm curious to know where the issue you have comes from as we don't
have it, keep us in touch.
Thanks,
-Fred
-Message d'origine-
From: Justin Mclean
Sent: Wednesday, March 27, 2013 8:44 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was
Hi,
> Couldn't you simply clone again the sdk, build on the develop branch,
> checkout the 'FLEX-33451' and build release on it ?
Tried that it failed as well.
Justin
Hi,
> For me, it is using the one in lib, not in ant/lib.
Mine was using the one in ant/lib and issue was fixed my moving the lib one to
this location. However I'd still like to know why it was using the one in
ant/lib and not lib - anyone know where this is specified?
As far as I know I only
Hi Justin,
Couldn't you simply clone again the sdk, build on the develop branch,
checkout the 'FLEX-33451' and build release on it ?
-Fred
-Message d'origine-
From: Justin Mclean
Sent: Wednesday, March 27, 2013 8:11 AM
To: dev@flex.apache.org
Subject: Re: a
Hi,
> For me, it is using the one in lib, not in ant/lib. Is it possible you have
> a Falcon flexTasks.jar in ant/lib?
Is there an easy way to tell which one it's using? I have flexTasks.jar in both
places.
Thanks,
Justin
I don't think so. I don't have a compiler.jar in my sdk tree and themes
build.
The build is failing on flexTasks.tasks loading classes from one of the two
flexTasks.jar you see in the build.xml. For me, it is using the one in lib,
not in ant/lib. Is it possible you have a Falcon flexTasks.jar i
Hi,
> If Justin doesn't help you with asdoc, I will try to find time tomorrow.
My build is still broken (unable to build the themes) so unable to help. Are
you sure a falcon dependancy hasn't accidentally got into the SDK release build
- that's the only reference to compiler.jar I could find.
I had to pull before I could see your branch. Once I checked it out, the
build script ran fine on my Mac. If Justin doesn't help you with asdoc, I
will try to find time tomorrow.
On 3/26/13 10:50 AM, "Frédéric THOMAS" wrote:
> Ok, I double checked, all good for the release except the build nu
Ok, I double checked, all good for the release except the build number and
the asdoc, so, TLF, empty.properties and .gitignore are ok.
If someone wants to give a hand for the asdoc, run the asdoc target of the
experimental build after you built the sdk.
Once fixed, uncomment in framework.build.
Okay. Done.
On Mar 19, 2013, at 1:51 PM, Justin Mclean wrote:
> HI,
>
>> I think the docs should be clearer on what to specify here. I propose the
>> following:
>>
>> Instead of: Returns all elements that have typeName set to typeNameValue.
>>
>> Returns all elements that have typeName as the
HI,
> I think the docs should be clearer on what to specify here. I propose the
> following:
>
> Instead of: Returns all elements that have typeName set to typeNameValue.
>
> Returns all elements that have typeName as the TextFlow markup tag set to
> typeNameValue.
The docs are generate from
> Also, I'd think that flow.getElementsByTypeName("ParagraphElement") should
> return an array of the ParagraphElements in the flow. This does not seem to
> work. It retruns an empty array in my tests. Am I going about it wrong, or is
> this a bug?
Okay. This was my error. This: flow.getElemen
57 matches
Mail list logo
