- Fixed and committed to develop branch last Mustella failure
(mobile/SoftKeyboard/properties/SK_StageText_Properties
SoftKeyboard_StageText_property_resizeForSoftKeyboard_false)
- fixed bug spotted by Om.
Run ALL mobile mustella tests: PASS (except locale-sensitive tests) .
It's good for me
It'll take another 10 hours or so before the Mustella VM cycles
through it's jobs and completes the mobile suite. But if it passes for
you, I expect no big issues ;-)
EdB
On Tue, Nov 19, 2013 at 9:40 AM, Maurice Amsellem
maurice.amsel...@systar.com wrote:
- Fixed and committed to develop
Hi Alex,
I have tried to write a JavaScript method using ExternalInterface to set the
focus of browser window first (As it is suggested in this forum -
http://forums.adobe.com/thread/452365), then I set the focus of textInput
control in Flex.
After this, I don't need to click manually on
Hi,
Did see my comment re new bitmaps and the issue with the y descender and
underlines? Think that need to be looked at.
Thanks,
Justin
Hi Maurice,
FLEX-33899 - Does your fix should be in current nightly builds ? I've
downloaded it today and problem is still exist.
Piotr
-
Flex/Air developer open to new job offers and challenges.
piotrzarzyck...@gmail.com
--
View this message in context:
Ok.
-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : mardi 19 novembre 2013 14:11
À : dev@flex.apache.org
Objet : Re: Mobile TextInput Implementation status
Hi,
Did see my comment re new bitmaps and the issue with the y descender and
underlines? Think
See RELEASE NOTES doc in the SDK root. The ticket should me mentioned if it's
fixed...
Maurice
-Message d'origine-
De : piotr.zarzycki [mailto:piotrzarzyck...@gmail.com]
Envoyé : mardi 19 novembre 2013 14:18
À : dev@flex.apache.org
Objet : RE: Need help on
Hi Justin,
I think you are talking about: baselines/
ActionBar_TitleDisplay_TextDecoration@android_240ppi.png, which is the only one
that turns black when crossing the descender y.
I found it weird at first sight, because StyleableStageText /
ScrollableStageText does not even have a
Also in Grid.as, line #856, you shoul have the following code:
const vsp:Number = gridMaxVSP == 0 ? 0 : (centerMaxVSP /
gridMaxVSP) * value;
(gridMaxVSP = 0 was causing a division error and NaN).
Let me know
Maurice
-Message d'origine-
De : Maurice Amsellem
Envoyé :
To be absolutely sure it was not related to TextInput, this is what I did:
In /components/ActionBar/swfs/ActionBar.mxml
I removed all the content, except:
comps:ActionBarBasic id=actionBar /
Then I did a minirun on that special test case:
./mini_run.sh -mobile
Sorry about that Maurice. Thank you. Really good job! Checked with my example
and in our application. :) Looking forrward for next release. :)
Piotr
-
Flex/Air developer open to new job offers and challenges.
piotrzarzyck...@gmail.com
--
View this message in context:
You re welcome
-Message d'origine-
De : piotr.zarzycki [mailto:piotrzarzyck...@gmail.com]
Envoyé : mardi 19 novembre 2013 15:50
À : dev@flex.apache.org
Objet : RE: Need help on https://issues.apache.org/jira/browse/FLEX-33813
(DataGrid goes blank)
Sorry about that Maurice. Thank you.
Hi,
Just wanted to let you know that the Mustella VM is a bit of a mess at
the moment, but I'm 'working hard' to get everything back online and
running smoothly again. Please give it a day or so before taking too
much notice of the failures...
EdB
--
Ix Multimedia Software
Jan Luykenstraat
On Nov 19, 2013 4:53 AM, Maurice Amsellem maurice.amsel...@systar.com
wrote:
Fixed a few other issues
(see https://issues.apache.org/jira/browse/FLEX-33166)
FIXED : Soft keyboard partially closes/opens when moving the focus
from one TI to another.
to fix the issue above, had to trigger TI
Since jenkins is down, do you need the updated swc ?
-Message d'origine-
De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de OmPrakash
Muppirala
Envoyé : mardi 19 novembre 2013 17:55
À : dev@flex.apache.org
Objet : RE: Mobile TextInput Implementation status
On Nov 19, 2013
On Nov 19, 2013 9:05 AM, Maurice Amsellem maurice.amsel...@systar.com
wrote:
Since jenkins is down, do you need the updated swc ?
Which project is it? I can just compile it and drop it in the sdk
directory.
Thanks,
Om
-Message d'origine-
De : omup...@gmail.com
On 11/19/13 2:21 AM, Devesh Mishra devesh.mis...@mastek.com wrote:
Hi Alex,
I have tried to write a JavaScript method using ExternalInterface to set
the focus of browser window first (As it is suggested in this forum -
http://forums.adobe.com/thread/452365), then I set the focus of textInput
Sure. You need mobilecomponents and mobiletheme
-Message d'origine-
De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de OmPrakash
Muppirala
Envoyé : mardi 19 novembre 2013 18:14
À : dev@flex.apache.org
Objet : RE: Mobile TextInput Implementation status
On Nov 19, 2013 9:05
Hi there,
I’m in the process of trying of rolling out Apache Flex 4.11 internally for
the other employees of my company, and I need to deploy the related
artifacts to the company Maven repo.
AFAIK, the only way to do this for 4.11 is by mavenizing/deploying a
downloaded FDK, is this right? I was
Hi Cosma, recentlly i was able to mavenize a mobile air application using
FDK 4.11 and AIR 3.9. I'll try to answer you. I hope to have understood
your questions and doubts.
Q1.: Yes, that is the way, although i had to do some tricks with package
names in flexmojos
Q2.: The mavenizer is able to
Sorry, I forgot that I was using adt-maven.plugin by yelbota and probably
was the plugin who required the zipped version of the SDK. Just try it and
let me know. In that case, maybe you should deploy SDKs versions like
3.9.win and 3.9.mac and use different profiles to build. Maybe someone has
a
Thank you very much Toni, I’ve just successfully (?) created the artifacts
locally, very straightforward so far, no need to provide a separate AIR SDK
to the mavenizer. Tomorrow I’ll try to deploy them to the m2 repo and I
will report back.
The artifact names are determined by the mavenizer
Hi Cosma,
as Toni already confirmed, the mavenizer is currently the easiest way to create
maven artifacts from a Flex SDK you downloaded using the Downloader.
The Mavenizer doesn't actually require the Air SDK, the problem was, that the
Mavenizer is able to mavenize any Flex SDK starting from
On Tue, Nov 19, 2013 at 11:47 AM, christofer.d...@c-ware.de
christofer.d...@c-ware.de wrote:
Hi Cosma,
as Toni already confirmed, the mavenizer is currently the easiest way to
create maven artifacts from a Flex SDK you downloaded using the Downloader.
The Mavenizer doesn't actually require
Hi,
I am attempting to take the DataGrid, written in ActionScript, and compile it
into JavaScript to see if that's a viable way to build JavaScript components -
or at least get a good head start on writing the JavaScript. I've run into a
couple of issues since taking the most recent falcon
Did the param fdktarget work for you, Cosma? I remember I tried to
configure that quite time ago but it didn't worked forme. I also remember
that Christofer recomended me not to use org.apache.flex package
(Flexmojos 6 was still in development). This last time I tried it, I just
changed the
Yep, those look like bugs to me.
-Alex
On 11/19/13 12:27 PM, Peter Ent p...@adobe.com wrote:
Hi,
I am attempting to take the DataGrid, written in ActionScript, and
compile it into JavaScript to see if that's a viable way to build
JavaScript components - or at least get a good head start on
Hi,
I had to install AIR itself via
http://www.ubuntubuzz.com/2012/08/how-to-install-adobe-air-on-ubuntu-1204.html
and then the .deb from our download page installs fine, as sadly it appears
Adobe are no longer publishing it in their main repository :
Yes, it worked as described in the README. What was your problem exactly? I
set the use-apache-gid parameter to false, because all of my project are
still using the old flexmojos versions
Noticed now that the README.txt does not describe the use-apache-god
parameter, that is correctly reported in
On 11/18/13 12:19 PM, Erik de Bruin e...@ixsoftware.nl wrote:
I'm clear. Sounds awesome! Let me know when the ant script is done,
I'll work it into a Jenkins job so we get a fresh overlay for each
commit to either Falcon(Jx) or FlexJS. Another advantage, besides
being always up to date, is that
I second that. I'll take a look tomorrow, if you file that JIRA ticket ;-)
EdB
On Tue, Nov 19, 2013 at 9:42 PM, Alex Harui aha...@adobe.com wrote:
Yep, those look like bugs to me.
-Alex
On 11/19/13 12:27 PM, Peter Ent p...@adobe.com wrote:
Hi,
I am attempting to take the DataGrid,
Hi Cosma,
yes you are right. The Downloader only downloads the artifacts for the current
operating-system. But for example older Adobe FDKs had the following structure:
{root}/runtimes/air
{root}/runtimes/air/android
{root}/runtimes/air/mac
{root}/runtimes/air/win
{root}/runtimes/player/10.2/
With the 7.0.0-SNAPSHOT I deployed 2 Days ago you can actually start using
org.apache.flex :-)
The Flexmojos 6 Branch requires you to have the Apache FDKs with a
com.adobe.flex groupId. So depending on the version of Flexmojos you are
intending on using, you have to either generate them as
I'll give the wiki document a workover ... stay tuned and thanks for the
feedback.
Chris
-Ursprüngliche Nachricht-
Von: Cosma Colanicchia [mailto:cosma...@gmail.com]
Gesendet: Dienstag, 19. November 2013 21:47
An: Apache Flex Developers ML
Betreff: Re: Questions about current mavenizer
Well, my problem was several months ago when I tried to use the package
org.apache.flex instead of com.adobe.flex, but it was because Flexmojos
6 was still being developed. This time I only remember I had to change the
property in the parent pom of Flexmojos to use org.apache.flex and it
worked
Thanks to you Chris, you're doing a great work.
2013/11/19 christofer.d...@c-ware.de christofer.d...@c-ware.de
I'll give the wiki document a workover ... stay tuned and thanks for the
feedback.
Chris
-Ursprüngliche Nachricht-
Von: Cosma Colanicchia [mailto:cosma...@gmail.com]
Hi,
To be absolutely sure it was not related to TextInput.
Then you need to revert the change to that single bitmap and we need to find
(and fix or revert) what checkin did cause the issue.
Thanks,
Justin
I filed two tickets for each issue.
Thanks. This is getting really close.
--peter
On 11/19/13 3:59 PM, Erik de Bruin e...@ixsoftware.nl wrote:
I second that. I'll take a look tomorrow, if you file that JIRA ticket ;-)
EdB
On Tue, Nov 19, 2013 at 9:42 PM, Alex Harui aha...@adobe.com wrote:
This is a maven problem, that I wasn't able to work myself around.
So Flexmojos 6.x uses com.apache.flex and Flexmojos 7.x uses org.apache.flex
So if you want to use Adobe FDKs you will have to stick to Flexmojos 6.x and if
you want to use the latest Apache Flex FDKs, you can use Flexmojos 6.x
Sorry ... Flexmojos 6.x uses com.adobe.flex and Flexmojos 7.x org.apache.flex
:-)
-Ursprüngliche Nachricht-
Von: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Gesendet: Dienstag, 19. November 2013 22:44
An: dev@flex.apache.org
Betreff: AW: Questions about current
Then you need to revert the change to that single bitmap and we need to find
(and fix or revert) what checkin did cause the issue.
Before of removing all the changes I made (that's a lot of work, and I am
really running out of time), I propose to set back defaults.css to use the
original
Hi,
Before of removing all the changes I made (that's a lot of work, and I am
really running out of time),
I wasn't suggesting that just the single bitmap that was checked in in error,
so we know there's still an issue. Then we try and hunt for it's cause.
Thanks,
Justin
Great work, thank you. Note about the wiki page: The actual Mavenizer
(SDKDeployer) maybe should be ... (SDKGenerator)? (If it is referred to
the related class name)
Il 19/nov/2013 22:47 christofer.d...@c-ware.de christofer.d...@c-ware.de
ha scritto:
Sorry ... Flexmojos 6.x uses com.adobe.flex
Also, there's probably a typo on url: (optional) The username used to
deploy the artifacts.
mvn: (required only if a username is provided) The password used to deploy
the artifacts
Il 19/nov/2013 23:00 Cosma Colanicchia cosma...@gmail.com ha scritto:
Great work, thank you. Note about the wiki
Thanks Chris!
Cosma, you should be able to request (on this list) for wiki access so that
you can start editing the documents yourself.
Regards,
Om
On Tue, Nov 19, 2013 at 2:02 PM, Cosma Colanicchia cosma...@gmail.comwrote:
Also, there's probably a typo on url: (optional) The username used
Justin,
I removed all my changes on my local git copy (applied revert patch), including
reverting the baseline bitmap.
Then generated the faulty test:
$ ./mini_run.sh -mobile -caseName=ActionBar_TitleDisplay_TextDecoration
tests/mobile/components/ActionBar/styles/ActionBar_Styles.mxml
As
Hi,
How is it possible to know when the test above succeeded for the last time ?
Possibly silly question but you did recompile the entire framework before
running the the tests? That's caught me out once or twice.
Maybe it was before we moved to AIR3.9/FP 11.9...
That's also a possibility.
Possibly silly question but you did recompile the entire framework before
running the the tests? That's caught me out once or twice.
Of course, how stupid I am.
I pulled all the changes from the remote develop, but didn't recompile the
framework to make them effective.
I am doing that right
Rebuilt the full SDK , and re-run the tests.
Same result...on y and underline.
So maybe AIR 3.9/FP 11.9
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : mardi 19 novembre 2013 23:36
À : dev@flex.apache.org
Objet : RE: git commit: [flex-sdk]
Ok ... so I fixed the two mistakes :-)
Thanks for reporting.
Chris
-Ursprüngliche Nachricht-
Von: Cosma Colanicchia [mailto:cosma...@gmail.com]
Gesendet: Dienstag, 19. November 2013 23:03
An: Apache Flex Developers ML
Betreff: Re: AW: Questions about current mavenizer status
Also,
Hi,
Same result...on y and underline.
Or another recent check in? You can revert the check in for that image as the
change is unrelated to your fix.
Thanks,
Justin
Or another recent check in? You can revert the check in for that image as the
change is unrelated to your fix.
Sorry I don't understand, what check in should I revert?
BTW, I would like to run the same test on SDK 4.11, so I changed sdk.dir in
local.properties.
But it complains that the SDK
I understand.
The png is the same, but the DL.xml is different, as I explained in earlier
email, it contains references to ScrollableStageText (my changes) but that are
not active (width=0 height=0).
That's why I checked in both, so that they are consistent.
So I will revert both files,
Hi,
The png is the same
The png is not the same look at it before and after in that checkin. Before the
underline is entirely white, after it is black where it crosses the y.
Github has some nice way of checking for bitmap differences.
Another possibility is that the tests in the file have side-effects. Are
you running a single test or all tests in a folder? Sometimes the other
tests in a folder affect the bitmap of a single test.
-Alex
On 11/19/13 3:15 PM, Justin Mclean jus...@classsoftware.com wrote:
Hi,
Same
On 11/19/13 4:24 PM, Maurice Amsellem maurice.amsel...@systar.com
wrote:
I am not sure of that last point.
When a baseline provides both the bitmap and the xml DL, and the bitmap
is the same, but the xml DL differs,
Will the test fail, and generate .bad for both ?
If the bitmap compares exactly
If the bitmap compares exactly the display list is not compared.
Thanks
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : mercredi 20 novembre 2013 01:43
À : dev@flex.apache.org
Objet : Re: git commit: [flex-sdk] [refs/heads/develop] - UPDATED - Tentative
FIX of
Another possibility is that the tests in the file have side-effects. Are you
running a single test or all tests in a folder? Sometimes the other tests in
a folder affect the bitmap of a single test.
I have run all the tests in mobile/ActionBar/styles, same result
-Message d'origine-
Some interesting findings:
This is what I did:
In mustella, local.properties, set
sdk.dir to point to latest SDK 4.11 GA
apollo_location=${sdk.dir}
then run again the same test.
The log says:
[echo] sdk.dir: C:/Program Files (x86)/Apache
Flex/Apache_Flex_SDK_411_GA
...
And also in SDK 4.10 GA.
So let's recap:
- running with the current SDK a standalone mobile air app that displays an
action bar with embedded font and underline = no artifact
- running current mustella test mobile/Action with current SDK = artifact is
there
- running current mustella test
60 matches
Mail list logo
