Re: [FALCONJX][FLEXJS] XML handling (was Re: [FlexJS] Back port)

[Harbs]

OK. I’m up to #2. I know of a number of problems/holes in the implementation as 
it stands and there’s probably a lot of problems I’m not aware of, but I’m 
going to try to get to the point where this compiles and actually does 
something to make the problems more visible.

Maybe some other folks can even help at that point… ;-)

On Feb 8, 2016, at 11:00 AM, Harbs  wrote:

> So here’s my current plan:
> 1. Finish up the methods (minus filtering) in the next day or two.
> 2. Sync up XML with the current FlexJS folder structure and get rid of some 
> junk (like all the JXON classes).
> 3. Get this all to compile.
> 4. Figure out the whole filtering issue.
> 5. Create test cases.

Re: [FALCONJX][FLEXJS] XML handling (was Re: [FlexJS] Back port)

[Harbs]

OK. I merged and copied the new folder structure. Unfortunately I have no idea 
how to set up the compilation. I just copied the folder structure like a 
monkey, but I have no idea how it’s supposed to work.

Can someone help me set up the scripts so it can actually compile something? 
Once I understand how the compilation is supposed to work, I can continue with 
this.

Harbs

On Feb 11, 2016, at 10:56 AM, Harbs  wrote:

> OK. I’m up to #2. I know of a number of problems/holes in the implementation 
> as it stands and there’s probably a lot of problems I’m not aware of, but I’m 
> going to try to get to the point where this compiles and actually does 
> something to make the problems more visible.
> 
> Maybe some other folks can even help at that point… ;-)
> 
> On Feb 8, 2016, at 11:00 AM, Harbs  wrote:
> 
>> So here’s my current plan:
>> 1. Finish up the methods (minus filtering) in the next day or two.
>> 2. Sync up XML with the current FlexJS folder structure and get rid of some 
>> junk (like all the JXON classes).
>> 3. Get this all to compile.
>> 4. Figure out the whole filtering issue.
>> 5. Create test cases.
> 

AW: AW: Re: AW: [DISCUSS] Adopting AS3Commons

[Christofer Dutz]

Yeah ... would have liked to, but as you use your own dogfood, the loggin is 
used in the other modules, so actually it's quite essential to get the logging 
runing before we can even think to get the rest running.

Chris


Von: Christophe Herreman 
Gesendet: Donnerstag, 11. Februar 2016 11:09
An: dev@flex.apache.org
Betreff: Re: AW: Re: AW: [DISCUSS] Adopting AS3Commons

I wouldn't care too much about all the logging framework integrations. We
have no data about usage but I suspect they are not used that much, if at
all. I assume you'll get feedback from users when an integration is missing
in which case it can still be added.

- Christophe

2016-02-11 7:58 GMT+01:00 Christofer Dutz :

> But if we don't have the libs, a can't compile the optional code. We
> wouldn't require users to have them, but in order to build the lib, we
> would need them ... That's the problem.
>
> Chris
>
>
>
> Von meinem Samsung Galaxy Smartphone gesendet.
>
>
>  Ursprüngliche Nachricht 
> Von: Alex Harui 
> Datum: 10.02.2016 19:05 (GMT+01:00)
> An: dev@flex.apache.org
> Betreff: Re: AW: Re: AW: [DISCUSS] Adopting AS3Commons
>
> I haven't looked at the code in detail, but if it is possible to have all
> the logging libraries as external dependencies, it should be ok to accept
> the AS3Commons Logging project, if at least a few of them have compatible
> licenses.
>
> Let's see where the revival of this discussion takes us.  Maybe we'll
> start a vote next week.
>
> -Alex
>
> On 2/10/16, 3:54 AM, "Christofer Dutz"  wrote:
>
> >Hi Christophe,
> >
> >I already had a detailed look at as3commons and what I found out is that
> >quite some of the dependencies (especially in the logging part) come from
> >projects that seem to have been given up. At least I couldn't find a
> >single source for those libraries. I also bet that we wouldn't need to
> >keep support for all of them. I think the logging module was one that I
> >was having most trouble with.
> >
> >If we were to continue as3commons, I think we should strip out code like
> >that. I wouldn't throw it away, but sort of save it somewhere until
> >someone asks for it and reactivate the code by providing optional modules
> >for each of these frameworks.
> >
> >I would be glad to help with this after all I was happy to see that most
> >is built with Flexmojos and I only gave up on non-maven stuff ;-)
> >
> >Chris
> >
> >
> >Von: Christophe Herreman 
> >Gesendet: Mittwoch, 10. Februar 2016 10:56
> >An: dev@flex.apache.org
> >Betreff: Re: Re: AW: [DISCUSS] Adopting AS3Commons
> >
> >Hi all,
> >
> >sorry to jump in late here. I'm the original founder and one of the main
> >authors of AS3Commons and wanted to give some feedback on the things I
> >read
> >here:
> >
> >- renaming: I don't have an issue with this but not sure what the gain is
> >here, apart from a more consistent and integrated feel with the SDK (which
> >could be the most important argument). Keep in mind that most of the
> >libraries are not Flex libraries, but rather ActionScript 3 libraries,
> >hence the name of the project. Flex related code is in separate libs
> >(Async
> >and Async-Flex) for instance.
> >
> >- FZip was indeed donated by Claus Wahlers to AS3Commons.
> >
> >- The Logging library has support for many other logging libraries and
> >targets, hence the many (optional) dependencies.
> >
> >- AS3Commons grew out of Spring ActionScript (SAS). This means that SAS
> >has
> >a lot of dependencies on AS3Commons. Perhaps that is something to take
> >into
> >account if you are thinking about renaming or refactoring the packages.
> >
> >- the domain name as3commons.org (and springactionscript.org) is about to
> >expire and I'll extend it. There is currently nothing behind these
> >domains.
> >I don't have the time to put up nor maintain a site here. Any suggestions
> >what we could do here?
> >
> >regards,
> >Christophe
> >
> >2015-12-09 13:40 GMT+01:00 Dev LFM :
> >
> >> Personally I've never used as3commons, but its ok for me..
> >>
> >> I would also like to see all the experimental stuff that Ted Patrick
> >> donated that is already in the sdk but not official..
> >>
> >> 2015-12-08 10:58 GMT+00:00 Kessler CTR Mark J
> >>:
> >>
> >> > We are talking about adopting the source.  It makes sense to bring
> >>over
> >> > ActionScript utilities that people still actively use.  Even when they
> >> stop
> >> > being supported in their current site.  It helps keep the echo system
> >>a
> >> > little stronger.
> >> >
> >> >
> >> > -Mark
> >> >
> >> > -Original Message-
> >> > From: lizhi [mailto:s...@qq.com]
> >> > Sent: Tuesday, December 08, 2015 2:15 AM
> >> > To: dev@flex.apache.org
> >> > Subject: Re: AW: [DISCUSS] Adopting AS3Commons
> 

Re: [FALCONJX][FLEXJS] XML handling (was Re: [FlexJS] Back port)

[Harbs]

I’m working on toXMLString, and I need to write new lines. Is there a 
recommended way of writing new lines in a platform agnostic manner?

Re: AW: Re: AW: [DISCUSS] Adopting AS3Commons

[Christophe Herreman]

I wouldn't care too much about all the logging framework integrations. We
have no data about usage but I suspect they are not used that much, if at
all. I assume you'll get feedback from users when an integration is missing
in which case it can still be added.

- Christophe

2016-02-11 7:58 GMT+01:00 Christofer Dutz :

> But if we don't have the libs, a can't compile the optional code. We
> wouldn't require users to have them, but in order to build the lib, we
> would need them ... That's the problem.
>
> Chris
>
>
>
> Von meinem Samsung Galaxy Smartphone gesendet.
>
>
>  Ursprüngliche Nachricht 
> Von: Alex Harui 
> Datum: 10.02.2016 19:05 (GMT+01:00)
> An: dev@flex.apache.org
> Betreff: Re: AW: Re: AW: [DISCUSS] Adopting AS3Commons
>
> I haven't looked at the code in detail, but if it is possible to have all
> the logging libraries as external dependencies, it should be ok to accept
> the AS3Commons Logging project, if at least a few of them have compatible
> licenses.
>
> Let's see where the revival of this discussion takes us.  Maybe we'll
> start a vote next week.
>
> -Alex
>
> On 2/10/16, 3:54 AM, "Christofer Dutz"  wrote:
>
> >Hi Christophe,
> >
> >I already had a detailed look at as3commons and what I found out is that
> >quite some of the dependencies (especially in the logging part) come from
> >projects that seem to have been given up. At least I couldn't find a
> >single source for those libraries. I also bet that we wouldn't need to
> >keep support for all of them. I think the logging module was one that I
> >was having most trouble with.
> >
> >If we were to continue as3commons, I think we should strip out code like
> >that. I wouldn't throw it away, but sort of save it somewhere until
> >someone asks for it and reactivate the code by providing optional modules
> >for each of these frameworks.
> >
> >I would be glad to help with this after all I was happy to see that most
> >is built with Flexmojos and I only gave up on non-maven stuff ;-)
> >
> >Chris
> >
> >
> >Von: Christophe Herreman 
> >Gesendet: Mittwoch, 10. Februar 2016 10:56
> >An: dev@flex.apache.org
> >Betreff: Re: Re: AW: [DISCUSS] Adopting AS3Commons
> >
> >Hi all,
> >
> >sorry to jump in late here. I'm the original founder and one of the main
> >authors of AS3Commons and wanted to give some feedback on the things I
> >read
> >here:
> >
> >- renaming: I don't have an issue with this but not sure what the gain is
> >here, apart from a more consistent and integrated feel with the SDK (which
> >could be the most important argument). Keep in mind that most of the
> >libraries are not Flex libraries, but rather ActionScript 3 libraries,
> >hence the name of the project. Flex related code is in separate libs
> >(Async
> >and Async-Flex) for instance.
> >
> >- FZip was indeed donated by Claus Wahlers to AS3Commons.
> >
> >- The Logging library has support for many other logging libraries and
> >targets, hence the many (optional) dependencies.
> >
> >- AS3Commons grew out of Spring ActionScript (SAS). This means that SAS
> >has
> >a lot of dependencies on AS3Commons. Perhaps that is something to take
> >into
> >account if you are thinking about renaming or refactoring the packages.
> >
> >- the domain name as3commons.org (and springactionscript.org) is about to
> >expire and I'll extend it. There is currently nothing behind these
> >domains.
> >I don't have the time to put up nor maintain a site here. Any suggestions
> >what we could do here?
> >
> >regards,
> >Christophe
> >
> >2015-12-09 13:40 GMT+01:00 Dev LFM :
> >
> >> Personally I've never used as3commons, but its ok for me..
> >>
> >> I would also like to see all the experimental stuff that Ted Patrick
> >> donated that is already in the sdk but not official..
> >>
> >> 2015-12-08 10:58 GMT+00:00 Kessler CTR Mark J
> >>:
> >>
> >> > We are talking about adopting the source.  It makes sense to bring
> >>over
> >> > ActionScript utilities that people still actively use.  Even when they
> >> stop
> >> > being supported in their current site.  It helps keep the echo system
> >>a
> >> > little stronger.
> >> >
> >> >
> >> > -Mark
> >> >
> >> > -Original Message-
> >> > From: lizhi [mailto:s...@qq.com]
> >> > Sent: Tuesday, December 08, 2015 2:15 AM
> >> > To: dev@flex.apache.org
> >> > Subject: Re: AW: [DISCUSS] Adopting AS3Commons
> >> >
> >> > i thinks it is just a lib.it in the github is good.why put it to
> flex?
> >> > the flex should clear.
> >> > if the flex can not use the lib from github,should fixed,it is a bug.
> >> > why put some lib in flex?
> >> >
> >> >
> >> >
> >> > --
> >> > View this message in context:
> >> >
> >>
> >>
> http://apache-flex-development.247.n4.nabble.com/DISCUSS-Adopting-AS3
> >>Commons-tp50473p50546.html
> >> > Sent from the Apache 

Re: AW: Re: AW: [DISCUSS] Adopting AS3Commons

[Christophe Herreman]

What I meant was that the logging integrations, not the logging library
itself, can be ignored IMO. Except for the Flex logger then.

- Christophe

2016-02-11 11:29 GMT+01:00 Christofer Dutz :

> Yeah ... would have liked to, but as you use your own dogfood, the loggin
> is used in the other modules, so actually it's quite essential to get the
> logging runing before we can even think to get the rest running.
>
> Chris
>
> 
> Von: Christophe Herreman 
> Gesendet: Donnerstag, 11. Februar 2016 11:09
> An: dev@flex.apache.org
> Betreff: Re: AW: Re: AW: [DISCUSS] Adopting AS3Commons
>
> I wouldn't care too much about all the logging framework integrations. We
> have no data about usage but I suspect they are not used that much, if at
> all. I assume you'll get feedback from users when an integration is missing
> in which case it can still be added.
>
> - Christophe
>
> 2016-02-11 7:58 GMT+01:00 Christofer Dutz :
>
> > But if we don't have the libs, a can't compile the optional code. We
> > wouldn't require users to have them, but in order to build the lib, we
> > would need them ... That's the problem.
> >
> > Chris
> >
> >
> >
> > Von meinem Samsung Galaxy Smartphone gesendet.
> >
> >
> >  Ursprüngliche Nachricht 
> > Von: Alex Harui 
> > Datum: 10.02.2016 19:05 (GMT+01:00)
> > An: dev@flex.apache.org
> > Betreff: Re: AW: Re: AW: [DISCUSS] Adopting AS3Commons
> >
> > I haven't looked at the code in detail, but if it is possible to have all
> > the logging libraries as external dependencies, it should be ok to accept
> > the AS3Commons Logging project, if at least a few of them have compatible
> > licenses.
> >
> > Let's see where the revival of this discussion takes us.  Maybe we'll
> > start a vote next week.
> >
> > -Alex
> >
> > On 2/10/16, 3:54 AM, "Christofer Dutz" 
> wrote:
> >
> > >Hi Christophe,
> > >
> > >I already had a detailed look at as3commons and what I found out is that
> > >quite some of the dependencies (especially in the logging part) come
> from
> > >projects that seem to have been given up. At least I couldn't find a
> > >single source for those libraries. I also bet that we wouldn't need to
> > >keep support for all of them. I think the logging module was one that I
> > >was having most trouble with.
> > >
> > >If we were to continue as3commons, I think we should strip out code like
> > >that. I wouldn't throw it away, but sort of save it somewhere until
> > >someone asks for it and reactivate the code by providing optional
> modules
> > >for each of these frameworks.
> > >
> > >I would be glad to help with this after all I was happy to see that most
> > >is built with Flexmojos and I only gave up on non-maven stuff ;-)
> > >
> > >Chris
> > >
> > >
> > >Von: Christophe Herreman 
> > >Gesendet: Mittwoch, 10. Februar 2016 10:56
> > >An: dev@flex.apache.org
> > >Betreff: Re: Re: AW: [DISCUSS] Adopting AS3Commons
> > >
> > >Hi all,
> > >
> > >sorry to jump in late here. I'm the original founder and one of the main
> > >authors of AS3Commons and wanted to give some feedback on the things I
> > >read
> > >here:
> > >
> > >- renaming: I don't have an issue with this but not sure what the gain
> is
> > >here, apart from a more consistent and integrated feel with the SDK
> (which
> > >could be the most important argument). Keep in mind that most of the
> > >libraries are not Flex libraries, but rather ActionScript 3 libraries,
> > >hence the name of the project. Flex related code is in separate libs
> > >(Async
> > >and Async-Flex) for instance.
> > >
> > >- FZip was indeed donated by Claus Wahlers to AS3Commons.
> > >
> > >- The Logging library has support for many other logging libraries and
> > >targets, hence the many (optional) dependencies.
> > >
> > >- AS3Commons grew out of Spring ActionScript (SAS). This means that SAS
> > >has
> > >a lot of dependencies on AS3Commons. Perhaps that is something to take
> > >into
> > >account if you are thinking about renaming or refactoring the packages.
> > >
> > >- the domain name as3commons.org (and springactionscript.org) is about
> to
> > >expire and I'll extend it. There is currently nothing behind these
> > >domains.
> > >I don't have the time to put up nor maintain a site here. Any
> suggestions
> > >what we could do here?
> > >
> > >regards,
> > >Christophe
> > >
> > >2015-12-09 13:40 GMT+01:00 Dev LFM :
> > >
> > >> Personally I've never used as3commons, but its ok for me..
> > >>
> > >> I would also like to see all the experimental stuff that Ted Patrick
> > >> donated that is already in the sdk but not official..
> > >>
> > >> 2015-12-08 10:58 GMT+00:00 Kessler CTR Mark J
> > >>:
> > >>
> > >> > We are talking about adopting the source.  

Re: FlexJS Logo?

[Nicholas Kwiatkowski]

I think everything would be branded under our existing "Apache Flex" logo,
but with different text.

I have the source EPS files they gave us, so I can make that.

FlexJS does have its own portion of the new website I'm working on -- but I
don't have any text.  If you'd be willing to supply it, I can put it up
right now.

-Nick

On Thu, Feb 11, 2016 at 2:46 AM, Christofer Dutz 
wrote:

>
> Hi,
>
> I would like to start creating a few FlexJS tools. I would like to add a
> Powered by FlexJS logo to them, that links them back to our FlexJS website
> (we do have such a thing? A shiny, landing page punting out the awesomeness
> of FlexJS). Do we have such a logo? If not, could someone whip up such a
> thing?
>
> Chris
>
>
> Von meinem Samsung Galaxy Smartphone gesendet.
>

AW: FlexJS Logo?

[Christofer Dutz]

I think I'm not the right person for some Text about FlexJS ... I'm just taking 
care of the tooling. Think Alex, Om or the others would be better suited to do 
that. I was just looking for something I can add to my stuff to make people 
curious and click on the link to the FlexJS page. If the logo simply is the 
Flex-Logo, most people won't click on it, but a FlexJS logo where the JS part 
pops the eye should definitely gain some attention.

Would be great if you could whip up some logo for that :-)

Chris


Von: Nicholas Kwiatkowski 
Gesendet: Donnerstag, 11. Februar 2016 13:54
An: dev@flex.apache.org
Betreff: Re: FlexJS Logo?

I think everything would be branded under our existing "Apache Flex" logo,
but with different text.

I have the source EPS files they gave us, so I can make that.

FlexJS does have its own portion of the new website I'm working on -- but I
don't have any text.  If you'd be willing to supply it, I can put it up
right now.

-Nick

On Thu, Feb 11, 2016 at 2:46 AM, Christofer Dutz 
wrote:

>
> Hi,
>
> I would like to start creating a few FlexJS tools. I would like to add a
> Powered by FlexJS logo to them, that links them back to our FlexJS website
> (we do have such a thing? A shiny, landing page punting out the awesomeness
> of FlexJS). Do we have such a logo? If not, could someone whip up such a
> thing?
>
> Chris
>
>
> Von meinem Samsung Galaxy Smartphone gesendet.
>

Re: [FALCONJX][FLEXJS] XML handling (was Re: [FlexJS] Back port)

[Alex Harui]

IIRC, you are trying to get the build to work in a new XML folder?

In theory, you can copy any build.xml from, say Binding into the root of
XML.  Open it and search for Binding and replace with XML.

Next, copy the src/main/resources folder from Binding.  Open
compile-config.xml and search and replace Binding.

Open compile-asjs-config.xml and do the same.

If you don't have a src/main/flex/XMLClasses.as file, create one and list
the files you want to compile.  If you don't want a particular class in
the AS version of the SWC, put it in a COMPILE::AS3 block.

Open basic-manifest.xml and comment everything out.  This is the list of
components that go in MXML, but I think you are emulating classes that are
already in the fx: namespace so you shouldn't need anything.

Then running "ant" from XML should "do the right thing".

To integrate into the main build, open frameworks/build.xml, search for
Binding and clone the patterns you see.

HTH,
-Alex

On 2/11/16, 1:25 AM, "Harbs"  wrote:

>OK. I merged and copied the new folder structure. Unfortunately I have no
>idea how to set up the compilation. I just copied the folder structure
>like a monkey, but I have no idea how it’s supposed to work.
>
>Can someone help me set up the scripts so it can actually compile
>something? Once I understand how the compilation is supposed to work, I
>can continue with this.
>
>Harbs
>
>On Feb 11, 2016, at 10:56 AM, Harbs  wrote:
>
>> OK. I’m up to #2. I know of a number of problems/holes in the
>>implementation as it stands and there’s probably a lot of problems I’m
>>not aware of, but I’m going to try to get to the point where this
>>compiles and actually does something to make the problems more visible.
>> 
>> Maybe some other folks can even help at that point… ;-)
>> 
>> On Feb 8, 2016, at 11:00 AM, Harbs  wrote:
>> 
>>> So here’s my current plan:
>>> 1. Finish up the methods (minus filtering) in the next day or two.
>>> 2. Sync up XML with the current FlexJS folder structure and get rid of
>>>some junk (like all the JXON classes).
>>> 3. Get this all to compile.
>>> 4. Figure out the whole filtering issue.
>>> 5. Create test cases.
>> 
>

Re: FlexJS Logo?

[Josh Tynjala]

The Apache Flex SDK Installer loads the following image when FlexJS is
selected:

http://flex.apache.org/installer/icons/apache_flexjs_logo_text.png

- Josh

On Thu, Feb 11, 2016 at 7:44 AM, Christofer Dutz 
wrote:

> I think I'm not the right person for some Text about FlexJS ... I'm just
> taking care of the tooling. Think Alex, Om or the others would be better
> suited to do that. I was just looking for something I can add to my stuff
> to make people curious and click on the link to the FlexJS page. If the
> logo simply is the Flex-Logo, most people won't click on it, but a FlexJS
> logo where the JS part pops the eye should definitely gain some attention.
>
> Would be great if you could whip up some logo for that :-)
>
> Chris
>
> 
> Von: Nicholas Kwiatkowski 
> Gesendet: Donnerstag, 11. Februar 2016 13:54
> An: dev@flex.apache.org
> Betreff: Re: FlexJS Logo?
>
> I think everything would be branded under our existing "Apache Flex" logo,
> but with different text.
>
> I have the source EPS files they gave us, so I can make that.
>
> FlexJS does have its own portion of the new website I'm working on -- but I
> don't have any text.  If you'd be willing to supply it, I can put it up
> right now.
>
> -Nick
>
> On Thu, Feb 11, 2016 at 2:46 AM, Christofer Dutz <
> christofer.d...@c-ware.de>
> wrote:
>
> >
> > Hi,
> >
> > I would like to start creating a few FlexJS tools. I would like to add a
> > Powered by FlexJS logo to them, that links them back to our FlexJS
> website
> > (we do have such a thing? A shiny, landing page punting out the
> awesomeness
> > of FlexJS). Do we have such a logo? If not, could someone whip up such a
> > thing?
> >
> > Chris
> >
> >
> > Von meinem Samsung Galaxy Smartphone gesendet.
> >
>

Re: FlexJS Logo?

[Nicholas Kwiatkowski]

Here is a quick stab at a FlexJS logo.  I don't have the original font they
used in the logo (they said it was Calibri, which is what I used here, but
it looks like there were some embellishments to it that aren't in that
font).  Let me know your thoughts.

​

On Thu, Feb 11, 2016 at 10:44 AM, Christofer Dutz  wrote:

> I think I'm not the right person for some Text about FlexJS ... I'm just
> taking care of the tooling. Think Alex, Om or the others would be better
> suited to do that. I was just looking for something I can add to my stuff
> to make people curious and click on the link to the FlexJS page. If the
> logo simply is the Flex-Logo, most people won't click on it, but a FlexJS
> logo where the JS part pops the eye should definitely gain some attention.
>
> Would be great if you could whip up some logo for that :-)
>
> Chris
>
> 
> Von: Nicholas Kwiatkowski 
> Gesendet: Donnerstag, 11. Februar 2016 13:54
> An: dev@flex.apache.org
> Betreff: Re: FlexJS Logo?
>
> I think everything would be branded under our existing "Apache Flex" logo,
> but with different text.
>
> I have the source EPS files they gave us, so I can make that.
>
> FlexJS does have its own portion of the new website I'm working on -- but I
> don't have any text.  If you'd be willing to supply it, I can put it up
> right now.
>
> -Nick
>
> On Thu, Feb 11, 2016 at 2:46 AM, Christofer Dutz <
> christofer.d...@c-ware.de>
> wrote:
>
> >
> > Hi,
> >
> > I would like to start creating a few FlexJS tools. I would like to add a
> > Powered by FlexJS logo to them, that links them back to our FlexJS
> website
> > (we do have such a thing? A shiny, landing page punting out the
> awesomeness
> > of FlexJS). Do we have such a logo? If not, could someone whip up such a
> > thing?
> >
> > Chris
> >
> >
> > Von meinem Samsung Galaxy Smartphone gesendet.
> >
>