Re: Compiling examples in asja

OK, thanks. I'll try to remember to add that. On 5/27/14 8:07 PM, "Darrell Loverin" wrote: >I figured out my problem. My FALCONJX_HOME was pointing to the repos >source >not the binary package. That was because I didn't know where to set it in >the binary package. In the repos source, compiler.

Re: Compiling examples in asja

I figured out my problem. My FALCONJX_HOME was pointing to the repos source not the binary package. That was because I didn't know where to set it in the binary package. In the repos source, compiler.jar was in the compiler.jx/lib/google directory. I created a 'closure-compiler' directory and moved

Re: IOS 7 and Android 4.3 Skinning

I recently found a good library of CSS Styles fpr mobile. http://goratchet.com/ Bobby On May 27, 2014, at 3:03 PM, OmPrakash Muppirala wrote: > On Mon, May 26, 2014 at 12:36 AM, Swen van Zanten wrote: > >> Hi Om, >> >> Do you have an example of what the components of android 4.x look like. >

RE: [Mustella] still failing, must fix

>I just looked at another failure (DataGroup). It also points at this set of >changes. It turns out that Sort.fields can be null if you don't have any >SortFields and only a Sort.compareFunction. It >fails on line 395. >You'll need a null check there. Thanks, that is the one I actually failed

RE: [Mustella] still failing, must fix

>- The Menu/MenuBar/Tree/DataGrid/MXItemRenderer failures are a result of the >XMLListCollection change. I looked at MXItemRenderer and it appears that the >test is expecting an updateComplete when an XML node is added to the >collection. Does this no longer happen because the parent is not no

Re: [Mustella] still failing, must fix

And in case you missed it, yesterday I found an problem with the commit for "FLEX-34078 fix callouts closing". I'm assuming we want to get all of these cleaned up before we do 4.12.2? I probably have a few days of install script work ahead of me to try to checksum downloads and handle caching in

Re: [Mustella] still failing, must fix

And finally: - The Menu/MenuBar/Tree/DataGrid/MXItemRenderer failures are a result of the XMLListCollection change. I looked at MXItemRenderer and it appears that the test is expecting an updateComplete when an XML node is added to the collection. Does this no longer happen because the parent is

Re: [Mustella] still failing, must fix

I just looked at another failure (DataGroup). It also points at this set of changes. It turns out that Sort.fields can be null if you don't have any SortFields and only a Sort.compareFunction. It fails on line 395. You'll need a null check there. On 5/27/14 1:16 PM, "Michael A. Labriola" wrote

RE: [Mustella] still failing, must fix

>You should get an arg count mismatch. By changing the (!hasFieldName) test on >Sort.as line 413 I got the expected result ("Find criteria must contain all >sort fields") Thanks. I think there may have been a bad merge on my part too as it seems the logic that was checked in is also missing an

Re: [Mustella] still failing, must fix

Hi, > FB can cache SWCs. I always close and re-open FB when changing SWCs in an > SDK. Could that somehow affect the different results you got on some > other mustella tests? Shouldn't do as those were via via the command line not from FB. justin

Re: [Mustella] still failing, must fix

FB can cache SWCs. I always close and re-open FB when changing SWCs in an SDK. Could that somehow affect the different results you got on some other mustella tests? I got failures in MXItemRenderer and DataGroup. I'm going to take a look at those now. On 5/27/14 12:58 PM, "Justin Mclean" wrote

Re: [Mustella] still failing, must fix

Hi, > Could you be linking against old SWCs? I'm definitely getting the "number > of arguments" error. Gr looks like FB cached the swcs or something (build number issue?). A clean "fixed" the issue. The app I posed below does get the wrong RTE if you use the latest develop branch so at le

Re: [Mustella] still failing, must fix

This is Justin's test case that replicates the problem in English. http://ns.adobe.com/mxml/2009"; xmlns:s="library://ns.adobe.com/flex/spark" xmlns:mx="library://ns.adobe.com/flex/mx" initialize="triggerFindConditionRTE()">

RE: [Mustella] still failing, must fix

>Mike, your thoughts on the logic? The test sets up two SortFields and a >compare function on the Sort (not the SortFields) then calls findItem. The first SortField's field name is a non-existent field. I think the old logic would see if the field existed in the data item. The new logic seems

Re: [Mustella] still failing, must fix

