Re: [FALCON] Should Falcon compile older SDKs?

On 9/17/13 9:21 PM, "Justin Mclean" wrote: >Hi, > >> Seems like the options are (at least): >> 1) The release notes say that Falcon only works with 4.11 and greater so >> 'too bad' if you try against an older SDK >> 2) Hard-code Spark as the default theme >> 3) Have Falcon report an warning if

Re: [FALCON] Should Falcon compile older SDKs?

Hi, > Seems like the options are (at least): > 1) The release notes say that Falcon only works with 4.11 and greater so > 'too bad' if you try against an older SDK > 2) Hard-code Spark as the default theme > 3) Have Falcon report an warning if no theme is found in any config file. > 4) Have Falcon

Re: [FALCON] Should Falcon compile older SDKs?

On 9/17/13 5:12 PM, "Justin Mclean" wrote: >Hi, > >> If Erik doesn't want to upgrade to 4.11, he can add a tag to >>his SDK's >> air-config.xml. Are we ok with that? >-1 to that, sorry but it's just going to confuse people. Seems like the options are (at least): 1) The release notes say that

Re: [FALCON] Should Falcon compile older SDKs?

On 9/17/13 6:50 PM, "Justin Mclean" wrote: >Hi, > >Also depending on how AIR is added to the Flex SDK, it may use the air >config file from the AIR SDK which will be missing the now required theme >line. I looked in my AIR 3.4 SDK and didn't see an air-config, so I thought the only copy was our

Re: Dynamic validation in AS

Hi, > validator.source = "{field}"; <<< Error: source attribute "{field}" can > not be of Type String [from mx.validators::Validator/set] validator.source = field;? Justin

Re: Dynamic validation in AS

On 9/18/2013 9:22 AM, Oleg Konovalov wrote: validator.source = "{field}"; <<< Error: source attribute "{field}" can shouldn't that just be validator.source=field;

Re: Dynamic validation in AS

OK, I tried the following: private function validateRequiredField(field:TextInput):void { var validator:StringValidator = new StringValidator(); validator.source = "{field}"; <<< Error: source attribute "{field}" can not be of Type String [from mx.validators::Validator/set] validator.property

Re: [FALCON] Should Falcon compile older SDKs?

Hi, Also depending on how AIR is added to the Flex SDK, it may use the air config file from the AIR SDK which will be missing the now required theme line. Justin

Re: [FALCON] Should Falcon compile older SDKs?

Hi, > If Erik doesn't want to upgrade to 4.11, he can add a tag to his SDK's > air-config.xml. Are we ok with that? -1 to that, sorry but it's just going to confuse people. > My internal customer's app specifies a long list of locales, including > en_GB. But they don't have custom resource bun

Re: Building SDK from sources and locales support

Hi, > Thank you very much, running the other.locales ant target right now.. maybe > we could drop a note about this in the README? Done. Justin

Re: Building SDK from sources and locales support

Hi, > I noticed that, in the compiled and "IDEnized" SDK, the > {sdkhome}/frameworks/locale/... folders don't contain the *_rb.swc files, > with the exception of the en_US locale. Is this the intended behavior? By default the SDK will compile for en_US. You can change this by passing -Dlocale= wh

Re: [FALCON] Should Falcon compile older SDKs?

On Sep 17, 2013 12:22 PM, "Erik de Bruin" wrote: > > >>> Erik compiles his AIR app against 4.10 with MXMLC. Works fine. Then > >>>uses > >>> Falcon and gets a bunch of errors about styles only supported in Spark > >>> theme. The root cause is that the air-config.xml in every shipping > >>> vers

Re: Scale-9 Design Tools for FXG files in Apache Flex

OK … here is the way how I solved it. Based on this tutorial [1], I have put the scaling attributes into the 2 FXG files 1) menuMiddle_upSkin.fxg and 2) menuMiddle_selectedSkin.fxg. Thereafter, I have linked the FXG files with the ToggleButton skin 3) MenuMiddleToggleButtonSkin.mxml. Unfortunate

Re: [FALCON] Should Falcon compile older SDKs?

On 9/17/13 12:38 PM, "OmPrakash Muppirala" wrote: >I am not sure what exactly the benefits are when switching to the new >Falcon compiler. Why exactly would I go through the hassle of modifying >all these? > >I think Alex mentioned a while ago that we cannot expect compile times to >improve a

RE: [FALCON] Should Falcon compile older SDKs?

> I'm assuming you have some desire to use Falcon. And right now, when you do use Falcon your app spits out those errors. Are you ok with the official answer being "upgrade from 4.10 to 4.11 and/or modify your air-config.xml"? Until it is well documented or we offer a patch, it seems acceptable

Re: [FALCON] Should Falcon compile older SDKs?

Yeah, there is an option for version hell there... On the other hand, if the libs were updated to work with Falcon, they would still work with the old compiler, if I'm not mistaken? EdB On Tue, Sep 17, 2013 at 7:00 PM, OmPrakash Muppirala wrote: > On Tue, Sep 17, 2013 at 9:30 AM, Erik de Bruin

Re: [FALCON] Should Falcon compile older SDKs?

