Re: [FlexJS] ASDoc: Any reason for additional config options?
It's about half past 8 AM and I'm in a Zombie Mode, so doing weird and unpredictable things! I hope my code will be ok at half past 1 PM when other guys from my Team will start doing Code Inspections. :D Thanks Chris! Looking forward to the results. :) Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-ASDoc-Any-reason-for-additional-config-options-tp57486p57489.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [FlexJS] ASDoc: Any reason for additional config options?
Hi Piotr, Yes it will be static html content as we know it from all other API docs for all other languages I have come across. It’s packaged as self-sufficient „{artifactid}-version-javadoc.jar“ files together with the artifact and the artifacts sources in typical Maven style. And how on earth did you manage to respond to my email before me writing it? ;-) Chris Am 21.12.16, 07:46 schrieb "piotrz": Hi Chris, What will be the results of your work ? I mean I will get documentation from source code AS and Java and I will see this documentation as code hint ? It will be an html output ? Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-ASDoc-Any-reason-for-additional-config-options-tp57486p57487.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [FlexJS] ASDoc: Any reason for additional config options?
Hi Chris, What will be the results of your work ? I mean I will get documentation from source code AS and Java and I will see this documentation as code hint ? It will be an html output ? Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-ASDoc-Any-reason-for-additional-config-options-tp57486p57487.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
[FlexJS] ASDoc: Any reason for additional config options?
Hi, I’m currently workin on Maven support of the ASDoc output. Now I’m sort of wondering, why we need these „doc-namespaces“ and „doc-sources“ config options? Shouldn’t the normal sources and namespaces be enough? Chris
Re: [DISCUSS] Apache Flex SDK 4.16 RC1 release
Hi, As per this: > Also be aware that I will have extremely limited internet access (no phone, > some access via satellite) from Friday my time (GMT +10) onwards and it’s > unlikely that I'll have the bandwidth to upload any further RCs for several > weeks after that date. Being Wednesday afternoon here I’ve run out of time to be able to create, test, release and finish a vote on the next RC and will have to wait until after I get back from being away. Thanks, Justin
Re: [DISCUSS] Apache Flex SDK 4.16 RC1 release
Apache projects aren't supposed to make forks without permission. Getting permission is a whole process. For me, it was easier to put a copy in the Adobe Flex SourceForge repo and get it from there. That way Adobe is still the distributor. -Alex On 12/20/16, 1:12 AM, "Christofer Dutz"wrote: >As we have been having problems like this quite regularly ... what would >prevent us from forking osmf and adding that to our flex extras git repo >and publishing osmf to maven-central. >Shouldn’t that resolve this type of problem once and for all? > >Chris > >Am 19.12.16, 23:27 schrieb "Justin Mclean" : > >Hi, > >The same download is also failing on OSX currently so it not just a >windows issue. > >However it's not failing consistently on my 3rd try it worked. > >Using curl -v I notice it's doing a 302 redirect to: > >https://pilotfiber.dl.sourceforge.net/project/osmf.adobe/OSMF%202.0%20Rele >ase%20%28final%20source%2C%20ASDocs%2C%20pdf%20guides%20and%20release%20no >tes%29/OSMF.swc > >Perhaps using that URL would give more consistent results? > >Justin >
[4.16.0] # Apache Flex SDK 4.16.0 nightly build 175: Successful
flex-sdk_release-candidate - Build #175 - Successful Changes since last build: No changes For more information, check the console output at http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/175/.
Re: Converting JavaScript libraries to AS3
On 12/20/16, 6:56 AM, "Christofer Dutz"wrote: >Hi, > >I think this is what our „externs“ do ... you sort of generate a no-op AS >counterpart which the IDE is able to use for content assist, but the >FlexJS then directly calls the JS library. >But I bet the others will be able to give you more detailled infos on >this. Our ExternC tool is capable of converting the Google Externs pattern of JS to AS. It cannot currently handle a full JS implementation, but probably could with a chunk of work. But even that would only be for what I would call prototype-based JS patterns with Google-style JSDoc. Plenty of libraries are written with other patterns like functions that generate the classes and use different annotations for type information. CreateJS and Jquery for example, can't currently be parsed by ExternC. Doing so would be a significant amount of work, IMO. But volunteers are welcome to try. I believe anyone could now write a JS library in AS and cross-compile it. I'm sure there are still transpilar bugs that need fixing though. But folks may not like the output format we currently support so new emitters would need to be written. And some folks simply like doing non-object-oriented, non-sealed-class tricks that JS allows that AS wouldn't in order to get performance or size. Evangelizing our transpilar is welcome. Keep in mind that Javascript is not really a 1995 thing any more. The ES5 and ES6 flavors are slowly pushing it into a more structured feel, not unlike AS2 to AS3. -Alex
Re: Converting JavaScript libraries to AS3
Hi, I think this is what our „externs“ do ... you sort of generate a no-op AS counterpart which the IDE is able to use for content assist, but the FlexJS then directly calls the JS library. But I bet the others will be able to give you more detailled infos on this. Chris Am 20.12.16, 15:34 schrieb "flex capacitor": There's a few large libraries out there that are written in JavaScript. I've been working with them and am disappointed it's not AS3 for obvious reasons. Since the community has been working on cross compiling AS3 to JS is there any work on taking a JavaScript library and parsing it into a AS3 class? I'm not talking about creating a swc that you drop in and then you have code completion in Flash Builder (I think this is externs?). I'm talking about taking a github library or source and parsing it into AS3 classes. Even if we may eventually cross compile that AS3 library back to JS I'd rather import the JS library, and then work with that AS3 version of it. Also, we as a community are catering to the JS community by converting AS3 down to JS. Can we rather convince developers to write their libraries in AS3 from now? I mean is that already possible (it's early morning here hope this makes sense)? I know we are working on frameworks like FlexJS but I'm talking about addressing the thousands of libraries written in JS. My thought on that is, along with everything else we're doing and all the progress we've made over the years, if it's already possible to convert AS3 to JS would making Flash Builder free draw JS developers to use AS3 for their libraries going forward? PS Sick and tired of catering to JS from 1995
Converting JavaScript libraries to AS3
There's a few large libraries out there that are written in JavaScript. I've been working with them and am disappointed it's not AS3 for obvious reasons. Since the community has been working on cross compiling AS3 to JS is there any work on taking a JavaScript library and parsing it into a AS3 class? I'm not talking about creating a swc that you drop in and then you have code completion in Flash Builder (I think this is externs?). I'm talking about taking a github library or source and parsing it into AS3 classes. Even if we may eventually cross compile that AS3 library back to JS I'd rather import the JS library, and then work with that AS3 version of it. Also, we as a community are catering to the JS community by converting AS3 down to JS. Can we rather convince developers to write their libraries in AS3 from now? I mean is that already possible (it's early morning here hope this makes sense)? I know we are working on frameworks like FlexJS but I'm talking about addressing the thousands of libraries written in JS. My thought on that is, along with everything else we're doing and all the progress we've made over the years, if it's already possible to convert AS3 to JS would making Flash Builder free draw JS developers to use AS3 for their libraries going forward? PS Sick and tired of catering to JS from 1995
Re: [DISCUSS] Apache Flex SDK 4.16 RC1 release
As we have been having problems like this quite regularly ... what would prevent us from forking osmf and adding that to our flex extras git repo and publishing osmf to maven-central. Shouldn’t that resolve this type of problem once and for all? Chris Am 19.12.16, 23:27 schrieb "Justin Mclean": Hi, The same download is also failing on OSX currently so it not just a windows issue. However it's not failing consistently on my 3rd try it worked. Using curl -v I notice it's doing a 302 redirect to: https://pilotfiber.dl.sourceforge.net/project/osmf.adobe/OSMF%202.0%20Release%20%28final%20source%2C%20ASDocs%2C%20pdf%20guides%20and%20release%20notes%29/OSMF.swc Perhaps using that URL would give more consistent results? Justin