Could you be linking against old SWCs? I'm definitely getting the "number of arguments" error. -Alex On 5/27/14 12:38 PM, "Justin Mclean" wrote: >Hi, > >> These particular tests are setup up with a try/catch block to trap a >> different error but end up trapping this one instead. > >Sure but w

Re: [Mustella] still failing, must fix

The JA langpack tests seem to be broken my Labriola's fix for FLEX-34320. The new logic around setting the hasFieldName and hadPreviousFieldName changed and is no longer trigging the expected error which lets the code continue and trigger this new error. Mike, your thoughts on the logic? The test

Re: [Mustella] still failing, must fix

Hi, > These particular tests are setup up with a try/catch block to trap a > different error but end up trapping this one instead. Sure but why does the stand alone code which replicates the test (posed in this thread) get the correct exception? Sort of implies there some sort of state going on

Re: [Mustella] still failing, must fix

These particular tests are setup up with a try/catch block to trap a different error but end up trapping this one instead. -Alex On 5/27/14 8:51 AM, "Justin Mclean" wrote: >Hi, > >Looking at the flash log on running the test I can see this error - not >sure why I don;t get this if I manually ru

Re: IOS 7 and Android 4.3 Skinning

On Mon, May 26, 2014 at 12:36 AM, Swen van Zanten wrote: > Hi Om, > > Do you have an example of what the components of android 4.x look like. > I don't know were to google for... :) All I get is the homescreen of > android 4. > > I would like to help you with this skinning. > I don't have any and

Re: Table cell selection

I guess if we discover that it’s a problem, we can always revert ISelectionManager and create a new interface for cell selection. But I agree that it’s highly unlikely that it’s a problem. On May 27, 2014, at 9:46 PM, Alex Harui wrote: > That's probably fine. However, consider that some folks

Re: Table cell selection

That's probably fine. However, consider that some folks are using third-party libraries that no longer have active developers so they won't always be able to fix it. Still, I will be surprised if we break anybody. -Alex On 5/27/14 9:32 AM, "Harbs" wrote: >Okay. I’m going to just implement it

RE : [FDB] Integration

Abobe still sells FB so Im not sure they really wanted to have the CLI version completely working, what Im sure instead as you may have noticed, is that it never been tested against workers. Happy to help if it can bring us complete integration in IntelliJ. Waiting for your feedback Envoyé de

Re: Table cell selection

Okay. I’m going to just implement it in ISelectionManager. On the odd chance that I do break someone’s implementation, it should be a relatively easy job to add some blank functions to honor the interface promise (assuming they don’t need the table support). On May 27, 2014, at 6:22 PM, Alex Ha

Re: [FLEXJS] Creating new TextButton in RunTime

Take a look at Application in the org.apache.flex.creatjs project. There's a note about bringing in the createJS package. Peter Ent Adobe Systems On 5/27/14 11:48 AM, "Logibérica - Paulo Esgaio" wrote: >Dear (ex?)Flexers, > >I'm having a problem while compiling a simple app that uses antipatt

Re: [FLEXJS] Creating new TextButton in RunTime

Are you trying to build a CreateJS application? Otherwise, try using org.apache.flex.html.TextButton. One of the differences in FlexJS is that there can be multiple implementations of a component. The createjs.TextButton wraps the button used in CreateJS. There is one for Jquery, hopefully othe

[FLEXJS] Creating new TextButton in RunTime

Dear (ex?)Flexers, I'm having a problem while compiling a simple app that uses antipatterns. Here's a partial sample: Error when compiling with FlexJS (FalconJX Release ) When I try to compile into JS the following error occurs: \bin\js-debug\org\apache\flex\createjs\core\UIBase.js:53: ERRO

Re: [Mustella] still failing, must fix

Hi, Looking at the flash log on running the test I can see this error - not sure why I don;t get this if I manually run the test via the code. Error #1063: Argument count mismatch on runtimeErrorTests/cmpFn(). Expected 2, got 3. Any one have a n idea why this may be the case? Thanks, Justin

Re: missing apache-flex-sdk-4-12-1 tag?

Hi, > Just so I understand. The practice is to tag some RC as the final tag? That should be the case for the SDK yes. I'm noticed in the past we've not always tagged each RC. Having the released tagged makes it clear what was released especially in TLF were it may of f tagged with the RC tags.