>>> Erik compiles his AIR app against 4.10 with MXMLC. Works fine. Then >>>uses >>> Falcon and gets a bunch of errors about styles only supported in Spark >>> theme. The root cause is that the air-config.xml in every shipping >>> version of Flex doesn't have a tag and MXMLC is hard-coded to >>>

Re: [FALCON] Should Falcon compile older SDKs?

On 9/17/13 11:36 AM, "Erik de Bruin" wrote: >> Erik compiles his AIR app against 4.10 with MXMLC. Works fine. Then >>uses >> Falcon and gets a bunch of errors about styles only supported in Spark >> theme. The root cause is that the air-config.xml in every shipping >> version of Flex doesn't

Re: [FALCON] Should Falcon compile older SDKs?

> Erik compiles his AIR app against 4.10 with MXMLC. Works fine. Then uses > Falcon and gets a bunch of errors about styles only supported in Spark > theme. The root cause is that the air-config.xml in every shipping > version of Flex doesn't have a tag and MXMLC is hard-coded to > assume Spark

RE: Building SDK from sources and locales support

>From what I remember, not compiling the compiler locales created some issues >at me as my OS is French, it looked at the localized.jars but didn't find >them, so, what you can do, given you found the name of the variable is to add >it to your build.properties -> localized.jars=true -Fred

MultiBitmapSource

Hi Community, MultiBitmapSource getSource(dpi) method is called 3 times in the SDK with exactly the same code: var app:Object = FlexGlobals.topLevelApplication; var dpi:Number; if ("runtimeDPI" in app) dpi = app["runtimeDPI"];

RE: [FALCON] Should Falcon compile older SDKs?

Clarifying... I support more strict. Warnings on simple things or corrections if they are affected in our Flex SDK. Giving the end developer a choice between the compilers is a fine option. -Mark -Original Message- From: Kessler CTR Mark J [mailto:mark.kessler@usmc.mil] Sent: Tue

RE: FlexUnit License

>"He may be also able to provide a more recent version of Mockolate." This is good. FlexUnit may not be built against the latest right now as I believe there were some method signature changes, so it's possible upgrading to the latest will cause some minor library changes. I am also going to com

Re: [FALCON] Should Falcon compile older SDKs?

I think we have consensus on stricter compilation. But here are two scenarios that aren't syntax-related. Erik compiles his AIR app against 4.10 with MXMLC. Works fine. Then uses Falcon and gets a bunch of errors about styles only supported in Spark theme. The root cause is that the air-config

RE: [FALCON] Should Falcon compile older SDKs?

Well if it's overall improvement, wouldn't it be worth the time to correct the issues anyways? What is the volume we are talking about? -Mark -Original Message- From: Erik de Bruin [mailto:e...@ixsoftware.nl] Sent: Tuesday, September 17, 2013 1:41 PM To: dev@flex.apache.org Subject

Re: [FALCON] Should Falcon compile older SDKs?

I say don't worry too much about backwards compatibility, that is always a sure road to over complicating a piece of software. What I do think should happen is to make the compiler 'selectable'... So you compile with either the old one (default for some time), or the new one. That way people can ev

RE: Building SDK from sources and locales support

The locales are in and are well managed by the Maven converter / deployer, use the SDK provided by the Installer or be sure you ran ant -other.locale after a standard ant build from the sources to generate the locales. -Fred -Message d'origine- De : Cosma Colanicchia [mailto:cosma...@gm

Re: [FALCON] Should Falcon compile older SDKs?

On Tue, Sep 17, 2013 at 9:30 AM, Erik de Bruin wrote: > I say don't worry too much about backwards compatibility, that is > always a sure road to over complicating a piece of software. What I do > think should happen is to make the compiler 'selectable'... So you > compile with either the old one

RE: Building SDK from sources and locales support

Well, I'm not sure to remember if I ran an ant -main or - binary-release(-noclean), so, see if it works for you. -Message d'origine- De : Frédéric THOMAS [mailto:webdoubl...@hotmail.com] Envoyé : mardi 17 septembre 2013 18:40 À : dev@flex.apache.org Objet : RE: Building SDK from sources

Re: Building SDK from sources and locales support

