Alex Harui wrote
> Depending on how you look at it, each class is a component, or maybe only
> classes listed in manifest.xml files are components.
> You might get a directory listing or parse the manifest files.
> I've been tempted to find a way to mark or annotate classes as being
> intended for
Just an idea of how we could eventually make writing the documentation a little
easier and keep flexible regarding the used CMS.
I use Asciidoctor for writing documentation. It's the same markup you use on
Github to auto-render these nice looking sites. The good thing would be that we
can cont
If you are getting a tomcat error page, probably Jenkins is currently running a
build and had cleaned up the workspaces target directory. In that case, just
wait for the build job to finish.
Chris
Von: Christofer Dutz
Gesendet: Freitag, 9. September 2016 10:26
I’m having trouble building a test case that exhibits the problem.
Here is the stack trace though in case it’s helpful…
set (Viewport.js:124)
org.apache.flex.utils.Language.superSetter (Language.js:329)
set (ScrollingViewport.js:98)
org.apache.flex.core.UIHTMLElementWrapper.addBead (UIHTMLElement
Christofer Dutz wrote
> You can also have a look at the output it creates at [1]
Looks very promising to me!
What would be the steps to achive a FlexJS component documentation using
this technique?
Probably we have to place one of these Asciidoc files for each relevant
strand and bead?
Would the
Hi Olaf,
Asdoc integration is on my to-do list. But for this we need to port/add the
asdoc support to falcon. An alternative would be to use the old flex version,
but we would need to publish the jar(s) to Maven central somehow.
Chris
Von meinem Samsung Galaxy Smartphone gesendet.
Hi,
I'll probably have some time at the weekend so I would like to continue my
work on a little FlexJS PureMVC demo.
Are there're any news/changes on how to create an swc from the as3 source
files using FlexJS?
Thanks,
Olaf
--
View this message in context:
http://apache-flex-development.2
FWIW, I’m using PureMVC in my FlexJS application. I just copied the source
files to my project and it “just works”.
On Sep 9, 2016, at 2:12 PM, OK wrote:
> Hi,
> I'll probably have some time at the weekend so I would like to continue my
> work on a little FlexJS PureMVC demo.
> Are there're any
Harbs wrote
> FWIW, I’m using PureMVC in my FlexJS application. I just copied the source
> files to my project and it “just works”.
I'm already doing this the same way and it works for me to ;-)
I'd like to publish a simple FlexJS PureMVC demo and for this purpose it
would be nice to provide PureM
I managed to create a simple test case which exhibits the problem.
Copy the linked project to examples and build it using ant. Running the debug
in the browser will result in an error.
https://www.dropbox.com/s/n43mz7tfj1ekqfu/TestApp.zip?dl=0
On Sep 8, 2016, at 11:01 PM, Harbs wrote:
> It’s
I dug in and figured things out by trial and error recently, and I think I
ended up exactly where Alex described in regards to the completion engine.
createInvisibleCompilationUnit() is defined on FlexProject (or maybe a
superclass). This will create a compilation unit for a specific file (and
any
The last time I tried building a SWC for JS, it was a two-step process.
1) Use js/bin/compc or js/bin/asjscompc (depending on your needs) to
generate the JS files. Looking over my build script, I output the JS files
in a js/src directory so that they'd have the right directory structure to
just co
Okay, I think I have everything set up properly, and I'm ready to commit
the updated binaries to SVN. However, as a final test just to be sure, I
tried to extract the new binary and manually run ant -f installer.xml.
Unfortunately, it failed. I noticed that installer.xml still references
0.6.0, so
If we know we want a Tour de FlexJS, one plan would be to create a Git
repo for it and recruit volunteers to start migrating Tour de Flex to this
new repo. Then we'd learn what to put in our migration document as well.
Thoughts?
-Alex
On 9/9/16, 2:49 AM, "OK" wrote:
>Christofer Dutz wrote
>> Y
On 9/9/16, 9:51 AM, "Josh Tynjala" wrote:
>Okay, I think I have everything set up properly, and I'm ready to commit
>the updated binaries to SVN. However, as a final test just to be sure, I
>tried to extract the new binary and manually run ant -f installer.xml.
>Unfortunately, it failed. I noti
Okay, I'll leave installer.xml as-is. I just committed the new binaries
with the missing file restored to the dist SVN.
- Josh
On Fri, Sep 9, 2016 at 9:59 AM, Alex Harui wrote:
>
>
> On 9/9/16, 9:51 AM, "Josh Tynjala" wrote:
>
> >Okay, I think I have everything set up properly, and I'm ready t
Hopefully, there are two kinds of SWCs in FlexJS: framework SWCs and
application SWCs.
Building framework SWCs will almost always be the two-step process,
although the pattern we are using is a bit different now than what Josh
describes below. Framework SWCs are likely to have different dependenc
Hi Josh,
I updated SVN and unzipped the binary, and compared it. More seems to
have changed than I think should have. Pom.xml files are referencing
0.8.0-SNAPSHOT, for example. Maybe the ant steps I gave injected newer
stuff, not sure. Can you verify what I'm seeing in case I did something
wro
Ah, I did mess up the instructions. Instead of unzipping the old package
into "out" you have to have a new "temp" folder and unzip it into there,
and then the zip and tar targets will stick the binaries in "out".
Sorry for the bad info earlier,
-Alex
On 9/9/16, 10:46 AM, "Alex Harui" wrote:
>H
Alright, I gave it another try with the temp directory, and when I extract
the packaged binary, I see 0.7.0 in the pom.xml. I think it's good this
time.
- Josh
On Fri, Sep 9, 2016 at 10:59 AM, Alex Harui wrote:
> Ah, I did mess up the instructions. Instead of unzipping the old package
> into "o
Hmm. I'm surprised more things didn't blow up.
It should be fixed now.
-Alex
On 9/9/16, 7:21 AM, "Harbs" wrote:
>I managed to create a simple test case which exhibits the problem.
>
>Copy the linked project to examples and build it using ant. Running the
>debug in the browser will result in a
As from my perspective as Flex SDK user, current wiki is like unorganized
book. And it has info for sdk-developers and for sdk-users, which IMHO, must
be always separated.
For a start, I think docs should be on some nice named location like:
http://flex.apache.org/flexjs/docs
I would really dig d
Everything looks ok to me now. Thanks for sticking with it.
The mirrors will take up to 24 hours to propagate these changes so some
folks may not have this file if they install today.
-Alex
On 9/9/16, 11:44 AM, "Josh Tynjala" wrote:
>Alright, I gave it another try with the temp directory, and
Please comment on the draft below. We need Om or someone to publish the
npm module.
---
The Apache Flex community is pleased to announce the release of Apache
FlexJS SDK 0.7.0 and Apache Flex FalconJX Compiler 0.7.0.
Apache Flex is a highly productive, open source application framework
On Fri, Sep 9, 2016 at 1:53 PM, Alex Harui wrote:
> Please comment on the draft below. We need Om or someone to publish the
> npm module.
>
On it.
Thanks,
Om
>
> ---
>
> The Apache Flex community is pleased to announce the release of Apache
> FlexJS SDK 0.7.0 and Apache Flex FalconJX
I just pushed flexjs 0.7.0 with a tag 'next'. If someone can test it on a
Mac and give me an all clear, I can go ahead and promote the package to a
release.
Run:
*npm install flexjs@next -g *
to test flexjs 0.7.0 npm package.
Thanks,
Om
On Fri, Sep 9, 2016 at 2:31 PM, OmPrakash Muppirala
wrote
Congratulations! I hope to try it out soon.
-Alex
On 9/8/16, 10:36 PM, "Justin M. Hill" wrote:
>
>Dear Apache Flex / FlexJS community --
>
>I am pleased to report we have finally reached a balance between Apple's
>security requirements for the App Store and the needs of the Moonshine IDE
>to i
On 9/9/16, 7:08 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
wrote:
>I just pushed flexjs 0.7.0 with a tag 'next'. If someone can test it on a
>Mac and give me an all clear, I can go ahead and promote the package to a
>release.
>
>Run:
>*npm install flexjs@next -g *
>to test flexjs
On 9/9/16, 12:19 PM, "Nemi" wrote:
>As from my perspective as Flex SDK user, current wiki is like unorganized
>book. And it has info for sdk-developers and for sdk-users, which IMHO,
>must
>be always separated.
>
>For a start, I think docs should be on some nice named location like:
>http://fle
AFAIK the ant build related stuff would be different. Everything else
should match. But, I’m not 100% sure.
Although in my tests, the included apps compiled fine using the npm
installed global tools, mxmlc and asjsc.
Thanks,
Om
On Sep 9, 2016 10:01 PM, "Alex Harui" wrote:
>
>
> On 9/9/16, 7
The SWCs did not match. I think they should. Did you get the SWCs from
the CI server or some other place?
-Alex
On 9/9/16, 10:43 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
wrote:
>AFAIK the ant build related stuff would be different. Everything else
>should match. But, I’m no
On Sep 9, 2016 10:46 PM, "Alex Harui" wrote:
>
> The SWCs did not match. I think they should. Did you get the SWCs from
> the CI server or some other place?
Hmm, I thought the swcs came with the binaries? If yes, it should be
loaded from some mirror.
Did you have an earlier npm flexjs version
32 matches
Mail list logo
