About what to do when the installation aborts ( copied from RC6 thread)
Piotr proposes to retry when the connection is recovered (or at least have a
retry button).
I understand and agree (dixit Alex) that's way more work that we want to put in
the installer.
IMO, the problem is that it's not
Congratulations Piotr.
I am happy to see you on board :-)
Maurice
-Message d'origine-
De : Christofer Dutz [mailto:christofer.d...@c-ware.de]
Envoyé : mardi 11 mars 2014 09:22
À : dev@flex.apache.org
Objet : AW: Please welcome Piotr Zarzycki as the newest Apache Flex committer
Test results of RC7.
Summary:
Connection errors are handled correctly at early steps (resource bundles,
config files), but not during downloads ( at least not in all places).
Details below:
Windows 7, locale=FR
General:
Minor: Install Log button tool tip says Display downloaded apps, and
I think all undefined checks should use ===.
Thanks Alex for the tip, I didn't know that.
I think my code needs some review ;-)
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : mardi 11 mars 2014 08:00
À : dev@flex.apache.org
Objet : Re: ADG Bug of the
to be frequent
enough, and they are getting harder to reproduce.
Thoughts?
-Alex
On 3/11/14 2:03 AM, Maurice Amsellem maurice.amsel...@systar.com wrote:
Test results of RC7.
Summary:
Connection errors are handled correctly at early steps (resource
bundles, config files), but not during downloads
Can you right-click on the Installer, select Verbose Log and try again, then
send the log content.
Maurice
-Message d'origine-
De : nitrobear [mailto:j...@netinfluence.ch]
Envoyé : mardi 11 mars 2014 22:29
À : dev@flex.apache.org
Objet : Re: Installer for 4.12.0 on Mac
Hello,
I try
Pretty sure. I will try to reproduce it. The error handler just switches to
the directory state. That's because the installer-config.xml file was
optional. But later I changed the sdk-installer-config-4.0 so we know
whether the installer-config.xml file should be there or not and didn't
-1 (Binding)
There are still issues (see discussion thread).
I am not confident with RC6.
Maurice
-Message d'origine-
De : Nicholas Kwiatkowski [mailto:nicho...@spoon.as]
Envoyé : lundi 10 mars 2014 03:19
À : dev@flex.apache.org
Objet : Re: [VOTE] Release Apache Flex SDK Installer
I agree.
Let's take the time to fix and test installer 3.0.
And release 4.12 now.
-Message d'origine-
De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de OmPrakash
Muppirala
Envoyé : lundi 10 mars 2014 07:34
À : dev@flex.apache.org
Objet : Re: [DISCUSS] Discuss Release
Browser cache issue. It shows 4.12 for me.
So I guess others will not see the update too.
Too bad it's not plain text. The web site design really needs a review now,
but that's another concern.
Maurice
-Message d'origine-
De : Erik de Bruin [mailto:e...@ixsoftware.nl]
Envoyé :
Justin, why do we do testing on the live site. Isn't that the purpose of
staging site ?
Maurice
-Message d'origine-
De : Justin Mclean [mailto:justinmcl...@me.com]
Envoyé : lundi 10 mars 2014 08:51
À : dev@flex.apache.org
Objet : 4.12 Release
Hi,
I've just updated the XML file and
Blocker: SDK installer badge shows an error:
Internet error: The application was unable to retrieve
the configuration file.
Refreshing the page does not fix the error.
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : lundi 10 mars 2014 08
Sorry. That error (config file) was on the staging web site.
There is no such error on the live site!
So I also have my answer for the other email (why live and not staging) ;-).
Maurice
-Message d'origine-
De : Maurice Amsellem
Envoyé : lundi 10 mars 2014 09:04
À : dev
I guess the official announcement on these lists has already been made.
Maurice
-Message d'origine-
De : Kessler CTR Mark J [mailto:mark.kessler@usmc.mil]
Envoyé : lundi 10 mars 2014 11:04
À : dev@flex.apache.org
Objet : RE: Should we release 4.12?
+1 to Nick's idea.
-Mark
I just noticed Installer page link still points to an obsolete 2.7 installer.
Because it fails at the end with the message Impossble to clean up temp dir,
Installation aborted.
I thought this was fixed in 2.7.
Maurice
-Message d'origine-
De : Justin Mclean
Good point.
I think that we could extend the warning to all OS, not only Windows, where AIR
runtime cannot be installed on the development machine.
( One customer of my company does not allow AIR runtime on the dev machines
(because it's considered as unsecure), so ANT installation would be
Things getting worse:
With the installer from the link page, the downloaded osmf.swc is not the good
one (only 18KB).
I am going to clean up caches and retry to see if it's better.
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé
I cleaned up the browser cache and retried.
Now it's OK.
Last minute panic ;-)
Maurice
-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : lundi 10 mars 2014 11:58
À : dev@flex.apache.org
Objet : Re: 4.12 Release
Hi,
With the installer from the link
@flex.apache.org
Objet : Re: 4.12 Release
This link on the news feature about Flex 4.12.0 on the landing page currently
leads to a can't find this page message:
https://blogs.apache.org/flex/entry/apache_flex_4_12_0
On Mon, Mar 10, 2014 at 7:47 AM, Maurice Amsellem
maurice.amsel...@systar.com wrote
.
-Nick
On Mon, Mar 10, 2014 at 7:57 AM, Maurice Amsellem
maurice.amsel...@systar.com wrote:
Yes, sorry for that. The post is ready but not published.
This will be fixed very soon.
Until then, you can directly download 4.12, in the installer page.
Maurice
-Message d'origine-
De
Blog post should have a link to the release notes, so that you can read it
before installing ?
https://dist.apache.org/repos/dist/release/flex/4.12.0/RELEASE_NOTES
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : lundi 10 mars 2014 13:22
Thanks a lot.
-Message d'origine-
De : DarkStone [mailto:darkst...@163.com]
Envoyé : lundi 10 mars 2014 13:33
À : Apache Flex Developers
Objet : Re:[ANNOUNCE] Apache Flex 4.12.0 released
Hi all,
To spread the release of Flex 4.12, I've just posted a blog about it, which is
written in
Ah, ok this is the general Hot Blogs:flex | 793
I got confused because I though it was for all Flex blogs.
But since it's counter for today, then definitely the 4.12 release
announcement.
Thanks for the info.
-Message d'origine-
De : Justin Mclean
. I tried red, but didn't like it. Then we
don't have to localize the strings in an Alert.
Thoughts?
-Alex
On 3/10/14 12:51 AM, Maurice Amsellem maurice.amsel...@systar.com
wrote:
I agree.
Let's take the time to fix and test installer 3.0.
And release 4.12 now.
-Message d'origine
, and localization errors are fixed
during the testing, is that benefit worth all the trouble:
- UI labels empty when connection is slow
- if resource bundles are not available, we cannot even display the error.
Just wondering...
Maurice
-Message d'origine-
De : Maurice Amsellem
Envoyé
/14 10:32 AM, Maurice Amsellem maurice.amsel...@systar.com
wrote:
There is something I don't understand about the installer:
It seems that localized strings from properties directories are
dynamically loaded ( from some URL) when the Installer is started.
I understand that strings
upgrading to InstallApacheFlex
3.0
Thoughts?
-Alex
On 3/8/14 1:32 PM, Maurice Amsellem maurice.amsel...@systar.com wrote:
If Installer 3.0 piggybacks with SDK 4.12, we will have a lot of folks
with an Installer that is capable of installing FlexJS.
Then once we actually release FlexJS 1.0, it is just
Testing RC6:
Configuration: Window 7, 64bit, FR
Test #1: Install FlexJS nightly with AIR 3.9/FP11.9, installer locale=FR,
download cache enabled
Results: OK
- guava caching passes ( escaped dir is created in download cache dir
remotecontent%3Ffilepath%3Dcom).
= So previous issue in RC4
Removing the scrollbars would require to change the UI design.
Maybe it's simpler to shorten the title for Adobe embedded fonts.
Replaces :
Bibliothèques Adobe polices embarquées et utilitaires (facultatif)
By:
Support Adobe des polices embarquées Adobe (faculatif)
Same meaning, but shorter.
Couldn't reproduce Test#2 issue ( FlexJS with SDK List in Locale ES)
The only evidence I have is the screenshot :-(
So let's consider it's not reproducible for now and reopen if it happens again.
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com
This is the correct link.
https://www.dropbox.com/s/wsonydx1ju3skkk/flexJS_complist_ES.png
As I said earlier, I didn't manage to reproduce it at a later time, and the
installation was correct although the licence list was wrong.
-Message d'origine-
De : Justin Mclean
A few thoughts:
Why should we announce the installer at all?
Do other products announce release of their installers ? I don't think so.
Whatever efforts and innovation there is in it, it's only a
convenience/commodity tool.
What new functionality does Installer 3.0 bring over 2.7 , from an
the new Installer.
Along which comes the new features like FlexJS, etc.
If we release the Installer after 4.12, then we miss the chance of getting
FlexJS into existing users machines.
Thanks,
Om
On Mar 8, 2014 1:16 AM, Maurice Amsellem maurice.amsel...@systar.com
wrote:
A few thoughts:
Why should
Why the stealth release now? What do we gain from that? Someone will
inevitably blog/tweet about it and we will be in a position to explain what's
happening.
I don't see any harm in waiting for a few days to release the sdk and the
Installer together.
- I agree there is no point for a
-Message d'origine-
De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de OmPrakash
Muppirala
Envoyé : samedi 8 mars 2014 22:13
À : dev@flex.apache.org
Objet : Re: Should we release 4.12?
On Sat, Mar 8, 2014 at 12:54 PM, Maurice Amsellem
maurice.amsel...@systar.com wrote:
Why
I have tried Installer 3.0 RC4 with FlexJS Nightly / AIR 3.9 :
I have used directories without spaces, including for download cache:
SDK target: D:\ApacheFlex\FlexJS\SDK
Installer cache: D:\Temp\flex_installer_cache
Windows 7, fr
Installer stops at guava downloading step (9th square) !!
Tried 3
I did another try disabling the download cache, and the installation completes
sucessfully.
HTH.
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : vendredi 7 mars 2014 14:47
À : dev@flex.apache.org
Objet : RE: [DISCUSS] Discuss Release
.
Are you sure caching was on? Or did you turn on verbose logging late?
-Alex
On 3/7/14 5:55 AM, Maurice Amsellem maurice.amsel...@systar.com wrote:
I did another try disabling the download cache, and the installation
completes sucessfully.
HTH.
Maurice
-Message d'origine-
De
Installer 3.0 - RC4
On 3/7/14 7:41 AM, Maurice Amsellem maurice.amsel...@systar.com wrote:
Caching was on the first tests (failing)= Caching was off on the last
tests (success).
It's possible I turned verbose logging after the download started.
Do you want me to try again, with caching
I have installed FlexSK SDK nightly with the installer, and got the error
Unsupported major.minor version 51.0.
So does this mean that the SDK installed binaries require Java 7, and that we
have to build manually to use with Java 6?
Or is there a way to use the SDK with Java 6 without
: vendredi 7 mars 2014 18:14
À : dev@flex.apache.org; Erik de Bruin
Objet : Re: [FLEXJS] IDE integration discussion
Good question. What was the stack trace? Was it Google Closure that was
complaining?
On 3/7/14 8:15 AM, Maurice Amsellem maurice.amsel...@systar.com wrote:
I have installed FlexSK
like it is time for RC6!
-Alex
On 3/7/14 8:04 AM, Maurice Amsellem maurice.amsel...@systar.com wrote:
Did the same test, with caching enabled, and verbose log enabled at
startup.
frozen at the same step (guava) : the busy indicator is running, but
nothing happens, even after 5 min.
I have
be
subdirectories. That might be easier than other possible solutions.
Thoughts?
-Alex
On 3/7/14 9:21 AM, Maurice Amsellem maurice.amsel...@systar.com wrote:
Alex, I suspected that too, so I tried to manually create a directory
named:
remotecontent%3ffilepath%3dcom
And it was successfully
path is to just escape and tell folks there is a
256 char limit (after escaping). If folks need to use a longer URL, they'll
have to use a URL shortener or not turn on the cache.
Thoughts?
-Alex
On 3/7/14 9:36 AM, Maurice Amsellem maurice.amsel...@systar.com wrote:
We are not escaping
MD5 for the path is not a good idea. As you said, it makes it difficult to find
and remove files.
So escaping and warning about the limit is fine.
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : vendredi 7 mars 2014 18:58
À : dev
Om says it's SWFObject than cannot download.
Maurice
-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : jeudi 6 mars 2014 22:40
À : dev@flex.apache.org
Objet : Re: [DISCUSS] Discuss Release Apache Flex SDK Installer 3.0 - RC4
Hi,
Just retested with
, then a
second later, it moves to center of the screen. It is quite jarring an
experience.
Thanks,
Om
On Tue, Mar 4, 2014 at 8:35 PM, Alex Harui aha...@adobe.com wrote:
On 3/4/14 1:30 AM, Maurice Amsellem maurice.amsel...@systar.com wrote:
In theory, only followers of the dev list should know how view
Tested RC4:
- Flex SDK 4.11 / AIR 13beta / FP 13:
- window 7 6bit,
-Locale : FR
Minor: some late string (testing cache) are not localized...
Minor: each time you click on Install log button, it opens a new log window.
Major: the downloaded file
Here is the verbose log :
https://www.dropbox.com/s/r85h5pq57st68gq/install_log_KO.zip
I am giving it another try.
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : jeudi 6 mars 2014 23:01
À : dev@flex.apache.org
Objet : RE: [DISCUSS] Discuss
No objection here. Someone did say that the 2.7 installer did not install
4.12 properly. Has that been verified?
In the latest tests I have made with SDK 4.12 RC4 (see email [VOTE] on 3/4th),
the problem with installer 2.7 disappeared, which means 4.12 installs
correctly with installer
.
Is that possible?
In that case the installation should have raised an error (eg. locked file)
instead of being stuck?
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : jeudi 6 mars 2014 23:07
À : dev@flex.apache.org
Objet : RE: [DISCUSS] Discuss
server.
On 3/6/14 2:21 PM, Maurice Amsellem maurice.amsel...@systar.com wrote:
On second try, the installation went well (SDK 4.11 / AIR 13beta / FP 13).
So maybe what could have happened is that I was browsing the cache
directories and files while the installation was in progress and maybe
I forgot: In Get.as
-Message d'origine-
De : Maurice Amsellem
Envoyé : jeudi 6 mars 2014 23:37
À : dev@flex.apache.org
Objet : RE: [DISCUSS] Discuss Release Apache Flex SDK Installer 3.0 - RC4
The installer could certainly use more error handling code.
According to the help
Minor spelling:
Improvements To = improvement to (small caps)
Swiz donation : the donator has not fil(l)ed the paperwork ?
Regarding the raised vs. fixed bugs, I have counted 256 updated tickets ( 143
created tickets ) in the last 90 days.
Otherwise, looks good to me.
Maurice
-Message
Alexander, I had exactly the same thoughts on the installer UI usability.
Thanks for sharing.
Maurice
-Message d'origine-
De : Alexander Doroshko [mailto:alexander.doros...@jetbrains.com]
Envoyé : mardi 4 mars 2014 08:49
À : dev@flex.apache.org
Objet : Re: [DISCUSS] Discuss Release
In theory, only followers of the dev list should know how view the dev builds,
so making a button on the main screen doesn't seem right.
Yes, but the information that dev builds are accessible from the right click is
not easily accessible to occasional testers.
You have to search in the dev list
features are not necessary for me (from the Flex
perspective) and keeping the minimum player version to something less recent
is acceptable.
Typically, I would like to install Flex SDK with AIR 4.0 and FP 11.1.
That's not currently possible.
Do other have the same concern ?
Regard,
Maurice
Well, the paired choice is good as a default.
but we could have a check box manual override or something.
WDYT ?
Maurice
-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : mardi 4 mars 2014 12:33
À : dev@flex.apache.org
Objet : Re: Apache Flex installer
+1 (binding)
Windows 7 64 bit fr
+checked release notes: OK
+ MD5 match: OK
+ manual build: OK
+ test manual build (AIR 4.0+FP 11.1): OK
+ with FB 4.7 mobile app : OK
+ with IntelliJ 13.0.3 , medium web app: OK
+ install RC4 (AIR 4.0+FP12) from Installer 2.7: OK
+ test SDK from
(and it was Java 1.6)
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : mardi 4 mars 2014 14:19
À : dev@flex.apache.org
Objet : RE: [VOTE] Apache Flex 4.12.0 RC4
+1 (binding)
Windows 7 64 bit fr
+checked release notes: OK
+ MD5 match: OK
+ manual
I will do.
Maurice
-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : lundi 3 mars 2014 03:57
À : dev@flex.apache.org
Objet : Re: Regression with DPI calculation
Hi,
Change back to if (iOS) - would be nice if there was another way as it punishes
Jose, are you voting for RC3? This is vote thread for RC2
-Message d'origine-
De : Jose Barragan [mailto:jose.barra...@codeoscopic.com]
Envoyé : lundi 3 mars 2014 16:28
À : dev@flex.apache.org
Objet : Re: [VOTE] Release Apache Flex SDK Installer 3.0 - RC2
+1
Finally this version, it's
Issue with RC3:
When I compile mobile app with SDK 4.12 RC3 + AIR 4.0 , that was built from
src, and run it with ADL = the app start correctly
However, I also installed RC3 using Apache Installer,with AIR 4.0 / FP12.0
The same mobile app compile fine, but when started with ADL I am getting the
False alert: I was using an old version of the installer (2.7.0) instead of
latest that I installed for testing and forgot to remove.
Will check with the latest installer now.
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : dimanche 2 mars 2014
You need to register to create a ticket,
Then you will then see a button Create an Issue at the top of the window.
Then Select project Apache Flex in the Create Issue dialog box and fill-in
the different field.
Maurice
-Message d'origine-
De : Hadi Tavakoli [mailto:taha...@gmail.com]
{airHome}/frameworks/libs/air/airglobal.swc/path-element
/external-library-path
{airhome} should not be there.
So the mobile app does not even compile now.
I am rather surprised having such issues.
Did I miss something ?
Maurice
-Message d'origine-
De : Maurice Amsellem
about the flex-config.xml having the wrong player/swf versions is actually a
problem in the SDK's installer.xml so it will require installing a nightly or
an SDK RC3 someday to see that it works
I have installed Flex SDK 4.12 RC3 using latest installer 3.0.0 from :
, this is a regression.
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : dimanche 2 mars 2014 15:24
À : dev@flex.apache.org
Objet : RE: [DISCUSS] Discuss Release Apache Flex SDK Installer 3.0 - RC2
about the flex-config.xml having the wrong player/swf
the installer.xml matches what is checked into git.
-Alex
On 3/2/14 6:53 AM, Maurice Amsellem maurice.amsel...@systar.com wrote:
More precisely, I am getting the following error when compiling a fresh
flex project in FB 4.7:
unable to open
'D:\ApacheFlex\testing\testing_RC\Flex_SDL_412_RC3
for catching that.
-Alex
On 3/2/14 7:19 AM, Maurice Amsellem maurice.amsel...@systar.com wrote:
link you posted said rc2 in it.
That was the link for the installer ( 3.0 RC2).
I couldn't find rc3 for the installer.
Installed Flex SDK was 4.12 RC3:
Extract from sdk-description:
nameApache Flex
-1 (Binding)
1) *-config.xml files are not correct (contains tokens such as
{playerGlobalHome} and {airHome} );
Flex project does not compile in FB 4.7
Note: the issue appears only when installing the SDK with the installer.
If the SDK is manually built, the tokens are correctly replaced.
: Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : dimanche 2 mars 2014 16:48
À : dev@flex.apache.org
Objet : RE: [VOTE] Apache Flex 4.12.0 RC3
-1 (Binding)
1) *-config.xml files are not correct (contains tokens such as
{playerGlobalHome} and {airHome} ); Flex project does not compile
installer 2.7 in order to pick up OSMF2 so we've done this
sort of thing before. But it does mean I'd better hurry to get the kinks out
of the new installer.
On 3/2/14 7:50 AM, Maurice Amsellem maurice.amsel...@systar.com wrote:
Also, ( but I am not sure of that) it seems that SDK does not install
one of those builds.
Thanks,
-Alex
On 3/2/14 8:18 AM, Maurice Amsellem maurice.amsel...@systar.com wrote:
Or fix the issue so that 2.7 installs correctly.
I will try to understand why the difference.
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com] Envoyé : dimanche 2 mars
: Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : dimanche 2 mars 2014 12:55
À : dev@flex.apache.org
Objet : RE: [DISCUSSION] Apache Flex 4.12.0 release candidate 3
I have tried installing 4.12 RC3 with the latest installer (3.0.0, from
https://dist.apache.org/repos/dist/dev/flex
Hi Justin,
While testing 4.12 RC3 I just noticed a regression in the way
RuntimeDPIProvider computes runtime DPI on iPad.
The intent is to get 160 DPI on iPad and 320 DPI on iPAD retina.
This is done by testing version includes iOS and extent = 1024 ( 2048 for
retina).
I didn't test os
Well, the test is on iOS only and extent be 1024 or 2048.
AFAIK, iPads are the only iOS devices so far to have the above characteristics.
http://en.wikipedia.org/wiki/List_of_iOS_devices
This could change in the future, but for now, it's true.
I know this is kind of hacky, but I couldn't find
Will changing it back to isIOS (rather than isIPad) have the same issue in the
emulator?
No, it will be fine in the emulator, because IOS is in version, which is the
same on ADL and device (IIRC).
Note: maybe you would want to change Platform.isIPad ASDOC comment to mention
that is returns
Hi,
I am currently testing 4.12 RC3.
Now that we have an new ANT based installer, I was wondering if the procedure
to build the RC SDK from its source has changed ?
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : samedi 1 mars 2014 17:21
À :
unless anyone wants to suggest a patch.
Committed fix to develop/branch
https://git-wip-us.apache.org/repos/asf?p=flex-sdk.git;a=commitdiff;h=5468de3f
Can you please review.
Note: if you search for hostComponent string in the SDK source, you will
find similar statements (eg. ScrollerLayout
I will also do some testing this week-end.
-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : jeudi 27 février 2014 23:12
À : dev@flex.apache.org
Objet : Re: [DISCUSSION] Apache Flex 4.12.0 release candidate 2
Hi,
Anyone tried out RC1/RC2 with Java 6 yet?
There is an error in the release notes:
Says Changed DPI to be 160 for iPad and 320 for iPad mini.
Actually it should be:
Changed DPI to be 160 for iPad/iPad mini and 320 for iPad retina/iPad min
retina
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé :
I am checking with iOS6 and iOS7.
Maurice
-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : jeudi 27 février 2014 11:44
À : dev@flex.apache.org
Objet : RC1/RC2 iOS possible issue
HI,
From the linkedin Apache Flex group:
The issue described by Simon
is set.
My bad.
I will fixed that immediately, so that it can be included in the next RC.
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : jeudi 27 février 2014 13:01
À : dev@flex.apache.org
Objet : RE: RC1/RC2 iOS possible issue
I am checking
of fullScreen in the AIR
descriptor.
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : jeudi 27 février 2014 13:13
À : dev@flex.apache.org
Objet : RE: RC1/RC2 iOS possible issue
Tested with SDK 4.12 RC2, AIR 4.0, andfullScreentrue
Or more simply, by testing stage.displayState at initialization.
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : jeudi 27 février 2014 13:57
À : dev@flex.apache.org
Objet : RE: RC1/RC2 iOS possible issue
Checked my code
You're welcome.
BTW, what font size and DPI are you using ? do you see any truncation of text
bottom as described in :
https://issues.apache.org/jira/browse/FLEX-34112
https://issues.apache.org/jira/secure/attachment/12630918/truncated_text_when_using_font_50.jpg
Also, I realize that the
Piotr, what font size are you using in your list ?
Regarding the separator css color:
Current separator are not really a color.
It is a shade of underneath renderer background color, which may vary
depending on alternatingItemColors.
(see code below).
topSeparatorColor = 0xFF;
OK, so truncation should occur, unless you increased the padding.
Maybe that's what you did.
Can you please attach a screenshot of the new rendering (after applying the
fix)?
Maurice
BTW, I just committed change to use CSS for useDrawBackground.
You will be able to use it when the build is
I have checked, they look good to me (gray and blue).
Maybe a network issue ?
Can you check again on your side ?
Maurice
-Message d'origine-
De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de OmPrakash
Muppirala
Envoyé : lundi 24 février 2014 06:51
À : dev@flex.apache.org
code.
This is on Firefox/Windows, btw.
Thanks,
Om
On Mon, Feb 24, 2014 at 12:48 AM, Maurice Amsellem
maurice.amsel...@systar.com wrote:
I have checked, they look good to me (gray and blue).
Maybe a network issue ?
Can you check again on your side ?
Maurice
-Message d'origine
that
could be used to compute it.
-Alex
From: Maurice Amsellem [maurice.amsel...@systar.com]
Sent: Sunday, February 23, 2014 1:56 PM
To: dev@flex.apache.org
Subject: RE: Need your help on problem with opaqueBackground
More findings (and questions):
I am
: Broken image links in Flex Showcase
On Mon, Feb 24, 2014 at 1:17 AM, Maurice Amsellem
maurice.amsel...@systar.com wrote:
Fix is ok , thank you.
Curiously, chrome on Windows 7 does not complain about that...
Yes, you are right. It works fine on Chrome. Looks like Chrome is converting
, so that overflow does not occur.
What do you think ?
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : lundi 24 février 2014 10:57
À : dev@flex.apache.org
Objet : RE: Need your help on problem with opaqueBackground
I looked quickly at how
Funny:
https://issues.apache.org/jira/browse/FLEX-34110
So it looks like I will have to fix this one as well ;-)
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : lundi 24 février 2014 12:57
À : dev@flex.apache.org
Objet : RE: Need your
the Mobile mustella tests to make sure
there are no regressions.
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : lundi 24 février 2014 15:57
À : dev@flex.apache.org; Maurice Amsellem
Objet : RE: Need your help on problem with opaqueBackground
Imo once
is such that you can't, you
might have to trade-off performance for accuracy by not setting opaque
background. I'd probably add some flag that controls whether you run new code
paths or leave it as it was.
-Alex
From: Maurice Amsellem [maurice.amsel
have to trade-off performance for accuracy by not setting opaque
background. I'd probably add some flag that controls whether you run new code
paths or leave it as it was.
-Alex
From: Maurice Amsellem [maurice.amsel...@systar.com]
Sent: Monday, February
-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : lundi 24 février 2014 20:14
À : dev@flex.apache.org
Objet : RE: Need your help on problem with opaqueBackground
Although it's not clearly stated in the documentation, my understanding of
opaqueBackground, is that , when used
bitmap in the background, that would
slow down more when opaqueBackground is set to false.
Any other test idea ?
I will do the tests.
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : lundi 24 février 2014 23:56
À : dev@flex.apache.org; Maurice Amsellem
201 - 300 of 1060 matches
Mail list logo