I'm looking at the binary-release target, trying to identify the required targets to run in order to IDEnize and mavenize an SDK from sources. - setup-binary-release (yes and no: we don't want to clean /in, but we want to set the localized.jars property to true) - main (yes) - frameworks-rsls (

RE: Building SDK from sources and locales support

Maybe yes, know as well there are many other targets, run ant -p to get them all displayed and be sure to run the IDE script you need from the sdk/ide folder, I guess as well you will need to create the compiler locales as well if you're not US but I can't remember the ant build variable to set,

Re: Building SDK from sources and locales support

Thank you very much, running the other.locales ant target right now.. maybe we could drop a note about this in the README? 2013/9/17 Frédéric THOMAS > The locales are in and are well managed by the Maven converter / deployer, > use the SDK provided by the Installer or be sure you ran ant -other

Building SDK from sources and locales support

Hi, I'm trying to build the latest SDK sources - I need to use it in Flash Builder and as mavenized artifacts. I noticed that, in the compiled and "IDEnized" SDK, the {sdkhome}/frameworks/locale/... folders don't contain the *_rb.swc files, with the exception of the en_US locale. Is this the inten

Re: Build failed in Jenkins: flex-sdk_mustella #311

> What would it take to have bad.png files stored somewhere so we don't have > to use RDP to go look (and find they are not there because the next run > has started)? Time, mostly ;-) It's no problem to set this up, we can even provide web access to Jenkins on the VM (like at builds@a.o.) and stor

Re: Build failed in Jenkins: flex-sdk_mustella #311

"Managers/StyleManager/SparkStyles/globalSelectors/GlobalStyles_mxmlOverride_tester GlobalStyles_MxmlOverride_focusColor Failed CompareBitmap(body:step 4) compare returned[object BitmapData]" Anyone have any idea why that may be failing? This is just the first run in which it fails, so nobody pan

Re: Build failed in Jenkins: flex-sdk_mustella #311

What would it take to have bad.png files stored somewhere so we don't have to use RDP to go look (and find they are not there because the next run has started)? Anyway, the focusColor test can fail is some other thing like an update warning on the machine takes focus away from the FP window. -Ale

[FALCON] Should Falcon compile older SDKs?

Falcon is catching subtle coding issues that MXMLC didn't catch like duplicate variable declarations, ambigous definitions and more. Therefore, there is a good chance that when you compile an existing app with Falcon you might have to fix some of your code. So far, I haven't seen anyone want t

Re: [Suggestion] CallOut and CalloutButton may add a modal:Boolean property.

Yes, CalloutButton. 2013/9/17 Maurice Amsellem > AFAIK, Callout already has open(owner, modal) method. > > However CalloutButton calls open(this, false), which makes it always > non-modal. > > So your suggestion is maybe only on CalloutButton ? > > Maurice > > -Message d'origine- > De :

Re: Dynamic validation in AS

Don't know if it could help, but you can check this: http://www.graniteds.org/public/docs/3.0.0/docs/reference/flex/en-US/html/graniteds.validation.html F. 2013/9/17 Oleg Konovalov > On Sep 16, 2013 7:36 PM, "Oleg Konovalov" wrote: > > > Hi, > > > > I need to validate dynamic form data in Fle

Re: Dynamic validation in AS

On Sep 16, 2013 7:36 PM, "Oleg Konovalov" wrote: > Hi, > > I need to validate dynamic form data in Flex 4.5 ADG, meaning that I don't > know column names, > order, but if the attribute is Required, than I have to make sure user > filled it in. > From all examples I have seen, validations is done

Re: FlexUnit License

"He may be also able to provide a more recent version of Mockolate." Wow, awesome! These should definitely go in the release notes when we have a chance. brought to you by the letters A, V, and I and the number 47 On Tue, Sep 17, 2013 at 11:11 AM, Justin Mclean wrote: > Hi, > > > Hamcrest look

RE: [Suggestion] CallOut and CalloutButton may add a modal:Boolean property.

AFAIK, Callout already has open(owner, modal) method. However CalloutButton calls open(this, false), which makes it always non-modal. So your suggestion is maybe only on CalloutButton ? Maurice -Message d'origine- De : Carlos Velasco [mailto:carlos.velasco.bla...@gmail.com] Envoyé : ma

[Suggestion] CallOut and CalloutButton may add a modal:Boolean property.

There are some cases where you may want your callout content to be modal; ie, not to be closed when clicking outside the callout content bounds. In that cases the component is desired to be closed programmatically or by clicking again the callout button. Adding such a property may not break the de

Re: migrating sdk

On 17/09/2013 09:32, Miguel Ferreira wrote: Without any more specification about where is the error occuring. And you are sure you have the debug player ? Do you maybe have a custom preloader or something ? Are you compiling with RSL ? If so, turn that off for now. I'd also suggest you just g

Re: Build failed in Jenkins: flex-sdk_release #184

I just sent an email to builds@a.o., they have tendency to "improve" the nodes with various tweaks. The 'release' and 'tlf' builds are also failing due to reasons that seem unconnected to changes to the code... EdB On Tue, Sep 17, 2013 at 10:26 AM, Justin Mclean wrote: > Hi, > > Anyone have an

migrating sdk

VerifyError: Error #1014: Class spark.components.supportClasses::ItemRenderer could not be found. Hi guys, I am trying to migrate a version 4.1 to 4.6 then to migrate to 4.10.The project that i am working on was also migrate from 3.5 to 4.1 some years ago so maybe can have some dirty trash from

Re: Build failed in Jenkins: flex-sdk_release #184

Hi, Anyone have any idea why fixcrlf may be failing? > BUILD FAILED > :586: The > following error occurred while executing this line: > :743: error > running fixcrlf on fil

Re: FlexUnit License

Hi, > Hamcrest looks like BSD, Mockolate looks like MIT. I spoke to Drew (developer of said libraries) and he confirmed: "Hamcrest-AS3 is BSD, same as Hamcrest for Java. Mockolate is MIT license. " He may be also able to provide a more recent version of Mockolate. Thanks, Justin