Thanks, Piotr.
I'm planning on structuring flex-tourjs like this:
flex-tourjs/
TourJS/ ‹ this is the source to the Tour de FlexJS project
examples/
visualComponents/
generalComponents/
alert/
bin/ ‹ the js-debug and js-release output
bin-debug/ ‹ the SWF output
src/ ‹ the usual maven-compatible FlexJS source project
structure
The examples/ folder follows the structure present in the
TourJS/src/main/resources/content.json control file. The idea is that a
build of flex-tourjs would build all of the examples and then move the
resulting modules into the TourJS/src/main/resources/content directory and
copy the example MXML file into there as well and then build TourJS
itself, making its JS and SWF directories ready to put up to a server.
I'd prefer to have the TourJS FlexJS app discover and build the tree
structure rather than code it into a control file, but that could be a
future release.
I'm presenting this concept and plan to the dev group so that anyone who
is interested in contributing examples will know the structure and maybe
present a better idea before we get too committed to this.
Let me know what you think.
Regards,
Peter Ent
Adobe Systems/Apache Flex Project
On 1/20/17, 5:26 AM, "piotrz" <[email protected]> wrote:
>Alex,
>
>I'll start work from adding Maven pom to build.:)
>
>Piotr
>
>
>
>-----
>Apache Flex PMC
>[email protected]
>--
>View this message in context:
>http://apache-flex-development.2333347.n4.nabble.com/FlexJS-Text-For-the-T
>our-tp58508p58526.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.