Re: missing apache-flex-sdk-4-12-1 tag?

Just so I understand. The practice is to tag some RC as the final tag? The RC and the "final" tag should point to the same revision? On 5/27/14 3:39 AM, "Justin Mclean" wrote: >HI, > >> There is a tag for each RC, I believe. Did I miss one? >Think so the tag for the actually release in missing

Re: Table cell selection

If someone has their own implementation of an interface, adding an API to an interface can break them. The verifier will see that not all methods are implemented. It is a trade-off. You can create an ISelectionManager2 or ITableSelectionManager to be completely safe, but the odds you will break

Re: [Mustella] still failing, must fix

Hi, > Are you sure you pulled and built Nick's XMLListCollection changes? 100% surre. On latest develop branch and have done a clean compile of everything in en_US and ja_JP. Git log shows his change and merge. (053f8619cd5647b867f04a19d9afe797eaccd58f and 89853fa181c6bd5f3b781cda88a4c9b967000

Re: [Mustella] still failing, must fix

Some tests require the full folder to be run all together. Cherry picking individual tests may not work. It shouldn't be this way, but sometimes there are other tests that affect the position of components in a subsequent test and the gradient can be slightly different and cause problems. -Alex

Re: [Installer] No more caching (at least, not in the installer)

Hi, > That might we worth doing? Any objections? No objections, but we would need to be careful in not to break the installers caching mechanism. Thanks, Justin

Re: [Installer] No more caching (at least, not in the installer)

On 5/27/14 5:59 AM, "Kessler CTR Mark J" wrote: >Would we also add timestamp property[1] sent when downloading a file to >make sure we do not grab the browser cache. That might we worth doing? Any objections? -Alex

Re: [Mustella] still failing, must fix

Are you sure you pulled and built Nick's XMLListCollection changes? On 5/27/14 5:23 AM, "Justin Mclean" wrote: >Hi, > >Also these all pass first run for me: >gumbo/components/MXItemRenderer >gumbo/core/DataGroup > >Justin >

Re: Compiling examples in asja

GOOG_HOME is for closure library, not closure compiler. It should be the absolute path to the SDK's js/lib/google/closure-library On 5/27/14 7:45 AM, "Darrell Loverin" wrote: >Should GOOG_HOME be pointing to one of those directories? > > >On Tue, May 27, 2014 at 12:32 AM, Alex Harui wrote: >

RE: Automated testing apps dev in flex ask

> I've also heard of FlexUnit, which I believe is more tuned for class > testing rather than UI interaction testing. I have heard of it being > used for UI testing, but it was tricky to setup. Just to reiterate, FlexUnit is definitely unit and some integration testing. It's not intended to do

Re: Compiling examples in asja

Should GOOG_HOME be pointing to one of those directories? On Tue, May 27, 2014 at 12:32 AM, Alex Harui wrote: > In a FlexJS SDK, the google closure compiler.jar goes in > > js/lib/google/closure-compiler/compiler.jar > > Are you sure you got your environment variables set up correctly?

Re: [FDB] Integration

Sounds awesome! Trying to support original buggy fdb from closed-source Adobe AIR SDK was a real headache for me. Now I start thinking about including your fdb into IntelliJ IDEA installation or just asking IDE users to use debugger from upcoming Apache Flex SDK. I'll play with your fdb today/t

Re: [Mustella] still failing, must fix

Hi, Running one of the Japanese tests manually with this code: http://ns.adobe.com/mxml/2009"; xmlns:s="library://ns.adobe.com/flex/spark" xmlns:mx="library://ns.adobe.com/flex/mx" initialize="triggerFindConditionRTE()">

RE: [FDB] Integration

Hi guys, Done !! see https://issues.apache.org/jira/browse/FLEX-34334 for the compiled FDB I changed completly what I did in the previous fixes to follow the original coding intention, I mean 1 BP for a file/line (or function) and 1 location per worker (swf), so, it means, 1 BP could be set f

Re: [Mustella] still failing, must fix

Hi, I can reproduce the Japanese test failures - but no sure what the issue is there. Justin

RE: [Installer] No more caching (at least, not in the installer)

Would we also add timestamp property[1] sent when downloading a file to make sure we do not grab the browser cache. [1] https://www.domain.com/filetodownload.ext?ts=1401195361932 -Mark On Tue, May 27, 2014 at 8:09 AM, Alex Harui wrote: > We're seeing lots of complaints about bad downloads du

Re: [Mustella] still failing, must fix

"We" are 99.9% sure, as there is nothing changed on the VM since May 15th, the last day all the SDK tests passed. EdB On Tue, May 27, 2014 at 2:07 PM, Justin Mclean wrote: > Hi, > > Are we 100% sure the build machine is set up correctly? > > I'm not seeingany failures on first run in: > compo

Re: [Mustella] still failing, must fix

Hi, Also these all pass first run for me: gumbo/components/MXItemRenderer gumbo/core/DataGroup Justin

Re: [Mustella] still failing, must fix

Hi, Are we 100% sure the build machine is set up correctly? I'm not seeingany failures on first run in: components/MenuBar/Halo components/Menu/Halo components/Menu/Spark components/Tree gumbo/components/ComboBox I had one failure in these which when rerun passed. gumbo/components/DataGrid gumbo

Re: No Flash Player version in Nightly build Intellij IDEA

To rebuild all indexes/caches there's File | Invalidate Caches and restart IDE. Actually this action is for troubleshooting, not for usual workflow. I guess that's not what you'd like to do on daily basis. Usually IntelliJ IDEA picks changes automatically, if it's not the case, File | Synchroniz

Re: No Flash Player version in Nightly build Intellij IDEA

Alex, In a slightly related question -- is there anyway to force IntelliJ to rebuild it's indexes / caches for a framework? I've been finding myself having to add/remove the SDK from the framework list multiple times a session if I'm trying to work on bugs in the SDK, then recompile, and then try

Re: [Mustella] still failing, must fix

Hi, I fixed the Alert test that were failing - what was odd was sometime the test passed and sometimes they failed due to sub pixel differences. New baseline images should fix that. Justin

Re: Table cell selection

Adding to an API shouldn't be a problem, as long as the new methods/properties don't change anything about the existing implementation... EdB On Tue, May 27, 2014 at 12:42 PM, Harbs wrote: > I’m working on cell selection of TLF tables. > > Cell selections does not fit into the normal index b

Table cell selection

I’m working on cell selection of TLF tables. Cell selections does not fit into the normal index based selection concept of text. To support cell selection, I need coordinate-based selection (to support rectangular selections within a table). Basically, I want to add some table-specific function

Re: [Mustella] still failing, must fix

HI, > Ok, one week later, there are 43 (!) tests failing: I'll take a look at the the two Alert tests tat are still failing. Justin

Re: missing apache-flex-sdk-4-12-1 tag?

HI, > There is a tag for each RC, I believe. Did I miss one? Think so the tag for the actually release in missing (in TLF as well). Justin

Re: No Flash Player version in Nightly build Intellij IDEA

Make sure you have [Flex SDK]/frameworks/libs/player/XX.X/playerglobal.swc file at least for one XX.X. If you change anything in Flex SDK installation (e.g. add playerglobal.swc file) then to make sure that IntelliJ IDEA noticed your changes do following: - File | Synchronize - Delete and add

Re: [Installer] No more caching (at least, not in the installer)

What EdB said ;-) Tom On 27/05/14 07:09, Alex Harui wrote: We're seeing lots of complaints about bad downloads during the install. The current caching code in the installer caches whatever gets downloaded. I'm going to introduce more MD5 checks into the install scripts and in order to make it

Re: Release build

So it is not an anomaly that only happens to me. thanks 2014-05-26 22:44 GMT+02:00 Greg Dove : > I have seen the same thing with Appstore (non-adhoc) builds working on test > devices. I *thought* this did not work in the past but yes it seems to be > "working" now, at least for the project I am

Re: Build failed in Jenkins: flex-sdk #108

This build had been stuck on the VM for 2+ days. There was a very non-descript dialog up complaining about an RTE in CS5. I've dismissed it and stopped the build. The other builds in the queue seem to pick up fine, so I'll let them run. EdB On Tue, May 27, 2014 at 9:23 AM, wrote: > See

Re: [Mustella] still failing, must fix

Ok, one week later, there are 43 (!) tests failing: http://flex-mustella.cloudapp.net/job/flex-sdk_mustella/926/consoleText If not all of the SDK committers from the past month or so take their responsibility and fix/revert, I'll start and veto the commits in reverse order, until we pass all Must