Re: [FlexJS] DOM/JQuery ASDocs viewable API html online.
Yeah, it would be probably really easy for you to create XML from the
intermediate model.
But, for now I don't feel good committing it, there are things I need to
reorganize and stuff, remove hundreds of license headers etc.
I will put it on my list of things to do, on the list of many. :)
You can try and see if you could get asdoc working on those files but, I
boiled it down and asdoc just didn't want to parse Object, it said
Namespace not found and pointed to the package { declaration.
Mike
On Tue, Jun 23, 2015 at 10:38 AM, Alex Harui aha...@adobe.com wrote:
On 6/23/15, 7:02 AM, Michael Schmalle teotigraphix...@gmail.com wrote:
No, this is a full program.
There is a huge amount of logic that goes into generating this stuff, same
would be the case for XML.
Right now it's AST - Intermediate Model - Velocity - HTML.
Ah yes, I remember you mentioning Intermediate Model”. Well, I can
probably figure out how to go from Intermediate Model to XML, so I have no
objections if you want to check it in. I think at least one other person
was interested in it.
-Alex
Re: [FlexJS] DOM/JQuery ASDocs viewable API html online.
On 6/23/15, 7:47 AM, Michael Schmalle teotigraphix...@gmail.com wrote:
You can try and see if you could get asdoc working on those files but, I
boiled it down and asdoc just didn't want to parse Object, it said
Namespace not found and pointed to the package { declaration.
I assume this is asdoc from the current Flex SDK? We still don’t have any
Falcon-based ASDoc other than what you wrote, right? I’d prefer not to
have to rummage through the old asdoc source.
I thought existing asdoc generated some intermediate files then somehow
ran XSLT on them. I’ll put this on my list, but right now it would go
after trying to get my other test app working across domains and trying to
improve the way it looks.
-Alex
Re: [FlexJS] DOM/JQuery ASDocs viewable API html online.
On 6/23/15, 7:02 AM, Michael Schmalle teotigraphix...@gmail.com wrote: No, this is a full program. There is a huge amount of logic that goes into generating this stuff, same would be the case for XML. Right now it's AST - Intermediate Model - Velocity - HTML. Ah yes, I remember you mentioning Intermediate Model”. Well, I can probably figure out how to go from Intermediate Model to XML, so I have no objections if you want to check it in. I think at least one other person was interested in it. -Alex
Re: [FlexJS] DOM/JQuery ASDocs viewable API html online.
Yeah, don't worry about it man! I was just showing you the error.
The Flex SDK asdoc emits DITA XML files and then runs XSL on the DITA
files. So I guess, if you produced the same DITA spec from the new
intermediate model, you could use the same XSL transformations. That would
be the way to do it instead of concocting some new XML dialect.
I'm doing a lot this summer with my mother-in laws house and finishing up
those audio apps, so my time is severely limited. I actually spent way more
time on Apache that I thought I was going to and have to make up some time.
:)
I just wanted to get this up so at least people could look at the available
API since ASDoc won't create the docs.
Mike
On Tue, Jun 23, 2015 at 11:35 AM, Alex Harui aha...@adobe.com wrote:
On 6/23/15, 7:47 AM, Michael Schmalle teotigraphix...@gmail.com wrote:
You can try and see if you could get asdoc working on those files but, I
boiled it down and asdoc just didn't want to parse Object, it said
Namespace not found and pointed to the package { declaration.
I assume this is asdoc from the current Flex SDK? We still don’t have any
Falcon-based ASDoc other than what you wrote, right? I’d prefer not to
have to rummage through the old asdoc source.
I thought existing asdoc generated some intermediate files then somehow
ran XSLT on them. I’ll put this on my list, but right now it would go
after trying to get my other test app working across domains and trying to
improve the way it looks.
-Alex
[FlexJS] DOM/JQuery ASDocs viewable API html online.
Hey, I wasted 1.5 hours trying to get asdoc working with these classes and it seems that old gramps wasn't having it. Had namespace issues, I really don't know what is wrong, Falcon parses this stuff fine but asdoc chokes and dies. So, just for people to get an example of the API, I posted the HTML asdocs of JS and JQuery SWCs up on my server for the time being. These docs were made with My documenter I mentioned weeks before. My program had no problem creating these. The only thing is, I never finished it for global functions and constants, which this project uses. So I hacked in them for the class summary and page summary, you can see them but I have not created full clickable pages. There is one bug in the js of the asdocs, that if you have inherited mebers expanded, the js doesn't redraw the rows until you click it again. Other than that, there are quite a few features I added in my docs that ASDoc doesn't have. http://www.teotigraphix.com/assets/apache/dom/asdoc/index.html Mike
Re: [FlexJS] DOM/JQuery ASDocs viewable API html online.
Thank you Mike! :) Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-DOM-JQuery-ASDocs-viewable-API-html-online-tp48154p48155.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [FlexJS] DOM/JQuery ASDocs viewable API html online.
No, this is a full program. There is a huge amount of logic that goes into generating this stuff, same would be the case for XML. Right now it's AST - Intermediate Model - Velocity - HTML. This has nothing to do with FalconJX right now, it's purely built off the Falcon framework of IDefinition etc. Mike On Tue, Jun 23, 2015 at 9:57 AM, Alex Harui aha...@adobe.com wrote: Sweet! Remind me: is your ASDoc “output” just another FalconJX emitter? I still want XML output or some other data structure for a future AIR-based doc viewer but I think that would be another emitter as well. I don’t know if anything gets lost if you go from XML to Velocity to HTML somehow instead of straight from AST to Velocity to HTML, but if you just have another emitter to check in, I’m totally fine with it. I think I’ve caught up with all of the other build stuff around the swcs so that I can help with integrating Velocity into our builds. -Alex On 6/23/15, 6:10 AM, Michael Schmalle teotigraphix...@gmail.com wrote: Hey, I wasted 1.5 hours trying to get asdoc working with these classes and it seems that old gramps wasn't having it. Had namespace issues, I really don't know what is wrong, Falcon parses this stuff fine but asdoc chokes and dies. So, just for people to get an example of the API, I posted the HTML asdocs of JS and JQuery SWCs up on my server for the time being. These docs were made with My documenter I mentioned weeks before. My program had no problem creating these. The only thing is, I never finished it for global functions and constants, which this project uses. So I hacked in them for the class summary and page summary, you can see them but I have not created full clickable pages. There is one bug in the js of the asdocs, that if you have inherited mebers expanded, the js doesn't redraw the rows until you click it again. Other than that, there are quite a few features I added in my docs that ASDoc doesn't have. http://www.teotigraphix.com/assets/apache/dom/asdoc/index.html Mike
Re: [FlexJS] DOM/JQuery ASDocs viewable API html online.
Sweet! Remind me: is your ASDoc “output” just another FalconJX emitter? I still want XML output or some other data structure for a future AIR-based doc viewer but I think that would be another emitter as well. I don’t know if anything gets lost if you go from XML to Velocity to HTML somehow instead of straight from AST to Velocity to HTML, but if you just have another emitter to check in, I’m totally fine with it. I think I’ve caught up with all of the other build stuff around the swcs so that I can help with integrating Velocity into our builds. -Alex On 6/23/15, 6:10 AM, Michael Schmalle teotigraphix...@gmail.com wrote: Hey, I wasted 1.5 hours trying to get asdoc working with these classes and it seems that old gramps wasn't having it. Had namespace issues, I really don't know what is wrong, Falcon parses this stuff fine but asdoc chokes and dies. So, just for people to get an example of the API, I posted the HTML asdocs of JS and JQuery SWCs up on my server for the time being. These docs were made with My documenter I mentioned weeks before. My program had no problem creating these. The only thing is, I never finished it for global functions and constants, which this project uses. So I hacked in them for the class summary and page summary, you can see them but I have not created full clickable pages. There is one bug in the js of the asdocs, that if you have inherited mebers expanded, the js doesn't redraw the rows until you click it again. Other than that, there are quite a few features I added in my docs that ASDoc doesn't have. http://www.teotigraphix.com/assets/apache/dom/asdoc/index.html Mike
Re: [FlexJS] DOM/JQuery ASDocs viewable API html online.
For others that use IJ, when you create a Lib for the JS swc, you can add
the;
http://www.teotigraphix.com/assets/apache/dom/asdoc/index.html
as a documentation URL to the library and you can then use Ctrl-Q to pin or
view the docs, which then shows you the function signature for all the
callbacks in the API.
Mike
On Tue, Jun 23, 2015 at 11:44 AM, Michael Schmalle
teotigraphix...@gmail.com wrote:
Yeah, don't worry about it man! I was just showing you the error.
The Flex SDK asdoc emits DITA XML files and then runs XSL on the DITA
files. So I guess, if you produced the same DITA spec from the new
intermediate model, you could use the same XSL transformations. That would
be the way to do it instead of concocting some new XML dialect.
I'm doing a lot this summer with my mother-in laws house and finishing up
those audio apps, so my time is severely limited. I actually spent way more
time on Apache that I thought I was going to and have to make up some time.
:)
I just wanted to get this up so at least people could look at the
available API since ASDoc won't create the docs.
Mike
On Tue, Jun 23, 2015 at 11:35 AM, Alex Harui aha...@adobe.com wrote:
On 6/23/15, 7:47 AM, Michael Schmalle teotigraphix...@gmail.com
wrote:
You can try and see if you could get asdoc working on those files but, I
boiled it down and asdoc just didn't want to parse Object, it said
Namespace not found and pointed to the package { declaration.
I assume this is asdoc from the current Flex SDK? We still don’t have any
Falcon-based ASDoc other than what you wrote, right? I’d prefer not to
have to rummage through the old asdoc source.
I thought existing asdoc generated some intermediate files then somehow
ran XSLT on them. I’ll put this on my list, but right now it would go
after trying to get my other test app working across domains and trying to
improve the way it looks.
-Alex
Re: [FalconJX] JS.swc actionscipt source for asdocs with the swc
To include asdocs in a (Flex) swc library, the following is required: - Generate asdocs adding the following arguments (via Ant): keep-xml = true skip-xsl = true - Create the swc as usual - Add the generated asdocs to the swc minus 2 files that aren't needed (ASDoc_Config.xml and overviews.xml). I've posted an ANT build that I use for one of my libs: http://apaste.info/YgG There's an article with some more info and another Ant sample build here: http://www.andygup.net/using-ant-to-build-swcs-with-asdoc-comments-included-on-windows-7/ Hope this is what you were looking for :) regards, Peter On 14/06/2015 8:16, Alex Harui wrote: On 6/13/15, 3:15 PM, Michael Schmalle teotigraphix...@gmail.com wrote: Hi, I was just curious if we can include the source for asdoc in the JS swc. IMHO it's pretty important dealing with the hundreds of classes and 1000's of fields and members a lot have some docs and most all have at least 1 @see tag that directs you to the w3c or whatever documentation. Not to mention @param and @return have pure JSType I am emitting that shows callback API on passed callback functions. I have no idea how to include this stuff. Me either. I think there is something called a fat swc? -Alex
Re: [FalconJX] JS.swc actionscipt source for asdocs with the swc
On 6/13/15, 3:15 PM, Michael Schmalle teotigraphix...@gmail.com wrote: Hi, I was just curious if we can include the source for asdoc in the JS swc. IMHO it's pretty important dealing with the hundreds of classes and 1000's of fields and members a lot have some docs and most all have at least 1 @see tag that directs you to the w3c or whatever documentation. Not to mention @param and @return have pure JSType I am emitting that shows callback API on passed callback functions. I have no idea how to include this stuff. Me either. I think there is something called a fat swc? -Alex
[FalconJX] JS.swc actionscipt source for asdocs with the swc
Hi, I was just curious if we can include the source for asdoc in the JS swc. IMHO it's pretty important dealing with the hundreds of classes and 1000's of fields and members a lot have some docs and most all have at least 1 @see tag that directs you to the w3c or whatever documentation. Not to mention @param and @return have pure JSType I am emitting that shows callback API on passed callback functions. I have no idea how to include this stuff. Mike
[FlexJS] Asdocs ANT build
Hi,
I finally committed some changes! Anyway I am not an ANT expert but there
is something that annoys me about that script and anybody that can fix it,
I will thank you. :)
In /asdoc/build.xml we have;
property name=FLEX_HOME value=${basedir}/../../flex-sdk/
Can somebody put a conditional in there to look for 'sdk' as well. I
checked out my repo in sdk and not flex-sdk.
I am only saying this because I have seen Fred's comments elsewhere and the
git checkout page says use sdk.
As it stands, I have asdocs for all the 10+ projects going so people that
like to see API or read asdoc, run the asdocs/build.xml and it should work.
I just rendered them 30 minutes ago using the current code and HEAD of
develop in asjs.
Mike
Re: [FlexJS] Asdocs ANT build
Ok try it.
On 5/26/15, 1:12 PM, Michael Schmalle teotigraphix...@gmail.com wrote:
Hi,
I finally committed some changes! Anyway I am not an ANT expert but there
is something that annoys me about that script and anybody that can fix it,
I will thank you. :)
In /asdoc/build.xml we have;
property name=FLEX_HOME value=${basedir}/../../flex-sdk/
Can somebody put a conditional in there to look for 'sdk' as well. I
checked out my repo in sdk and not flex-sdk.
I am only saying this because I have seen Fred's comments elsewhere and
the
git checkout page says use sdk.
As it stands, I have asdocs for all the 10+ projects going so people that
like to see API or read asdoc, run the asdocs/build.xml and it should
work.
I just rendered them 30 minutes ago using the current code and HEAD of
develop in asjs.
Mike
Re: [FlexJS] Asdocs ANT build
Ok it works great. For some reason it ran fine but now it's barfing on the
TitleBarView.mxml. I took the mx namespace declaration out but it still
gives an error. So I just committed something that comments out HTML/asjs
source.
Teoti@TEOTI-PC ~/Documents/ApacheFlex/asjs/asdoc (develop)
$ ant
Buildfile: c:\Users\Teoti\Documents\ApacheFlex\asjs\asdoc\build.xml
[echo] FLEX_HOME =
c:\Users\Teoti\Documents\ApacheFlex\asjs\asdoc/../../sdk
[echo] flexlib = c:\Users\Teoti\Documents\ApacheFlex\asjs\frameworks
[echo] doc_output =
c:\Users\Teoti\Documents\ApacheFlex\asjs\asdoc-output
[echo] compiler.source-path =
c:\Users\Teoti\Documents\ApacheFlex\asjs\frameworks\projects/*/as/src
[echo] compiler.source-path =
c:\Users\Teoti\Documents\ApacheFlex\asjs\frameworks\projects/*/asjs/src
clean:
[delete] Deleting directory
c:\Users\Teoti\Documents\ApacheFlex\asjs\asdoc-output
doc:
[asdoc] Loading configuration file
C:\Users\Teoti\Documents\ApacheFlex\asjs\frameworks\asdoc-config.xml
[asdoc]
C:\Users\Teoti\Documents\ApacheFlex\asjs\frameworks\projects\HTML\asjs\src\org\apache\flex\html\beads\TitleBarView.mxml(-1):
Error: Namespace was n
ot found or is not a compile-time constant.
[asdoc]
[asdoc] ?xml version=1.0 encoding=utf-8?
[asdoc]
BUILD FAILED
c:\Users\Teoti\Documents\ApacheFlex\asjs\asdoc\build.xml:74: asdoc task
failed.
Total time: 5 seconds
Mike
On Tue, May 26, 2015 at 4:28 PM, Alex Harui aha...@adobe.com wrote:
Ok try it.
On 5/26/15, 1:12 PM, Michael Schmalle teotigraphix...@gmail.com wrote:
Hi,
I finally committed some changes! Anyway I am not an ANT expert but there
is something that annoys me about that script and anybody that can fix it,
I will thank you. :)
In /asdoc/build.xml we have;
property name=FLEX_HOME value=${basedir}/../../flex-sdk/
Can somebody put a conditional in there to look for 'sdk' as well. I
checked out my repo in sdk and not flex-sdk.
I am only saying this because I have seen Fred's comments elsewhere and
the
git checkout page says use sdk.
As it stands, I have asdocs for all the 10+ projects going so people that
like to see API or read asdoc, run the asdocs/build.xml and it should
work.
I just rendered them 30 minutes ago using the current code and HEAD of
develop in asjs.
Mike
Re: [4.14.1] volunteers needed to update site, asdocs and post a blog
On 31/03/15 12:45, Nicholas Kwiatkowski wrote: The only thing that isn't done is asdocs. The Apache SVN was doing weird things last night when I got to that point. I'll try again this evening. Did you crack this problem yet ? I'm going to be busy next week. Tom
Re: [4.14.1] volunteers needed to update site, asdocs and post a blog
I did notice that on the installer page [1], the version number is not showing up on the badge. Can anybody take a stab at that one? Done. EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: [4.14.1] volunteers needed to update site, asdocs and post a blog
gah. Moved onto the next shiny thing and forgot. Seems like it's pushing live now. I did notice that on the installer page [1], the version number is not showing up on the badge. Can anybody take a stab at that one? -Nick [1] http://flex.apache.org/installer.html On Tue, Apr 7, 2015 at 3:56 AM, Tom Chiverton t...@extravision.com wrote: On 31/03/15 12:45, Nicholas Kwiatkowski wrote: The only thing that isn't done is asdocs. The Apache SVN was doing weird things last night when I got to that point. I'll try again this evening. Did you crack this problem yet ? I'm going to be busy next week. Tom
Re: [4.14.1] volunteers needed to update site, asdocs and post a blog
On it. I'll have it out this evening when I get home from work. Awesome! Thanks, EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: [4.14.1] volunteers needed to update site, asdocs and post a blog
The only thing that isn't done is asdocs. The Apache SVN was doing weird things last night when I got to that point. I'll try again this evening. -Nick On Tue, Mar 31, 2015 at 4:25 AM, Erik de Bruin e...@ixsoftware.nl wrote: On it. I'll have it out this evening when I get home from work. Awesome! Thanks, EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
[4.14.1] volunteers needed to update site, asdocs and post a blog
Hi, While the update is officially released, we still need to: - update the website [1] - publish the new ASDocs [2] - blog about the release [3] Thanks for volunteering! EdB 1: https://issues.apache.org/jira/browse/FLEX-34793 2: https://issues.apache.org/jira/browse/FLEX-34794 3: https://issues.apache.org/jira/browse/FLEX-34796 -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: [4.14.1] volunteers needed to update site, asdocs and post a blog
On it. I'll have it out this evening when I get home from work. -Nick On Mon, Mar 30, 2015 at 6:29 AM, Erik de Bruin e...@ixsoftware.nl wrote: Hi, While the update is officially released, we still need to: - update the website [1] - publish the new ASDocs [2] - blog about the release [3] Thanks for volunteering! EdB 1: https://issues.apache.org/jira/browse/FLEX-34793 2: https://issues.apache.org/jira/browse/FLEX-34794 3: https://issues.apache.org/jira/browse/FLEX-34796 -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
FlexUnit Tutorials and ASDocs
Just a heads up, I've finished putting the FlexUnit tutorials and ASDocs on the staging website. For the most part, they should be good to go, but may need some styling tweaks because of the mdtext parser. If anybody wants to make any edits / corrections / additions to them, feel free. They've also been added to the site's navigation. If nobody screams too loudly, I'll push these to production tomorrow evening. Big thanks to Mike for rescuing the sources to these. -Nick
ASDocs on Flex Website
Just a heads up -- I just pushed the 4.12 docs onto staging. When we feel good about the Team page, we can publish both changesets to production. Whomever ends up doing that -- just a heads up, it will take a long while (15 minutes) for everything to get pushed because of the number of changes that have to be published. -Nick
[DISCUSSION] 4.11.0 RC 2 ASDocs
Just reposting with new subject to separate conversations... On 21/10/2013 16:03, Lee Burrows wrote: Sorry, that was for the asdocs build - it seems to be doing everything correctly (including temporary creation of tempdita folder) but no files (other than examples) exist at the end of the process. On 21/10/2013 15:53, Maurice Amsellem wrote: Lee wrote: Ant build completed successfully in 5m 12s at 21/10/13 13:52 SDK usually takes longer for a clean build. Maybe it was not that successful... Can you try using the SDK Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 15:44 À : dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 Yes, it's there. Don't worry too much about it; if its working for most people, i assume its a problem on my end. I'm also having issues with sdk build (cant build with JDK 1.7, cant include flash integration kit) and the frustration has removed my interest in attempting some bug fixes for now :) On 21/10/2013 14:30, Maurice Amsellem wrote: Lee, Can you check that you have flexTasks.jar in sdk/lib/ directory? Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 15:00 À : dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 I have already done a full sdk build and ant does report success for asdocs build: Ant build completed successfully in 5m 12s at 21/10/13 13:52 But the only contents in asdoc-output folder are the examples. FYI, i am using github develop branch, not apache develop branch. On 21/10/2013 13:43, Maurice Amsellem wrote: I tried generating ASdocs (with asdoc target in main build file). Ok, so the lib directory is probably missing in your configuration. It's generated when running the full SDK build. Did you run a full build before building the asdocs, or did you run asdoc build directly? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 21 octobre 2013 14:40 À : dev@flex.apache.org Objet : RE: [DISCUSSION] Apache Flex 4.11.0 RC 2 I tried generating ASdocs (with asdoc target in main build file). FI, ASDOC Build work on the develop branch Checking differences with the release -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 21 octobre 2013 14:37 À : dev@flex.apache.org Objet : RE: [DISCUSSION] Apache Flex 4.11.0 RC 2 Same. It says could not load flexTasks.task, so basically asdocs fails at the beginning . I am checking what's wrong... Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 14:22 À : dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 I tried generating ASdocs (with asdoc target in main build file). The build runs without errors but the output only consists of an include_examples folder (and subfolders) - there are none of the usual asdocs files. Anyone else experiencing this? On 21/10/2013 07:03, Frédéric THOMAS wrote: Thanks, so, that's should be fine, will rerun it later anyway as too many tests were failing, not the time this morning to examine why, some were because of the timeouts though. But given everyone have successfully run it, it should be something in my conf, will check that later. -Fred -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : lundi 21 octobre 2013 07:57 À : dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 What failures are you getting? Erik's VM has run all tests twice a day. -Alex On 10/20/13 10:54 PM, Frédéric THOMAS webdoubl...@hotmail.com wrote: Hi, I had a lot of tests failed, does someone knows when Jenkins ran successfully the full test suite for the last time ? looking in the commit list, I've seen only partial tests, the ones relying on changes. -Fred -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : lundi 21 octobre 2013 04:16 À : dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 I'm not working on these tests. I'm totally unfamiliar with Callout-related stuff. I'm not sure why these tests aren't failing in the CI runs but in other runs. On 10/20/13 12:22 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: Hi, Alex already asked about these tests ( thread [Mustella] tests/experimental/spark/components/CallOutButton started Oct 16th) And I understood from our discussion that he was working on fixing the tests. I don't know what is the current status. Maurice -Message d'origine- De : Frédéric THOMAS [mailto:webdoubl...@hotmail.com] Envoyé : dimanche 20 octobre 2013 20:12 À : dev@flex.apache.org Objet : RE: [DISCUSSION] Apache Flex 4.11.0 RC 2 Hi Maurice, So, shouldn't those tests have been removed or at least excluded ? -Fred -Message d'origine- De
RE: [DISCUSSION] 4.11.0 RC 2 ASDocs
Can you add the following to the ascdoc ant task: keep-xml=true so that the intermediary files are not deleted. Then zip and share asdoc-output/tempdita folder Thanks Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 17:08 À : dev@flex.apache.org Objet : [DISCUSSION] 4.11.0 RC 2 ASDocs Just reposting with new subject to separate conversations... On 21/10/2013 16:03, Lee Burrows wrote: Sorry, that was for the asdocs build - it seems to be doing everything correctly (including temporary creation of tempdita folder) but no files (other than examples) exist at the end of the process. On 21/10/2013 15:53, Maurice Amsellem wrote: Lee wrote: Ant build completed successfully in 5m 12s at 21/10/13 13:52 SDK usually takes longer for a clean build. Maybe it was not that successful... Can you try using the SDK Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 15:44 À : dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 Yes, it's there. Don't worry too much about it; if its working for most people, i assume its a problem on my end. I'm also having issues with sdk build (cant build with JDK 1.7, cant include flash integration kit) and the frustration has removed my interest in attempting some bug fixes for now :) On 21/10/2013 14:30, Maurice Amsellem wrote: Lee, Can you check that you have flexTasks.jar in sdk/lib/ directory? Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 15:00 À : dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 I have already done a full sdk build and ant does report success for asdocs build: Ant build completed successfully in 5m 12s at 21/10/13 13:52 But the only contents in asdoc-output folder are the examples. FYI, i am using github develop branch, not apache develop branch. On 21/10/2013 13:43, Maurice Amsellem wrote: I tried generating ASdocs (with asdoc target in main build file). Ok, so the lib directory is probably missing in your configuration. It's generated when running the full SDK build. Did you run a full build before building the asdocs, or did you run asdoc build directly? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 21 octobre 2013 14:40 À : dev@flex.apache.org Objet : RE: [DISCUSSION] Apache Flex 4.11.0 RC 2 I tried generating ASdocs (with asdoc target in main build file). FI, ASDOC Build work on the develop branch Checking differences with the release -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 21 octobre 2013 14:37 À : dev@flex.apache.org Objet : RE: [DISCUSSION] Apache Flex 4.11.0 RC 2 Same. It says could not load flexTasks.task, so basically asdocs fails at the beginning . I am checking what's wrong... Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 14:22 À : dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 I tried generating ASdocs (with asdoc target in main build file). The build runs without errors but the output only consists of an include_examples folder (and subfolders) - there are none of the usual asdocs files. Anyone else experiencing this? On 21/10/2013 07:03, Frédéric THOMAS wrote: Thanks, so, that's should be fine, will rerun it later anyway as too many tests were failing, not the time this morning to examine why, some were because of the timeouts though. But given everyone have successfully run it, it should be something in my conf, will check that later. -Fred -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : lundi 21 octobre 2013 07:57 À : dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 What failures are you getting? Erik's VM has run all tests twice a day. -Alex On 10/20/13 10:54 PM, Frédéric THOMAS webdoubl...@hotmail.com wrote: Hi, I had a lot of tests failed, does someone knows when Jenkins ran successfully the full test suite for the last time ? looking in the commit list, I've seen only partial tests, the ones relying on changes. -Fred -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : lundi 21 octobre 2013 04:16 À : dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 I'm not working on these tests. I'm totally unfamiliar with Callout-related stuff. I'm not sure why these tests aren't failing in the CI runs but in other runs. On 10/20/13 12:22 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: Hi, Alex already asked about these tests ( thread [Mustella] tests/experimental/spark/components
RE: [DISCUSSION] 4.11.0 RC 2 ASDocs
Thanks. Since it contains static files only, can you also send topLevel.xml file located at the root of asdoc-output. Maurice De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 18:04 À : dev@flex.apache.org Objet : Re: [DISCUSSION] 4.11.0 RC 2 ASDocs zip attached. On 21/10/2013 16:33, Maurice Amsellem wrote: Can you add the following to the ascdoc ant task: keep-xml=true so that the intermediary files are not deleted. Then zip and share asdoc-output/tempdita folder Thanks Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 17:08 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : [DISCUSSION] 4.11.0 RC 2 ASDocs Just reposting with new subject to separate conversations... On 21/10/2013 16:03, Lee Burrows wrote: Sorry, that was for the asdocs build - it seems to be doing everything correctly (including temporary creation of tempdita folder) but no files (other than examples) exist at the end of the process. On 21/10/2013 15:53, Maurice Amsellem wrote: Lee wrote: Ant build completed successfully in 5m 12s at 21/10/13 13:52 SDK usually takes longer for a clean build. Maybe it was not that successful... Can you try using the SDK Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 15:44 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 Yes, it's there. Don't worry too much about it; if its working for most people, i assume its a problem on my end. I'm also having issues with sdk build (cant build with JDK 1.7, cant include flash integration kit) and the frustration has removed my interest in attempting some bug fixes for now :) On 21/10/2013 14:30, Maurice Amsellem wrote: Lee, Can you check that you have flexTasks.jar in sdk/lib/ directory? Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 15:00 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 I have already done a full sdk build and ant does report success for asdocs build: Ant build completed successfully in 5m 12s at 21/10/13 13:52 But the only contents in asdoc-output folder are the examples. FYI, i am using github develop branch, not apache develop branch. On 21/10/2013 13:43, Maurice Amsellem wrote: I tried generating ASdocs (with asdoc target in main build file). Ok, so the lib directory is probably missing in your configuration. It's generated when running the full SDK build. Did you run a full build before building the asdocs, or did you run asdoc build directly? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 21 octobre 2013 14:40 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : RE: [DISCUSSION] Apache Flex 4.11.0 RC 2 I tried generating ASdocs (with asdoc target in main build file). FI, ASDOC Build work on the develop branch Checking differences with the release -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 21 octobre 2013 14:37 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : RE: [DISCUSSION] Apache Flex 4.11.0 RC 2 Same. It says could not load flexTasks.task, so basically asdocs fails at the beginning . I am checking what's wrong... Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 14:22 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 I tried generating ASdocs (with asdoc target in main build file). The build runs without errors but the output only consists of an include_examples folder (and subfolders) - there are none of the usual asdocs files. Anyone else experiencing this? On 21/10/2013 07:03, Frédéric THOMAS wrote: Thanks, so, that's should be fine, will rerun it later anyway as too many tests were failing, not the time this morning to examine why, some were because of the timeouts though. But given everyone have successfully run it, it should be something in my conf, will check that later. -Fred -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : lundi 21 octobre 2013 07:57 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 What failures are you getting? Erik's VM has run all tests twice a day. -Alex On 10/20/13 10:54 PM, Frédéric THOMAS webdoubl...@hotmail.commailto:webdoubl...@hotmail.com wrote: Hi, I had a lot of tests failed, does someone knows when Jenkins ran successfully the full test suite for the last time ? looking in the commit list, I've seen
Re: [DISCUSSION] 4.11.0 RC 2 ASDocs
I included everything there was (except include_examples) On 21/10/2013 17:26, Maurice Amsellem wrote: Thanks. Since it contains static files only, can you also send topLevel.xml file located at the root of asdoc-output. Maurice De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 18:04 À : dev@flex.apache.org Objet : Re: [DISCUSSION] 4.11.0 RC 2 ASDocs zip attached. On 21/10/2013 16:33, Maurice Amsellem wrote: Can you add the following to the ascdoc ant task: keep-xml=true so that the intermediary files are not deleted. Then zip and share asdoc-output/tempdita folder Thanks Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 17:08 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : [DISCUSSION] 4.11.0 RC 2 ASDocs Just reposting with new subject to separate conversations... On 21/10/2013 16:03, Lee Burrows wrote: Sorry, that was for the asdocs build - it seems to be doing everything correctly (including temporary creation of tempdita folder) but no files (other than examples) exist at the end of the process. On 21/10/2013 15:53, Maurice Amsellem wrote: Lee wrote: Ant build completed successfully in 5m 12s at 21/10/13 13:52 SDK usually takes longer for a clean build. Maybe it was not that successful... Can you try using the SDK Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 15:44 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 Yes, it's there. Don't worry too much about it; if its working for most people, i assume its a problem on my end. I'm also having issues with sdk build (cant build with JDK 1.7, cant include flash integration kit) and the frustration has removed my interest in attempting some bug fixes for now :) On 21/10/2013 14:30, Maurice Amsellem wrote: Lee, Can you check that you have flexTasks.jar in sdk/lib/ directory? Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 15:00 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 I have already done a full sdk build and ant does report success for asdocs build: Ant build completed successfully in 5m 12s at 21/10/13 13:52 But the only contents in asdoc-output folder are the examples. FYI, i am using github develop branch, not apache develop branch. On 21/10/2013 13:43, Maurice Amsellem wrote: I tried generating ASdocs (with asdoc target in main build file). Ok, so the lib directory is probably missing in your configuration. It's generated when running the full SDK build. Did you run a full build before building the asdocs, or did you run asdoc build directly? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 21 octobre 2013 14:40 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : RE: [DISCUSSION] Apache Flex 4.11.0 RC 2 I tried generating ASdocs (with asdoc target in main build file). FI, ASDOC Build work on the develop branch Checking differences with the release -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 21 octobre 2013 14:37 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : RE: [DISCUSSION] Apache Flex 4.11.0 RC 2 Same. It says could not load flexTasks.task, so basically asdocs fails at the beginning . I am checking what's wrong... Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 14:22 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 I tried generating ASdocs (with asdoc target in main build file). The build runs without errors but the output only consists of an include_examples folder (and subfolders) - there are none of the usual asdocs files. Anyone else experiencing this? On 21/10/2013 07:03, Frédéric THOMAS wrote: Thanks, so, that's should be fine, will rerun it later anyway as too many tests were failing, not the time this morning to examine why, some were because of the timeouts though. But given everyone have successfully run it, it should be something in my conf, will check that later. -Fred -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : lundi 21 octobre 2013 07:57 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 What failures are you getting? Erik's VM has run all tests twice a day. -Alex On 10/20/13 10:54 PM, Frédéric THOMAS webdoubl...@hotmail.commailto:webdoubl...@hotmail.com wrote: Hi, I had a lot of tests failed, does someone knows
RE: [DISCUSSION] 4.11.0 RC 2 ASDocs
That is going to be difficult to help you. It's probably one of the asdoc tools/libs that is missing or incorrectly build, or one of the environments variables that is not correctly set. Did you set all the environments variables required for the build ? # AIR_HOME # FLASHPLAYER_DEBUGGER # PLAYERGLOBAL_HOME # PIXELBENDER_HOME OR maybe the best is just to download the official 4.11 RC2 from Apache Flex and not from github. Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 18:34 À : dev@flex.apache.org Objet : Re: [DISCUSSION] 4.11.0 RC 2 ASDocs I included everything there was (except include_examples) On 21/10/2013 17:26, Maurice Amsellem wrote: Thanks. Since it contains static files only, can you also send topLevel.xml file located at the root of asdoc-output. Maurice De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 18:04 À : dev@flex.apache.org Objet : Re: [DISCUSSION] 4.11.0 RC 2 ASDocs zip attached. On 21/10/2013 16:33, Maurice Amsellem wrote: Can you add the following to the ascdoc ant task: keep-xml=true so that the intermediary files are not deleted. Then zip and share asdoc-output/tempdita folder Thanks Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 17:08 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : [DISCUSSION] 4.11.0 RC 2 ASDocs Just reposting with new subject to separate conversations... On 21/10/2013 16:03, Lee Burrows wrote: Sorry, that was for the asdocs build - it seems to be doing everything correctly (including temporary creation of tempdita folder) but no files (other than examples) exist at the end of the process. On 21/10/2013 15:53, Maurice Amsellem wrote: Lee wrote: Ant build completed successfully in 5m 12s at 21/10/13 13:52 SDK usually takes longer for a clean build. Maybe it was not that successful... Can you try using the SDK Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 15:44 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 Yes, it's there. Don't worry too much about it; if its working for most people, i assume its a problem on my end. I'm also having issues with sdk build (cant build with JDK 1.7, cant include flash integration kit) and the frustration has removed my interest in attempting some bug fixes for now :) On 21/10/2013 14:30, Maurice Amsellem wrote: Lee, Can you check that you have flexTasks.jar in sdk/lib/ directory? Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 15:00 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 I have already done a full sdk build and ant does report success for asdocs build: Ant build completed successfully in 5m 12s at 21/10/13 13:52 But the only contents in asdoc-output folder are the examples. FYI, i am using github develop branch, not apache develop branch. On 21/10/2013 13:43, Maurice Amsellem wrote: I tried generating ASdocs (with asdoc target in main build file). Ok, so the lib directory is probably missing in your configuration. It's generated when running the full SDK build. Did you run a full build before building the asdocs, or did you run asdoc build directly? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 21 octobre 2013 14:40 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : RE: [DISCUSSION] Apache Flex 4.11.0 RC 2 I tried generating ASdocs (with asdoc target in main build file). FI, ASDOC Build work on the develop branch Checking differences with the release -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 21 octobre 2013 14:37 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : RE: [DISCUSSION] Apache Flex 4.11.0 RC 2 Same. It says could not load flexTasks.task, so basically asdocs fails at the beginning . I am checking what's wrong... Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 14:22 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 I tried generating ASdocs (with asdoc target in main build file). The build runs without errors but the output only consists of an include_examples folder (and subfolders) - there are none of the usual asdocs files. Anyone else experiencing this? On 21/10/2013 07:03, Frédéric THOMAS wrote: Thanks, so, that's should
Re: [DISCUSSION] 4.11.0 RC 2 ASDocs
my last word on the subject ;) ... asdocs build successfully when i use 4.10 (apache git master branch) On 21/10/2013 17:50, Maurice Amsellem wrote: That is going to be difficult to help you. It's probably one of the asdoc tools/libs that is missing or incorrectly build, or one of the environments variables that is not correctly set. Did you set all the environments variables required for the build ? # AIR_HOME # FLASHPLAYER_DEBUGGER # PLAYERGLOBAL_HOME # PIXELBENDER_HOME OR maybe the best is just to download the official 4.11 RC2 from Apache Flex and not from github. Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 18:34 À : dev@flex.apache.org Objet : Re: [DISCUSSION] 4.11.0 RC 2 ASDocs I included everything there was (except include_examples) On 21/10/2013 17:26, Maurice Amsellem wrote: Thanks. Since it contains static files only, can you also send topLevel.xml file located at the root of asdoc-output. Maurice De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 18:04 À : dev@flex.apache.org Objet : Re: [DISCUSSION] 4.11.0 RC 2 ASDocs zip attached. On 21/10/2013 16:33, Maurice Amsellem wrote: Can you add the following to the ascdoc ant task: keep-xml=true so that the intermediary files are not deleted. Then zip and share asdoc-output/tempdita folder Thanks Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 17:08 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : [DISCUSSION] 4.11.0 RC 2 ASDocs Just reposting with new subject to separate conversations... On 21/10/2013 16:03, Lee Burrows wrote: Sorry, that was for the asdocs build - it seems to be doing everything correctly (including temporary creation of tempdita folder) but no files (other than examples) exist at the end of the process. On 21/10/2013 15:53, Maurice Amsellem wrote: Lee wrote: Ant build completed successfully in 5m 12s at 21/10/13 13:52 SDK usually takes longer for a clean build. Maybe it was not that successful... Can you try using the SDK Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 15:44 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 Yes, it's there. Don't worry too much about it; if its working for most people, i assume its a problem on my end. I'm also having issues with sdk build (cant build with JDK 1.7, cant include flash integration kit) and the frustration has removed my interest in attempting some bug fixes for now :) On 21/10/2013 14:30, Maurice Amsellem wrote: Lee, Can you check that you have flexTasks.jar in sdk/lib/ directory? Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 15:00 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 I have already done a full sdk build and ant does report success for asdocs build: Ant build completed successfully in 5m 12s at 21/10/13 13:52 But the only contents in asdoc-output folder are the examples. FYI, i am using github develop branch, not apache develop branch. On 21/10/2013 13:43, Maurice Amsellem wrote: I tried generating ASdocs (with asdoc target in main build file). Ok, so the lib directory is probably missing in your configuration. It's generated when running the full SDK build. Did you run a full build before building the asdocs, or did you run asdoc build directly? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 21 octobre 2013 14:40 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : RE: [DISCUSSION] Apache Flex 4.11.0 RC 2 I tried generating ASdocs (with asdoc target in main build file). FI, ASDOC Build work on the develop branch Checking differences with the release -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 21 octobre 2013 14:37 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : RE: [DISCUSSION] Apache Flex 4.11.0 RC 2 Same. It says could not load flexTasks.task, so basically asdocs fails at the beginning . I am checking what's wrong... Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 octobre 2013 14:22 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : Re: [DISCUSSION] Apache Flex 4.11.0 RC 2 I tried generating ASdocs (with asdoc target in main build file). The build runs without errors but the output only consists of an include_examples folder (and subfolders) - there are none of the usual asdocs files. Anyone else experiencing this? On 21/10/2013
Re: ASDocs issue
Hi, Did you push the other ASDoc fixes required to get to this problem? Yes in the release branch. But the release branch is merged with develop so you should see it there as well. Some minor stuff like missing imports for Falcon and some improvements for SWFDump, but also: FLEX-33690 https://issues.apache.org/jira/browse/FLEX-33690 (overlapping windows and focus) FLEX-33678 https://issues.apache.org/jira/browse/FLEX-33678 (scrollbar issue in DG) FLEX-33052 https://issues.apache.org/jira/browse/FLEX-33052 (charts in modules) Sounds fine to me, update the RELEASE_NOTES as well if you can. Thanks, Justin
Re: ASDocs issue
On 10/10/13 10:59 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Did you push the other ASDoc fixes required to get to this problem? Yes in the release branch. But the release branch is merged with develop so you should see it there as well. Hmm. I'll rebuild develop and see. None of the commit emails I see from you seem to mention develop branch. If that doesn't work I'll switch branches and try the release branch. Some minor stuff like missing imports for Falcon and some improvements for SWFDump, but also: FLEX-33690 https://issues.apache.org/jira/browse/FLEX-33690 (overlapping windows and focus) FLEX-33678 https://issues.apache.org/jira/browse/FLEX-33678 (scrollbar issue in DG) FLEX-33052 https://issues.apache.org/jira/browse/FLEX-33052 (charts in modules) Sounds fine to me, update the RELEASE_NOTES as well if you can. Do you know the best way to handle this given they've been committed to my local develop branch? Should I just push everything to develop then merge all of it to release? Anything I have to watch out for? Thanks, -Alex
Re: ASDocs issue
Hi, None of the commit emails I see from you seem to mention develop branch. Look like my local develop branch was tracking release for some odd reason I'll fix and merge for you. Should I just push everything to develop then merge all of it to release? That seems the simplest way to me. Anything I have to watch out for? Given that these were done a long time ago that there no merge issues. Thanks, Justin
Re: ASDocs issue
On 10/10/13 11:12 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, None of the commit emails I see from you seem to mention develop branch. Look like my local develop branch was tracking release for some odd reason I'll fix and merge for you. OK, was able to reproduce the problem. I've never worked with ASDoc, but in looking at the ant script, it appears there are no Flex SWCs in the process and everything is based on source paths. Also, it appears that there is a separate namespace for mobilecomponents and that may be why this code doesn't compile, since the s in the mxml is mapped to the spark namespace which is mapped to a manifest that doesn't have mobile components. But if that were true, I'd think there'd be lots of other failures like this. Let me know if you get past this before you quit for the day otherwise I'll try to dig deeper. Should I just push everything to develop then merge all of it to release? That seems the simplest way to me. OK, pushed and merged (I think). Anything I have to watch out for? Given that these were done a long time ago that there no merge issues. I'm about to shut down for the night. I'll see what the mustella runs report in the morning. Thanks, -Alex
Re: ASDocs issue
Hi, Let me know if you get past this before you quit for the day otherwise I'll try to dig deeper. Day is already over for me. Any help would be appreciated. OK, pushed and merged (I think). Yep. looks good. Mind updating the RELEASE_NOTES? Thanks, Justin
RE: ASDocs issue
Hi Justin, I have created a test subdirectory in asdoc containing this single file and also build_test.xml so that I can quickly quickly changes to the asdoc compiler or templates Without having to run through the whole SDK classes asdocs (while I was working on the experimental asdoc changes). I thought it could be useful for other people so I committed it. I have just added the missing header and committed/pushed to develop. Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : vendredi 11 octobre 2013 04:16 À : dev@flex.apache.org Objet : ASDocs issue Hi, Looks like this file is showing up in ASdocs: SampleExperimental.as Should that be the case? and if so why is it missing an Apache header? Thanks, Justin
RE: ASDocs issue
I have run the asdoc build.xml and getting this error: D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\mobiletheme\src\spark\skins\mobile\ViewMenuSkin.mxml: Could not resolve s:ViewMenuLayout to a component implementation. s:ViewMenuLayout horizontalGap=2 verticalGap=2 id=contentGroupLayout It seems to be related to the manifest issue you are talking about. I will check later today when I have some time. Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 11 octobre 2013 08:58 À : dev@flex.apache.org Objet : Re: ASDocs issue On 10/10/13 11:12 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, None of the commit emails I see from you seem to mention develop branch. Look like my local develop branch was tracking release for some odd reason I'll fix and merge for you. OK, was able to reproduce the problem. I've never worked with ASDoc, but in looking at the ant script, it appears there are no Flex SWCs in the process and everything is based on source paths. Also, it appears that there is a separate namespace for mobilecomponents and that may be why this code doesn't compile, since the s in the mxml is mapped to the spark namespace which is mapped to a manifest that doesn't have mobile components. But if that were true, I'd think there'd be lots of other failures like this. Let me know if you get past this before you quit for the day otherwise I'll try to dig deeper. Should I just push everything to develop then merge all of it to release? That seems the simplest way to me. OK, pushed and merged (I think). Anything I have to watch out for? Given that these were done a long time ago that there no merge issues. I'm about to shut down for the night. I'll see what the mustella runs report in the morning. Thanks, -Alex
RE: ASDocs issue
I have checked the asdoc build.xml and it's missing some of the changes I have made before (and I am sure I have commited and pushed, on 10/6). I have also noticed some of the classes I have removed in experimental (CalloutDropDownController, CallOutSkin) have reappeared when I merged from origin. I don't know what went wrong. I can make sure the asdoc build works again on my side and recommit/push the changes to origin. Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 09:39 À : dev@flex.apache.org Objet : RE: ASDocs issue I have run the asdoc build.xml and getting this error: D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\mobiletheme\src\spark\skins\mobile\ViewMenuSkin.mxml: Could not resolve s:ViewMenuLayout to a component implementation. s:ViewMenuLayout horizontalGap=2 verticalGap=2 id=contentGroupLayout It seems to be related to the manifest issue you are talking about. I will check later today when I have some time. Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 11 octobre 2013 08:58 À : dev@flex.apache.org Objet : Re: ASDocs issue On 10/10/13 11:12 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, None of the commit emails I see from you seem to mention develop branch. Look like my local develop branch was tracking release for some odd reason I'll fix and merge for you. OK, was able to reproduce the problem. I've never worked with ASDoc, but in looking at the ant script, it appears there are no Flex SWCs in the process and everything is based on source paths. Also, it appears that there is a separate namespace for mobilecomponents and that may be why this code doesn't compile, since the s in the mxml is mapped to the spark namespace which is mapped to a manifest that doesn't have mobile components. But if that were true, I'd think there'd be lots of other failures like this. Let me know if you get past this before you quit for the day otherwise I'll try to dig deeper. Should I just push everything to develop then merge all of it to release? That seems the simplest way to me. OK, pushed and merged (I think). Anything I have to watch out for? Given that these were done a long time ago that there no merge issues. I'm about to shut down for the night. I'll see what the mustella runs report in the morning. Thanks, -Alex
RE: ASDocs issue
Actually, the problem comes from asdoc build.xml It's referencing (line 150 and 168 the namespace library://ns.adobe.com/flex/spark-mobilecomponents which does not exist) As far as I know, mobile components are also in the regular spar namespace (library://ns.adobe.com/flex/spark) Since mobile components and spark components are referenced in a different manifest file in the asdoc build (166 and 168). it's legal that they use the same namespace. It shouldn't cause any collision or overlap. So I made the change above, and now I have the AnimationTarget compilation error :-(. Regarding this error, it's because AnimationTarget (which has been removed from experimental, as it was redundant with spark) has mysteriously reappeared . Trying to fix -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 09:48 À : dev@flex.apache.org Objet : RE: ASDocs issue I have checked the asdoc build.xml and it's missing some of the changes I have made before (and I am sure I have commited and pushed, on 10/6). I have also noticed some of the classes I have removed in experimental (CalloutDropDownController, CallOutSkin) have reappeared when I merged from origin. I don't know what went wrong. I can make sure the asdoc build works again on my side and recommit/push the changes to origin. Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 09:39 À : dev@flex.apache.org Objet : RE: ASDocs issue I have run the asdoc build.xml and getting this error: D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\mobiletheme\src\spark\skins\mobile\ViewMenuSkin.mxml: Could not resolve s:ViewMenuLayout to a component implementation. s:ViewMenuLayout horizontalGap=2 verticalGap=2 id=contentGroupLayout It seems to be related to the manifest issue you are talking about. I will check later today when I have some time. Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 11 octobre 2013 08:58 À : dev@flex.apache.org Objet : Re: ASDocs issue On 10/10/13 11:12 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, None of the commit emails I see from you seem to mention develop branch. Look like my local develop branch was tracking release for some odd reason I'll fix and merge for you. OK, was able to reproduce the problem. I've never worked with ASDoc, but in looking at the ant script, it appears there are no Flex SWCs in the process and everything is based on source paths. Also, it appears that there is a separate namespace for mobilecomponents and that may be why this code doesn't compile, since the s in the mxml is mapped to the spark namespace which is mapped to a manifest that doesn't have mobile components. But if that were true, I'd think there'd be lots of other failures like this. Let me know if you get past this before you quit for the day otherwise I'll try to dig deeper. Should I just push everything to develop then merge all of it to release? That seems the simplest way to me. OK, pushed and merged (I think). Anything I have to watch out for? Given that these were done a long time ago that there no merge issues. I'm about to shut down for the night. I'll see what the mustella runs report in the morning. Thanks, -Alex
RE: ASDocs issue
Actually , there is a general problem here, that a number of files that were removed have reappeared, of changes that was made have been cancelled, after I made a pull/merge. I am not familiar enough with git to understand how this can happen. Anyway I feel like it's not safe to just try to recover that lost changes by hand. Any idea ? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 10:13 À : dev@flex.apache.org Objet : RE: ASDocs issue Actually, the problem comes from asdoc build.xml It's referencing (line 150 and 168 the namespace library://ns.adobe.com/flex/spark-mobilecomponents which does not exist) As far as I know, mobile components are also in the regular spar namespace (library://ns.adobe.com/flex/spark) Since mobile components and spark components are referenced in a different manifest file in the asdoc build (166 and 168). it's legal that they use the same namespace. It shouldn't cause any collision or overlap. So I made the change above, and now I have the AnimationTarget compilation error :-(. Regarding this error, it's because AnimationTarget (which has been removed from experimental, as it was redundant with spark) has mysteriously reappeared . Trying to fix -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 09:48 À : dev@flex.apache.org Objet : RE: ASDocs issue I have checked the asdoc build.xml and it's missing some of the changes I have made before (and I am sure I have commited and pushed, on 10/6). I have also noticed some of the classes I have removed in experimental (CalloutDropDownController, CallOutSkin) have reappeared when I merged from origin. I don't know what went wrong. I can make sure the asdoc build works again on my side and recommit/push the changes to origin. Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 09:39 À : dev@flex.apache.org Objet : RE: ASDocs issue I have run the asdoc build.xml and getting this error: D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\mobiletheme\src\spark\skins\mobile\ViewMenuSkin.mxml: Could not resolve s:ViewMenuLayout to a component implementation. s:ViewMenuLayout horizontalGap=2 verticalGap=2 id=contentGroupLayout It seems to be related to the manifest issue you are talking about. I will check later today when I have some time. Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 11 octobre 2013 08:58 À : dev@flex.apache.org Objet : Re: ASDocs issue On 10/10/13 11:12 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, None of the commit emails I see from you seem to mention develop branch. Look like my local develop branch was tracking release for some odd reason I'll fix and merge for you. OK, was able to reproduce the problem. I've never worked with ASDoc, but in looking at the ant script, it appears there are no Flex SWCs in the process and everything is based on source paths. Also, it appears that there is a separate namespace for mobilecomponents and that may be why this code doesn't compile, since the s in the mxml is mapped to the spark namespace which is mapped to a manifest that doesn't have mobile components. But if that were true, I'd think there'd be lots of other failures like this. Let me know if you get past this before you quit for the day otherwise I'll try to dig deeper. Should I just push everything to develop then merge all of it to release? That seems the simplest way to me. OK, pushed and merged (I think). Anything I have to watch out for? Given that these were done a long time ago that there no merge issues. I'm about to shut down for the night. I'll see what the mustella runs report in the morning. Thanks, -Alex
RE: ASDocs issue
This is because original spark AnimationTarget is marked as internal, and that's probably why it was duplicated in experimental, to make it public. Since the redundant class was removed from experimental, the original internal class cannot be accessed anymore. I has changed spark AnimationTarget to public, and the problem has gone. Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : vendredi 11 octobre 2013 04:34 À : dev@flex.apache.org Objet : ASDocs issue Hi, We're currently getting this: doc: [asdoc] Loading configuration file /Users/justinmclean/Documents/ApacheFlex4.11.0/frameworks/flex-config.xml [asdoc] /Users/justinmclean/Documents/ApacheFlex4.11.0/frameworks/projects/experimental/src/spark/layouts/supportClasses/AnimationNavigatorLayoutBase.as(277): col: 19 Error: Type was not found or was not a compile-time constant: AnimationTarget. [asdoc] [asdoc] var animTarget:AnimationTarget = new AnimationTarget(); [asdoc]^ [asdoc] It's probably related to me renaming supportClazzes to supportClasses but I can't see any remaining references to supportClazzes - any one have any idea why we might be getting the error. AnimationTarget class is in ExperimentalClasses.as so that's not teh issue. Thanks, Justin
Re: ASDocs issue
Check the web view of the branch e.g. https://git-wip-us.apache.org/repos/asf/flex-sdk/repo?p=flex-sdk.git;a=shortlog;h=refs/heads/develop and or the tree https://git-wip-us.apache.org/repos/asf/flex-sdk/repo?p=flex-sdk.git;a=tree;h=refs/heads/develop;hb=refs/heads/develop and find the commitdiff that brought them back ? Tom On 11/10/2013 09:19, Maurice Amsellem wrote: Actually , there is a general problem here, that a number of files that were removed have reappeared, of changes that was made have been cancelled, after I made a pull/merge. I am not familiar enough with git to understand how this can happen. Anyway I feel like it's not safe to just try to recover that lost changes by hand. Any idea ? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 10:13 À : dev@flex.apache.org Objet : RE: ASDocs issue Actually, the problem comes from asdoc build.xml It's referencing (line 150 and 168 the namespace library://ns.adobe.com/flex/spark-mobilecomponents which does not exist) As far as I know, mobile components are also in the regular spar namespace (library://ns.adobe.com/flex/spark) Since mobile components and spark components are referenced in a different manifest file in the asdoc build (166 and 168). it's legal that they use the same namespace. It shouldn't cause any collision or overlap. So I made the change above, and now I have the AnimationTarget compilation error :-(. Regarding this error, it's because AnimationTarget (which has been removed from experimental, as it was redundant with spark) has mysteriously reappeared . Trying to fix -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 09:48 À : dev@flex.apache.org Objet : RE: ASDocs issue I have checked the asdoc build.xml and it's missing some of the changes I have made before (and I am sure I have commited and pushed, on 10/6). I have also noticed some of the classes I have removed in experimental (CalloutDropDownController, CallOutSkin) have reappeared when I merged from origin. I don't know what went wrong. I can make sure the asdoc build works again on my side and recommit/push the changes to origin. Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 09:39 À : dev@flex.apache.org Objet : RE: ASDocs issue I have run the asdoc build.xml and getting this error: D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\mobiletheme\src\spark\skins\mobile\ViewMenuSkin.mxml: Could not resolve s:ViewMenuLayout to a component implementation. s:ViewMenuLayout horizontalGap=2 verticalGap=2 id=contentGroupLayout It seems to be related to the manifest issue you are talking about. I will check later today when I have some time. Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 11 octobre 2013 08:58 À : dev@flex.apache.org Objet : Re: ASDocs issue On 10/10/13 11:12 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, None of the commit emails I see from you seem to mention develop branch. Look like my local develop branch was tracking release for some odd reason I'll fix and merge for you. OK, was able to reproduce the problem. I've never worked with ASDoc, but in looking at the ant script, it appears there are no Flex SWCs in the process and everything is based on source paths. Also, it appears that there is a separate namespace for mobilecomponents and that may be why this code doesn't compile, since the s in the mxml is mapped to the spark namespace which is mapped to a manifest that doesn't have mobile components. But if that were true, I'd think there'd be lots of other failures like this. Let me know if you get past this before you quit for the day otherwise I'll try to dig deeper. Should I just push everything to develop then merge all of it to release? That seems the simplest way to me. OK, pushed and merged (I think). Anything I have to watch out for? Given that these were done a long time ago that there no merge issues. I'm about to shut down for the night. I'll see what the mustella runs report in the morning. Thanks, -Alex __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __
RE: ASDocs issue
Thanks, I will do. -Message d'origine- De : Tom Chiverton [mailto:t...@extravision.com] Envoyé : vendredi 11 octobre 2013 10:46 À : dev@flex.apache.org Objet : Re: ASDocs issue Check the web view of the branch e.g. https://git-wip-us.apache.org/repos/asf/flex-sdk/repo?p=flex-sdk.git;a=shortlog;h=refs/heads/develop and or the tree https://git-wip-us.apache.org/repos/asf/flex-sdk/repo?p=flex-sdk.git;a=tree;h=refs/heads/develop;hb=refs/heads/develop and find the commitdiff that brought them back ? Tom On 11/10/2013 09:19, Maurice Amsellem wrote: Actually , there is a general problem here, that a number of files that were removed have reappeared, of changes that was made have been cancelled, after I made a pull/merge. I am not familiar enough with git to understand how this can happen. Anyway I feel like it's not safe to just try to recover that lost changes by hand. Any idea ? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 10:13 À : dev@flex.apache.org Objet : RE: ASDocs issue Actually, the problem comes from asdoc build.xml It's referencing (line 150 and 168 the namespace library://ns.adobe.com/flex/spark-mobilecomponents which does not exist) As far as I know, mobile components are also in the regular spar namespace (library://ns.adobe.com/flex/spark) Since mobile components and spark components are referenced in a different manifest file in the asdoc build (166 and 168). it's legal that they use the same namespace. It shouldn't cause any collision or overlap. So I made the change above, and now I have the AnimationTarget compilation error :-(. Regarding this error, it's because AnimationTarget (which has been removed from experimental, as it was redundant with spark) has mysteriously reappeared . Trying to fix -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 09:48 À : dev@flex.apache.org Objet : RE: ASDocs issue I have checked the asdoc build.xml and it's missing some of the changes I have made before (and I am sure I have commited and pushed, on 10/6). I have also noticed some of the classes I have removed in experimental (CalloutDropDownController, CallOutSkin) have reappeared when I merged from origin. I don't know what went wrong. I can make sure the asdoc build works again on my side and recommit/push the changes to origin. Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 09:39 À : dev@flex.apache.org Objet : RE: ASDocs issue I have run the asdoc build.xml and getting this error: D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\mobiletheme\src\spark\skins\mobile\ViewMenuSkin.mxml: Could not resolve s:ViewMenuLayout to a component implementation. s:ViewMenuLayout horizontalGap=2 verticalGap=2 id=contentGroupLayout It seems to be related to the manifest issue you are talking about. I will check later today when I have some time. Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 11 octobre 2013 08:58 À : dev@flex.apache.org Objet : Re: ASDocs issue On 10/10/13 11:12 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, None of the commit emails I see from you seem to mention develop branch. Look like my local develop branch was tracking release for some odd reason I'll fix and merge for you. OK, was able to reproduce the problem. I've never worked with ASDoc, but in looking at the ant script, it appears there are no Flex SWCs in the process and everything is based on source paths. Also, it appears that there is a separate namespace for mobilecomponents and that may be why this code doesn't compile, since the s in the mxml is mapped to the spark namespace which is mapped to a manifest that doesn't have mobile components. But if that were true, I'd think there'd be lots of other failures like this. Let me know if you get past this before you quit for the day otherwise I'll try to dig deeper. Should I just push everything to develop then merge all of it to release? That seems the simplest way to me. OK, pushed and merged (I think). Anything I have to watch out for? Given that these were done a long time ago that there no merge issues. I'm about to shut down for the night. I'll see what the mustella runs report in the morning. Thanks, -Alex __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __
RE: ASDocs issue
I have fixed the issue with AnimationTarget, and experimental manifest and now Experimental.swc and asdoc are compiling ok. Didn't commit yet. However, I noticed that asdoc experimental disclaimer does not show anymore :-( I am going to dig into the history of diffs, as suggested by Tom, to understand what went wrong. Maurice -Message d'origine- De : Maurice Amsellem Envoyé : vendredi 11 octobre 2013 11:04 À : dev@flex.apache.org Objet : RE: ASDocs issue Thanks, I will do. -Message d'origine- De : Tom Chiverton [mailto:t...@extravision.com] Envoyé : vendredi 11 octobre 2013 10:46 À : dev@flex.apache.org Objet : Re: ASDocs issue Check the web view of the branch e.g. https://git-wip-us.apache.org/repos/asf/flex-sdk/repo?p=flex-sdk.git;a=shortlog;h=refs/heads/develop and or the tree https://git-wip-us.apache.org/repos/asf/flex-sdk/repo?p=flex-sdk.git;a=tree;h=refs/heads/develop;hb=refs/heads/develop and find the commitdiff that brought them back ? Tom On 11/10/2013 09:19, Maurice Amsellem wrote: Actually , there is a general problem here, that a number of files that were removed have reappeared, of changes that was made have been cancelled, after I made a pull/merge. I am not familiar enough with git to understand how this can happen. Anyway I feel like it's not safe to just try to recover that lost changes by hand. Any idea ? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 10:13 À : dev@flex.apache.org Objet : RE: ASDocs issue Actually, the problem comes from asdoc build.xml It's referencing (line 150 and 168 the namespace library://ns.adobe.com/flex/spark-mobilecomponents which does not exist) As far as I know, mobile components are also in the regular spar namespace (library://ns.adobe.com/flex/spark) Since mobile components and spark components are referenced in a different manifest file in the asdoc build (166 and 168). it's legal that they use the same namespace. It shouldn't cause any collision or overlap. So I made the change above, and now I have the AnimationTarget compilation error :-(. Regarding this error, it's because AnimationTarget (which has been removed from experimental, as it was redundant with spark) has mysteriously reappeared . Trying to fix -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 09:48 À : dev@flex.apache.org Objet : RE: ASDocs issue I have checked the asdoc build.xml and it's missing some of the changes I have made before (and I am sure I have commited and pushed, on 10/6). I have also noticed some of the classes I have removed in experimental (CalloutDropDownController, CallOutSkin) have reappeared when I merged from origin. I don't know what went wrong. I can make sure the asdoc build works again on my side and recommit/push the changes to origin. Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 09:39 À : dev@flex.apache.org Objet : RE: ASDocs issue I have run the asdoc build.xml and getting this error: D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\mobiletheme\src\spark\skins\mobile\ViewMenuSkin.mxml: Could not resolve s:ViewMenuLayout to a component implementation. s:ViewMenuLayout horizontalGap=2 verticalGap=2 id=contentGroupLayout It seems to be related to the manifest issue you are talking about. I will check later today when I have some time. Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 11 octobre 2013 08:58 À : dev@flex.apache.org Objet : Re: ASDocs issue On 10/10/13 11:12 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, None of the commit emails I see from you seem to mention develop branch. Look like my local develop branch was tracking release for some odd reason I'll fix and merge for you. OK, was able to reproduce the problem. I've never worked with ASDoc, but in looking at the ant script, it appears there are no Flex SWCs in the process and everything is based on source paths. Also, it appears that there is a separate namespace for mobilecomponents and that may be why this code doesn't compile, since the s in the mxml is mapped to the spark namespace which is mapped to a manifest that doesn't have mobile components. But if that were true, I'd think there'd be lots of other failures like this. Let me know if you get past this before you quit for the day otherwise I'll try to dig deeper. Should I just push everything to develop then merge all of it to release? That seems the simplest way to me. OK, pushed and merged (I think). Anything I have to watch out for? Given that these were done a long time ago that there no merge issues. I'm about to shut down for the night. I'll see what
RE: ASDocs issue
However, I noticed that asdoc experimental disclaimer does not show anymore :-( Fixed ( I forgot to rebuild the asdoc compiler jars). Status: - build is OK - asdoc build is OK (no error) - asdoc content looks good. Committing/pushing now. Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 11:07 À : dev@flex.apache.org Objet : RE: ASDocs issue I have fixed the issue with AnimationTarget, and experimental manifest and now Experimental.swc and asdoc are compiling ok. Didn't commit yet. However, I noticed that asdoc experimental disclaimer does not show anymore :-( I am going to dig into the history of diffs, as suggested by Tom, to understand what went wrong. Maurice -Message d'origine- De : Maurice Amsellem Envoyé : vendredi 11 octobre 2013 11:04 À : dev@flex.apache.org Objet : RE: ASDocs issue Thanks, I will do. -Message d'origine- De : Tom Chiverton [mailto:t...@extravision.com] Envoyé : vendredi 11 octobre 2013 10:46 À : dev@flex.apache.org Objet : Re: ASDocs issue Check the web view of the branch e.g. https://git-wip-us.apache.org/repos/asf/flex-sdk/repo?p=flex-sdk.git;a=shortlog;h=refs/heads/develop and or the tree https://git-wip-us.apache.org/repos/asf/flex-sdk/repo?p=flex-sdk.git;a=tree;h=refs/heads/develop;hb=refs/heads/develop and find the commitdiff that brought them back ? Tom On 11/10/2013 09:19, Maurice Amsellem wrote: Actually , there is a general problem here, that a number of files that were removed have reappeared, of changes that was made have been cancelled, after I made a pull/merge. I am not familiar enough with git to understand how this can happen. Anyway I feel like it's not safe to just try to recover that lost changes by hand. Any idea ? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 10:13 À : dev@flex.apache.org Objet : RE: ASDocs issue Actually, the problem comes from asdoc build.xml It's referencing (line 150 and 168 the namespace library://ns.adobe.com/flex/spark-mobilecomponents which does not exist) As far as I know, mobile components are also in the regular spar namespace (library://ns.adobe.com/flex/spark) Since mobile components and spark components are referenced in a different manifest file in the asdoc build (166 and 168). it's legal that they use the same namespace. It shouldn't cause any collision or overlap. So I made the change above, and now I have the AnimationTarget compilation error :-(. Regarding this error, it's because AnimationTarget (which has been removed from experimental, as it was redundant with spark) has mysteriously reappeared . Trying to fix -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 09:48 À : dev@flex.apache.org Objet : RE: ASDocs issue I have checked the asdoc build.xml and it's missing some of the changes I have made before (and I am sure I have commited and pushed, on 10/6). I have also noticed some of the classes I have removed in experimental (CalloutDropDownController, CallOutSkin) have reappeared when I merged from origin. I don't know what went wrong. I can make sure the asdoc build works again on my side and recommit/push the changes to origin. Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 09:39 À : dev@flex.apache.org Objet : RE: ASDocs issue I have run the asdoc build.xml and getting this error: D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\mobiletheme\src\spark\skins\mobile\ViewMenuSkin.mxml: Could not resolve s:ViewMenuLayout to a component implementation. s:ViewMenuLayout horizontalGap=2 verticalGap=2 id=contentGroupLayout It seems to be related to the manifest issue you are talking about. I will check later today when I have some time. Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 11 octobre 2013 08:58 À : dev@flex.apache.org Objet : Re: ASDocs issue On 10/10/13 11:12 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, None of the commit emails I see from you seem to mention develop branch. Look like my local develop branch was tracking release for some odd reason I'll fix and merge for you. OK, was able to reproduce the problem. I've never worked with ASDoc, but in looking at the ant script, it appears there are no Flex SWCs in the process and everything is based on source paths. Also, it appears that there is a separate namespace for mobilecomponents and that may be why this code doesn't compile, since the s in the mxml is mapped to the spark namespace which is mapped to a manifest that doesn't have mobile components. But if that were true, I'd think there'd be lots of other
RE: ASDocs issue
Committed to : https://git-wip-us.apache.org/repos/asf?p=flex-sdk.git;a=commit;h=5ae5a847 -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 12:10 À : dev@flex.apache.org Objet : RE: ASDocs issue However, I noticed that asdoc experimental disclaimer does not show anymore :-( Fixed ( I forgot to rebuild the asdoc compiler jars). Status: - build is OK - asdoc build is OK (no error) - asdoc content looks good. Committing/pushing now. Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 11:07 À : dev@flex.apache.org Objet : RE: ASDocs issue I have fixed the issue with AnimationTarget, and experimental manifest and now Experimental.swc and asdoc are compiling ok. Didn't commit yet. However, I noticed that asdoc experimental disclaimer does not show anymore :-( I am going to dig into the history of diffs, as suggested by Tom, to understand what went wrong. Maurice -Message d'origine- De : Maurice Amsellem Envoyé : vendredi 11 octobre 2013 11:04 À : dev@flex.apache.org Objet : RE: ASDocs issue Thanks, I will do. -Message d'origine- De : Tom Chiverton [mailto:t...@extravision.com] Envoyé : vendredi 11 octobre 2013 10:46 À : dev@flex.apache.org Objet : Re: ASDocs issue Check the web view of the branch e.g. https://git-wip-us.apache.org/repos/asf/flex-sdk/repo?p=flex-sdk.git;a=shortlog;h=refs/heads/develop and or the tree https://git-wip-us.apache.org/repos/asf/flex-sdk/repo?p=flex-sdk.git;a=tree;h=refs/heads/develop;hb=refs/heads/develop and find the commitdiff that brought them back ? Tom On 11/10/2013 09:19, Maurice Amsellem wrote: Actually , there is a general problem here, that a number of files that were removed have reappeared, of changes that was made have been cancelled, after I made a pull/merge. I am not familiar enough with git to understand how this can happen. Anyway I feel like it's not safe to just try to recover that lost changes by hand. Any idea ? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 10:13 À : dev@flex.apache.org Objet : RE: ASDocs issue Actually, the problem comes from asdoc build.xml It's referencing (line 150 and 168 the namespace library://ns.adobe.com/flex/spark-mobilecomponents which does not exist) As far as I know, mobile components are also in the regular spar namespace (library://ns.adobe.com/flex/spark) Since mobile components and spark components are referenced in a different manifest file in the asdoc build (166 and 168). it's legal that they use the same namespace. It shouldn't cause any collision or overlap. So I made the change above, and now I have the AnimationTarget compilation error :-(. Regarding this error, it's because AnimationTarget (which has been removed from experimental, as it was redundant with spark) has mysteriously reappeared . Trying to fix -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 09:48 À : dev@flex.apache.org Objet : RE: ASDocs issue I have checked the asdoc build.xml and it's missing some of the changes I have made before (and I am sure I have commited and pushed, on 10/6). I have also noticed some of the classes I have removed in experimental (CalloutDropDownController, CallOutSkin) have reappeared when I merged from origin. I don't know what went wrong. I can make sure the asdoc build works again on my side and recommit/push the changes to origin. Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : vendredi 11 octobre 2013 09:39 À : dev@flex.apache.org Objet : RE: ASDocs issue I have run the asdoc build.xml and getting this error: D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\mobiletheme\src\spark\skins\mobile\ViewMenuSkin.mxml: Could not resolve s:ViewMenuLayout to a component implementation. s:ViewMenuLayout horizontalGap=2 verticalGap=2 id=contentGroupLayout It seems to be related to the manifest issue you are talking about. I will check later today when I have some time. Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 11 octobre 2013 08:58 À : dev@flex.apache.org Objet : Re: ASDocs issue On 10/10/13 11:12 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, None of the commit emails I see from you seem to mention develop branch. Look like my local develop branch was tracking release for some odd reason I'll fix and merge for you. OK, was able to reproduce the problem. I've never worked with ASDoc, but in looking at the ant script, it appears there are no Flex SWCs in the process and everything is based on source paths. Also, it appears
Re: ASDocs issue
Hi, Status: - build is OK - asdoc build is OK (no error) - asdoc content looks good. Much appreciated for sorting that out. Thanks, Justin
RE: ASDocs issue
You're welcome. My configuration being a little tweaked (with .gitignored files), can you please double check ... Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : vendredi 11 octobre 2013 13:01 À : dev@flex.apache.org Objet : Re: ASDocs issue Hi, Status: - build is OK - asdoc build is OK (no error) - asdoc content looks good. Much appreciated for sorting that out. Thanks, Justin
Re: ASDocs issue
Hi, My configuration being a little tweaked (with .gitignored files), can you please double check ... You might want to not check in changes to flex-sdk-description.xml but other than that all good from what I can see. Thanks, Justin
RE: ASDocs issue
Ah, OK sorry for that one. I will add it to my .gitignore. Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : vendredi 11 octobre 2013 14:57 À : dev@flex.apache.org Objet : Re: ASDocs issue Hi, My configuration being a little tweaked (with .gitignored files), can you please double check ... You might want to not check in changes to flex-sdk-description.xml but other than that all good from what I can see. Thanks, Justin
Re: ASDocs issue
Hi, Ah, OK sorry for that one. I will add it to my .gitignore. I wouldn't do that, sometime it does need to change and if someone else changes it you'll need to update it. Justin
RE: ASDocs issue
Ok, I will add it to .ignoreButKeepAnEyeOnIt file :-) -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : vendredi 11 octobre 2013 23:29 À : dev@flex.apache.org Objet : Re: ASDocs issue Hi, Ah, OK sorry for that one. I will add it to my .gitignore. I wouldn't do that, sometime it does need to change and if someone else changes it you'll need to update it. Justin
ASDocs issue
Hi, Looks like this file is showing up in ASdocs: SampleExperimental.as Should that be the case? and if so why is it missing an Apache header? Thanks, Justin
ASDocs issue
Hi, We're currently getting this: doc: [asdoc] Loading configuration file /Users/justinmclean/Documents/ApacheFlex4.11.0/frameworks/flex-config.xml [asdoc] /Users/justinmclean/Documents/ApacheFlex4.11.0/frameworks/projects/experimental/src/spark/layouts/supportClasses/AnimationNavigatorLayoutBase.as(277): col: 19 Error: Type was not found or was not a compile-time constant: AnimationTarget. [asdoc] [asdoc] var animTarget:AnimationTarget = new AnimationTarget(); [asdoc]^ [asdoc] It's probably related to me renaming supportClazzes to supportClasses but I can't see any remaining references to supportClazzes - any one have any idea why we might be getting the error. AnimationTarget class is in ExperimentalClasses.as so that's not teh issue. Thanks, Justin
Re: ASDocs issue
Hi, Looks like an issue with the asdocs build file - just trying to sort. Justin
Re: ASDocs issue
Hi, Fixed that issue (and a few more) but now have this one: doc: [asdoc] Loading configuration file /Users/justinmclean/Documents/ApacheFlex4.11.0/frameworks/flex-config.xml [asdoc] /Users/justinmclean/Documents/ApacheFlex4.11.0/frameworks/projects/mobiletheme/src/spark/skins/mobile/ViewMenuSkin.mxml(187): Error: Could not resolve s:ViewMenuLayout to a component implementation. [asdoc] [asdoc] s:ViewMenuLayout horizontalGap=2 verticalGap=2 id=contentGroupLayout [asdoc] ViewMenuSkin is in the mobile manifest file and that is being included in the asdoc ant file. I'd appreciate if someone could take a look at this and I'm out of ideas and it's stopping me from making a release candidate. Thanks, Justin
Re: ASDocs issue
On 10/10/13 8:21 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Fixed that issue (and a few more) but now have this one: doc: [asdoc] Loading configuration file /Users/justinmclean/Documents/ApacheFlex4.11.0/frameworks/flex-config.xml [asdoc] /Users/justinmclean/Documents/ApacheFlex4.11.0/frameworks/projects/mobilet heme/src/spark/skins/mobile/ViewMenuSkin.mxml(187): Error: Could not resolve s:ViewMenuLayout to a component implementation. [asdoc] [asdoc] s:ViewMenuLayout horizontalGap=2 verticalGap=2 id=contentGroupLayout [asdoc] ViewMenuSkin is in the mobile manifest file and that is being included in the asdoc ant file. I assume you meant ViewMenuLayout? The manifests, etc look ok. I guess you could dump the mobilecomponents.swc and see if that class is actually in there, but the main build should have failed in the same way. I'd appreciate if someone could take a look at this and I'm out of ideas and it's stopping me from making a release candidate. I have a fix for that FTETextField bug. The revert you did to fix the mustella tests effectively re-opens FLEX-33428. Unfortunately, I also discovered that I have a bunch of other commits that never got pushed. I think I held off last time mustella was broken and forgot to go back and push them afterwards. I also have one commit pending for tlf. I'm thinking of pushing them all to the develop branch and see if the full mustella run passes, and then we can move them to the release branch if nothing breaks. Thoughts?
Re: ASDocs issue
Hi, I assume you meant ViewMenuLayout? The manifests, etc look ok. Yep I meant ViewMenuLayout. I guess you could dump the mobilecomponents.swc and see if that class is actually in there It;s in there: swfdump ./mobile/mobilecomponents.swc | grep ViewMenuLayout DoABC2 name='spark/layouts/ViewMenuLayout' but the main build should have failed in the same way. It compiles no issues. I have a fix for that FTETextField bug. The revert you did to fix the mustella tests effectively re-opens FLEX-33428. Check it into release if you can, FLEX-33428 was not resolved yet so don't think any issue there. Unfortunately, I also discovered that I have a bunch of other commits that never got pushed. What are they? Thanks, Justin
Re: ASDocs issue
On 10/10/13 10:22 PM, Justin Mclean jus...@classsoftware.com wrote: but the main build should have failed in the same way. It compiles no issues. Did you push the other ASDoc fixes required to get to this problem? I just ran ant asdoc and got the AnimationTarget issue. I have a fix for that FTETextField bug. The revert you did to fix the mustella tests effectively re-opens FLEX-33428. Check it into release if you can, FLEX-33428 was not resolved yet so don't think any issue there. Unfortunately, I also discovered that I have a bunch of other commits that never got pushed. What are they? Some minor stuff like missing imports for Falcon and some improvements for SWFDump, but also: FLEX-33690 https://issues.apache.org/jira/browse/FLEX-33690 (overlapping windows and focus) FLEX-33678 https://issues.apache.org/jira/browse/FLEX-33678 (scrollbar issue in DG) FLEX-33052 https://issues.apache.org/jira/browse/FLEX-33052 (charts in modules) I'm still trying to find out the TLF change. -Alex
Re: ASDocs issue
The TLF change is part of https://issues.apache.org/jira/browse/FLEX-33409 On 10/10/13 10:44 PM, Alex Harui aha...@adobe.com wrote: On 10/10/13 10:22 PM, Justin Mclean jus...@classsoftware.com wrote: but the main build should have failed in the same way. It compiles no issues. Did you push the other ASDoc fixes required to get to this problem? I just ran ant asdoc and got the AnimationTarget issue. I have a fix for that FTETextField bug. The revert you did to fix the mustella tests effectively re-opens FLEX-33428. Check it into release if you can, FLEX-33428 was not resolved yet so don't think any issue there. Unfortunately, I also discovered that I have a bunch of other commits that never got pushed. What are they? Some minor stuff like missing imports for Falcon and some improvements for SWFDump, but also: FLEX-33690 https://issues.apache.org/jira/browse/FLEX-33690 (overlapping windows and focus) FLEX-33678 https://issues.apache.org/jira/browse/FLEX-33678 (scrollbar issue in DG) FLEX-33052 https://issues.apache.org/jira/browse/FLEX-33052 (charts in modules) I'm still trying to find out the TLF change. -Alex
[jira] [Created] (FLEX-33586) Packages missing from online asdocs
Lee Burrows created FLEX-33586: -- Summary: Packages missing from online asdocs Key: FLEX-33586 URL: https://issues.apache.org/jira/browse/FLEX-33586 Project: Apache Flex Issue Type: Documentation Components: ASDoc Content Affects Versions: Apache Flex 4.10.0 Environment: Comparing Adobe online docs (http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/index.html) and Apache online docs (http://flex.apache.org/asdoc/index.html) Reporter: Lee Burrows Priority: Minor Some spark packages are not listed in asdocs: spark.automation.delegates spark.automation.delegates.components spark.automation.delegates.components.gridClasses spark.automation.delegates.components.mediaClasses spark.automation.delegates.components.supportClasses spark.automation.delegates.skins.spark spark.automation.events spark.skins.mobile spark.skins.mobile.supportClasses spark.skins.wireframe spark.skins.wireframe.mediaClasses spark.skins.wireframe.mediaClasses.fullScreen -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[DISCUSS] website asdocs
Having the asdoc in the site folder, is this a good idea? The seems really wrong on a gut level to me but I don't have another solution at the moment. I am sitting still waiting on a broadband connection just to change my site info. This is also why I only selectively check out whiteboard folders so I don't get multiple copied branches of the 1's of framework files and tests. In reply to the Flash docs, IMHO me a re screwed and another reason to keep running from Adobe. :) Since I have been working on a new ASDOc tool/program I can see using the SWCs API to create the entries and links in the docs but have links in them to the Adobe live docs. This way you would get the api right in fornt of you all the way up to Object but not the descriptions. Mike -- Michael Schmalle - Teoti Graphix, LLC http://www.teotigraphix.com http://blog.teotigraphix.com
Re: [DISCUSS] website asdocs
Personally, I like having the ASDocs on the website (and therefore, we have to have it in the SVN). Otherwise I have to download 8 copies for my 8 different machines. I asked infra on IRC to see about the possibility to get a help.flex.apache.org that wasn't run through the CMS or something to that effect, and they didn't like the idea.. By the way, when anybody updates the ASdocs, the CMS will take about 2 hours to process it. It also causes the buildbot process to crash ;S -Nick On Mon, Jan 14, 2013 at 5:12 AM, Michael Schmalle apa...@teotigraphix.comwrote: Having the asdoc in the site folder, is this a good idea? The seems really wrong on a gut level to me but I don't have another solution at the moment. I am sitting still waiting on a broadband connection just to change my site info. This is also why I only selectively check out whiteboard folders so I don't get multiple copied branches of the 1's of framework files and tests. In reply to the Flash docs, IMHO me a re screwed and another reason to keep running from Adobe. :) Since I have been working on a new ASDOc tool/program I can see using the SWCs API to create the entries and links in the docs but have links in them to the Adobe live docs. This way you would get the api right in fornt of you all the way up to Object but not the descriptions. Mike -- Michael Schmalle - Teoti Graphix, LLC http://www.teotigraphix.com http://blog.teotigraphix.com
Re: [DISCUSS] website asdocs
I wasn't debating the fact that asdocs need to be public, I was questioning if having them in the CMS is our only option. As you said, republishing them kills the build and that proves there must be some other option or hosting solution. Mike Quoting Nicholas Kwiatkowski nicho...@spoon.as: Personally, I like having the ASDocs on the website (and therefore, we have to have it in the SVN). Otherwise I have to download 8 copies for my 8 different machines. I asked infra on IRC to see about the possibility to get a help.flex.apache.org that wasn't run through the CMS or something to that effect, and they didn't like the idea.. By the way, when anybody updates the ASdocs, the CMS will take about 2 hours to process it. It also causes the buildbot process to crash ;S -Nick On Mon, Jan 14, 2013 at 5:12 AM, Michael Schmalle apa...@teotigraphix.comwrote: Having the asdoc in the site folder, is this a good idea? The seems really wrong on a gut level to me but I don't have another solution at the moment. I am sitting still waiting on a broadband connection just to change my site info. This is also why I only selectively check out whiteboard folders so I don't get multiple copied branches of the 1's of framework files and tests. In reply to the Flash docs, IMHO me a re screwed and another reason to keep running from Adobe. :) Since I have been working on a new ASDOc tool/program I can see using the SWCs API to create the entries and links in the docs but have links in them to the Adobe live docs. This way you would get the api right in fornt of you all the way up to Object but not the descriptions. Mike -- Michael Schmalle - Teoti Graphix, LLC http://www.teotigraphix.com http://blog.teotigraphix.com -- Michael Schmalle - Teoti Graphix, LLC http://www.teotigraphix.com http://blog.teotigraphix.com
RE: [DISCUSS] website asdocs
I like the https://flex.apache.org/v2/asdoc ASDOCs atm. It has less clutter than the adobe ones and load faster. -Original Message- From: Nicholas Kwiatkowski [mailto:nicho...@spoon.as] Sent: Monday, January 14, 2013 7:55 To: dev@flex.apache.org Subject: Re: [DISCUSS] website asdocs Personally, I like having the ASDocs on the website (and therefore, we have to have it in the SVN). Otherwise I have to download 8 copies for my 8 different machines. I asked infra on IRC to see about the possibility to get a help.flex.apache.org that wasn't run through the CMS or something to that effect, and they didn't like the idea.. By the way, when anybody updates the ASdocs, the CMS will take about 2 hours to process it. It also causes the buildbot process to crash ;S -Nick On Mon, Jan 14, 2013 at 5:12 AM, Michael Schmalle apa...@teotigraphix.comwrote: Having the asdoc in the site folder, is this a good idea? The seems really wrong on a gut level to me but I don't have another solution at the moment. I am sitting still waiting on a broadband connection just to change my site info. This is also why I only selectively check out whiteboard folders so I don't get multiple copied branches of the 1's of framework files and tests. In reply to the Flash docs, IMHO me a re screwed and another reason to keep running from Adobe. :) Since I have been working on a new ASDOc tool/program I can see using the SWCs API to create the entries and links in the docs but have links in them to the Adobe live docs. This way you would get the api right in fornt of you all the way up to Object but not the descriptions. Mike -- Michael Schmalle - Teoti Graphix, LLC http://www.teotigraphix.com http://blog.teotigraphix.com
Re: [DISCUSS] website asdocs
Actually, I have to check into this but if adobe has publicly available SWCs that the new asdoc generator could load and parse the DITA with their documentation, adding Flash Player documentation is possible. I'm speaking from ignorance here and I would have to investigate if the playerglobal.swc somewhere has asdocs embedded. Mike Quoting Michael Schmalle apa...@teotigraphix.com: Quoting Harbs harbs.li...@gmail.com: Maybe, but there is the issue of the missing core classes (which I mentioned in the other thread I started). I answered this, the only way to get core classes is by creating a new asdoc that parses and renders the API from SWCs which I know is possible, this way you get the API. I see no real option of getting the descriptions with those, only code generated links that point to the Adobe livedocs for each member etc which would be really akward. I've also used the filter in the Adobe ASDocs based on Flash/AIR version on occasion. For the classes where it matters, those filters are useful. The current template for asdoc does not have all the JavaScript for filtering. At the moment this is impossible. If we're picking the ASDocs apart, I'd add a padding to the Apache Flex logo at the top right and probably make it a bit smaller? I just updated the image, I'm definitely not a web designer. Harbs On Jan 14, 2013, at 3:03 PM, Kessler CTR Mark J wrote: I like the https://flex.apache.org/v2/asdoc ASDOCs atm. It has less clutter than the adobe ones and load faster. -Original Message- From: Nicholas Kwiatkowski [mailto:nicho...@spoon.as] Sent: Monday, January 14, 2013 7:55 To: dev@flex.apache.org Subject: Re: [DISCUSS] website asdocs Personally, I like having the ASDocs on the website (and therefore, we have to have it in the SVN). Otherwise I have to download 8 copies for my 8 different machines. I asked infra on IRC to see about the possibility to get a help.flex.apache.org that wasn't run through the CMS or something to that effect, and they didn't like the idea.. By the way, when anybody updates the ASdocs, the CMS will take about 2 hours to process it. It also causes the buildbot process to crash ;S -Nick On Mon, Jan 14, 2013 at 5:12 AM, Michael Schmalle apa...@teotigraphix.comwrote: Having the asdoc in the site folder, is this a good idea? The seems really wrong on a gut level to me but I don't have another solution at the moment. I am sitting still waiting on a broadband connection just to change my site info. This is also why I only selectively check out whiteboard folders so I don't get multiple copied branches of the 1's of framework files and tests. In reply to the Flash docs, IMHO me a re screwed and another reason to keep running from Adobe. :) Since I have been working on a new ASDOc tool/program I can see using the SWCs API to create the entries and links in the docs but have links in them to the Adobe live docs. This way you would get the api right in fornt of you all the way up to Object but not the descriptions. Mike -- Michael Schmalle - Teoti Graphix, LLC http://www.teotigraphix.com http://blog.teotigraphix.com -- Michael Schmalle - Teoti Graphix, LLC http://www.teotigraphix.com http://blog.teotigraphix.com -- Michael Schmalle - Teoti Graphix, LLC http://www.teotigraphix.com http://blog.teotigraphix.com
