I'll have a look at it today.
EdB
On Wednesday, October 30, 2013, Peter Ent wrote:
> Thanks, Erik. Interesting read. FlexJS uses a lot of interfaces so we'll
> have to find a reasonable solution for this. We've managed to avoid the
> situation in JavaScript but it is coming up quickly.
>
> --p
On 10/30/13 7:38 AM, "Tom Chiverton" wrote:
>On 29/10/2013 17:02, Alex Harui wrote:
>> to debug and test on all of the various browsers and platforms out
>>there.
>> It was doable at one point in time, but with the explosion of mobile
>That was what the Open Screen Project was meant to achieve,
Thanks, Erik. Interesting read. FlexJS uses a lot of interfaces so we'll
have to find a reasonable solution for this. We've managed to avoid the
situation in JavaScript but it is coming up quickly.
--peter
On 10/30/13 3:10 PM, "Erik de Bruin" wrote:
>Some guidance can be found here [1] and here
IMO, having two copies of this code is better than breaking people's apps.
However, I'm not sure how often RPCUIDUtils is actually imported and used
in other people's apps. I haven't looked at the code, but there might be
an option 3 where UIDUtils.getUID has a "soft reference" to the class
depen
Thanks Alex!
Joel
On Oct 30, 2013, at 11:53 PM, Alexander Doroshko
wrote:
> ADL tool from Adobe AIR SDK 3.9.0.1200 (beta) released today works well with
> IntelliJ IDEA again.
> http://labs.adobe.com/downloads/air.html
>
> I still have no idea what's wrong with AIR SDK 3.9.0.1030, but it
Hi,
Someone on twitter pointed this bug out:
https://issues.apache.org/jira/browse/FLEX-25721
Anyone know if a) it still true in AIR 3.9 and b) what the limit is?
Thanks,
Justin
I can confirm these figures for SDK 4.10
- iPad 1+2 = 160 dpi (real: 132)
- iPad 3+4 = 240 dpi(real: 263)
- iPad mini 1 = 160 dpi (real: 163).
And for SDK 4.11:
- iPad 1+2 = 120 dpi (real: 132)
- iPad 3 = 240 dpi(real: 263)
So if the buckets didn't change in SDK 4.11, I gue
>I generally don't setting the application dpi to anything to avoid any scaling.
I understand and I agree that the rendering is more accurate.
However, I think people will use applicationDPI because it simplifies their
code.
That is, without applicationDPI, many "absolute" UI properties, th
Hi,
Currently this is what classifyDPI returns:
- iPad1+2 = 120 dpi
- iPad 3+4+Air = 240 dpi
- iPad min 1 = 160 dpi
- iPad mini 2 = 320 dpi
Or so I assueme form the specs anyone confirm on a real device?
Thanks,
Justin
To summarize, whatever changes we make, IMO, DPI calculations should meet the
following rules for iOS devices:
- "retina" devices should always get the double DPI of their non retina
equivalent
- "mini" devices should always get the same DPI of their non-mini equivalent.
Do you agree with that
Hi,
> There are very few UI components that compensate for this behavior (
> typically StyleableTextField, )
Yep but usually only for IOS search code for isiOS and you find that.
> Is that correct ?
As far as I'm aware yes. I generally don't setting the application dpi to
anything to avoid an
>It's set in the skins see for example how layoutBorderSize is set in
>ButtonSkin.as.
Again correct me if I am wrong:
if you set applicationDPI=240 and run the app on a 160 DPI device:
In ButtonSkin.as, the code will execute ' case DPIClassification.DPI_240:' and
layoutBorderSize will be set
> On a similar subject do we need to do anyting to support/improve support for
> the iPad mini 1st gen (160) or 2nd gen (320)?
IMO, Apple and Flex took two different approaches :
1) According to Apple, same app running on iPad mini should look the same
that the app running on ipad 2.
Which m
Hi,
> Correct me if I am wrong, but when you set eg. applicationDPI=120 in the
> Application, only the css @media 120 is considered, same for actionScript
> applicaitonDPI tests, and global scaling is applied to the application
> (through stage.transform), which means you will get fractional
> May not work that well when it comes to borders width and control padding,
> looking through the old skins the borders changed non proportionally to dpi.
Correct me if I am wrong, but when you set eg. applicationDPI=120 in the
Application, only the css @media 120 is considered, same for acti
On Wed, Oct 30, 2013 at 3:41 PM, Maurice Amsellem <
maurice.amsel...@systar.com> wrote:
> There is still something that I don't get:
>
> According to my tests, flex navigation bar is now roughly 0.27' high on
> all devices with SDK 4.11
> and it was 0.34' with SDK 4.10 on iPad 2, and 0.27 on all
There is still something that I don't get:
According to my tests, flex navigation bar is now roughly 0.27' high on all
devices with SDK 4.11
and it was 0.34' with SDK 4.10 on iPad 2, and 0.27 on all other devices.
So now people complain that it's too small on iPad.
So why didn't they complain
On Wed, Oct 30, 2013 at 3:24 PM, Maurice Amsellem <
maurice.amsel...@systar.com> wrote:
> > I think it would be too disruptive to change it now. Perhaps we could
> document a way to modify it for folks who want more control? What are our
> options?
>
> IMO, 4.11 is already disruptive change for
> It's easy enough for a user to change by setting the application's
> runtimeDPIProvider property
> change the boundary that 120 kicks in at
> change classifyDPI to have a special case for iPad 1+2's
Do you mean that would give 160 DPI for iPad 1+2 instead of 120.
In this case, we fall back in
On Wed, Oct 30, 2013 at 3:19 PM, Justin Mclean wrote:
> Hi,
>
> > I think it would be too disruptive to change it now. Perhaps we could
> > document a way to modify it for folks who want more control? What are
> our
> > options?
>
> I see 3 options:
> - It's easy enough for a user to change by
> I think it would be too disruptive to change it now. Perhaps we could
> document a way to modify it for folks who want more control? What are our
> options?
IMO, 4.11 is already disruptive change for mobile apps (at least for iPad 2).
Maurice
-Message d'origine-
De : omup...@gmail
Hi,
> I think it would be too disruptive to change it now. Perhaps we could
> document a way to modify it for folks who want more control? What are our
> options?
I see 3 options:
- It's easy enough for a user to change by setting the application's
runtimeDPIProvider property
- change the bo
Hi,
On a similar subject do we need to do anyting to support/improve support for
the iPad mini 1st gen (160) or 2nd gen (320)?
We could just "fix" this issue by changing classifyDPI to return 160 rather
than 120 for the iPad1 + 2 or perhaps dropping the lower boundary from 140 to
135? (think i
On Wed, Oct 30, 2013 at 2:38 PM, Maurice Amsellem <
maurice.amsel...@systar.com> wrote:
> Hi Team,
>
> Some users complained that their mobile application UI looked smaller
> than before with SDK 4.11 on iPads
> Cf. https://issues.apache.org/jira/browse/FLEX-33861
>
> I explained in the JIRA tick
Hi Team,
Some users complained that their mobile application UI looked smaller than
before with SDK 4.11 on iPads
Cf. https://issues.apache.org/jira/browse/FLEX-33861
I explained in the JIRA tickets that this was because iPad 2 DPI is now 120,
(was: 160) which is closer to its actual DPI (132)
Some guidance can be found here [1] and here [2].
EdB
1:
http://blogs.adobe.com/bparadie/2011/11/26/classes-inheritance-interfaces-packages-and-namespaces/
2:
https://cwiki.apache.org/confluence/display/FLEX/Simulating+AS3+language+features+in+JavaScript+using+AMD+and+ES5
On Wed, Oct 30, 201
"instanceof" doesn't check if an interface is implemented, neither in
Flex nor using Closure inheritance in JavaScript. What we need for
runtime checking of interface implementation is an global "is"
function... I think I taught FalconJx to translate "ClassA is ClassB"
as "is(ClassA, ClassB)". All
Reviving this thread...
Peter says he wants to test to see if an object implements an interface at
runtime. What mechanism do we want to use?
I don't think we need to make instanceof work, just have some test to call.
-Alex
On 7/30/13 12:46 AM, "Erik de Bruin" wrote:
>When using interfaces f
>You won't get an answer from the flexlib issues list or mailing list.
You are correct.
I quickly checked that the last reported issue was on Jan. 2013 and mistakenly
assumed the project was still active, but didn't notice that the last
*accepted* issue was back on Mar. 2010.
Yet another "gh
You won't get an answer from the flexlib issues list or mailing list.
SuperTabNavigator is just an extended TabNavigator. There's nothing
different about accessing its children rather than the children of a normal
mx TabNavigator.
On Wed, Oct 30, 2013 at 1:33 AM, Maurice Amsellem <
maurice.amsel.
Thanks Alexander for the info.
-Message d'origine-
De : Alexander Doroshko [mailto:alexander.doros...@jetbrains.com]
Envoyé : mercredi 30 octobre 2013 16:54
À : dev@flex.apache.org
Objet : Re: ADL Bug - Apache Flex 4.11.0
ADL tool from Adobe AIR SDK 3.9.0.1200 (beta) released today works
ADL tool from Adobe AIR SDK 3.9.0.1200 (beta) released today works well
with IntelliJ IDEA again.
http://labs.adobe.com/downloads/air.html
I still have no idea what's wrong with AIR SDK 3.9.0.1030, but it is not
a problem any more.
Alexander
On 29.10.2013 17:40, Joel Tan wrote:
Hi, not sure
Got it.
In effect, UIDUtils has dependencies to framework.swc from the additional
getUID() function that is not in RPCUIDUtils.
So I see two options:
Option 1) keep the redundancy, and just port the optimizations to RPCUIDUtils.
Option 2) split UIDUtils in two parts, maybe UIDUtils and UIDFlex
Well, so far, I believe every Apache Flex release has allowed it, but I
haven't tested to make sure we haven't added unwanted dependencies. It
was the main reason behind core.swc.
-Alex
On 10/30/13 7:00 AM, "Maurice Amsellem"
wrote:
>Thanks Alex, that must be the reason.
>
>Do we have this co
On 29/10/2013 17:02, Alex Harui wrote:
to debug and test on all of the various browsers and platforms out there.
It was doable at one point in time, but with the explosion of mobile
That was what the Open Screen Project was meant to achieve, I thought,
outsourcing the Player development to the r
Thanks Alex, that must be the reason.
Do we have this constraint anymore in Apache Flex ?
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : mercredi 30 octobre 2013 14:16
À : dev@flex.apache.org
Objet : Re: UIUtils vs RCPUIDUtils
Without looking, it may
Without looking, it may be that RPCUIDUtils exists to allow the RPC SWC to
have fewer dependencies on other Flex classes. It was a goal to have
folks use RPC in non-Flex apps (certain AS-only projects).
On 10/30/13 2:09 AM, "Maurice Amsellem"
wrote:
>Hi team,
>
>Benoit Wiart has ported the UIDU
Thanks Alexander!
Joel
On Oct 30, 2013, at 3:13 PM, Alexander Doroshko
wrote:
> Indeed ADL from AIR SDK 3.9 behaves incorrectly when launched by IntelliJ
> IDEA on Mac OS. No issues with Windows or Air SDK 3.8.
> The most strange thing is that if you launch from Terminal the same ADL
> com
You can cast a sub class to its super class, not the opposite
Maurice
-Message d'origine-
De : Seema Makkar [mailto:seema.mak...@aricent.com]
Envoyé : mercredi 30 octobre 2013 10:50
À : dev@flex.apache.org
Objet : Issues in Type casting
Hello all ,
I have created customize class that e
"arr" is an instance of "ArrayCollection", not an instance of "
PagingArrayCollection"
On 30 October 2013 17:49, Seema Makkar wrote:
> Hello all ,
>
> I have created customize class that extends Arraycollection
> For eg
>
> Public class PagingArrayCollection extends Arraycollection
>
> Now I ha
Hello all ,
I have created customize class that extends Arraycollection
For eg
Public class PagingArrayCollection extends Arraycollection
Now I have to cast ArrayCollection to PagingArrayCollection.
Suppose
Var arr: ArrayCollection = new ArrayCollection();
Var lst: PagingArrayCollection= new Pag
Hi team,
Benoit Wiart has ported the UIDUtil optimization to RPCUIDUtil
https://issues.apache.org/jira/browse/FLEX-33852
However, looking at the code, the two classes have the exact same behavior,
except the additional getUID(item:Object):String in UIDUtils
I don't know why there were two class
That may sound obvious to you, but did you turn on useVirtualLayout on the
list's layout, so that the list can recycle renderers, instead of creating
them for each item to display ?.
Maurice
-Message d'origine-
De : Seema Makkar [mailto:seema.mak...@aricent.com]
Envoyé : mercredi 30
Thanks Alexander for the explanation.
I hope this issue will be fixed soon.
Maurice
-Message d'origine-
De : Alexander Doroshko [mailto:alexander.doros...@jetbrains.com]
Envoyé : mercredi 30 octobre 2013 08:14
À : dev@flex.apache.org
Objet : Re: ADL Bug - Apache Flex 4.11.0
Indeed ADL
Hi Oleg,
SuperTabNavigator is not part of core Flex SDK, but rather is part of flexlib
library.
You can get more easily an answer if you post directly to flexlib issues:
https://code.google.com/p/flexlib/issues/list
Maurice
-Message d'origine-
De : Oleg Konovalov [mailto:oleg...@gma
Hi,
> I'm sorry for such a late report, but the issue is still there in 4.11
> release (4.11.0.20131017).
> flex-config.xml contains invalid names like
> framework_4.11.0.0.swf
Yep can confirm it but not had a chance to look at the issue in detail, so I'm
not 100% sure if it's an installer issu
On 28.10.2013 15:10, Alexander Doroshko wrote:
On 28.10.2013 15:04, Justin Mclean wrote:
I'm sorry for such a late report, but the issue is still there in
4.11 release (4.11.0.20131017).
flex-config.xml contains invalid names like
framework_4.11.0.0.swf
How did you install the 4.11.0 SDK?
Usi
Hi Naveen,
I haven't got time to implement it yet.
But I figure it out a better solution:
1. Create a class named "VisualStageText" which extends SpriteVisualElement
class and implements IEditableText interface.
2. In the VisualStageText class implementation, define a private variable
stageTe
Indeed ADL from AIR SDK 3.9 behaves incorrectly when launched by
IntelliJ IDEA on Mac OS. No issues with Windows or Air SDK 3.8.
The most strange thing is that if you launch from Terminal the same ADL
command that you see in IntelliJ IDEA console - it will work correctly.
We at JetBrains are eva
49 matches
Mail list logo
