OK, I looked at the code. It occurred to me that clipping text could be
"dangerous" in that some important words at the end of the alert message
could end up not being shown to the user.
Example: "Are you sure you want to delete? This action cannot be
undone"
I would recommend adding a static f
On 5/20/14 6:31 PM, "airycanon" wrote:
>There are also others URLs which banned in China,I would like to list all
>if
>necessary.
I guess I'm trying to understand if the download site for Antlr is banned
or any download of Antlr is banned. You might be able to find it in
Maven, for example. A
There are also others URLs which banned in China,I would like to list all if
necessary.
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/problem-on-FlexJS-tp37583p37660.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
It looks like the latest Closure Compiler reports this as an error in
Google Closure Library.
Try using an older version of the Google Closure Compiler. If you are
working from the repos, remove the lib/google folder and the
compiler-latest.zip from the "in" folder and run the build with
-Dclosu
I'm getting errors when compiling the examples in asja.
First I ran 'ant' in the main directory and it built without any noticeable
errors:
compile:
[echo] running gjslint
[exec] 149 files checked, no errors found.
[echo] running jshint
Next I ran 'ant examples' to build the e
the theme is awesome
On Wed, May 21, 2014 at 7:41 AM, Alex Harui wrote:
>
>
> On 5/20/14 3:56 PM, "Frédéric THOMAS" wrote:
>
> >There is already this one, someone talked about on the list and twitter
> >recently https://github.com/akamud/FlatSpark
> The author would have to donate it to Apache
On 5/20/14 3:56 PM, "Frédéric THOMAS" wrote:
>There is already this one, someone talked about on the list and twitter
>recently https://github.com/akamud/FlatSpark
The author would have to donate it to Apache, but if folks like it, we can
ask.
-Alex
I ran the Shader filter tests. The baseline looks "ok" but with the
changes, the text is shifted down and obscured by the button. If someone
else did this same thing, they would probably notice. I'm wondering if
there is a way to retain old behavior but still fix this bug. I'm going
to look at
There is already this one, someone talked about on the list and twitter
recently https://github.com/akamud/FlatSpark
Frédéric THOMAS
> From: aha...@adobe.com
> To: dev@flex.apache.org
> Subject: [FlexJS] Designers needed for default theme
> Date: Tue, 20 May 2014 22:47:40 +
>
> Hi,
>
> So
Hi,
So far, we've been using developer "art" for FlexJS examples. Several
folks at 360|Flex agreed that it would be good to have a new theme for
FlexJS. It should not be Spark or MX revisited. If anybody has design
skills and wants to offer up a default look for a button, checkbox, radio
button
I haven't looked at your changes yet. Are you saying that if someone sets
explicit dimensions on the Alert that those dimensions may be overruled by
this change? Or only if you determine the Alert is too small? Usually,
we let folks use their explicit values for whatever reason even if we
might
Hi,
> Another related question: why did the fix, which I thought was for a
> specific overflow case, require changing other alerts?
It's just sub pixel differences if you compare the images in the Alert tests,
in these test the text is moved down a few pixels.
Justin
Hi,
> The main question should be: are any of our customers relying on the old
> behavior and will be broken by the new behavior. Sometimes, folks
> actually care about a couple of pixels.
Sure. I't not going to be common but would be possible to effect someone if
they were doing the wrong thin
On 5/20/14 2:38 PM, "OmPrakash Muppirala" wrote:
>On Tue, May 20, 2014 at 2:35 PM, Alex Harui wrote:
>
>> The main question should be: are any of our customers relying on the old
>> behavior and will be broken by the new behavior. Sometimes, folks
>> actually care about a couple of pixels.
>>
On Tue, May 20, 2014 at 2:35 PM, Alex Harui wrote:
> The main question should be: are any of our customers relying on the old
> behavior and will be broken by the new behavior. Sometimes, folks
> actually care about a couple of pixels.
>
>
I agree that it is good to be careful, but in this scena
The main question should be: are any of our customers relying on the old
behavior and will be broken by the new behavior. Sometimes, folks
actually care about a couple of pixels.
On 5/20/14 2:32 PM, "Justin Mclean" wrote:
>HI,
>
>Just to add, the height the alert box is being set to is less tha
HI,
Just to add, the height the alert box is being set to is less than the minimum
height it wants to be - removing the two lines from the tests that set the
height may be an option. After all this test isn't really a test on Alerts.
Justin
On Tue, May 20, 2014 at 2:27 PM, Justin Mclean wrote:
> Hi,
>
> >>[java]
> gumbo/filters/ShaderFilter/Integration/ShaderFilter_integration
> >> integration_popup_test1 Failed CompareBitmap(body:step 1) compare
> >> returned[object BitmapData]
> >>
> >>[java]
> gumbo/filters/ShaderFilter/I
Hi,
>>[java] gumbo/filters/ShaderFilter/Integration/ShaderFilter_integration
>> integration_popup_test1 Failed CompareBitmap(body:step 1) compare
>> returned[object BitmapData]
>>
>>[java] gumbo/filters/ShaderFilter/Integration/ShaderFilter_integration
>> integration_popup_test2 Failed C
hello
some time ago my app in ios environment with certified appstore, created an
ipa file that was installed via itunes but did not execute on a test device.
Today the same app with the same production certificates on ios7.1.1 nstall
and run the app without difference with certificates of develop
I'll try to look at Alert sometime today.
On 5/20/14 10:16 AM, "Justin Mclean" wrote:
>Hi,
>
>> [java]
>>gumbo/filters/ShaderFilter/Integration/ShaderFilter_integration
>> integration_popup_test1 Failed CompareBitmap(body:step 1) compare
>> returned[object BitmapData]
>>
>> [java]
>>
The tests can probably be fixed but I didn't want to leave mustella in a
bad state any longer. The problem is the MarshallPlan tests seem to get
stuck in a loop of running the same test over and over without advancing to
the next test. I can looking into fixing this but it may take a while. The
cur
Hi,
> [java] gumbo/filters/ShaderFilter/Integration/ShaderFilter_integration
> integration_popup_test1 Failed CompareBitmap(body:step 1) compare
> returned[object BitmapData]
>
> [java] gumbo/filters/ShaderFilter/Integration/ShaderFilter_integration
> integration_popup_test2 Failed Compa
Hi,
> The mustella-test commit was causing the failures of the StyleManager and
> MarshallPlan tests.
>
> I have reverted the changes. Sorry for the inconvenience.
Any way we can fix the tests rather than revert the changes? They did seem
useful.
Thanks,
Justin
Thanks for bringing that to our attention. Leaving the jira reference here
too for the bug.
issues.apache.org/jira/browse/FLEX-34325
On Tue, May 20, 2014 at 4:32 AM, Dominik Šotola (EXT)
wrote:
> Hi,
> please check this thread:
> http://stackoverflow.com/questions/23753885/flex-4-12-0-setfocu
Likewise, it was great to meet you too.
On Mon, May 19, 2014 at 10:19 PM, Alex Harui wrote:
> Yes, thanks for the update, and nice to meet you in person.
>
> Hopefully someone will find time to get started on a more efficient data
> class generation for Flex and FlexJS.
>
> -Alex
>
> On 5/19/14
The mustella-test commit was causing the failures of the StyleManager and
MarshallPlan tests.
I have reverted the changes. Sorry for the inconvenience.
-Darrell
On Mon, May 19, 2014 at 10:34 PM, Darrell Loverin wrote:
> I looked into the failing ShaderFilter tests:
>
> [java] ===
Hi,
please check this thread:
http://stackoverflow.com/questions/23753885/flex-4-12-0-setfocus
Thanks.
Best regards,
DS
Hi,
Welcome! Thanks !
Rgs,
Sugan Naicker
South Africa
-Original Message-
From: mark.kessler@usmc.mil [mailto:mark.kessler@usmc.mil]
Sent: 20 May 2014 12:52 PM
To: dev@flex.apache.org
Subject: RE: Please welcome Mihai Chira as the newest Apache Flex committer
Gratz and welcome
Gratz and welcome :)
-Mark
-Original Message-
From: Justin Mclean [mailto:jus...@classsoftware.com]
Sent: Monday, May 19, 2014 2:56 PM
To: dev@flex.apache.org
Subject: Please welcome Mihai Chira as the newest Apache Flex committer
Hi,
I am pleased to announce that the Project Management
Wonder if torrent would work for distribution...
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Tuesday, May 20, 2014 1:18 AM
To: dev@flex.apache.org
Subject: Re: problem on FlexJS
Is antlr banned in China? Can you get a copy some other way?
On 5/19/14 6:39 PM, "ai
Congrats Mihai!
On 20 May 2014 10:30, wrote:
> Welcome Mihai.
>
> Hope to see much more value addition in future with your presence.
>
> Tx
> AV
> Sent from BlackBerry® on Airtel
>
> -Original Message-
> From: Carlos Rovira
> Sender: carlos.rov...@gmail.com
> Date: Tue, 20 May 2014 10:
Welcome Mihai.
Hope to see much more value addition in future with your presence.
Tx
AV
Sent from BlackBerry® on Airtel
-Original Message-
From: Carlos Rovira
Sender: carlos.rov...@gmail.com
Date: Tue, 20 May 2014 10:32:01
To: dev@flex.apache.org
Reply-To: dev@flex.apache.org
Subject:
Welcome Mihai!
Great to see you joining! :)
C.
2014-05-20 9:11 GMT+02:00 Christofer Dutz :
> Hi and welcome :-)
>
> Congrats :-)
>
> Chris
>
> Von: Igor Costa
> Gesendet: Dienstag, 20. Mai 2014 04:26
> An: dev@flex.apache.org
> Betreff: Re: Please welc
On May 20, 2014 12:11 AM, "Justin Mclean" wrote:
>
> Hi,
>
> > Should we perhaps revert back to the earlier version of the Installer
while
> > we investigate this?
>
> It's not 100% certain that the old installer wasn't getting that many
failures.
Not sure if I follow. Triple negatives are confu
On 5/20/14 12:06 AM, "OmPrakash Muppirala" wrote:
>
>> >
>> >I can add the console log tracking right away if you are okay with
>> >releasing that as 3.0.1. Works?
>> Any concerns the log gets too long or is too different so it is hard to
>> track? I was going to try to add some status string
Would this URL work?.
http://search.maven.org/remotecontent?filepath=org/antlr/antlr/3.1.3/antlr-3.1.3.jar
Chris
Von: Justin Mclean
Gesendet: Dienstag, 20. Mai 2014 03:58
An: dev@flex.apache.org
Betreff: Re: problem on FlexJS
HI,
> http://antlr3.org/dow
Hi and welcome :-)
Congrats :-)
Chris
Von: Igor Costa
Gesendet: Dienstag, 20. Mai 2014 04:26
An: dev@flex.apache.org
Betreff: Re: Please welcome Mihai Chira as the newest Apache Flex committer
Welcome aboard dude.
Igor Cos
Hi,
> Should we perhaps revert back to the earlier version of the Installer while
> we investigate this?
It's not 100% certain that the old installer wasn't getting that many failures.
From what people have reported I'd assume the new installer is getting more
errors but that's just a guess. Fe
Hi,
If you want some automated tests of your entire UI instead of Flex unit tests,
I'd have a look at Selenium WebDriver.
Haven't tried it yet, I have to admit though as I'm currently using Silk4J for
that job which seems to be pretty much the same, but at the time I bought my
license webdriver
On May 19, 2014 11:59 PM, "Alex Harui" wrote:
>
>
>
> On 5/19/14 11:35 PM, "OmPrakash Muppirala" wrote:
>
> >On May 19, 2014 11:28 PM, "Alex Harui" wrote:
> >>
> >> I believe we don't know if the failure rate is lower with 2.7. It
could
> >> simply be the same, especially if folks are getting a
On 5/19/14 11:35 PM, "OmPrakash Muppirala" wrote:
>On May 19, 2014 11:28 PM, "Alex Harui" wrote:
>>
>> I believe we don't know if the failure rate is lower with 2.7. It could
>> simply be the same, especially if folks are getting as far as antlr,
>>gcc,
>> or some other third-party download b
42 matches
Mail list logo