You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Alex Harui <ah...@adobe.com> on 2013/11/18 20:56:16 UTC
[FLEXJS] Overlays and SWC Refactoring
Right now, you can play with FlexJS by getting a FlexJSOverlay.zip and
following a set of instructions. The reason it is called FlexJSOVERLAY is
because it overlays a hacked up copy of framework.swc on top of the
framework.swc in a working Flex SDK.
Framework.swc is used by MXMLC when it compiles your code as you type.
Classes in framework.swc are not use in Falcon compiles your code. I
think I've now identified the set of classes that MXMLC was counting on,
and built "shim" classes for them in FlexJSUI.swc, so that we no longer
need to overlay framework.swc. The latest FlexJSOverlay.zip I just posted
no longer does the overlay and doesn't have a framework.swc at all, MXMLC
finds the shim classes in FlexJSUI.swc.
That said, FlexJSUI.swc now contains around two dozen shim classes. I now
want to separate them into their own MXMLCClasses.swc. This will require
some re-organization of classes in frameworks/as. I want to make sure
everyone is mostly checked in before I go and do this.
No longer having to hack framework.swc has one other big benefit. It
simplifies the steps to packaging so it now starts to make sense to manage
the packaging as part of an Ant script, so once I get the SWCs refactored
I'm going to create an Ant script that makes the FlexJSOverlay.zip. I'll
probably keep the name for now until after we get a true installer ready.
So, let me know if it is safe to do this refactoring.
-Alex
Re: [FLEXJS] Overlays and SWC Refactoring
Posted by Erik de Bruin <er...@ixsoftware.nl>.
>>They are actually overrides of the defaults set in the Configuration
>>class and it's super classes. Nothing special, nothing dynamic ;-)
> OK, I'll have to look into it. I'm specifically interested in how the
> -js-lib entries get set.
'sdk-js-lib' is handled in JSGoogConfiguration.
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [FLEXJS] Overlays and SWC Refactoring
Posted by Alex Harui <ah...@adobe.com>.
On 11/18/13 1:33 PM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>>>By the way, did you see my commit for the defaults for the command
>>>line arguments to FalconJx? Having those should make the launch files
>>>a bit lighter, not having to set these arguments and all.
>> No, I missed that. How does it work? FalconJX is also picking up the
>> -library-path and main mxml file from the FB config, but having a way to
>> pick up the other options would be great too.
>
>They are actually overrides of the defaults set in the Configuration
>class and it's super classes. Nothing special, nothing dynamic ;-)
OK, I'll have to look into it. I'm specifically interested in how the
-js-lib entries get set.
>
>> One thing I see coming up is that if you have a big enough project to
>>have
>> your own SWCs, once you cross-compile that SWC to a folder of JS files,
>> there is no automagic mapping of the library-path to the SWC to the
>>folder
>> of JS files for that SWC. Maybe we can guess the folder of JS files
>>from
>> certain library-path entries?
>
>You mean: how does my main project (JS version) connect to the SWC (JS
>version, compiled previously/separately)? Not sure if that's possible
>at all, as I said in a previous thread. The GCC process ALL files
>together, calculating dependencies and renaming/inlining whatever it
>finds, from all over the files. Now, there are way to 'publish' the
>API of one project/SWC (export, externs) and tell another project
>about it, but I'm not sure we'll be able to that automagically...
Yes, we will have to handle the equivalent of external libraries, but in
this case I'm asking about other libraries that get linked/compiled-in at
publish time. Consider this case: In a large app with multiple
engineers, each one is assigned a SWC to work on. Everybody's FB
workspace has each of the SWC projects and the one main app project.
Things are broken up to reduce compile time: changes to one SWC generally
don't affect the other SWCs. The main apps' compiler settings has a
-library-path entry pointing to each SWC. The SWF compiler sucks all of
the ABC code from those SWCs into the SWF. On the JS side, those SWC
engineers can run COMPCJX and get a pile of JS files. When building the
JS app, they should also get the benefits of not having to wait to
cross-compile every file from every SWC. This works today if you add
additional -js-lib arguments to point to the other piles of JS code. GCC
then compiles everything into one minified file.
So my question for this scenario was whether there would be a way to map
-library-path entries to -js-lib entries. The folks setting up their
projects have a place to put the -library-path settings (in the compiler
options), but there isn't a place (other than the launch configs) to put
additional -js-lib folders. Maybe the default output folder for the JS
code can be guessed from the -library-path settings?
-Alex
Re: [FLEXJS] Overlays and SWC Refactoring
Posted by Erik de Bruin <er...@ixsoftware.nl>.
>>By the way, did you see my commit for the defaults for the command
>>line arguments to FalconJx? Having those should make the launch files
>>a bit lighter, not having to set these arguments and all.
> No, I missed that. How does it work? FalconJX is also picking up the
> -library-path and main mxml file from the FB config, but having a way to
> pick up the other options would be great too.
They are actually overrides of the defaults set in the Configuration
class and it's super classes. Nothing special, nothing dynamic ;-)
> One thing I see coming up is that if you have a big enough project to have
> your own SWCs, once you cross-compile that SWC to a folder of JS files,
> there is no automagic mapping of the library-path to the SWC to the folder
> of JS files for that SWC. Maybe we can guess the folder of JS files from
> certain library-path entries?
You mean: how does my main project (JS version) connect to the SWC (JS
version, compiled previously/separately)? Not sure if that's possible
at all, as I said in a previous thread. The GCC process ALL files
together, calculating dependencies and renaming/inlining whatever it
finds, from all over the files. Now, there are way to 'publish' the
API of one project/SWC (export, externs) and tell another project
about it, but I'm not sure we'll be able to that automagically...
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [FLEXJS] Overlays and SWC Refactoring
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Wed, Nov 20, 2013 at 1:54 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
> Well, we keep the honorary major version 4 and do the actual numbering
> with the minor version and the build number. We start with 4.0.1 for
> alpha 1 and work our way up to 4.1.0 for the first release.
>
>
I like this but I would prefer it to start from 5. Flex 4.1.0 is already a
thing. Whereas if we message things correctly, Flex 5.1.0 and FlexJS 5.1.0
can co-exist without too much confusion.
Thanks,
Om
> EdB
>
>
>
> On Wed, Nov 20, 2013 at 10:10 PM, Alex Harui <ah...@adobe.com> wrote:
> >
> >
> > On 11/20/13 12:43 PM, "OmPrakash Muppirala" <bi...@gmail.com>
> wrote:
> >
> >>On Nov 19, 2013 12:51 PM, "Alex Harui" <ah...@adobe.com> wrote:
> >>>
> >>>
> >>>
> >>> On 11/18/13 12:19 PM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
> >>>
> >>> >I'm clear. Sounds awesome! Let me know when the ant script is done,
> >>> >I'll work it into a Jenkins job so we get a fresh overlay for each
> >>> >commit to either Falcon(Jx) or FlexJS. Another advantage, besides
> >>> >being always up to date, is that this way there will be a fixed URL
> >>> >pointing to the latest and greatest overlay.
> >>> I checked in enough ant stuff to make the 'ant release' binary package
> >>>be
> >>> equivalent to the FlexJSOverlay.
> >>>
> >>> Doing so exposed a couple of things:
> >>> 1) FB won't accept an SDK if its version number in
> >>> flex-sdk-description.xml is less than 4. So, I think FlexJS may have
> to
> >>> start with version 4.0.0.
> >>
> >>That's interesting. How about the other IDEs? Should we reach out to
> >>them?
> > Feel free to do so. I keep hoping the IntelliJ folks would jump in.
> >>
> >>If we have to go this route, we could probably start it with 5.0. That
> >>would have a nice ring to it.
> > I guess, but my main concern is that the first release should be a 0.x to
> > make it more clear that this is new stuff. The title in the description
> > can say anything, just the version tag matters, AFAICT.
> >
> > -Alex
> >
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>
Re: [FLEXJS] Overlays and SWC Refactoring
Posted by Erik de Bruin <er...@ixsoftware.nl>.
Well, we keep the honorary major version 4 and do the actual numbering
with the minor version and the build number. We start with 4.0.1 for
alpha 1 and work our way up to 4.1.0 for the first release.
EdB
On Wed, Nov 20, 2013 at 10:10 PM, Alex Harui <ah...@adobe.com> wrote:
>
>
> On 11/20/13 12:43 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>
>>On Nov 19, 2013 12:51 PM, "Alex Harui" <ah...@adobe.com> wrote:
>>>
>>>
>>>
>>> On 11/18/13 12:19 PM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>>>
>>> >I'm clear. Sounds awesome! Let me know when the ant script is done,
>>> >I'll work it into a Jenkins job so we get a fresh overlay for each
>>> >commit to either Falcon(Jx) or FlexJS. Another advantage, besides
>>> >being always up to date, is that this way there will be a fixed URL
>>> >pointing to the latest and greatest overlay.
>>> I checked in enough ant stuff to make the 'ant release' binary package
>>>be
>>> equivalent to the FlexJSOverlay.
>>>
>>> Doing so exposed a couple of things:
>>> 1) FB won't accept an SDK if its version number in
>>> flex-sdk-description.xml is less than 4. So, I think FlexJS may have to
>>> start with version 4.0.0.
>>
>>That's interesting. How about the other IDEs? Should we reach out to
>>them?
> Feel free to do so. I keep hoping the IntelliJ folks would jump in.
>>
>>If we have to go this route, we could probably start it with 5.0. That
>>would have a nice ring to it.
> I guess, but my main concern is that the first release should be a 0.x to
> make it more clear that this is new stuff. The title in the description
> can say anything, just the version tag matters, AFAICT.
>
> -Alex
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [FLEXJS] Overlays and SWC Refactoring
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Hi Alexander,
I update the ticket to reflect what I think it's the basic set of tools.
Mainly:
* Create a FlexJS Project
* Add a FlexJS SDK
* Compile files in the project with the selected SDK
* Get the output in some selected folder
* Have a "Run App" for this kind of app that would let the developer to
select what kind of output (SWF, JS-HTML, JS-HTML5, JS-CREATEJS,
JS-JQUERY,...) and launch the output in a browser.
Hope this list is what you are referring to.
Best
Carlos
2013/11/25 Alexander Doroshko <al...@jetbrains.com>
> I could file such a request myself :)
>
> I'd appreciate if somebody could add detailed instructions on what needs
> to be done at IDE side.
>
>
> On 25.11.2013 15:15, Carlos Rovira wrote:
>
>> Ok! :)
>>
>> just created it: http://youtrack.jetbrains.com/issue/IDEA-116986
>>
>> Please feel free to add, modify with whatever info you guys need to make
>> it
>> a valid feature request.
>>
>> Thanks Alexander!
>>
>> Carlos
>>
>>
>>
>> 2013/11/25 Alexander Doroshko <al...@jetbrains.com>
>>
>> I wrote "just file a feature request", not "I've just filed feature
>>> request" :)
>>>
>>>
>>> On 25.11.2013 14:15, Carlos Rovira wrote:
>>>
>>> Thanks to you Alexander,
>>>>
>>>> If IntelliJ will support FlexJS, It will bring many people to the new
>>>> technology and things would evolve more quickly. If you need some help
>>>> in
>>>> trying/testing, let me know to help you.
>>>>
>>>> Please, could you share the permalink to the feature request you filled?
>>>>
>>>> Thanks,
>>>>
>>>> Carlos
>>>>
>>>>
>>>> 2013/11/25 Alexander Doroshko <al...@jetbrains.com>
>>>>
>>>> On 21.11.2013 1:10, Alex Harui wrote:
>>>>
>>>>> I keep hoping the IntelliJ folks would jump in.
>>>>>
>>>>>> Sure, just file a feature request at http://youtrack.jetbrains.com/
>>>>>>
>>>>> issues/IDEA with instructions what we need to do.
>>>>>
>>>>> Alexander
>>>>>
>>>>>
>>>>>
>>>>
>>
>
--
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F: +34 912 94 80 80
http://www.codeoscopic.com
http://www.directwriter.es
http://www.avant2.es
Re: [FLEXJS] Overlays and SWC Refactoring
Posted by Alexander Doroshko <al...@jetbrains.com>.
I could file such a request myself :)
I'd appreciate if somebody could add detailed instructions on what needs
to be done at IDE side.
On 25.11.2013 15:15, Carlos Rovira wrote:
> Ok! :)
>
> just created it: http://youtrack.jetbrains.com/issue/IDEA-116986
>
> Please feel free to add, modify with whatever info you guys need to make it
> a valid feature request.
>
> Thanks Alexander!
>
> Carlos
>
>
>
> 2013/11/25 Alexander Doroshko <al...@jetbrains.com>
>
>> I wrote "just file a feature request", not "I've just filed feature
>> request" :)
>>
>>
>> On 25.11.2013 14:15, Carlos Rovira wrote:
>>
>>> Thanks to you Alexander,
>>>
>>> If IntelliJ will support FlexJS, It will bring many people to the new
>>> technology and things would evolve more quickly. If you need some help in
>>> trying/testing, let me know to help you.
>>>
>>> Please, could you share the permalink to the feature request you filled?
>>>
>>> Thanks,
>>>
>>> Carlos
>>>
>>>
>>> 2013/11/25 Alexander Doroshko <al...@jetbrains.com>
>>>
>>> On 21.11.2013 1:10, Alex Harui wrote:
>>>> I keep hoping the IntelliJ folks would jump in.
>>>>> Sure, just file a feature request at http://youtrack.jetbrains.com/
>>>> issues/IDEA with instructions what we need to do.
>>>>
>>>> Alexander
>>>>
>>>>
>>>
>
Re: [FLEXJS] Overlays and SWC Refactoring
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Ok! :)
just created it: http://youtrack.jetbrains.com/issue/IDEA-116986
Please feel free to add, modify with whatever info you guys need to make it
a valid feature request.
Thanks Alexander!
Carlos
2013/11/25 Alexander Doroshko <al...@jetbrains.com>
> I wrote "just file a feature request", not "I've just filed feature
> request" :)
>
>
> On 25.11.2013 14:15, Carlos Rovira wrote:
>
>> Thanks to you Alexander,
>>
>> If IntelliJ will support FlexJS, It will bring many people to the new
>> technology and things would evolve more quickly. If you need some help in
>> trying/testing, let me know to help you.
>>
>> Please, could you share the permalink to the feature request you filled?
>>
>> Thanks,
>>
>> Carlos
>>
>>
>> 2013/11/25 Alexander Doroshko <al...@jetbrains.com>
>>
>> On 21.11.2013 1:10, Alex Harui wrote:
>>>
>>> I keep hoping the IntelliJ folks would jump in.
>>>>
>>>> Sure, just file a feature request at http://youtrack.jetbrains.com/
>>> issues/IDEA with instructions what we need to do.
>>>
>>> Alexander
>>>
>>>
>>
>>
>
--
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F: +34 912 94 80 80
http://www.codeoscopic.com
http://www.directwriter.es
http://www.avant2.es
Re: [FLEXJS] Overlays and SWC Refactoring
Posted by Alexander Doroshko <al...@jetbrains.com>.
I wrote "just file a feature request", not "I've just filed feature
request" :)
On 25.11.2013 14:15, Carlos Rovira wrote:
> Thanks to you Alexander,
>
> If IntelliJ will support FlexJS, It will bring many people to the new
> technology and things would evolve more quickly. If you need some help in
> trying/testing, let me know to help you.
>
> Please, could you share the permalink to the feature request you filled?
>
> Thanks,
>
> Carlos
>
>
> 2013/11/25 Alexander Doroshko <al...@jetbrains.com>
>
>> On 21.11.2013 1:10, Alex Harui wrote:
>>
>>> I keep hoping the IntelliJ folks would jump in.
>>>
>> Sure, just file a feature request at http://youtrack.jetbrains.com/
>> issues/IDEA with instructions what we need to do.
>>
>> Alexander
>>
>
>
Re: [FLEXJS] Overlays and SWC Refactoring
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Thanks to you Alexander,
If IntelliJ will support FlexJS, It will bring many people to the new
technology and things would evolve more quickly. If you need some help in
trying/testing, let me know to help you.
Please, could you share the permalink to the feature request you filled?
Thanks,
Carlos
2013/11/25 Alexander Doroshko <al...@jetbrains.com>
> On 21.11.2013 1:10, Alex Harui wrote:
>
>> I keep hoping the IntelliJ folks would jump in.
>>
> Sure, just file a feature request at http://youtrack.jetbrains.com/
> issues/IDEA with instructions what we need to do.
>
> Alexander
>
--
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F: +34 912 94 80 80
http://www.codeoscopic.com
http://www.directwriter.es
http://www.avant2.es
Re: [FLEXJS] Overlays and SWC Refactoring
Posted by Alexander Doroshko <al...@jetbrains.com>.
On 21.11.2013 1:10, Alex Harui wrote:
> I keep hoping the IntelliJ folks would jump in.
Sure, just file a feature request at
http://youtrack.jetbrains.com/issues/IDEA with instructions what we need
to do.
Alexander
Re: [FLEXJS] Overlays and SWC Refactoring
Posted by Alex Harui <ah...@adobe.com>.
On 11/20/13 12:43 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>On Nov 19, 2013 12:51 PM, "Alex Harui" <ah...@adobe.com> wrote:
>>
>>
>>
>> On 11/18/13 12:19 PM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>>
>> >I'm clear. Sounds awesome! Let me know when the ant script is done,
>> >I'll work it into a Jenkins job so we get a fresh overlay for each
>> >commit to either Falcon(Jx) or FlexJS. Another advantage, besides
>> >being always up to date, is that this way there will be a fixed URL
>> >pointing to the latest and greatest overlay.
>> I checked in enough ant stuff to make the 'ant release' binary package
>>be
>> equivalent to the FlexJSOverlay.
>>
>> Doing so exposed a couple of things:
>> 1) FB won't accept an SDK if its version number in
>> flex-sdk-description.xml is less than 4. So, I think FlexJS may have to
>> start with version 4.0.0.
>
>That's interesting. How about the other IDEs? Should we reach out to
>them?
Feel free to do so. I keep hoping the IntelliJ folks would jump in.
>
>If we have to go this route, we could probably start it with 5.0. That
>would have a nice ring to it.
I guess, but my main concern is that the first release should be a 0.x to
make it more clear that this is new stuff. The title in the description
can say anything, just the version tag matters, AFAICT.
-Alex
Re: [FLEXJS] Overlays and SWC Refactoring
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Nov 19, 2013 12:51 PM, "Alex Harui" <ah...@adobe.com> wrote:
>
>
>
> On 11/18/13 12:19 PM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>
> >I'm clear. Sounds awesome! Let me know when the ant script is done,
> >I'll work it into a Jenkins job so we get a fresh overlay for each
> >commit to either Falcon(Jx) or FlexJS. Another advantage, besides
> >being always up to date, is that this way there will be a fixed URL
> >pointing to the latest and greatest overlay.
> I checked in enough ant stuff to make the 'ant release' binary package be
> equivalent to the FlexJSOverlay.
>
> Doing so exposed a couple of things:
> 1) FB won't accept an SDK if its version number in
> flex-sdk-description.xml is less than 4. So, I think FlexJS may have to
> start with version 4.0.0.
That's interesting. How about the other IDEs? Should we reach out to them?
If we have to go this route, we could probably start it with 5.0. That
would have a nice ring to it.
Thanks,
Om
>
> 2) A true Apache release package should more closely match the repo
> structure. So, my next task is to update the ant and other scripts so
> that the packages look more like Apache releases. I won't be moving any
> .AS or .JS files, just modifying the build.xml and .sh files. I don't
> know if that will affect any Jenkins job or not so it might be worth
> holding off until I get this fixed up.
>
> FWIW, after that, I'm going to try to integrate a port of basictests.
>
> -Alex
>
Re: [FLEXJS] Overlays and SWC Refactoring
Posted by Alex Harui <ah...@adobe.com>.
OK, I've moved the as code into a subfolder. The ant build for
FlexJSUI.swc is probably broken, but I'll be working on it and a
uber-script now. But you should be able to modify AS classes after
pulling and any further work I do should not result in a conflict.
-Alex
On 11/18/13 12:30 PM, "Alex Harui" <ah...@adobe.com> wrote:
>
>
>On 11/18/13 12:19 PM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>
>>I'm clear. Sounds awesome! Let me know when the ant script is done,
>>I'll work it into a Jenkins job so we get a fresh overlay for each
>>commit to either Falcon(Jx) or FlexJS. Another advantage, besides
>>being always up to date, is that this way there will be a fixed URL
>>pointing to the latest and greatest overlay.
>>
>>By the way, did you see my commit for the defaults for the command
>>line arguments to FalconJx? Having those should make the launch files
>>a bit lighter, not having to set these arguments and all.
>No, I missed that. How does it work? FalconJX is also picking up the
>-library-path and main mxml file from the FB config, but having a way to
>pick up the other options would be great too.
>
>One thing I see coming up is that if you have a big enough project to have
>your own SWCs, once you cross-compile that SWC to a folder of JS files,
>there is no automagic mapping of the library-path to the SWC to the folder
>of JS files for that SWC. Maybe we can guess the folder of JS files from
>certain library-path entries?
>
>-Alex
>
Re: [FLEXJS] Overlays and SWC Refactoring
Posted by Alex Harui <ah...@adobe.com>.
On 11/18/13 12:19 PM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>I'm clear. Sounds awesome! Let me know when the ant script is done,
>I'll work it into a Jenkins job so we get a fresh overlay for each
>commit to either Falcon(Jx) or FlexJS. Another advantage, besides
>being always up to date, is that this way there will be a fixed URL
>pointing to the latest and greatest overlay.
>
>By the way, did you see my commit for the defaults for the command
>line arguments to FalconJx? Having those should make the launch files
>a bit lighter, not having to set these arguments and all.
No, I missed that. How does it work? FalconJX is also picking up the
-library-path and main mxml file from the FB config, but having a way to
pick up the other options would be great too.
One thing I see coming up is that if you have a big enough project to have
your own SWCs, once you cross-compile that SWC to a folder of JS files,
there is no automagic mapping of the library-path to the SWC to the folder
of JS files for that SWC. Maybe we can guess the folder of JS files from
certain library-path entries?
-Alex
Re: [FLEXJS] Overlays and SWC Refactoring
Posted by Alex Harui <ah...@adobe.com>.
On 11/18/13 12:19 PM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>I'm clear. Sounds awesome! Let me know when the ant script is done,
>I'll work it into a Jenkins job so we get a fresh overlay for each
>commit to either Falcon(Jx) or FlexJS. Another advantage, besides
>being always up to date, is that this way there will be a fixed URL
>pointing to the latest and greatest overlay.
I checked in enough ant stuff to make the 'ant release' binary package be
equivalent to the FlexJSOverlay.
Doing so exposed a couple of things:
1) FB won't accept an SDK if its version number in
flex-sdk-description.xml is less than 4. So, I think FlexJS may have to
start with version 4.0.0.
2) A true Apache release package should more closely match the repo
structure. So, my next task is to update the ant and other scripts so
that the packages look more like Apache releases. I won't be moving any
.AS or .JS files, just modifying the build.xml and .sh files. I don't
know if that will affect any Jenkins job or not so it might be worth
holding off until I get this fixed up.
FWIW, after that, I'm going to try to integrate a port of basictests.
-Alex
Re: [FLEXJS] Overlays and SWC Refactoring
Posted by Erik de Bruin <er...@ixsoftware.nl>.
I'm clear. Sounds awesome! Let me know when the ant script is done,
I'll work it into a Jenkins job so we get a fresh overlay for each
commit to either Falcon(Jx) or FlexJS. Another advantage, besides
being always up to date, is that this way there will be a fixed URL
pointing to the latest and greatest overlay.
By the way, did you see my commit for the defaults for the command
line arguments to FalconJx? Having those should make the launch files
a bit lighter, not having to set these arguments and all.
EdB
On Mon, Nov 18, 2013 at 8:56 PM, Alex Harui <ah...@adobe.com> wrote:
> Right now, you can play with FlexJS by getting a FlexJSOverlay.zip and
> following a set of instructions. The reason it is called FlexJSOVERLAY is
> because it overlays a hacked up copy of framework.swc on top of the
> framework.swc in a working Flex SDK.
>
> Framework.swc is used by MXMLC when it compiles your code as you type.
> Classes in framework.swc are not use in Falcon compiles your code. I
> think I've now identified the set of classes that MXMLC was counting on,
> and built "shim" classes for them in FlexJSUI.swc, so that we no longer
> need to overlay framework.swc. The latest FlexJSOverlay.zip I just posted
> no longer does the overlay and doesn't have a framework.swc at all, MXMLC
> finds the shim classes in FlexJSUI.swc.
>
> That said, FlexJSUI.swc now contains around two dozen shim classes. I now
> want to separate them into their own MXMLCClasses.swc. This will require
> some re-organization of classes in frameworks/as. I want to make sure
> everyone is mostly checked in before I go and do this.
>
> No longer having to hack framework.swc has one other big benefit. It
> simplifies the steps to packaging so it now starts to make sense to manage
> the packaging as part of an Ant script, so once I get the SWCs refactored
> I'm going to create an Ant script that makes the FlexJSOverlay.zip. I'll
> probably keep the name for now until after we get a true installer ready.
>
> So, let me know if it is safe to do this refactoring.
>
> -Alex
>
>
>
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl