AW: RE : RE : Java 1.6

Well I use Flexmojos in a lot of Projects being built with Java 7, the only Thing is that the build of Flexmojos itself seems to fail because of some incompatabilities in some APIs ... I'll investigate this Problem. Chris Von: webdoublefx Gesendet: Mitt

TLF 3.0.0 Table support

Hi, Is there any way to get a simple table functioning in the current version of Flex and TLF 3.0? I know its not officially support until TLF 4.0, but there also seems to be a lot of work already done too support it and I only need basic table functionality. I've tried looking through the classe

Re: Java 1.6

Hi, > OK, I got the SDK to build with Java 7. Could somebody still using Java 6 > give it a try? Current develop branch compiles fine with 1.6 and 1.7 (for me). > Do we continue to ship binary release compiled for Java 6? Does it actually have any effect? What may make more of a difference is

Re: Java 1.6

Hi, And in the interest of future compatibility I just tried out Java 1.8. It compiles but you get a few extra warnings. [javac] warning: [options] source value 1.5 is obsolete and will be removed in a future release [javac] Note: Some input files use or override a deprecated API. Not fu

RE : Java 1.6

I drop an email last week with stack trace, can repost tomorrow if needed Envoyé depuis un mobile Samsung Message d'origine De : Justin Mclean Date :21/01/2014 23:34 (GMT+00:00) A : dev@flex.apache.org Objet : Re: Java 1.6 Hi, I been compiling with Java 1.7 for about a y

Re: Java 1.6

On 1/21/14 3:49 PM, "Justin Mclean" wrote: >Hi, > >> No, it got me when I finally upgraded my Mac. According to [1], it is >>an >> injection that you should see when you go the latest Java 7 JDK (0_51). > >Odd I'm running on a brand new laptop (OSX 10.9.1) but it installed Java >1.7.0_10. Not

Re: New Flex MaskedTextInput Spark Component

Just created the ticket: https://issues.apache.org/jira/browse/FLEX-34053 And make the first commit of this component to Apache Flex. As well fixed the copy/paste issue mentioned some days ago. Hope people can test and share now that the component is already in the sdk. I'll make some revisions

Re: Java 1.6

Hi, > No, it got me when I finally upgraded my Mac. According to [1], it is an > injection that you should see when you go the latest Java 7 JDK (0_51). Odd I'm running on a brand new laptop (OSX 10.9.1) but it installed Java 1.7.0_10. Not 100% sure of the Java version on my previous laptop but

Re: [3/3] git commit: [flex-sdk] [refs/heads/develop] - using enum as variable name caused issues in Java 7 compiler

On 1/21/14 3:44 PM, "Justin Mclean" wrote: >Hi, > >> I didn't think of them as keys. > >Really - even though they are populated by a method called keys? Really. I didn't even look at how they got populated. I was just getting rid of using a keyword as a variable name. I am sorry I did not tak

Re: Java 1.6

On 1/21/14 3:42 PM, "Justin Mclean" wrote: >Hi, > >Also I notice that it's using the "-source 1.4" option so does using Java >7 actually make any difference? Not sure either, but it wasn't compiling on Java 7 and now it will. -Alex

Re: [3/3] git commit: [flex-sdk] [refs/heads/develop] - using enum as variable name caused issues in Java 7 compiler

Hi, > I didn't think of them as keys. Really - even though they are populated by a method called keys? Enumeration enm = objs.keys(); Justin

Re: Java 1.6

On 1/21/14 3:33 PM, "Justin Mclean" wrote: >Hi, > >I been compiling with Java 1.7 for about a year on OSX and not run into >any issues. Is this a windows only issue? No, it got me when I finally upgraded my Mac. According to [1], it is an injection that you should see when you go the latest Ja

Re: Java 1.6

Hi, Also I notice that it's using the "-source 1.4" option so does using Java 7 actually make any difference? Thanks, Justin

Re: [3/3] git commit: [flex-sdk] [refs/heads/develop] - using enum as variable name caused issues in Java 7 compiler

I didn't think of them as keys. But feel free to change it if it makes you happy. On 1/21/14 3:16 PM, "Justin Mclean" wrote: >Hi, > >Not a big deal but why not use "keys" rather than "enm"? > >Justin

Re: Java 1.6

Hi, I been compiling with Java 1.7 for about a year on OSX and not run into any issues. Is this a windows only issue? When compiling velocity I see: java.home = /Library/Java/JavaVirtualMachines/jdk1.7.0_10.jdk/Contents/Home/jre The enum issues just come up as warnings not errors and it still p

Re: [3/3] git commit: [flex-sdk] [refs/heads/develop] - using enum as variable name caused issues in Java 7 compiler

Hi, Not a big deal but why not use "keys" rather than "enm"? Justin

RE : RE : Java 1.6

Im still not clear with the impact of the built sdk on application and I maybe mis understood for FM but thought it was ok to use it but not to built it only. Thanks. Envoyé depuis un mobile Samsung Message d'origine De : Carlos Rovira Date :21/01/2014 23:08 (GMT+00:00) A

Re: RE : Java 1.6

Right, people using flexmojos, java on server side and so on with Java 6 will have to migrate all to get all the system in the same version of Java. But it implies changes to flexmojos to get working with Java 7 (as Chris said). Maybe people could opt for a gradual migration and start only with fle

Re: Java 1.6

Hi Gordon, it depends on the maintenance effort, maybe get compatibility could be a huge task...or maybe maintain two branches could be harder...sincerily I don't know. I only want to point that left Java 6 and go Java 7 only route could be a problem for or user base and will make people stay in J

Re: Java 1.6

OK, I got the SDK to build with Java 7. Could somebody still using Java 6 give it a try? But the question remains: Do we continue to ship binary release compiled for Java 6? Sounds like folks want us to do that. -Alex On 1/21/14 2:34 PM, "Gordon Smith" wrote: >Carlos, suppose it turns out t

RE : Java 1.6

Velocity is the only dependency have seen which made the build failed at the moment. @Carlos, what kind of impact could it be on client applications ? I can figure out some issues for FM / IDEs which uses the built java modules but not for client app. Envoyé depuis un mobile Samsung

RE: Java 1.6

Carlos, suppose it turns out that we can't be compatible with both 6 and 7. (I hope that's not the case, but I don't think we know yet.) Are you saying we have to stick with 6? Rather than do that, we should probably instead have two branches and two builds if we can't have compatibility with bo

Re: Java 1.6

I'd like to go Java 7, but in my case we have products in Java 6 that can't be upgraded right now. I suppose that many people are in the same situation. So I think compatibility with Java 6 is a must. 2014/1/21 Gordon Smith > We should definitely fix the problems that make us incompatible with

Re: Java 1.6

Well, I'll tryŠ But there remains a logistical issue, even if this is possible which is: Currently the Jenkins builds that create the Nightly Builds are using Java 7 to build the compilers, and then you can't download and use the compilers on Java 6. This is fine from a pure Apache perspective si

RE: Java 1.6

We should definitely fix the problems that make us incompatible with Java 7, and then make that our recommended version (and switch out build systems). But staying compatible with Java 6, if that's possible, would also be a good thing. - Gordon -Original Message- From: aYo [mailto:a...

AW: Java 1.6

Gee ... this would finally make me have to fix Flexmojos, as there are currently some used libs in there, that prevent using Java 7 (For building Flexmojos ...not for using it) :-( But mabe this would be the final push I need to finally fix this ;-) Chris -Ursprüngliche Nachricht- Von:

Re: flex-sdk_mustella - Build # 657 - Fixed!

That'll take another 1.5 days to confirm, but I'd guess yes :-) EdB On Tuesday, January 21, 2014, OmPrakash Muppirala wrote: > Awesome! > > So all combinations of FP and AIR versions work fine now? > > Thanks, > Om > On Jan 21, 2014 9:57 AM, "Erik de Bruin" wrote: > > > Party! > > > > Thanks

Re: Java 1.6

The future is Java 7+, but I think we need to be 6 compatible for a while. There will be lots of teams out there that will not be pleased if there is a sudden loss of support for 6. As you know, it can be seriously disruptive On Tue 21 Jan 2014 20:35:55 WAT, Alex Harui wrote: More and more th

Java 1.6

More and more things are requiring Java 7. Java 6 standard support is over. Should we just move to Java 7 or do we need to remain Java 6 compatible? BTW, there appears to be errors when you try to get Flex to build on Java 7. I'm looking into it now. Thoughts? -Alex

Re: flex-sdk_mustella - Build # 657 - Fixed!

Awesome! So all combinations of FP and AIR versions work fine now? Thanks, Om On Jan 21, 2014 9:57 AM, "Erik de Bruin" wrote: > Party! > > Thanks everyone ;-) > > EdB > > > > On Tue, Jan 21, 2014 at 6:07 PM, wrote: > > flex-sdk_mustella - Build # 657 - Fixed: > > > > http://flex-mustella.clou

Re: flex-sdk_mustella - Build # 657 - Fixed!

Party! Thanks everyone ;-) EdB On Tue, Jan 21, 2014 at 6:07 PM, wrote: > flex-sdk_mustella - Build # 657 - Fixed: > > http://flex-mustella.cloudapp.net/job/flex-sdk_mustella/657/ > > Changes for Build #651 > [maurice.amsellem] FIXED - FLEX-34038 Mobilegrid overflow > > > Changes for Build #6

Re: Extracting XML from web service result with namespace

Try searching for "actionscript xml namespaces tutorial" From: Oleg Konovalov mailto:oleg...@gmail.com>> Date: Tuesday, January 21, 2014 6:45 AM To: aharui mailto:aha...@adobe.com>>, "dev@flex.apache.org" mailto:dev@flex.apache.org>> Subject: Re: Extracting XML from w

Re: AW: Flex at ApacheCon

Sounds good to me. I'm still pondering whether to go and propose a presentation. -Alex On 1/21/14 3:06 AM, "Christofer Dutz" wrote: >Reconcidering my last Statement ... > >As Maven, Flex, BlazeDS, FlexUnit are all Flex and Apache Technologies >(or BlazeDS will be pretty soon) ... eventually a

Re: Extracting XML from web service result with namespace

Alex, Could you please elaborate? I haven't used either of those classes and not sure which document you are referring to, which version of Flex, etc. and how to use these classes to extract useful XML from XML with namespaces. Any code samples? TIA, Oleg. On Mon, Jan 20, 2014 at 12:33 PM, Al

Re: svn commit: r4123 - in /release/flex: ./ pixelbender/ pixelbender/1.0/ pixelbender/1.0/binaries/

Good question. I have to update the main build scripts to point to this release, but I have to wait for the mirrors to propagate. I was getting 60% failures last night. -Alex On 1/21/14 12:18 AM, "Erik de Bruin" wrote: >Do we still need the artefacts from the 'flex-sdk_pixelbender' Jenkins >j

AW: Flex at ApacheCon

Reconcidering my last Statement ... As Maven, Flex, BlazeDS, FlexUnit are all Flex and Apache Technologies (or BlazeDS will be pretty soon) ... eventually a talk on bringing that all together wouldn't be that a bad idea ... what do you Think? - How to Setup the maven build for a Flex / Hybrid

AW: Flex at ApacheCon

Hi, I'm currently planning on going to the ApacheCon too ... who else from the Flex Team will be attending and what Hotels are you planning on staying? The call for papers is still open and I was thinking about submitting something, but as I always work on stuff between the Technologies (Flex +

Re: svn commit: r4123 - in /release/flex: ./ pixelbender/ pixelbender/1.0/ pixelbender/1.0/binaries/

Do we still need the artefacts from the 'flex-sdk_pixelbender' Jenkins job, or have those been replaced by this release? EdB On Mon, Jan 20, 2014 at 9:48 PM, wrote: > Author: aharui > Date: Mon Jan 20 20:48:04 2014 > New Revision: 4123 > > Log: > post pixelbender package > > Added: > rele