You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Maurice Amsellem <ma...@systar.com> on 2013/11/03 21:13:03 UTC
IOS7 status bar management ( FLEX-33860)
Hi Team,
iOS7 manages the status bar differently than iOS 6.1: application is displayed in full screen and the status bar is displayed on top of the app, either in black or white font color (depending on some setting).
Current flex apps running on iOS7 will have the status bar partly covering the top navigation bar buttons and text.
The usual workaround is to increase ActionBar paddingTop to remove the overlap.
(see : https://issues.apache.org/jira/browse/FLEX-33860)
I would like to discuss the different approaches for a permanent fix of this issue in the Flex SDK.
There are two points to discuss: how to provide room for the status bar, and how to determine/control when to do it:
Point #1: how to provide room for the status Bar:
Option 1) increase the top ActionBar paddingTop, to leave space for the status bar.
Note that the top padding must be applied to the top ActionBar only, not to the other ActionBars.
This is easy for ViewNavigatorApplication, but not obvious when the ActionBar(s) are added indirectly, for example through SplitViewNavigator.
This could be done eg. by testing the ActionBar stage y, and add the padding if < 10
Option 2) modify the various mobile ApplicationSkin classes (ApplicaitonSkin, TabbedViewNavigatorApplicationSkin, ViewNavigatorApplicationSkin) to leave 20 px space for the status bar.
This space could be filled with application background color, instead of being black.
----
Point #2: How to determine when to add the top padding:
Option 1)
- Dynamically determine that application is running on iOS7 (based on Capabilities.version and Capabilities.os)
- Size the padding top accordingly ( set if IOS7, not set if not IOS7)
⇨ Simple, but not flexible.
Option 2)
- Introduce a new numerical os-version @media selector
Eg.
@media (application-dpi: 160) AND (os-platform:"IOS") AND (os-version >= 7) {
statusBarHeight: 20;
}
Pros: opens up new possilibilities, for example to provide iOS7 specific skins.
Cons: much more difficult to implement.
_____
What do you think ?
Maurice
RE: IOS7 status bar management ( FLEX-33860)
Posted by Maurice Amsellem <ma...@systar.com>.
I think it can be solved at the SDK level.
have been working on it but still didn't have time to complete.
AFAIU, it's more or less adding a paddingTop to ActionBar, when running on iOS7.
Maurice
-----Message d'origine-----
De : Christian Kiefer [mailto:christian.kiefer@goal-games.de]
Envoyé : mardi 26 novembre 2013 11:41
À : dev@flex.apache.org
Objet : Re: IOS7 status bar management ( FLEX-33860)
Does anyone of you knows if adobe is going to fix this issue in Air 3.9x or Air 4.X or is something planned for a an upcoming Flex SDK?
The issue doesn't seem to be high priority for Adobe (but many
developers) ...
https://bugbase.adobe.com/index.cfm?event=bug&id=3633422
Christian
Am 04.11.2013 14:25, schrieb Maurice Amsellem:
> There's already one:
>
> https://bugbase.adobe.com/index.cfm?event=bug&id=3633422
>
> Maurice
>
> -----Message d'origine-----
> De : Alex Harui [mailto:aharui@adobe.com] Envoyé : lundi 4 novembre
> 2013 05:52 À : dev@flex.apache.org Objet : Re: IOS7 status bar
> management ( FLEX-33860)
>
>
>
> On 11/3/13 12:38 PM, "Lee Burrows" <su...@leeburrows.com> wrote:
>
>> creators of native ios apps do have the ability to force the
>> statusbar to behave in the 'old' way (opaque and not overlaying the
>> app) and i'm sure i've read somewhere that adobe are working on a fix
>> for this in the air player.... so an sdk change may not be necessary.
>>
>> perhaps alex could confirm (or refute) this?
> I have no information on that either way. Best way to find out is to file an issue with AIR at Adobe.
>
> -Alex
>
>
Re: IOS7 status bar management ( FLEX-33860)
Posted by Christian Kiefer <ch...@goal-games.de>.
Does anyone of you knows if adobe is going to fix this issue in Air 3.9x
or Air 4.X or is something planned for a an upcoming Flex SDK?
The issue doesn't seem to be high priority for Adobe (but many
developers) ...
https://bugbase.adobe.com/index.cfm?event=bug&id=3633422
Christian
Am 04.11.2013 14:25, schrieb Maurice Amsellem:
> There's already one:
>
> https://bugbase.adobe.com/index.cfm?event=bug&id=3633422
>
> Maurice
>
> -----Message d'origine-----
> De : Alex Harui [mailto:aharui@adobe.com]
> Envoyé : lundi 4 novembre 2013 05:52
> À : dev@flex.apache.org
> Objet : Re: IOS7 status bar management ( FLEX-33860)
>
>
>
> On 11/3/13 12:38 PM, "Lee Burrows" <su...@leeburrows.com> wrote:
>
>> creators of native ios apps do have the ability to force the statusbar
>> to behave in the 'old' way (opaque and not overlaying the app) and i'm
>> sure i've read somewhere that adobe are working on a fix for this in
>> the air player.... so an sdk change may not be necessary.
>>
>> perhaps alex could confirm (or refute) this?
> I have no information on that either way. Best way to find out is to file an issue with AIR at Adobe.
>
> -Alex
>
>
RE: IOS7 status bar management ( FLEX-33860)
Posted by Maurice Amsellem <ma...@systar.com>.
There's already one:
https://bugbase.adobe.com/index.cfm?event=bug&id=3633422
Maurice
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com]
Envoyé : lundi 4 novembre 2013 05:52
À : dev@flex.apache.org
Objet : Re: IOS7 status bar management ( FLEX-33860)
On 11/3/13 12:38 PM, "Lee Burrows" <su...@leeburrows.com> wrote:
>creators of native ios apps do have the ability to force the statusbar
>to behave in the 'old' way (opaque and not overlaying the app) and i'm
>sure i've read somewhere that adobe are working on a fix for this in
>the air player.... so an sdk change may not be necessary.
>
>perhaps alex could confirm (or refute) this?
I have no information on that either way. Best way to find out is to file an issue with AIR at Adobe.
-Alex
Re: IOS7 status bar management ( FLEX-33860)
Posted by Lee Burrows <su...@leeburrows.com>.
cant remember where (it was a week or 2 ago); either the apple dev site
or a blog - but i'm not an ios dev either so i may have misunderstood
On 03/11/2013 23:58, Maurice Amsellem wrote:
> Hi,
>
>> >creators of native ios apps do have the ability to force the statusbar to behave in the 'old' way (opaque and not overlaying the app)
> http://stackoverflow.com/questions/18294872/ios-7-status-bar-back-to-ios-6-style
> AND:
> https://developer.apple.com/library/ios/documentation/userexperience/conceptual/transitionguide/Bars.html
>
> So where did you read this ?
>
> Note: I have never written a native iOS app, let alone in IOS7.
>
> Maurice
--
Lee Burrows
ActionScripter
RE: IOS7 status bar management ( FLEX-33860)
Posted by Maurice Amsellem <ma...@systar.com>.
Hi,
> creators of native ios apps do have the ability to force the statusbar to behave in the 'old' way (opaque and not overlaying the app)
http://stackoverflow.com/questions/18294872/ios-7-status-bar-back-to-ios-6-style
AND:
https://developer.apple.com/library/ios/documentation/userexperience/conceptual/transitionguide/Bars.html
So where did you read this ?
Note: I have never written a native iOS app, let alone in IOS7.
Maurice
-----Message d'origine-----
De : Lee Burrows [mailto:subscriptions@leeburrows.com]
Envoyé : dimanche 3 novembre 2013 21:39
À : dev@flex.apache.org
Objet : Re: IOS7 status bar management ( FLEX-33860)
creators of native ios apps do have the ability to force the statusbar to behave in the 'old' way (opaque and not overlaying the app) and i'm sure i've read somewhere that adobe are working on a fix for this in the air player.... so an sdk change may not be necessary.
perhaps alex could confirm (or refute) this?
On 03/11/2013 20:13, Maurice Amsellem wrote:
> Hi Team,
>
> iOS7 manages the status bar differently than iOS 6.1: application is displayed in full screen and the status bar is displayed on top of the app, either in black or white font color (depending on some setting).
>
> Current flex apps running on iOS7 will have the status bar partly covering the top navigation bar buttons and text.
>
> The usual workaround is to increase ActionBar paddingTop to remove the overlap.
>
> (see : https://issues.apache.org/jira/browse/FLEX-33860)
>
> I would like to discuss the different approaches for a permanent fix of this issue in the Flex SDK.
>
> There are two points to discuss: how to provide room for the status bar, and how to determine/control when to do it:
>
>
> Point #1: how to provide room for the status Bar:
>
> Option 1) increase the top ActionBar paddingTop, to leave space for the status bar.
>
> Note that the top padding must be applied to the top ActionBar only, not to the other ActionBars.
> This is easy for ViewNavigatorApplication, but not obvious when the ActionBar(s) are added indirectly, for example through SplitViewNavigator.
> This could be done eg. by testing the ActionBar stage y, and add the
> padding if < 10
>
> Option 2) modify the various mobile ApplicationSkin classes (ApplicaitonSkin, TabbedViewNavigatorApplicationSkin, ViewNavigatorApplicationSkin) to leave 20 px space for the status bar.
> This space could be filled with application background color, instead of being black.
>
> ----
>
> Point #2: How to determine when to add the top padding:
>
> Option 1)
> - Dynamically determine that application is running on iOS7 (based on
> Capabilities.version and Capabilities.os)
> - Size the padding top accordingly ( set if IOS7, not set if not IOS7)
>
> ⇨ Simple, but not flexible.
>
> Option 2)
> - Introduce a new numerical os-version @media selector
>
> Eg.
>
> @media (application-dpi: 160) AND (os-platform:"IOS") AND (os-version >= 7) {
> statusBarHeight: 20;
> }
>
> Pros: opens up new possilibilities, for example to provide iOS7 specific skins.
> Cons: much more difficult to implement.
>
>
> _____
>
> What do you think ?
>
> Maurice
--
Lee Burrows
ActionScripter
Re: IOS7 status bar management ( FLEX-33860)
Posted by Alex Harui <ah...@adobe.com>.
On 11/3/13 12:38 PM, "Lee Burrows" <su...@leeburrows.com> wrote:
>creators of native ios apps do have the ability to force the statusbar
>to behave in the 'old' way (opaque and not overlaying the app) and i'm
>sure i've read somewhere that adobe are working on a fix for this in the
>air player.... so an sdk change may not be necessary.
>
>perhaps alex could confirm (or refute) this?
I have no information on that either way. Best way to find out is to file
an issue with AIR at Adobe.
-Alex
Re: IOS7 status bar management ( FLEX-33860)
Posted by Lee Burrows <su...@leeburrows.com>.
creators of native ios apps do have the ability to force the statusbar
to behave in the 'old' way (opaque and not overlaying the app) and i'm
sure i've read somewhere that adobe are working on a fix for this in the
air player.... so an sdk change may not be necessary.
perhaps alex could confirm (or refute) this?
On 03/11/2013 20:13, Maurice Amsellem wrote:
> Hi Team,
>
> iOS7 manages the status bar differently than iOS 6.1: application is displayed in full screen and the status bar is displayed on top of the app, either in black or white font color (depending on some setting).
>
> Current flex apps running on iOS7 will have the status bar partly covering the top navigation bar buttons and text.
>
> The usual workaround is to increase ActionBar paddingTop to remove the overlap.
>
> (see : https://issues.apache.org/jira/browse/FLEX-33860)
>
> I would like to discuss the different approaches for a permanent fix of this issue in the Flex SDK.
>
> There are two points to discuss: how to provide room for the status bar, and how to determine/control when to do it:
>
>
> Point #1: how to provide room for the status Bar:
>
> Option 1) increase the top ActionBar paddingTop, to leave space for the status bar.
>
> Note that the top padding must be applied to the top ActionBar only, not to the other ActionBars.
> This is easy for ViewNavigatorApplication, but not obvious when the ActionBar(s) are added indirectly, for example through SplitViewNavigator.
> This could be done eg. by testing the ActionBar stage y, and add the padding if < 10
>
> Option 2) modify the various mobile ApplicationSkin classes (ApplicaitonSkin, TabbedViewNavigatorApplicationSkin, ViewNavigatorApplicationSkin) to leave 20 px space for the status bar.
> This space could be filled with application background color, instead of being black.
>
> ----
>
> Point #2: How to determine when to add the top padding:
>
> Option 1)
> - Dynamically determine that application is running on iOS7 (based on Capabilities.version and Capabilities.os)
> - Size the padding top accordingly ( set if IOS7, not set if not IOS7)
>
> ⇨ Simple, but not flexible.
>
> Option 2)
> - Introduce a new numerical os-version @media selector
>
> Eg.
>
> @media (application-dpi: 160) AND (os-platform:"IOS") AND (os-version >= 7) {
> statusBarHeight: 20;
> }
>
> Pros: opens up new possilibilities, for example to provide iOS7 specific skins.
> Cons: much more difficult to implement.
>
>
> _____
>
> What do you think ?
>
> Maurice
--
Lee Burrows
ActionScripter
Re: Flex and server technology
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Very interesting Fréderic,
thanks for the info! :)
2014-02-25 0:33 GMT+01:00 Frédéric THOMAS <we...@hotmail.com>:
> Done !
>
> Feel free to comment or amend.
>
>
> https://cwiki.apache.org/confluence/display/FLEX/Flex+Server+Technologies+-+Comparative+table
>
> Thanks,
> Frédéric THOMAS
>
> > From: bigosmallm@gmail.com
> > Date: Sun, 16 Feb 2014 12:10:55 -0800
> > Subject: Re: Flex and server technology
> > To: dev@flex.apache.org
> >
> > Fred, this looks fine to me. I had assumed that this was going to be
> more
> > of an editorial commentary. This looks like a straightforward feature
> > comparison table.
> > +1 from me.
> >
> > Thanks for the clarification.
> >
> > Om
> >
> >
> > On Sun, Feb 16, 2014 at 10:05 AM, Frédéric THOMAS
> > <we...@hotmail.com>wrote:
> >
> > > Well, it was well printed, this link should work though.
> > >
> > >
> > >
> https://docs.google.com/spreadsheet/ccc?key=0AkSnI9jZINzGdExMRlc0cTkzNWJ4UjNiWTVJM1piM3c#gid=0
> > >
> > > Frédéric THOMAS
> > >
> > > > From: webdoublefx@hotmail.com
> > > > To: dev@flex.apache.org
> > > > Subject: RE: Flex and server technology
> > > > Date: Sun, 16 Feb 2014 17:53:06 +0000
> > > >
> > > > Hi,
> > > >
> > > > @Alex, good news :-)
> > > >
> > > > @Om, Not sure I follow you, could please review what I was describing
> > > and tell me if it was what you thought ? (I hope that will be printed
> > > correctly)
> > > >
> > > >
> > > > BlazeDSLCDSGraniteDSFramework integrationSpring(1)xxEJB 3
> > > >
> > > > xCDI
> > > >
> > > > xJPA engine supportHibernate(2)xxEclipseLink
> > > >
> > > > xOpenJPA
> > > >
> > > > xDataNucleus
> > > >
> > > > xMessaging (real-time)Blocking I/O http long-pollingxxxBlocking I/O
> http
> > > streamingxx
> > > > Non-blocking I/O http long-polling(3)xxNon-blocking I/O http
> > > streaming(3)x
> > > > RTMP
> > > > x
> > > > WebSocket
> > > >
> > > > xUDP
> > > >
> > > > xData managementBean validation
> > > >
> > > > xBig numbers
> > > >
> > > > xCode generation
> > > > xxData paging
> > > > xxData synchonization / conflict resolution
> > > > xxDisconnected mode
> > > > xplannedOthersMonitoring
> > > > x
> > > > Load testing tools(4)(4)(4)PDF generation
> > > > x
> > > > LicensingOpen sourcex
> > > > xCommercial
> > > > xx
> > > >
> > > >
> > > >
> > > > 1 - Using the project Spring-Flex2 - Partial support in Spring-Flex
> or
> > > dpHibernate3 - Possible with some third party extensions4 - Supported
> by
> > > NeoLoad, HP LoadRunner, IBM Rational Performance Tester
> > > >
> > > > Frédéric THOMAS
> > > >
> > > > > Date: Sun, 16 Feb 2014 09:29:56 -0800
> > > > > Subject: Re: Flex and server technology
> > > > > From: bigosmallm@gmail.com
> > > > > To: dev@flex.apache.org
> > > > >
> > > > > On Feb 16, 2014 3:25 AM, "Frédéric THOMAS" <
> webdoublefx@hotmail.com>
> > > wrote:
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I have a comparative feature table for BlazeDS / LCDS /
> GraniteDS,
> > > given
> > > > > some people are asking about it at time, do you think it is
> something
> > > that
> > > > > could fit on our wiki ?
> > > > >
> > > > > -1
> > > > >
> > > > > If it were just a listing instead of a comparison, that would be
> fine.
> > > > >
> > > > > Given that we will be controlling BlazeDS as part of Apache Flex,
> it
> > > may
> > > > > not be fair to GraniteDS or LCDS. We should avoid even the
> appearance
> > > of
> > > > > favoritism.
> > > > >
> > > > > It might be better to put this up on your personal blog.
> > > > >
> > > > > Thanks,
> > > > > Om
> > > > >
> > > > > >
> > > > > > Thanks,
> > > > > > Frédéric THOMAS
> > > > > >
> > > >
> > >
> > >
>
>
--
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F: +34 912 94 80 80
http://www.codeoscopic.com
http://www.directwriter.es
http://www.avant2.es
RE: Flex and server technology
Posted by Frédéric THOMAS <we...@hotmail.com>.
Just sent the author (Shashank Tiwari) an email with the hope he would like to contribute it to blazeDS, let's see as well on this side.
Frédéric THOMAS
> Date: Tue, 25 Feb 2014 20:42:19 +0700
> From: paul.hastings@gmail.com
> To: dev@flex.apache.org
> Subject: Re: Flex and server technology
>
> On 2/25/2014 7:46 PM, Frédéric THOMAS wrote:
> > It seems it was a project [1] done by the guy who wrote Professional BlazeDS
> > but can't see the source code anymore, maybe someone knows the current status
> > of this project and where it is hosted now if still or another thirdparty.
>
> seems there never was any source? the projects i looked thru only had the
> initial dir commits & nothing more. too bad, seems like some good/interesting ideas.
>
> > I don't know CF, it was not used that much in EU but feel free to amend /
> > annotate the wiki itself, I guess you've got the karma to do it, if not, just
> > ask it here :-)
>
> not 100% sure its appropriate for that list except maybe as more notes? anyways
> let it stew a few days.
AW: AW: Flex and server technology
Posted by Christofer Dutz <ch...@c-ware.de>.
+1 as Long as we extend the comparison with a "language" column ;-)
Chris
________________________________________
Von: João Fernandes <jo...@gmail.com>
Gesendet: Dienstag, 25. Februar 2014 15:53
An: dev@flex.apache.org
Betreff: Re: AW: Flex and server technology
Shouldn't we include other solutions besides Java based ones?
There is FluorineFx, PyAMF, WebOrb, AMFPHP, ZendAMF, RubyAMF,erlang-AMF etc
etc...
On 25 February 2014 14:27, Frédéric THOMAS <we...@hotmail.com> wrote:
> I added your link to
> https://cwiki.apache.org/confluence/display/FLEX/Flex+Server+Technologies+-+Comparative+table
>
> That's definitly things to explore.
>
> Thanks,
> Frédéric THOMAS
>
> > From: webdoublefx@hotmail.com
> > To: dev@flex.apache.org
> > Subject: RE: AW: Flex and server technology
> > Date: Tue, 25 Feb 2014 14:12:25 +0000
> >
> > Hi Chris,
> >
> > Thanks for the link.
> >
> > Frédéric THOMAS
> >
> > > From: christofer.dutz@c-ware.de
> > > To: dev@flex.apache.org
> > > Subject: AW: Flex and server technology
> > > Date: Tue, 25 Feb 2014 13:58:37 +0000
> > >
> > > Just used Google a Little and found this page:
> > >
> http://blog.hiraash.org/2012/04/13/scaling-blazeds-with-servlet-3-concurrency/
> > > Seems the author summed up several approaches.
> > >
> > > Chris
> > >
> > >
> > > ________________________________________
> > > Von: Christofer Dutz <ch...@c-ware.de>
> > > Gesendet: Dienstag, 25. Februar 2014 14:54
> > > An: dev@flex.apache.org; paul.hastings@gmail.com
> > > Betreff: AW: Flex and server technology
> > >
> > > As far as I remember there were several Solutions utilizing Jettys
> properitary Continuation concept.
> > > I once started working on a Servlet 3 NIO AMF connector, but Project
> life sort of sucked all time I had away from me.
> > > Now with the Servlet api being official, this is one of the fist
> things I am hoping on getting dirty on as soon as BlazeDS is officially
> Apache :-)
> > >
> > > Chris
> > > ________________________________________
> > > Von: Paul Hastings <pa...@gmail.com>
> > > Gesendet: Dienstag, 25. Februar 2014 14:42
> > > An: dev@flex.apache.org
> > > Betreff: Re: Flex and server technology
> > >
> > > On 2/25/2014 7:46 PM, Frédéric THOMAS wrote:
> > > > It seems it was a project [1] done by the guy who wrote Professional
> BlazeDS
> > > > but can't see the source code anymore, maybe someone knows the
> current status
> > > > of this project and where it is hosted now if still or another
> thirdparty.
> > >
> > > seems there never was any source? the projects i looked thru only had
> the
> > > initial dir commits & nothing more. too bad, seems like some
> good/interesting ideas.
> > >
> > > > I don't know CF, it was not used that much in EU but feel free to
> amend /
> > > > annotate the wiki itself, I guess you've got the karma to do it, if
> not, just
> > > > ask it here :-)
> > >
> > > not 100% sure its appropriate for that list except maybe as more
> notes? anyways
> > > let it stew a few days.
> >
>
>
--
João Fernandes
AW: Flex and server technology
Posted by Christofer Dutz <ch...@c-ware.de>.
Anyone have worked with the Red5 Server yet? Would really like to see that popup in the comparison list.
http://www.red5.org/
Chris
________________________________________
Von: Marcio Fermino <pr...@gmail.com>
Gesendet: Dienstag, 25. Februar 2014 18:45
An: dev@flex.apache.org
Betreff: Re: Flex and server technology
Exato..
Em 25/02/2014, à(s) 12:34, Christofer Dutz <ch...@c-ware.de> escreveu:
> Well I'd simply say that they don't have EJB and Spring Support ... so what? ... I bet BLazeDS doesn't Support PHP or .Net ;-)
> Why not just add the missing Frameworks and make your "x"es to mark the Frameworks the others Support.
>
> Chris
>
> ________________________________________
> Von: João Fernandes <jo...@gmail.com>
> Gesendet: Dienstag, 25. Februar 2014 16:20
> An: dev@flex.apache.org
> Betreff: Re: AW: Flex and server technology
>
> It's hard to have a comparative table since a ruby or a .net will hardly
> have integration with EJB, Spring etc :)
>
> For example, FluorineFX does provide support for messaging with I/O
> endpoints, (not sure fur NIO under HTTP), RTMP channels,
> RemoteSharedObjects and FMS recording capabilities like Red5 and Wooza
> which BlazeDS doesn't support.
>
> It would be interesting to also list which ones are still under development
> and not.
>
>
> On 25 February 2014 15:07, Frédéric THOMAS <we...@hotmail.com> wrote:
>
>> +1 from me too, do you have an already made comparative table ?
>>
>> Frédéric THOMAS
>>
>>> From: joaopedromartinsfernandes@gmail.com
>>> Date: Tue, 25 Feb 2014 14:53:04 +0000
>>> Subject: Re: AW: Flex and server technology
>>> To: dev@flex.apache.org
>>>
>>> Shouldn't we include other solutions besides Java based ones?
>>> There is FluorineFx, PyAMF, WebOrb, AMFPHP, ZendAMF, RubyAMF,erlang-AMF
>> etc
>>> etc...
>>>
>>>
>>> On 25 February 2014 14:27, Frédéric THOMAS <we...@hotmail.com>
>> wrote:
>>>
>>>> I added your link to
>>>>
>> https://cwiki.apache.org/confluence/display/FLEX/Flex+Server+Technologies+-+Comparative+table
>>>>
>>>> That's definitly things to explore.
>>>>
>>>> Thanks,
>>>> Frédéric THOMAS
>>>>
>>>>> From: webdoublefx@hotmail.com
>>>>> To: dev@flex.apache.org
>>>>> Subject: RE: AW: Flex and server technology
>>>>> Date: Tue, 25 Feb 2014 14:12:25 +0000
>>>>>
>>>>> Hi Chris,
>>>>>
>>>>> Thanks for the link.
>>>>>
>>>>> Frédéric THOMAS
>>>>>
>>>>>> From: christofer.dutz@c-ware.de
>>>>>> To: dev@flex.apache.org
>>>>>> Subject: AW: Flex and server technology
>>>>>> Date: Tue, 25 Feb 2014 13:58:37 +0000
>>>>>>
>>>>>> Just used Google a Little and found this page:
>>>>>>
>>>>
>> http://blog.hiraash.org/2012/04/13/scaling-blazeds-with-servlet-3-concurrency/
>>>>>> Seems the author summed up several approaches.
>>>>>>
>>>>>> Chris
>>>>>>
>>>>>>
>>>>>> ________________________________________
>>>>>> Von: Christofer Dutz <ch...@c-ware.de>
>>>>>> Gesendet: Dienstag, 25. Februar 2014 14:54
>>>>>> An: dev@flex.apache.org; paul.hastings@gmail.com
>>>>>> Betreff: AW: Flex and server technology
>>>>>>
>>>>>> As far as I remember there were several Solutions utilizing Jettys
>>>> properitary Continuation concept.
>>>>>> I once started working on a Servlet 3 NIO AMF connector, but
>> Project
>>>> life sort of sucked all time I had away from me.
>>>>>> Now with the Servlet api being official, this is one of the fist
>>>> things I am hoping on getting dirty on as soon as BlazeDS is officially
>>>> Apache :-)
>>>>>>
>>>>>> Chris
>>>>>> ________________________________________
>>>>>> Von: Paul Hastings <pa...@gmail.com>
>>>>>> Gesendet: Dienstag, 25. Februar 2014 14:42
>>>>>> An: dev@flex.apache.org
>>>>>> Betreff: Re: Flex and server technology
>>>>>>
>>>>>> On 2/25/2014 7:46 PM, Frédéric THOMAS wrote:
>>>>>>> It seems it was a project [1] done by the guy who wrote
>> Professional
>>>> BlazeDS
>>>>>>> but can't see the source code anymore, maybe someone knows the
>>>> current status
>>>>>>> of this project and where it is hosted now if still or another
>>>> thirdparty.
>>>>>>
>>>>>> seems there never was any source? the projects i looked thru only
>> had
>>>> the
>>>>>> initial dir commits & nothing more. too bad, seems like some
>>>> good/interesting ideas.
>>>>>>
>>>>>>> I don't know CF, it was not used that much in EU but feel free to
>>>> amend /
>>>>>>> annotate the wiki itself, I guess you've got the karma to do it,
>> if
>>>> not, just
>>>>>>> ask it here :-)
>>>>>>
>>>>>> not 100% sure its appropriate for that list except maybe as more
>>>> notes? anyways
>>>>>> let it stew a few days.
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> João Fernandes
>>
>>
>
>
>
> --
>
> João Fernandes
Re: Flex and server technology
Posted by Marcio Fermino <pr...@gmail.com>.
Exato..
Em 25/02/2014, à(s) 12:34, Christofer Dutz <ch...@c-ware.de> escreveu:
> Well I'd simply say that they don't have EJB and Spring Support ... so what? ... I bet BLazeDS doesn't Support PHP or .Net ;-)
> Why not just add the missing Frameworks and make your "x"es to mark the Frameworks the others Support.
>
> Chris
>
> ________________________________________
> Von: João Fernandes <jo...@gmail.com>
> Gesendet: Dienstag, 25. Februar 2014 16:20
> An: dev@flex.apache.org
> Betreff: Re: AW: Flex and server technology
>
> It's hard to have a comparative table since a ruby or a .net will hardly
> have integration with EJB, Spring etc :)
>
> For example, FluorineFX does provide support for messaging with I/O
> endpoints, (not sure fur NIO under HTTP), RTMP channels,
> RemoteSharedObjects and FMS recording capabilities like Red5 and Wooza
> which BlazeDS doesn't support.
>
> It would be interesting to also list which ones are still under development
> and not.
>
>
> On 25 February 2014 15:07, Frédéric THOMAS <we...@hotmail.com> wrote:
>
>> +1 from me too, do you have an already made comparative table ?
>>
>> Frédéric THOMAS
>>
>>> From: joaopedromartinsfernandes@gmail.com
>>> Date: Tue, 25 Feb 2014 14:53:04 +0000
>>> Subject: Re: AW: Flex and server technology
>>> To: dev@flex.apache.org
>>>
>>> Shouldn't we include other solutions besides Java based ones?
>>> There is FluorineFx, PyAMF, WebOrb, AMFPHP, ZendAMF, RubyAMF,erlang-AMF
>> etc
>>> etc...
>>>
>>>
>>> On 25 February 2014 14:27, Frédéric THOMAS <we...@hotmail.com>
>> wrote:
>>>
>>>> I added your link to
>>>>
>> https://cwiki.apache.org/confluence/display/FLEX/Flex+Server+Technologies+-+Comparative+table
>>>>
>>>> That's definitly things to explore.
>>>>
>>>> Thanks,
>>>> Frédéric THOMAS
>>>>
>>>>> From: webdoublefx@hotmail.com
>>>>> To: dev@flex.apache.org
>>>>> Subject: RE: AW: Flex and server technology
>>>>> Date: Tue, 25 Feb 2014 14:12:25 +0000
>>>>>
>>>>> Hi Chris,
>>>>>
>>>>> Thanks for the link.
>>>>>
>>>>> Frédéric THOMAS
>>>>>
>>>>>> From: christofer.dutz@c-ware.de
>>>>>> To: dev@flex.apache.org
>>>>>> Subject: AW: Flex and server technology
>>>>>> Date: Tue, 25 Feb 2014 13:58:37 +0000
>>>>>>
>>>>>> Just used Google a Little and found this page:
>>>>>>
>>>>
>> http://blog.hiraash.org/2012/04/13/scaling-blazeds-with-servlet-3-concurrency/
>>>>>> Seems the author summed up several approaches.
>>>>>>
>>>>>> Chris
>>>>>>
>>>>>>
>>>>>> ________________________________________
>>>>>> Von: Christofer Dutz <ch...@c-ware.de>
>>>>>> Gesendet: Dienstag, 25. Februar 2014 14:54
>>>>>> An: dev@flex.apache.org; paul.hastings@gmail.com
>>>>>> Betreff: AW: Flex and server technology
>>>>>>
>>>>>> As far as I remember there were several Solutions utilizing Jettys
>>>> properitary Continuation concept.
>>>>>> I once started working on a Servlet 3 NIO AMF connector, but
>> Project
>>>> life sort of sucked all time I had away from me.
>>>>>> Now with the Servlet api being official, this is one of the fist
>>>> things I am hoping on getting dirty on as soon as BlazeDS is officially
>>>> Apache :-)
>>>>>>
>>>>>> Chris
>>>>>> ________________________________________
>>>>>> Von: Paul Hastings <pa...@gmail.com>
>>>>>> Gesendet: Dienstag, 25. Februar 2014 14:42
>>>>>> An: dev@flex.apache.org
>>>>>> Betreff: Re: Flex and server technology
>>>>>>
>>>>>> On 2/25/2014 7:46 PM, Frédéric THOMAS wrote:
>>>>>>> It seems it was a project [1] done by the guy who wrote
>> Professional
>>>> BlazeDS
>>>>>>> but can't see the source code anymore, maybe someone knows the
>>>> current status
>>>>>>> of this project and where it is hosted now if still or another
>>>> thirdparty.
>>>>>>
>>>>>> seems there never was any source? the projects i looked thru only
>> had
>>>> the
>>>>>> initial dir commits & nothing more. too bad, seems like some
>>>> good/interesting ideas.
>>>>>>
>>>>>>> I don't know CF, it was not used that much in EU but feel free to
>>>> amend /
>>>>>>> annotate the wiki itself, I guess you've got the karma to do it,
>> if
>>>> not, just
>>>>>>> ask it here :-)
>>>>>>
>>>>>> not 100% sure its appropriate for that list except maybe as more
>>>> notes? anyways
>>>>>> let it stew a few days.
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> João Fernandes
>>
>>
>
>
>
> --
>
> João Fernandes
AW: AW: Flex and server technology
Posted by Christofer Dutz <ch...@c-ware.de>.
Well I'd simply say that they don't have EJB and Spring Support ... so what? ... I bet BLazeDS doesn't Support PHP or .Net ;-)
Why not just add the missing Frameworks and make your "x"es to mark the Frameworks the others Support.
Chris
________________________________________
Von: João Fernandes <jo...@gmail.com>
Gesendet: Dienstag, 25. Februar 2014 16:20
An: dev@flex.apache.org
Betreff: Re: AW: Flex and server technology
It's hard to have a comparative table since a ruby or a .net will hardly
have integration with EJB, Spring etc :)
For example, FluorineFX does provide support for messaging with I/O
endpoints, (not sure fur NIO under HTTP), RTMP channels,
RemoteSharedObjects and FMS recording capabilities like Red5 and Wooza
which BlazeDS doesn't support.
It would be interesting to also list which ones are still under development
and not.
On 25 February 2014 15:07, Frédéric THOMAS <we...@hotmail.com> wrote:
> +1 from me too, do you have an already made comparative table ?
>
> Frédéric THOMAS
>
> > From: joaopedromartinsfernandes@gmail.com
> > Date: Tue, 25 Feb 2014 14:53:04 +0000
> > Subject: Re: AW: Flex and server technology
> > To: dev@flex.apache.org
> >
> > Shouldn't we include other solutions besides Java based ones?
> > There is FluorineFx, PyAMF, WebOrb, AMFPHP, ZendAMF, RubyAMF,erlang-AMF
> etc
> > etc...
> >
> >
> > On 25 February 2014 14:27, Frédéric THOMAS <we...@hotmail.com>
> wrote:
> >
> > > I added your link to
> > >
> https://cwiki.apache.org/confluence/display/FLEX/Flex+Server+Technologies+-+Comparative+table
> > >
> > > That's definitly things to explore.
> > >
> > > Thanks,
> > > Frédéric THOMAS
> > >
> > > > From: webdoublefx@hotmail.com
> > > > To: dev@flex.apache.org
> > > > Subject: RE: AW: Flex and server technology
> > > > Date: Tue, 25 Feb 2014 14:12:25 +0000
> > > >
> > > > Hi Chris,
> > > >
> > > > Thanks for the link.
> > > >
> > > > Frédéric THOMAS
> > > >
> > > > > From: christofer.dutz@c-ware.de
> > > > > To: dev@flex.apache.org
> > > > > Subject: AW: Flex and server technology
> > > > > Date: Tue, 25 Feb 2014 13:58:37 +0000
> > > > >
> > > > > Just used Google a Little and found this page:
> > > > >
> > >
> http://blog.hiraash.org/2012/04/13/scaling-blazeds-with-servlet-3-concurrency/
> > > > > Seems the author summed up several approaches.
> > > > >
> > > > > Chris
> > > > >
> > > > >
> > > > > ________________________________________
> > > > > Von: Christofer Dutz <ch...@c-ware.de>
> > > > > Gesendet: Dienstag, 25. Februar 2014 14:54
> > > > > An: dev@flex.apache.org; paul.hastings@gmail.com
> > > > > Betreff: AW: Flex and server technology
> > > > >
> > > > > As far as I remember there were several Solutions utilizing Jettys
> > > properitary Continuation concept.
> > > > > I once started working on a Servlet 3 NIO AMF connector, but
> Project
> > > life sort of sucked all time I had away from me.
> > > > > Now with the Servlet api being official, this is one of the fist
> > > things I am hoping on getting dirty on as soon as BlazeDS is officially
> > > Apache :-)
> > > > >
> > > > > Chris
> > > > > ________________________________________
> > > > > Von: Paul Hastings <pa...@gmail.com>
> > > > > Gesendet: Dienstag, 25. Februar 2014 14:42
> > > > > An: dev@flex.apache.org
> > > > > Betreff: Re: Flex and server technology
> > > > >
> > > > > On 2/25/2014 7:46 PM, Frédéric THOMAS wrote:
> > > > > > It seems it was a project [1] done by the guy who wrote
> Professional
> > > BlazeDS
> > > > > > but can't see the source code anymore, maybe someone knows the
> > > current status
> > > > > > of this project and where it is hosted now if still or another
> > > thirdparty.
> > > > >
> > > > > seems there never was any source? the projects i looked thru only
> had
> > > the
> > > > > initial dir commits & nothing more. too bad, seems like some
> > > good/interesting ideas.
> > > > >
> > > > > > I don't know CF, it was not used that much in EU but feel free to
> > > amend /
> > > > > > annotate the wiki itself, I guess you've got the karma to do it,
> if
> > > not, just
> > > > > > ask it here :-)
> > > > >
> > > > > not 100% sure its appropriate for that list except maybe as more
> > > notes? anyways
> > > > > let it stew a few days.
> > > >
> > >
> > >
> >
> >
> >
> > --
> >
> > João Fernandes
>
>
--
João Fernandes
Re: AW: Flex and server technology
Posted by João Fernandes <jo...@gmail.com>.
It's hard to have a comparative table since a ruby or a .net will hardly
have integration with EJB, Spring etc :)
For example, FluorineFX does provide support for messaging with I/O
endpoints, (not sure fur NIO under HTTP), RTMP channels,
RemoteSharedObjects and FMS recording capabilities like Red5 and Wooza
which BlazeDS doesn't support.
It would be interesting to also list which ones are still under development
and not.
On 25 February 2014 15:07, Frédéric THOMAS <we...@hotmail.com> wrote:
> +1 from me too, do you have an already made comparative table ?
>
> Frédéric THOMAS
>
> > From: joaopedromartinsfernandes@gmail.com
> > Date: Tue, 25 Feb 2014 14:53:04 +0000
> > Subject: Re: AW: Flex and server technology
> > To: dev@flex.apache.org
> >
> > Shouldn't we include other solutions besides Java based ones?
> > There is FluorineFx, PyAMF, WebOrb, AMFPHP, ZendAMF, RubyAMF,erlang-AMF
> etc
> > etc...
> >
> >
> > On 25 February 2014 14:27, Frédéric THOMAS <we...@hotmail.com>
> wrote:
> >
> > > I added your link to
> > >
> https://cwiki.apache.org/confluence/display/FLEX/Flex+Server+Technologies+-+Comparative+table
> > >
> > > That's definitly things to explore.
> > >
> > > Thanks,
> > > Frédéric THOMAS
> > >
> > > > From: webdoublefx@hotmail.com
> > > > To: dev@flex.apache.org
> > > > Subject: RE: AW: Flex and server technology
> > > > Date: Tue, 25 Feb 2014 14:12:25 +0000
> > > >
> > > > Hi Chris,
> > > >
> > > > Thanks for the link.
> > > >
> > > > Frédéric THOMAS
> > > >
> > > > > From: christofer.dutz@c-ware.de
> > > > > To: dev@flex.apache.org
> > > > > Subject: AW: Flex and server technology
> > > > > Date: Tue, 25 Feb 2014 13:58:37 +0000
> > > > >
> > > > > Just used Google a Little and found this page:
> > > > >
> > >
> http://blog.hiraash.org/2012/04/13/scaling-blazeds-with-servlet-3-concurrency/
> > > > > Seems the author summed up several approaches.
> > > > >
> > > > > Chris
> > > > >
> > > > >
> > > > > ________________________________________
> > > > > Von: Christofer Dutz <ch...@c-ware.de>
> > > > > Gesendet: Dienstag, 25. Februar 2014 14:54
> > > > > An: dev@flex.apache.org; paul.hastings@gmail.com
> > > > > Betreff: AW: Flex and server technology
> > > > >
> > > > > As far as I remember there were several Solutions utilizing Jettys
> > > properitary Continuation concept.
> > > > > I once started working on a Servlet 3 NIO AMF connector, but
> Project
> > > life sort of sucked all time I had away from me.
> > > > > Now with the Servlet api being official, this is one of the fist
> > > things I am hoping on getting dirty on as soon as BlazeDS is officially
> > > Apache :-)
> > > > >
> > > > > Chris
> > > > > ________________________________________
> > > > > Von: Paul Hastings <pa...@gmail.com>
> > > > > Gesendet: Dienstag, 25. Februar 2014 14:42
> > > > > An: dev@flex.apache.org
> > > > > Betreff: Re: Flex and server technology
> > > > >
> > > > > On 2/25/2014 7:46 PM, Frédéric THOMAS wrote:
> > > > > > It seems it was a project [1] done by the guy who wrote
> Professional
> > > BlazeDS
> > > > > > but can't see the source code anymore, maybe someone knows the
> > > current status
> > > > > > of this project and where it is hosted now if still or another
> > > thirdparty.
> > > > >
> > > > > seems there never was any source? the projects i looked thru only
> had
> > > the
> > > > > initial dir commits & nothing more. too bad, seems like some
> > > good/interesting ideas.
> > > > >
> > > > > > I don't know CF, it was not used that much in EU but feel free to
> > > amend /
> > > > > > annotate the wiki itself, I guess you've got the karma to do it,
> if
> > > not, just
> > > > > > ask it here :-)
> > > > >
> > > > > not 100% sure its appropriate for that list except maybe as more
> > > notes? anyways
> > > > > let it stew a few days.
> > > >
> > >
> > >
> >
> >
> >
> > --
> >
> > João Fernandes
>
>
--
João Fernandes
RE: AW: Flex and server technology
Posted by Frédéric THOMAS <we...@hotmail.com>.
+1 from me too, do you have an already made comparative table ?
Frédéric THOMAS
> From: joaopedromartinsfernandes@gmail.com
> Date: Tue, 25 Feb 2014 14:53:04 +0000
> Subject: Re: AW: Flex and server technology
> To: dev@flex.apache.org
>
> Shouldn't we include other solutions besides Java based ones?
> There is FluorineFx, PyAMF, WebOrb, AMFPHP, ZendAMF, RubyAMF,erlang-AMF etc
> etc...
>
>
> On 25 February 2014 14:27, Frédéric THOMAS <we...@hotmail.com> wrote:
>
> > I added your link to
> > https://cwiki.apache.org/confluence/display/FLEX/Flex+Server+Technologies+-+Comparative+table
> >
> > That's definitly things to explore.
> >
> > Thanks,
> > Frédéric THOMAS
> >
> > > From: webdoublefx@hotmail.com
> > > To: dev@flex.apache.org
> > > Subject: RE: AW: Flex and server technology
> > > Date: Tue, 25 Feb 2014 14:12:25 +0000
> > >
> > > Hi Chris,
> > >
> > > Thanks for the link.
> > >
> > > Frédéric THOMAS
> > >
> > > > From: christofer.dutz@c-ware.de
> > > > To: dev@flex.apache.org
> > > > Subject: AW: Flex and server technology
> > > > Date: Tue, 25 Feb 2014 13:58:37 +0000
> > > >
> > > > Just used Google a Little and found this page:
> > > >
> > http://blog.hiraash.org/2012/04/13/scaling-blazeds-with-servlet-3-concurrency/
> > > > Seems the author summed up several approaches.
> > > >
> > > > Chris
> > > >
> > > >
> > > > ________________________________________
> > > > Von: Christofer Dutz <ch...@c-ware.de>
> > > > Gesendet: Dienstag, 25. Februar 2014 14:54
> > > > An: dev@flex.apache.org; paul.hastings@gmail.com
> > > > Betreff: AW: Flex and server technology
> > > >
> > > > As far as I remember there were several Solutions utilizing Jettys
> > properitary Continuation concept.
> > > > I once started working on a Servlet 3 NIO AMF connector, but Project
> > life sort of sucked all time I had away from me.
> > > > Now with the Servlet api being official, this is one of the fist
> > things I am hoping on getting dirty on as soon as BlazeDS is officially
> > Apache :-)
> > > >
> > > > Chris
> > > > ________________________________________
> > > > Von: Paul Hastings <pa...@gmail.com>
> > > > Gesendet: Dienstag, 25. Februar 2014 14:42
> > > > An: dev@flex.apache.org
> > > > Betreff: Re: Flex and server technology
> > > >
> > > > On 2/25/2014 7:46 PM, Frédéric THOMAS wrote:
> > > > > It seems it was a project [1] done by the guy who wrote Professional
> > BlazeDS
> > > > > but can't see the source code anymore, maybe someone knows the
> > current status
> > > > > of this project and where it is hosted now if still or another
> > thirdparty.
> > > >
> > > > seems there never was any source? the projects i looked thru only had
> > the
> > > > initial dir commits & nothing more. too bad, seems like some
> > good/interesting ideas.
> > > >
> > > > > I don't know CF, it was not used that much in EU but feel free to
> > amend /
> > > > > annotate the wiki itself, I guess you've got the karma to do it, if
> > not, just
> > > > > ask it here :-)
> > > >
> > > > not 100% sure its appropriate for that list except maybe as more
> > notes? anyways
> > > > let it stew a few days.
> > >
> >
> >
>
>
>
> --
>
> João Fernandes
Re: AW: Flex and server technology
Posted by João Fernandes <jo...@gmail.com>.
Shouldn't we include other solutions besides Java based ones?
There is FluorineFx, PyAMF, WebOrb, AMFPHP, ZendAMF, RubyAMF,erlang-AMF etc
etc...
On 25 February 2014 14:27, Frédéric THOMAS <we...@hotmail.com> wrote:
> I added your link to
> https://cwiki.apache.org/confluence/display/FLEX/Flex+Server+Technologies+-+Comparative+table
>
> That's definitly things to explore.
>
> Thanks,
> Frédéric THOMAS
>
> > From: webdoublefx@hotmail.com
> > To: dev@flex.apache.org
> > Subject: RE: AW: Flex and server technology
> > Date: Tue, 25 Feb 2014 14:12:25 +0000
> >
> > Hi Chris,
> >
> > Thanks for the link.
> >
> > Frédéric THOMAS
> >
> > > From: christofer.dutz@c-ware.de
> > > To: dev@flex.apache.org
> > > Subject: AW: Flex and server technology
> > > Date: Tue, 25 Feb 2014 13:58:37 +0000
> > >
> > > Just used Google a Little and found this page:
> > >
> http://blog.hiraash.org/2012/04/13/scaling-blazeds-with-servlet-3-concurrency/
> > > Seems the author summed up several approaches.
> > >
> > > Chris
> > >
> > >
> > > ________________________________________
> > > Von: Christofer Dutz <ch...@c-ware.de>
> > > Gesendet: Dienstag, 25. Februar 2014 14:54
> > > An: dev@flex.apache.org; paul.hastings@gmail.com
> > > Betreff: AW: Flex and server technology
> > >
> > > As far as I remember there were several Solutions utilizing Jettys
> properitary Continuation concept.
> > > I once started working on a Servlet 3 NIO AMF connector, but Project
> life sort of sucked all time I had away from me.
> > > Now with the Servlet api being official, this is one of the fist
> things I am hoping on getting dirty on as soon as BlazeDS is officially
> Apache :-)
> > >
> > > Chris
> > > ________________________________________
> > > Von: Paul Hastings <pa...@gmail.com>
> > > Gesendet: Dienstag, 25. Februar 2014 14:42
> > > An: dev@flex.apache.org
> > > Betreff: Re: Flex and server technology
> > >
> > > On 2/25/2014 7:46 PM, Frédéric THOMAS wrote:
> > > > It seems it was a project [1] done by the guy who wrote Professional
> BlazeDS
> > > > but can't see the source code anymore, maybe someone knows the
> current status
> > > > of this project and where it is hosted now if still or another
> thirdparty.
> > >
> > > seems there never was any source? the projects i looked thru only had
> the
> > > initial dir commits & nothing more. too bad, seems like some
> good/interesting ideas.
> > >
> > > > I don't know CF, it was not used that much in EU but feel free to
> amend /
> > > > annotate the wiki itself, I guess you've got the karma to do it, if
> not, just
> > > > ask it here :-)
> > >
> > > not 100% sure its appropriate for that list except maybe as more
> notes? anyways
> > > let it stew a few days.
> >
>
>
--
João Fernandes
RE: AW: Flex and server technology
Posted by Frédéric THOMAS <we...@hotmail.com>.
I added your link to https://cwiki.apache.org/confluence/display/FLEX/Flex+Server+Technologies+-+Comparative+table
That's definitly things to explore.
Thanks,
Frédéric THOMAS
> From: webdoublefx@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: AW: Flex and server technology
> Date: Tue, 25 Feb 2014 14:12:25 +0000
>
> Hi Chris,
>
> Thanks for the link.
>
> Frédéric THOMAS
>
> > From: christofer.dutz@c-ware.de
> > To: dev@flex.apache.org
> > Subject: AW: Flex and server technology
> > Date: Tue, 25 Feb 2014 13:58:37 +0000
> >
> > Just used Google a Little and found this page:
> > http://blog.hiraash.org/2012/04/13/scaling-blazeds-with-servlet-3-concurrency/
> > Seems the author summed up several approaches.
> >
> > Chris
> >
> >
> > ________________________________________
> > Von: Christofer Dutz <ch...@c-ware.de>
> > Gesendet: Dienstag, 25. Februar 2014 14:54
> > An: dev@flex.apache.org; paul.hastings@gmail.com
> > Betreff: AW: Flex and server technology
> >
> > As far as I remember there were several Solutions utilizing Jettys properitary Continuation concept.
> > I once started working on a Servlet 3 NIO AMF connector, but Project life sort of sucked all time I had away from me.
> > Now with the Servlet api being official, this is one of the fist things I am hoping on getting dirty on as soon as BlazeDS is officially Apache :-)
> >
> > Chris
> > ________________________________________
> > Von: Paul Hastings <pa...@gmail.com>
> > Gesendet: Dienstag, 25. Februar 2014 14:42
> > An: dev@flex.apache.org
> > Betreff: Re: Flex and server technology
> >
> > On 2/25/2014 7:46 PM, Frédéric THOMAS wrote:
> > > It seems it was a project [1] done by the guy who wrote Professional BlazeDS
> > > but can't see the source code anymore, maybe someone knows the current status
> > > of this project and where it is hosted now if still or another thirdparty.
> >
> > seems there never was any source? the projects i looked thru only had the
> > initial dir commits & nothing more. too bad, seems like some good/interesting ideas.
> >
> > > I don't know CF, it was not used that much in EU but feel free to amend /
> > > annotate the wiki itself, I guess you've got the karma to do it, if not, just
> > > ask it here :-)
> >
> > not 100% sure its appropriate for that list except maybe as more notes? anyways
> > let it stew a few days.
>
RE: AW: Flex and server technology
Posted by Frédéric THOMAS <we...@hotmail.com>.
Hi Chris,
Thanks for the link.
Frédéric THOMAS
> From: christofer.dutz@c-ware.de
> To: dev@flex.apache.org
> Subject: AW: Flex and server technology
> Date: Tue, 25 Feb 2014 13:58:37 +0000
>
> Just used Google a Little and found this page:
> http://blog.hiraash.org/2012/04/13/scaling-blazeds-with-servlet-3-concurrency/
> Seems the author summed up several approaches.
>
> Chris
>
>
> ________________________________________
> Von: Christofer Dutz <ch...@c-ware.de>
> Gesendet: Dienstag, 25. Februar 2014 14:54
> An: dev@flex.apache.org; paul.hastings@gmail.com
> Betreff: AW: Flex and server technology
>
> As far as I remember there were several Solutions utilizing Jettys properitary Continuation concept.
> I once started working on a Servlet 3 NIO AMF connector, but Project life sort of sucked all time I had away from me.
> Now with the Servlet api being official, this is one of the fist things I am hoping on getting dirty on as soon as BlazeDS is officially Apache :-)
>
> Chris
> ________________________________________
> Von: Paul Hastings <pa...@gmail.com>
> Gesendet: Dienstag, 25. Februar 2014 14:42
> An: dev@flex.apache.org
> Betreff: Re: Flex and server technology
>
> On 2/25/2014 7:46 PM, Frédéric THOMAS wrote:
> > It seems it was a project [1] done by the guy who wrote Professional BlazeDS
> > but can't see the source code anymore, maybe someone knows the current status
> > of this project and where it is hosted now if still or another thirdparty.
>
> seems there never was any source? the projects i looked thru only had the
> initial dir commits & nothing more. too bad, seems like some good/interesting ideas.
>
> > I don't know CF, it was not used that much in EU but feel free to amend /
> > annotate the wiki itself, I guess you've got the karma to do it, if not, just
> > ask it here :-)
>
> not 100% sure its appropriate for that list except maybe as more notes? anyways
> let it stew a few days.
AW: Flex and server technology
Posted by Christofer Dutz <ch...@c-ware.de>.
Just used Google a Little and found this page:
http://blog.hiraash.org/2012/04/13/scaling-blazeds-with-servlet-3-concurrency/
Seems the author summed up several approaches.
Chris
________________________________________
Von: Christofer Dutz <ch...@c-ware.de>
Gesendet: Dienstag, 25. Februar 2014 14:54
An: dev@flex.apache.org; paul.hastings@gmail.com
Betreff: AW: Flex and server technology
As far as I remember there were several Solutions utilizing Jettys properitary Continuation concept.
I once started working on a Servlet 3 NIO AMF connector, but Project life sort of sucked all time I had away from me.
Now with the Servlet api being official, this is one of the fist things I am hoping on getting dirty on as soon as BlazeDS is officially Apache :-)
Chris
________________________________________
Von: Paul Hastings <pa...@gmail.com>
Gesendet: Dienstag, 25. Februar 2014 14:42
An: dev@flex.apache.org
Betreff: Re: Flex and server technology
On 2/25/2014 7:46 PM, Frédéric THOMAS wrote:
> It seems it was a project [1] done by the guy who wrote Professional BlazeDS
> but can't see the source code anymore, maybe someone knows the current status
> of this project and where it is hosted now if still or another thirdparty.
seems there never was any source? the projects i looked thru only had the
initial dir commits & nothing more. too bad, seems like some good/interesting ideas.
> I don't know CF, it was not used that much in EU but feel free to amend /
> annotate the wiki itself, I guess you've got the karma to do it, if not, just
> ask it here :-)
not 100% sure its appropriate for that list except maybe as more notes? anyways
let it stew a few days.
AW: Flex and server technology
Posted by Christofer Dutz <ch...@c-ware.de>.
As far as I remember there were several Solutions utilizing Jettys properitary Continuation concept.
I once started working on a Servlet 3 NIO AMF connector, but Project life sort of sucked all time I had away from me.
Now with the Servlet api being official, this is one of the fist things I am hoping on getting dirty on as soon as BlazeDS is officially Apache :-)
Chris
________________________________________
Von: Paul Hastings <pa...@gmail.com>
Gesendet: Dienstag, 25. Februar 2014 14:42
An: dev@flex.apache.org
Betreff: Re: Flex and server technology
On 2/25/2014 7:46 PM, Frédéric THOMAS wrote:
> It seems it was a project [1] done by the guy who wrote Professional BlazeDS
> but can't see the source code anymore, maybe someone knows the current status
> of this project and where it is hosted now if still or another thirdparty.
seems there never was any source? the projects i looked thru only had the
initial dir commits & nothing more. too bad, seems like some good/interesting ideas.
> I don't know CF, it was not used that much in EU but feel free to amend /
> annotate the wiki itself, I guess you've got the karma to do it, if not, just
> ask it here :-)
not 100% sure its appropriate for that list except maybe as more notes? anyways
let it stew a few days.
Re: Flex and server technology
Posted by Paul Hastings <pa...@gmail.com>.
On 2/25/2014 7:46 PM, Frédéric THOMAS wrote:
> It seems it was a project [1] done by the guy who wrote Professional BlazeDS
> but can't see the source code anymore, maybe someone knows the current status
> of this project and where it is hosted now if still or another thirdparty.
seems there never was any source? the projects i looked thru only had the
initial dir commits & nothing more. too bad, seems like some good/interesting ideas.
> I don't know CF, it was not used that much in EU but feel free to amend /
> annotate the wiki itself, I guess you've got the karma to do it, if not, just
> ask it here :-)
not 100% sure its appropriate for that list except maybe as more notes? anyways
let it stew a few days.
RE: Flex and server technology
Posted by Frédéric THOMAS <we...@hotmail.com>.
Hi Paul,
Thanks for your comments.
> for blazeDS's "Non-blocking I/O http long-polling", what would the "Possible
> with some third party extensions" actually be?
It seems it was a project [1] done by the guy who wrote Professional BlazeDS but can't see the source code anymore, maybe someone knows the current status of this project and where it is hosted now if still or another thirdparty.
I don't know CF, it was not used that much in EU but feel free to amend / annotate the wiki itself, I guess you've got the karma to do it, if not, just ask it here :-)
Frédéric THOMAS
[1] http://code.google.com/p/dsadapters/
> Date: Tue, 25 Feb 2014 10:44:34 +0700
> From: paul.hastings@gmail.com
> To: dev@flex.apache.org
> Subject: Re: Flex and server technology
>
> On 2/25/2014 6:33 AM, Fr�d�ric THOMAS wrote:
> > Done !
> >
> > Feel free to comment or amend.
> >
> > https://cwiki.apache.org/confluence/display/FLEX/Flex+Server+Technologies+-+Comparative+table
>
> for blazeDS's "Non-blocking I/O http long-polling", what would the "Possible
> with some third party extensions" actually be?
>
> not sure if this appropriate but for "Data paging" & "Data
> synchonization/conflict resolution" you can go a long way using coldfusion
> (which uses blazeDS) to handle those bits--though have to basically code much of
> those yourself.
>
> i guess the same would apply to spring (via a couple-three OS cf projects) &
> hibernate (built-into coldfusion).
>
> for me coldfusion & flex go together like a peanut butter & jelly sandwich ;-)
>
>
Re: Flex and server technology
Posted by Paul Hastings <pa...@gmail.com>.
On 2/25/2014 6:33 AM, Fr�d�ric THOMAS wrote:
> Done !
>
> Feel free to comment or amend.
>
> https://cwiki.apache.org/confluence/display/FLEX/Flex+Server+Technologies+-+Comparative+table
for blazeDS's "Non-blocking I/O http long-polling", what would the "Possible
with some third party extensions" actually be?
not sure if this appropriate but for "Data paging" & "Data
synchonization/conflict resolution" you can go a long way using coldfusion
(which uses blazeDS) to handle those bits--though have to basically code much of
those yourself.
i guess the same would apply to spring (via a couple-three OS cf projects) &
hibernate (built-into coldfusion).
for me coldfusion & flex go together like a peanut butter & jelly sandwich ;-)
RE: Flex and server technology
Posted by Frédéric THOMAS <we...@hotmail.com>.
Done !
Feel free to comment or amend.
https://cwiki.apache.org/confluence/display/FLEX/Flex+Server+Technologies+-+Comparative+table
Thanks,
Frédéric THOMAS
> From: bigosmallm@gmail.com
> Date: Sun, 16 Feb 2014 12:10:55 -0800
> Subject: Re: Flex and server technology
> To: dev@flex.apache.org
>
> Fred, this looks fine to me. I had assumed that this was going to be more
> of an editorial commentary. This looks like a straightforward feature
> comparison table.
> +1 from me.
>
> Thanks for the clarification.
>
> Om
>
>
> On Sun, Feb 16, 2014 at 10:05 AM, Frédéric THOMAS
> <we...@hotmail.com>wrote:
>
> > Well, it was well printed, this link should work though.
> >
> >
> > https://docs.google.com/spreadsheet/ccc?key=0AkSnI9jZINzGdExMRlc0cTkzNWJ4UjNiWTVJM1piM3c#gid=0
> >
> > Frédéric THOMAS
> >
> > > From: webdoublefx@hotmail.com
> > > To: dev@flex.apache.org
> > > Subject: RE: Flex and server technology
> > > Date: Sun, 16 Feb 2014 17:53:06 +0000
> > >
> > > Hi,
> > >
> > > @Alex, good news :-)
> > >
> > > @Om, Not sure I follow you, could please review what I was describing
> > and tell me if it was what you thought ? (I hope that will be printed
> > correctly)
> > >
> > >
> > > BlazeDSLCDSGraniteDSFramework integrationSpring(1)xxEJB 3
> > >
> > > xCDI
> > >
> > > xJPA engine supportHibernate(2)xxEclipseLink
> > >
> > > xOpenJPA
> > >
> > > xDataNucleus
> > >
> > > xMessaging (real-time)Blocking I/O http long-pollingxxxBlocking I/O http
> > streamingxx
> > > Non-blocking I/O http long-polling(3)xxNon-blocking I/O http
> > streaming(3)x
> > > RTMP
> > > x
> > > WebSocket
> > >
> > > xUDP
> > >
> > > xData managementBean validation
> > >
> > > xBig numbers
> > >
> > > xCode generation
> > > xxData paging
> > > xxData synchonization / conflict resolution
> > > xxDisconnected mode
> > > xplannedOthersMonitoring
> > > x
> > > Load testing tools(4)(4)(4)PDF generation
> > > x
> > > LicensingOpen sourcex
> > > xCommercial
> > > xx
> > >
> > >
> > >
> > > 1 - Using the project Spring-Flex2 - Partial support in Spring-Flex or
> > dpHibernate3 - Possible with some third party extensions4 - Supported by
> > NeoLoad, HP LoadRunner, IBM Rational Performance Tester
> > >
> > > Frédéric THOMAS
> > >
> > > > Date: Sun, 16 Feb 2014 09:29:56 -0800
> > > > Subject: Re: Flex and server technology
> > > > From: bigosmallm@gmail.com
> > > > To: dev@flex.apache.org
> > > >
> > > > On Feb 16, 2014 3:25 AM, "Frédéric THOMAS" <we...@hotmail.com>
> > wrote:
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Hi,
> > > > >
> > > > > I have a comparative feature table for BlazeDS / LCDS / GraniteDS,
> > given
> > > > some people are asking about it at time, do you think it is something
> > that
> > > > could fit on our wiki ?
> > > >
> > > > -1
> > > >
> > > > If it were just a listing instead of a comparison, that would be fine.
> > > >
> > > > Given that we will be controlling BlazeDS as part of Apache Flex, it
> > may
> > > > not be fair to GraniteDS or LCDS. We should avoid even the appearance
> > of
> > > > favoritism.
> > > >
> > > > It might be better to put this up on your personal blog.
> > > >
> > > > Thanks,
> > > > Om
> > > >
> > > > >
> > > > > Thanks,
> > > > > Frédéric THOMAS
> > > > >
> > >
> >
> >
Re: Flex and server technology
Posted by OmPrakash Muppirala <bi...@gmail.com>.
Fred, this looks fine to me. I had assumed that this was going to be more
of an editorial commentary. This looks like a straightforward feature
comparison table.
+1 from me.
Thanks for the clarification.
Om
On Sun, Feb 16, 2014 at 10:05 AM, Frédéric THOMAS
<we...@hotmail.com>wrote:
> Well, it was well printed, this link should work though.
>
>
> https://docs.google.com/spreadsheet/ccc?key=0AkSnI9jZINzGdExMRlc0cTkzNWJ4UjNiWTVJM1piM3c#gid=0
>
> Frédéric THOMAS
>
> > From: webdoublefx@hotmail.com
> > To: dev@flex.apache.org
> > Subject: RE: Flex and server technology
> > Date: Sun, 16 Feb 2014 17:53:06 +0000
> >
> > Hi,
> >
> > @Alex, good news :-)
> >
> > @Om, Not sure I follow you, could please review what I was describing
> and tell me if it was what you thought ? (I hope that will be printed
> correctly)
> >
> >
> > BlazeDSLCDSGraniteDSFramework integrationSpring(1)xxEJB 3
> >
> > xCDI
> >
> > xJPA engine supportHibernate(2)xxEclipseLink
> >
> > xOpenJPA
> >
> > xDataNucleus
> >
> > xMessaging (real-time)Blocking I/O http long-pollingxxxBlocking I/O http
> streamingxx
> > Non-blocking I/O http long-polling(3)xxNon-blocking I/O http
> streaming(3)x
> > RTMP
> > x
> > WebSocket
> >
> > xUDP
> >
> > xData managementBean validation
> >
> > xBig numbers
> >
> > xCode generation
> > xxData paging
> > xxData synchonization / conflict resolution
> > xxDisconnected mode
> > xplannedOthersMonitoring
> > x
> > Load testing tools(4)(4)(4)PDF generation
> > x
> > LicensingOpen sourcex
> > xCommercial
> > xx
> >
> >
> >
> > 1 - Using the project Spring-Flex2 - Partial support in Spring-Flex or
> dpHibernate3 - Possible with some third party extensions4 - Supported by
> NeoLoad, HP LoadRunner, IBM Rational Performance Tester
> >
> > Frédéric THOMAS
> >
> > > Date: Sun, 16 Feb 2014 09:29:56 -0800
> > > Subject: Re: Flex and server technology
> > > From: bigosmallm@gmail.com
> > > To: dev@flex.apache.org
> > >
> > > On Feb 16, 2014 3:25 AM, "Frédéric THOMAS" <we...@hotmail.com>
> wrote:
> > > >
> > > >
> > > >
> > > >
> > > > Hi,
> > > >
> > > > I have a comparative feature table for BlazeDS / LCDS / GraniteDS,
> given
> > > some people are asking about it at time, do you think it is something
> that
> > > could fit on our wiki ?
> > >
> > > -1
> > >
> > > If it were just a listing instead of a comparison, that would be fine.
> > >
> > > Given that we will be controlling BlazeDS as part of Apache Flex, it
> may
> > > not be fair to GraniteDS or LCDS. We should avoid even the appearance
> of
> > > favoritism.
> > >
> > > It might be better to put this up on your personal blog.
> > >
> > > Thanks,
> > > Om
> > >
> > > >
> > > > Thanks,
> > > > Frédéric THOMAS
> > > >
> >
>
>
RE: Flex and server technology
Posted by Frédéric THOMAS <we...@hotmail.com>.
Well, it was well printed, this link should work though.
https://docs.google.com/spreadsheet/ccc?key=0AkSnI9jZINzGdExMRlc0cTkzNWJ4UjNiWTVJM1piM3c#gid=0
Frédéric THOMAS
> From: webdoublefx@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: Flex and server technology
> Date: Sun, 16 Feb 2014 17:53:06 +0000
>
> Hi,
>
> @Alex, good news :-)
>
> @Om, Not sure I follow you, could please review what I was describing and tell me if it was what you thought ? (I hope that will be printed correctly)
>
>
> BlazeDSLCDSGraniteDSFramework integrationSpring(1)xxEJB 3
>
> xCDI
>
> xJPA engine supportHibernate(2)xxEclipseLink
>
> xOpenJPA
>
> xDataNucleus
>
> xMessaging (real-time)Blocking I/O http long-pollingxxxBlocking I/O http streamingxx
> Non-blocking I/O http long-polling(3)xxNon-blocking I/O http streaming(3)x
> RTMP
> x
> WebSocket
>
> xUDP
>
> xData managementBean validation
>
> xBig numbers
>
> xCode generation
> xxData paging
> xxData synchonization / conflict resolution
> xxDisconnected mode
> xplannedOthersMonitoring
> x
> Load testing tools(4)(4)(4)PDF generation
> x
> LicensingOpen sourcex
> xCommercial
> xx
>
>
>
> 1 - Using the project Spring-Flex2 - Partial support in Spring-Flex or dpHibernate3 - Possible with some third party extensions4 - Supported by NeoLoad, HP LoadRunner, IBM Rational Performance Tester
>
> Frédéric THOMAS
>
> > Date: Sun, 16 Feb 2014 09:29:56 -0800
> > Subject: Re: Flex and server technology
> > From: bigosmallm@gmail.com
> > To: dev@flex.apache.org
> >
> > On Feb 16, 2014 3:25 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
> > >
> > >
> > >
> > >
> > > Hi,
> > >
> > > I have a comparative feature table for BlazeDS / LCDS / GraniteDS, given
> > some people are asking about it at time, do you think it is something that
> > could fit on our wiki ?
> >
> > -1
> >
> > If it were just a listing instead of a comparison, that would be fine.
> >
> > Given that we will be controlling BlazeDS as part of Apache Flex, it may
> > not be fair to GraniteDS or LCDS. We should avoid even the appearance of
> > favoritism.
> >
> > It might be better to put this up on your personal blog.
> >
> > Thanks,
> > Om
> >
> > >
> > > Thanks,
> > > Frédéric THOMAS
> > >
>
RE: Flex and server technology
Posted by Frédéric THOMAS <we...@hotmail.com>.
Hi,
@Alex, good news :-)
@Om, Not sure I follow you, could please review what I was describing and tell me if it was what you thought ? (I hope that will be printed correctly)
BlazeDSLCDSGraniteDSFramework integrationSpring(1)xxEJB 3
xCDI
xJPA engine supportHibernate(2)xxEclipseLink
xOpenJPA
xDataNucleus
xMessaging (real-time)Blocking I/O http long-pollingxxxBlocking I/O http streamingxx
Non-blocking I/O http long-polling(3)xxNon-blocking I/O http streaming(3)x
RTMP
x
WebSocket
xUDP
xData managementBean validation
xBig numbers
xCode generation
xxData paging
xxData synchonization / conflict resolution
xxDisconnected mode
xplannedOthersMonitoring
x
Load testing tools(4)(4)(4)PDF generation
x
LicensingOpen sourcex
xCommercial
xx
1 - Using the project Spring-Flex2 - Partial support in Spring-Flex or dpHibernate3 - Possible with some third party extensions4 - Supported by NeoLoad, HP LoadRunner, IBM Rational Performance Tester
Frédéric THOMAS
> Date: Sun, 16 Feb 2014 09:29:56 -0800
> Subject: Re: Flex and server technology
> From: bigosmallm@gmail.com
> To: dev@flex.apache.org
>
> On Feb 16, 2014 3:25 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
> >
> >
> >
> >
> > Hi,
> >
> > I have a comparative feature table for BlazeDS / LCDS / GraniteDS, given
> some people are asking about it at time, do you think it is something that
> could fit on our wiki ?
>
> -1
>
> If it were just a listing instead of a comparison, that would be fine.
>
> Given that we will be controlling BlazeDS as part of Apache Flex, it may
> not be fair to GraniteDS or LCDS. We should avoid even the appearance of
> favoritism.
>
> It might be better to put this up on your personal blog.
>
> Thanks,
> Om
>
> >
> > Thanks,
> > Frédéric THOMAS
> >
Re: Flex and server technology
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Feb 16, 2014 3:25 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
>
>
>
>
> Hi,
>
> I have a comparative feature table for BlazeDS / LCDS / GraniteDS, given
some people are asking about it at time, do you think it is something that
could fit on our wiki ?
-1
If it were just a listing instead of a comparison, that would be fine.
Given that we will be controlling BlazeDS as part of Apache Flex, it may
not be fair to GraniteDS or LCDS. We should avoid even the appearance of
favoritism.
It might be better to put this up on your personal blog.
Thanks,
Om
>
> Thanks,
> Frédéric THOMAS
>
AW: Flex and server technology
Posted by Christofer Dutz <ch...@c-ware.de>.
+1
And what is the current state of the BlazeDS donation anyway?
-----Ursprüngliche Nachricht-----
Von: Frédéric THOMAS [mailto:webdoublefx@hotmail.com]
Gesendet: Sonntag, 16. Februar 2014 12:24
An: dev@flex.apache.org
Betreff: Flex and server technology
Hi,
I have a comparative feature table for BlazeDS / LCDS / GraniteDS, given some people are asking about it at time, do you think it is something that could fit on our wiki ?
Thanks,
Frédéric THOMAS
Flex and server technology
Posted by Frédéric THOMAS <we...@hotmail.com>.
Hi,
I have a comparative feature table for BlazeDS / LCDS / GraniteDS, given some people are asking about it at time, do you think it is something that could fit on our wiki ?
Thanks,
Frédéric THOMAS
RE: IOS7 status bar management ( FLEX-33860)
Posted by Maurice Amsellem <ma...@systar.com>.
>is it recommended to go online with the 4.12.0 SDK ? I mean to update my application to Apple store and Google android store with 4.12 SDK ?
4.12 RC1, as it's name implies, is not a final release, and it may coming residual bugs.
You can decide to use it on the AppStore, but it's under your own responsibility.
If you want to stay on 4.11 with custom skin, this is how it's done in 4.12 ViewNavigatorApplicationSkin:
https://github.com/apache/flex-sdk/blob/develop/frameworks/projects/mobiletheme/src/spark/skins/mobile/ViewNavigatorApplicationSkin.as
Look at the code in layoutContents
Maurice
-----Message d'origine-----
De : Rami Tarabay [mailto:rtarabay@codefish.com]
Envoyé : vendredi 14 février 2014 11:06
À : dev@flex.apache.org
Objet : Re: IOS7 status bar management ( FLEX-33860)
Hi,
Thanks for your reply.
I can get the 4.12.0 RC1(dev use only), but is it recommended to go online with the 4.12.0 SDK ? I mean to update my application to Apple store and Google android store with 4.12 SDK ?.
Extending ViewNavigatorApplicationSkin it is already done.
I am overriding drawBackground function to add landscape Background image, portrait Background image, busy Indicator and popUp.
I have tried to setStyle("paddingTop") inside the drawBackground function and did not work.
I did the override to the function createChildren and setStyle to
navigator: navigator.setStyle("paddingTop",40) and did not work.
Any suggestions ?
Best,
On Fri, Feb 14, 2014 at 11:02 AM, Maurice Amsellem < maurice.amsellem@systar.com> wrote:
> Hi Rami,
>
> If you can get the 4.12 SDK nightly, iOS7 status bar is managed
> automatically.
>
> If you can't:
> Regarding your code below, it does not work because everything happens
> in the skin (ViewNavigatorApplicationSkin), so it's there where you
> should shift your view.
> So make a custom skin, and shift the content (navigator skinPart).
>
> HTH
>
> Maurice
>
> -----Message d'origine-----
> De : Rami Tarabay [mailto:rtarabay@codefish.com] Envoyé : vendredi 14
> février 2014 09:49 À : dev@flex.apache.org Objet : Re: IOS7 status bar
> management ( FLEX-33860)
>
> Hi,
>
> I'm using flex 4.11 SDK with adobe air 4.0 and flash player 12.0 I'm
> trying to paddingTop my entire ViewNavigatorApplication on
> creationComplete or on drawbackground and it is not working.
>
> protected function
> abstractmainview1_creationCompleteHandler(event:FlexEvent):void
> {
> var osInfo:Array = Capabilities.os.split(" ");
> var versionNumber:Number = parseFloat(osInfo[2]);
>
> if(versionNumber >= 7) {
> var t:Number = height>=960 ? 40 : 20;
> // setStyle("top",t);
> setStyle("paddingTop",t);
>
> }
> }
>
> Any workaround ?!
>
>
> On Tue, Dec 3, 2013 at 3:18 AM, Maurice Amsellem <
> maurice.amsellem@systar.com> wrote:
>
> > Thanks
> >
> > -----Message d'origine-----
> > De : Justin Mclean [mailto:justin@classsoftware.com] Envoyé : mardi
> > 3 décembre 2013 01:33 À : dev@flex.apache.org Objet : Re: IOS7
> > status bar management ( FLEX-33860)
> >
> > Hi,
> >
> > I think the proposed solution is a good compromise, we need to be
> > able to support iOS7, and as noted other framework are also having
> > this exact same issue. It's almost like Apple only wants you to only
> > write native apps :-)
> >
> > > The main and simple reason for that is am physically exhausted.
> > Feel free to take a break or go slow for a while, you don't have to
> > fix something every day. Plus it makes the rest of us look lazy :-)
> >
> > Thanks,
> > Justin
> >
> >
>
>
> --
>
> Kind Regards,
>
>
> Rami Tarabay
>
>
>
> Mobile App Developer | Codefish Apps | www.codefish.com
>
> t +961 5 450824 | m +961 70 170857
>
--
Kind Regards,
Rami Tarabay
Mobile App Developer | Codefish Apps | www.codefish.com
t +961 5 450824 | m +961 70 170857
Re: IOS7 status bar management ( FLEX-33860)
Posted by Rami Tarabay <rt...@codefish.com>.
Hi,
Thanks for your reply.
I can get the 4.12.0 RC1(dev use only), but is it recommended to go online
with the 4.12.0 SDK ? I mean to update my application to Apple store and
Google android store with 4.12 SDK ?.
Extending ViewNavigatorApplicationSkin it is already done.
I am overriding drawBackground function to add landscape Background image,
portrait Background image, busy Indicator and popUp.
I have tried to setStyle("paddingTop") inside the drawBackground function
and did not work.
I did the override to the function createChildren and setStyle to
navigator: navigator.setStyle("paddingTop",40) and did not work.
Any suggestions ?
Best,
On Fri, Feb 14, 2014 at 11:02 AM, Maurice Amsellem <
maurice.amsellem@systar.com> wrote:
> Hi Rami,
>
> If you can get the 4.12 SDK nightly, iOS7 status bar is managed
> automatically.
>
> If you can't:
> Regarding your code below, it does not work because everything happens in
> the skin (ViewNavigatorApplicationSkin), so it's there where you should
> shift your view.
> So make a custom skin, and shift the content (navigator skinPart).
>
> HTH
>
> Maurice
>
> -----Message d'origine-----
> De : Rami Tarabay [mailto:rtarabay@codefish.com]
> Envoyé : vendredi 14 février 2014 09:49
> À : dev@flex.apache.org
> Objet : Re: IOS7 status bar management ( FLEX-33860)
>
> Hi,
>
> I'm using flex 4.11 SDK with adobe air 4.0 and flash player 12.0 I'm
> trying to paddingTop my entire ViewNavigatorApplication on creationComplete
> or on drawbackground and it is not working.
>
> protected function
> abstractmainview1_creationCompleteHandler(event:FlexEvent):void
> {
> var osInfo:Array = Capabilities.os.split(" ");
> var versionNumber:Number = parseFloat(osInfo[2]);
>
> if(versionNumber >= 7) {
> var t:Number = height>=960 ? 40 : 20;
> // setStyle("top",t);
> setStyle("paddingTop",t);
>
> }
> }
>
> Any workaround ?!
>
>
> On Tue, Dec 3, 2013 at 3:18 AM, Maurice Amsellem <
> maurice.amsellem@systar.com> wrote:
>
> > Thanks
> >
> > -----Message d'origine-----
> > De : Justin Mclean [mailto:justin@classsoftware.com] Envoyé : mardi 3
> > décembre 2013 01:33 À : dev@flex.apache.org Objet : Re: IOS7 status
> > bar management ( FLEX-33860)
> >
> > Hi,
> >
> > I think the proposed solution is a good compromise, we need to be able
> > to support iOS7, and as noted other framework are also having this
> > exact same issue. It's almost like Apple only wants you to only write
> > native apps :-)
> >
> > > The main and simple reason for that is am physically exhausted.
> > Feel free to take a break or go slow for a while, you don't have to
> > fix something every day. Plus it makes the rest of us look lazy :-)
> >
> > Thanks,
> > Justin
> >
> >
>
>
> --
>
> Kind Regards,
>
>
> Rami Tarabay
>
>
>
> Mobile App Developer | Codefish Apps | www.codefish.com
>
> t +961 5 450824 | m +961 70 170857
>
--
Kind Regards,
Rami Tarabay
Mobile App Developer | Codefish Apps | www.codefish.com
t +961 5 450824 | m +961 70 170857
RE: IOS7 status bar management ( FLEX-33860)
Posted by Maurice Amsellem <ma...@systar.com>.
Hi Rami,
If you can get the 4.12 SDK nightly, iOS7 status bar is managed automatically.
If you can't:
Regarding your code below, it does not work because everything happens in the skin (ViewNavigatorApplicationSkin), so it's there where you should shift your view.
So make a custom skin, and shift the content (navigator skinPart).
HTH
Maurice
-----Message d'origine-----
De : Rami Tarabay [mailto:rtarabay@codefish.com]
Envoyé : vendredi 14 février 2014 09:49
À : dev@flex.apache.org
Objet : Re: IOS7 status bar management ( FLEX-33860)
Hi,
I'm using flex 4.11 SDK with adobe air 4.0 and flash player 12.0 I'm trying to paddingTop my entire ViewNavigatorApplication on creationComplete or on drawbackground and it is not working.
protected function
abstractmainview1_creationCompleteHandler(event:FlexEvent):void
{
var osInfo:Array = Capabilities.os.split(" ");
var versionNumber:Number = parseFloat(osInfo[2]);
if(versionNumber >= 7) {
var t:Number = height>=960 ? 40 : 20;
// setStyle("top",t);
setStyle("paddingTop",t);
}
}
Any workaround ?!
On Tue, Dec 3, 2013 at 3:18 AM, Maurice Amsellem < maurice.amsellem@systar.com> wrote:
> Thanks
>
> -----Message d'origine-----
> De : Justin Mclean [mailto:justin@classsoftware.com] Envoyé : mardi 3
> décembre 2013 01:33 À : dev@flex.apache.org Objet : Re: IOS7 status
> bar management ( FLEX-33860)
>
> Hi,
>
> I think the proposed solution is a good compromise, we need to be able
> to support iOS7, and as noted other framework are also having this
> exact same issue. It's almost like Apple only wants you to only write
> native apps :-)
>
> > The main and simple reason for that is am physically exhausted.
> Feel free to take a break or go slow for a while, you don't have to
> fix something every day. Plus it makes the rest of us look lazy :-)
>
> Thanks,
> Justin
>
>
--
Kind Regards,
Rami Tarabay
Mobile App Developer | Codefish Apps | www.codefish.com
t +961 5 450824 | m +961 70 170857
Re: IOS7 status bar management ( FLEX-33860)
Posted by Rami Tarabay <rt...@codefish.com>.
Hi,
I'm using flex 4.11 SDK with adobe air 4.0 and flash player 12.0
I'm trying to paddingTop my entire ViewNavigatorApplication on
creationComplete or on drawbackground and it is not working.
protected function
abstractmainview1_creationCompleteHandler(event:FlexEvent):void
{
var osInfo:Array = Capabilities.os.split(" ");
var versionNumber:Number = parseFloat(osInfo[2]);
if(versionNumber >= 7) {
var t:Number = height>=960 ? 40 : 20;
// setStyle("top",t);
setStyle("paddingTop",t);
}
}
Any workaround ?!
On Tue, Dec 3, 2013 at 3:18 AM, Maurice Amsellem <
maurice.amsellem@systar.com> wrote:
> Thanks
>
> -----Message d'origine-----
> De : Justin Mclean [mailto:justin@classsoftware.com]
> Envoyé : mardi 3 décembre 2013 01:33
> À : dev@flex.apache.org
> Objet : Re: IOS7 status bar management ( FLEX-33860)
>
> Hi,
>
> I think the proposed solution is a good compromise, we need to be able to
> support iOS7, and as noted other framework are also having this exact same
> issue. It's almost like Apple only wants you to only write native apps :-)
>
> > The main and simple reason for that is am physically exhausted.
> Feel free to take a break or go slow for a while, you don't have to fix
> something every day. Plus it makes the rest of us look lazy :-)
>
> Thanks,
> Justin
>
>
--
Kind Regards,
Rami Tarabay
Mobile App Developer | Codefish Apps | www.codefish.com
t +961 5 450824 | m +961 70 170857
RE: IOS7 status bar management ( FLEX-33860)
Posted by Maurice Amsellem <ma...@systar.com>.
Thanks
-----Message d'origine-----
De : Justin Mclean [mailto:justin@classsoftware.com]
Envoyé : mardi 3 décembre 2013 01:33
À : dev@flex.apache.org
Objet : Re: IOS7 status bar management ( FLEX-33860)
Hi,
I think the proposed solution is a good compromise, we need to be able to support iOS7, and as noted other framework are also having this exact same issue. It's almost like Apple only wants you to only write native apps :-)
> The main and simple reason for that is am physically exhausted.
Feel free to take a break or go slow for a while, you don't have to fix something every day. Plus it makes the rest of us look lazy :-)
Thanks,
Justin
Re: IOS7 status bar management ( FLEX-33860)
Posted by Alex Harui <ah...@adobe.com>.
On 12/2/13 4:32 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>>The main and simple reason for that is am physically exhausted.
>Feel free to take a break or go slow for a while, you don't have to fix
>something every day. Plus it makes the rest of us look lazy :-)
Yes, definitely.
-Alex
Re: IOS7 status bar management ( FLEX-33860)
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
I think the proposed solution is a good compromise, we need to be able to support iOS7, and as noted other framework are also having this exact same issue. It's almost like Apple only wants you to only write native apps :-)
> The main and simple reason for that is am physically exhausted.
Feel free to take a break or go slow for a while, you don't have to fix something every day. Plus it makes the rest of us look lazy :-)
Thanks,
Justin
RE: IOS7 status bar management ( FLEX-33860)
Posted by Maurice Amsellem <ma...@systar.com>.
>Again, I don't really understand this particular issue, but why don't other non-Flex IOS apps have to react to this difference when running on IOS? Or are they?
As Om said, many non-native iOS frameworks are dealing with this issue.
Even iOS native apps developers are "annoyed" by this change.
Alex,
After evaluating the new proposal again (changing iOS to more W3C compliant css selectors), I realize that I will not be able to do it, although I agree on the principle.
So I will keep it as "os-version", and just implement the version-computation for Android (using build.prop file) (and of course fix the failed mustella tests).
It's not that bad, and it will certainly be useful to handle iOS 7 / Android skins.
The main and simple reason for that is am physically exhausted. It's just too much work for me.
Moreover, I already committed to many other Flex tasks and I have to prioritize things.
I Hope you understand.
I will get back to it later in a few months.
Maurice
-----Message d'origine-----
De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de OmPrakash Muppirala
Envoyé : lundi 2 décembre 2013 20:44
À : dev@flex.apache.org
Objet : Re: IOS7 status bar management ( FLEX-33860)
On Mon, Dec 2, 2013 at 11:41 AM, Alex Harui <ah...@adobe.com> wrote:
>
>
> On 12/2/13 11:29 AM, "Maurice Amsellem" <ma...@systar.com>
> wrote:
>
> >>I think mozilla's custom properties is more on the right track.
> >>IOW, what is it about the screen that is or isn't changing?
> >>Whatever it is, while it got introduced in IOS 7, it doesn't mean
> >>that whatever it is won't be implemented in other OS's over time, or
> >>that there will someday be an option to turn that thing on and off.
> >>So if it is a status >bar appearing, maybe the property should
> >>simply be called pop-up-status-bar, or maybe the code should be
> >>watching for changes to screen-height or something like that.
> >
> >I see what you mean. Mozilla has other props like that:
> >" -moz-scrollbar-thumb-proportional"
> >
> >So it could be implemented as :
> >"-flex-status-bar-overlap"
> >And maybe:
> >"-ios-theme"=ios7|classic
> >
> >But technically, there is no way of knowing that the status bar is
> >overlapping, based on "os-independent"screen change).
> >The only valid test at the moment is the following:
> >- OS=iOS and version >= 7 + other iOS specific settings in air
> >descriptor file.
> >
> >Same for ios-theme => the internal test is based on the os+version.
> The internal test may have to trigger on os-version or other
> system.Capabilities info for now, but that's ok, IMO. If some future
> IOS makes status-bar-overlap optional, hopefully AIR will provide a
> way to find that out (or we'll make an ANE that can do that).
>
> Again, I don't really understand this particular issue, but why don't
> other non-Flex IOS apps have to react to this difference when running
> on IOS? Or are they?
>
They are having to. Either via direct APIs [1] or through hacks [2]
Thanks,
Om
[1]
http://www.doubleencore.com/2013/09/developers-guide-to-the-ios-7-status-bar/
[1]
http://www.icenium.com/blog/icenium-team-blog/2013/11/07/everything-hybrid-web-apps-need-to-know-about-the-status-bar-in-ios7
> >
> > Another point is that this same "os-version" prop was meant to be
> >used for seting different skins for different versions of Androids (
> >suggestion from Om) Here again, we could have defined
> >android-specific props such as:
> >"-flex-android-theme=A|B|C"
> Yes, if the theme can be determined and that is what matters to the code.
> You never know when the next version of Android will allow a choice of
> skins/themes.
>
> -Alex
>
>
Re: IOS7 status bar management ( FLEX-33860)
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Mon, Dec 2, 2013 at 11:41 AM, Alex Harui <ah...@adobe.com> wrote:
>
>
> On 12/2/13 11:29 AM, "Maurice Amsellem" <ma...@systar.com>
> wrote:
>
> >>I think mozilla's custom properties is more on the right track. IOW,
> >>what is it about the screen that is or isn't changing?
> >>Whatever it is, while it got introduced in IOS 7, it doesn't mean that
> >>whatever it is won't be implemented in other OS's over time, or that
> >>there will someday be an option to turn that thing on and off. So if it
> >>is a status >bar appearing, maybe the property should simply be called
> >>pop-up-status-bar, or maybe the code should be watching for changes to
> >>screen-height or something like that.
> >
> >I see what you mean. Mozilla has other props like that:
> >" -moz-scrollbar-thumb-proportional"
> >
> >So it could be implemented as :
> >"-flex-status-bar-overlap"
> >And maybe:
> >"-ios-theme"=ios7|classic
> >
> >But technically, there is no way of knowing that the status bar is
> >overlapping, based on "os-independent"screen change).
> >The only valid test at the moment is the following:
> >- OS=iOS and version >= 7 + other iOS specific settings in air descriptor
> >file.
> >
> >Same for ios-theme => the internal test is based on the os+version.
> The internal test may have to trigger on os-version or other
> system.Capabilities info for now, but that's ok, IMO. If some future IOS
> makes status-bar-overlap optional, hopefully AIR will provide a way to
> find that out (or we'll make an ANE that can do that).
>
> Again, I don't really understand this particular issue, but why don't
> other non-Flex IOS apps have to react to this difference when running on
> IOS? Or are they?
>
They are having to. Either via direct APIs [1] or through hacks [2]
Thanks,
Om
[1]
http://www.doubleencore.com/2013/09/developers-guide-to-the-ios-7-status-bar/
[1]
http://www.icenium.com/blog/icenium-team-blog/2013/11/07/everything-hybrid-web-apps-need-to-know-about-the-status-bar-in-ios7
> >
> > Another point is that this same "os-version" prop was meant to be used
> >for seting different skins for different versions of Androids (
> >suggestion from Om)
> >Here again, we could have defined android-specific props such as:
> >"-flex-android-theme=A|B|C"
> Yes, if the theme can be determined and that is what matters to the code.
> You never know when the next version of Android will allow a choice of
> skins/themes.
>
> -Alex
>
>
Re: IOS7 status bar management ( FLEX-33860)
Posted by Alex Harui <ah...@adobe.com>.
On 12/2/13 11:29 AM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>>I think mozilla's custom properties is more on the right track. IOW,
>>what is it about the screen that is or isn't changing?
>>Whatever it is, while it got introduced in IOS 7, it doesn't mean that
>>whatever it is won't be implemented in other OS's over time, or that
>>there will someday be an option to turn that thing on and off. So if it
>>is a status >bar appearing, maybe the property should simply be called
>>pop-up-status-bar, or maybe the code should be watching for changes to
>>screen-height or something like that.
>
>I see what you mean. Mozilla has other props like that:
>" -moz-scrollbar-thumb-proportional"
>
>So it could be implemented as :
>"-flex-status-bar-overlap"
>And maybe:
>"-ios-theme"=ios7|classic
>
>But technically, there is no way of knowing that the status bar is
>overlapping, based on "os-independent"screen change).
>The only valid test at the moment is the following:
>- OS=iOS and version >= 7 + other iOS specific settings in air descriptor
>file.
>
>Same for ios-theme => the internal test is based on the os+version.
The internal test may have to trigger on os-version or other
system.Capabilities info for now, but that's ok, IMO. If some future IOS
makes status-bar-overlap optional, hopefully AIR will provide a way to
find that out (or we'll make an ANE that can do that).
Again, I don't really understand this particular issue, but why don't
other non-Flex IOS apps have to react to this difference when running on
IOS? Or are they?
>
> Another point is that this same "os-version" prop was meant to be used
>for seting different skins for different versions of Androids (
>suggestion from Om)
>Here again, we could have defined android-specific props such as:
>"-flex-android-theme=A|B|C"
Yes, if the theme can be determined and that is what matters to the code.
You never know when the next version of Android will allow a choice of
skins/themes.
-Alex
RE: IOS7 status bar management ( FLEX-33860)
Posted by Maurice Amsellem <ma...@systar.com>.
>I think mozilla's custom properties is more on the right track. IOW, what is it about the screen that is or isn't changing?
>Whatever it is, while it got introduced in IOS 7, it doesn't mean that whatever it is won't be implemented in other OS's over time, or that there will someday be an option to turn that thing on and off. So if it is a status >bar appearing, maybe the property should simply be called pop-up-status-bar, or maybe the code should be watching for changes to screen-height or something like that.
I see what you mean. Mozilla has other props like that:
" -moz-scrollbar-thumb-proportional"
So it could be implemented as :
"-flex-status-bar-overlap"
And maybe:
"-ios-theme"=ios7|classic
But technically, there is no way of knowing that the status bar is overlapping, based on "os-independent"screen change).
The only valid test at the moment is the following:
- OS=iOS and version >= 7 + other iOS specific settings in air descriptor file.
Same for ios-theme => the internal test is based on the os+version.
Another point is that this same "os-version" prop was meant to be used for seting different skins for different versions of Androids ( suggestion from Om)
Here again, we could have defined android-specific props such as:
"-flex-android-theme=A|B|C"
WDYT?
Maurice
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com]
Envoyé : lundi 2 décembre 2013 20:05
À : dev@flex.apache.org
Objet : Re: IOS7 status bar management ( FLEX-33860)
On 12/2/13 12:34 AM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>Anyway, I think it's too late to change that:
>- changing the existing css selectors (eg. os-platform =>
>-flex-os-platform, or application-dpi to resolution) would break
>existing applications
>- implementing standard W3C media css selectors will be difficult to
>implement, and may conflict with other Flex "responsive-design"
>techniques (states)
Yeah, I'm not suggesting going back and making it all compliant, but I am suggesting that we think through whether this code-path switch should really be tied to an OS and its version or something more "media"-oriented. I think mozilla's custom properties is more on the right track. IOW, what is it about the screen that is or isn't changing?
Whatever it is, while it got introduced in IOS 7, it doesn't mean that whatever it is won't be implemented in other OS's over time, or that there will someday be an option to turn that thing on and off. So if it is a status bar appearing, maybe the property should simply be called pop-up-status-bar, or maybe the code should be watching for changes to screen-height or something like that.
-Alex
Re: IOS7 status bar management ( FLEX-33860)
Posted by Alex Harui <ah...@adobe.com>.
On 12/2/13 12:34 AM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>Anyway, I think it's too late to change that:
>- changing the existing css selectors (eg. os-platform =>
>-flex-os-platform, or application-dpi to resolution) would break
>existing applications
>- implementing standard W3C media css selectors will be difficult to
>implement, and may conflict with other Flex "responsive-design"
>techniques (states)
Yeah, I'm not suggesting going back and making it all compliant, but I am
suggesting that we think through whether this code-path switch should
really be tied to an OS and its version or something more
"media"-oriented. I think mozilla's custom properties is more on the
right track. IOW, what is it about the screen that is or isn't changing?
Whatever it is, while it got introduced in IOS 7, it doesn't mean that
whatever it is won't be implemented in other OS's over time, or that there
will someday be an option to turn that thing on and off. So if it is a
status bar appearing, maybe the property should simply be called
pop-up-status-bar, or maybe the code should be watching for changes to
screen-height or something like that.
-Alex
RE: IOS7 status bar management ( FLEX-33860)
Posted by Maurice Amsellem <ma...@systar.com>.
> 1) Flex cheats already, but non-standard media query properties I think are supposed to be prefixed with a "-" and owner.
That's correct. As you said, Flex does not follow this rule already.
Even more, I would say that NONE of flex media selectors are standard (type, application-dpi, os-platform, os-version), even when the equivalent exists.
(If flex followed W3C, application-dpi should have been named resolution: XXX dpi)
And Flex does not support any of the standard media css selectors (width, height, orientation, etc...)
> 2) It is interesting that the W3C doesn't think that os-version is necessary.
They don't even have os-platform. I guess that's in the W3C approach, "brand" characteristics are too specific.
Mozilla is on the other extreme, with css queries such as "-moz-mac-graphite-theme" and " -moz-windows-default-theme".
Can't be more specific than that :-).
Anyway, I think it's too late to change that:
- changing the existing css selectors (eg. os-platform => -flex-os-platform, or application-dpi to resolution) would break existing applications
- implementing standard W3C media css selectors will be difficult to implement, and may conflict with other Flex "responsive-design" techniques (states)
WDYT ?
Maurice
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com]
Envoyé : lundi 2 décembre 2013 05:52
À : dev@flex.apache.org
Objet : Re: IOS7 status bar management ( FLEX-33860)
I haven't really been following, but I just wanted to note a couple of
things:
1) Flex cheats already, but non-standard media query properties I think are supposed to be prefixed with a "-" and owner.
2) It is interesting that the W3C doesn't think that os-version is necessary. It made me wonder why. Should whatever code paths we are planning to change based on this proposed property really be triggered by some other media properties?
-Alex
On 12/1/13 9:01 AM, "Maurice Amsellem" <ma...@systar.com> wrote:
>FYI, committed/pushed to develop branch:
>https://issues.apache.org/jira/browse/FLEX-33949 ( os-version media
>css)
>https://issues.apache.org/jira/browse/FLEX-33860 (ios 7 status bar)
>
>os-version implementation covers iOS and desktop OS only.
>Android os-version yet to be done.
>
>(I didn't want to delay iOS7 status bar fix, because of Android).
>
>Maurice
>
>-----Message d'origine-----
>De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de
>OmPrakash Muppirala Envoyé : dimanche 1 décembre 2013 03:15 À :
>dev@flex.apache.org Objet : RE: IOS7 status bar management (
>FLEX-33860)
>
>On Nov 30, 2013 4:30 PM, "Maurice Amsellem"
><ma...@systar.com>
>wrote:
>>
>> Hi,
>>
>> Unfortunately, Capabilities.os on Android returns the Linux kernel
>version, not the Android version.
>>
>http://stackoverflow.com/questions/11293236/how-can-i-detect-the-androi
>d-o
>s-version-in-adobe-air
>>
>> The workaround is to get the info form a system file called
>/system/build.prop
>> As described in:
>> https://github.com/funky-monkey/Android-Native-Device-Info
>>
>> These is no licencing information associated with the code.
>>
>> Possibilities:
>> - contact the author and ask for donation of the code to AF
>> - "borrow" the idea (reading system/build.prop) and re-implement the
>parse code, shouldn't be that difficult.
>>
>> What do you think?
>
>I think that as long as we don't copy the code, we should be good.
>
>>
>> Note: of course, getting the version of Android is not required for
>managing iOS7 status bar.
>> I am raising this issue because Om once mentioned that css media
>> query
>os-version would be useful for Android as well, to apply different
>skins to different versions of Android.
>> It's also required for completeness, so that os-version returns
>consistent results on Android as well.
>
>I was really hoping that you would implement this for Android as well
>:-)
>
>Thanks,
>Om
>
>>
>> Maurice
>>
>> -----Message d'origine-----
>> De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>> Envoyé : samedi 30 novembre 2013 21:43 À : dev@flex.apache.org Objet :
>> RE: IOS7 status bar management ( FLEX-33860)
>>
>> I discovered in CSS Media specs the 'min' and 'max' operators, so IOS
>version categories are not needed anymore.
>>
>> I have added a new css media property called 'os-version' of type
>>Number.
>>
>> And this is how to condition styles for IOS6 and IOS7:
>>
>> ISO6:
>> @media (os-platform: 'IOS') and (max-os-version: 6.5)
>>
>> IOS7:
>> @media (os-platform: 'IOS') and (min-os-version: 7.0)
>>
>> It would work the same for Android...
>>
>> Maurice
>>
>> -----Message d'origine-----
>> De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>> Envoyé : samedi 30 novembre 2013 16:11 À : dev@flex.apache.org Objet :
>> RE: IOS7 status bar management ( FLEX-33860)
>>
>> Back to this issue.
>>
>> I am working on adding os-version capability to MediaQueryParser.
>>
>> My first intention was to implement it that way:
>> os-version >= 7.0
>>
>> But it appears that CSS Media only support equality operator ( : ) ,
>> so
>version should be a category rather than a figure.
>>
>> For iOS, it would be more like :
>>
>> os-version: 'ios6-' | 'ios7+'
>>
>> ios6- = ios 6 or less
>> ios7+ = ios 7 or more
>>
>> (until Apple decides to change its ios design again :-( ) .
>>
>> For Android, what would be the relevant classes ?
>>
>> Regards,
>>
>> Maurice
>>
>> -----Message d'origine-----
>> De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de
>> OmPrakash
>Muppirala Envoyé : dimanche 3 novembre 2013 21:36 À :
>dev@flex.apache.orgObjet : Re: IOS7 status bar management (
>FLEX-33860)
>>
>>
Re: IOS7 status bar management ( FLEX-33860)
Posted by Alex Harui <ah...@adobe.com>.
I haven't really been following, but I just wanted to note a couple of
things:
1) Flex cheats already, but non-standard media query properties I think
are supposed to be prefixed with a "-" and owner.
2) It is interesting that the W3C doesn't think that os-version is
necessary. It made me wonder why. Should whatever code paths we are
planning to change based on this proposed property really be triggered by
some other media properties?
-Alex
On 12/1/13 9:01 AM, "Maurice Amsellem" <ma...@systar.com> wrote:
>FYI, committed/pushed to develop branch:
>https://issues.apache.org/jira/browse/FLEX-33949 ( os-version media css)
>https://issues.apache.org/jira/browse/FLEX-33860 (ios 7 status bar)
>
>os-version implementation covers iOS and desktop OS only.
>Android os-version yet to be done.
>
>(I didn't want to delay iOS7 status bar fix, because of Android).
>
>Maurice
>
>-----Message d'origine-----
>De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de OmPrakash
>Muppirala
>Envoyé : dimanche 1 décembre 2013 03:15
>À : dev@flex.apache.org
>Objet : RE: IOS7 status bar management ( FLEX-33860)
>
>On Nov 30, 2013 4:30 PM, "Maurice Amsellem" <ma...@systar.com>
>wrote:
>>
>> Hi,
>>
>> Unfortunately, Capabilities.os on Android returns the Linux kernel
>version, not the Android version.
>>
>http://stackoverflow.com/questions/11293236/how-can-i-detect-the-android-o
>s-version-in-adobe-air
>>
>> The workaround is to get the info form a system file called
>/system/build.prop
>> As described in:
>> https://github.com/funky-monkey/Android-Native-Device-Info
>>
>> These is no licencing information associated with the code.
>>
>> Possibilities:
>> - contact the author and ask for donation of the code to AF
>> - "borrow" the idea (reading system/build.prop) and re-implement the
>parse code, shouldn't be that difficult.
>>
>> What do you think?
>
>I think that as long as we don't copy the code, we should be good.
>
>>
>> Note: of course, getting the version of Android is not required for
>managing iOS7 status bar.
>> I am raising this issue because Om once mentioned that css media query
>os-version would be useful for Android as well, to apply different skins
>to different versions of Android.
>> It's also required for completeness, so that os-version returns
>consistent results on Android as well.
>
>I was really hoping that you would implement this for Android as well :-)
>
>Thanks,
>Om
>
>>
>> Maurice
>>
>> -----Message d'origine-----
>> De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>> Envoyé : samedi 30 novembre 2013 21:43 À : dev@flex.apache.org Objet :
>> RE: IOS7 status bar management ( FLEX-33860)
>>
>> I discovered in CSS Media specs the 'min' and 'max' operators, so IOS
>version categories are not needed anymore.
>>
>> I have added a new css media property called 'os-version' of type
>>Number.
>>
>> And this is how to condition styles for IOS6 and IOS7:
>>
>> ISO6:
>> @media (os-platform: 'IOS') and (max-os-version: 6.5)
>>
>> IOS7:
>> @media (os-platform: 'IOS') and (min-os-version: 7.0)
>>
>> It would work the same for Android...
>>
>> Maurice
>>
>> -----Message d'origine-----
>> De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>> Envoyé : samedi 30 novembre 2013 16:11 À : dev@flex.apache.org Objet :
>> RE: IOS7 status bar management ( FLEX-33860)
>>
>> Back to this issue.
>>
>> I am working on adding os-version capability to MediaQueryParser.
>>
>> My first intention was to implement it that way:
>> os-version >= 7.0
>>
>> But it appears that CSS Media only support equality operator ( : ) ,
>> so
>version should be a category rather than a figure.
>>
>> For iOS, it would be more like :
>>
>> os-version: 'ios6-' | 'ios7+'
>>
>> ios6- = ios 6 or less
>> ios7+ = ios 7 or more
>>
>> (until Apple decides to change its ios design again :-( ) .
>>
>> For Android, what would be the relevant classes ?
>>
>> Regards,
>>
>> Maurice
>>
>> -----Message d'origine-----
>> De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de
>> OmPrakash
>Muppirala Envoyé : dimanche 3 novembre 2013 21:36 À :
>dev@flex.apache.orgObjet : Re: IOS7 status bar management (
>FLEX-33860)
>>
>>
RE: IOS7 status bar management ( FLEX-33860)
Posted by Maurice Amsellem <ma...@systar.com>.
FYI, committed/pushed to develop branch:
https://issues.apache.org/jira/browse/FLEX-33949 ( os-version media css)
https://issues.apache.org/jira/browse/FLEX-33860 (ios 7 status bar)
os-version implementation covers iOS and desktop OS only.
Android os-version yet to be done.
(I didn't want to delay iOS7 status bar fix, because of Android).
Maurice
-----Message d'origine-----
De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de OmPrakash Muppirala
Envoyé : dimanche 1 décembre 2013 03:15
À : dev@flex.apache.org
Objet : RE: IOS7 status bar management ( FLEX-33860)
On Nov 30, 2013 4:30 PM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>
> Hi,
>
> Unfortunately, Capabilities.os on Android returns the Linux kernel
version, not the Android version.
>
http://stackoverflow.com/questions/11293236/how-can-i-detect-the-android-os-version-in-adobe-air
>
> The workaround is to get the info form a system file called
/system/build.prop
> As described in:
> https://github.com/funky-monkey/Android-Native-Device-Info
>
> These is no licencing information associated with the code.
>
> Possibilities:
> - contact the author and ask for donation of the code to AF
> - "borrow" the idea (reading system/build.prop) and re-implement the
parse code, shouldn't be that difficult.
>
> What do you think?
I think that as long as we don't copy the code, we should be good.
>
> Note: of course, getting the version of Android is not required for
managing iOS7 status bar.
> I am raising this issue because Om once mentioned that css media query
os-version would be useful for Android as well, to apply different skins to different versions of Android.
> It's also required for completeness, so that os-version returns
consistent results on Android as well.
I was really hoping that you would implement this for Android as well :-)
Thanks,
Om
>
> Maurice
>
> -----Message d'origine-----
> De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
> Envoyé : samedi 30 novembre 2013 21:43 À : dev@flex.apache.org Objet :
> RE: IOS7 status bar management ( FLEX-33860)
>
> I discovered in CSS Media specs the 'min' and 'max' operators, so IOS
version categories are not needed anymore.
>
> I have added a new css media property called 'os-version' of type Number.
>
> And this is how to condition styles for IOS6 and IOS7:
>
> ISO6:
> @media (os-platform: 'IOS') and (max-os-version: 6.5)
>
> IOS7:
> @media (os-platform: 'IOS') and (min-os-version: 7.0)
>
> It would work the same for Android...
>
> Maurice
>
> -----Message d'origine-----
> De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
> Envoyé : samedi 30 novembre 2013 16:11 À : dev@flex.apache.org Objet :
> RE: IOS7 status bar management ( FLEX-33860)
>
> Back to this issue.
>
> I am working on adding os-version capability to MediaQueryParser.
>
> My first intention was to implement it that way:
> os-version >= 7.0
>
> But it appears that CSS Media only support equality operator ( : ) ,
> so
version should be a category rather than a figure.
>
> For iOS, it would be more like :
>
> os-version: 'ios6-' | 'ios7+'
>
> ios6- = ios 6 or less
> ios7+ = ios 7 or more
>
> (until Apple decides to change its ios design again :-( ) .
>
> For Android, what would be the relevant classes ?
>
> Regards,
>
> Maurice
>
> -----Message d'origine-----
> De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de
> OmPrakash
Muppirala Envoyé : dimanche 3 novembre 2013 21:36 À :
dev@flex.apache.orgObjet : Re: IOS7 status bar management (
FLEX-33860)
>
>
RE: IOS7 status bar management ( FLEX-33860)
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Nov 30, 2013 4:30 PM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>
> Hi,
>
> Unfortunately, Capabilities.os on Android returns the Linux kernel
version, not the Android version.
>
http://stackoverflow.com/questions/11293236/how-can-i-detect-the-android-os-version-in-adobe-air
>
> The workaround is to get the info form a system file called
/system/build.prop
> As described in:
> https://github.com/funky-monkey/Android-Native-Device-Info
>
> These is no licencing information associated with the code.
>
> Possibilities:
> - contact the author and ask for donation of the code to AF
> - "borrow" the idea (reading system/build.prop) and re-implement the
parse code, shouldn't be that difficult.
>
> What do you think?
I think that as long as we don't copy the code, we should be good.
>
> Note: of course, getting the version of Android is not required for
managing iOS7 status bar.
> I am raising this issue because Om once mentioned that css media query
os-version would be useful for Android as well, to apply different skins to
different versions of Android.
> It's also required for completeness, so that os-version returns
consistent results on Android as well.
I was really hoping that you would implement this for Android as well :-)
Thanks,
Om
>
> Maurice
>
> -----Message d'origine-----
> De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
> Envoyé : samedi 30 novembre 2013 21:43
> À : dev@flex.apache.org
> Objet : RE: IOS7 status bar management ( FLEX-33860)
>
> I discovered in CSS Media specs the 'min' and 'max' operators, so IOS
version categories are not needed anymore.
>
> I have added a new css media property called 'os-version' of type Number.
>
> And this is how to condition styles for IOS6 and IOS7:
>
> ISO6:
> @media (os-platform: 'IOS') and (max-os-version: 6.5)
>
> IOS7:
> @media (os-platform: 'IOS') and (min-os-version: 7.0)
>
> It would work the same for Android...
>
> Maurice
>
> -----Message d'origine-----
> De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
> Envoyé : samedi 30 novembre 2013 16:11
> À : dev@flex.apache.org
> Objet : RE: IOS7 status bar management ( FLEX-33860)
>
> Back to this issue.
>
> I am working on adding os-version capability to MediaQueryParser.
>
> My first intention was to implement it that way:
> os-version >= 7.0
>
> But it appears that CSS Media only support equality operator ( : ) , so
version should be a category rather than a figure.
>
> For iOS, it would be more like :
>
> os-version: 'ios6-' | 'ios7+'
>
> ios6- = ios 6 or less
> ios7+ = ios 7 or more
>
> (until Apple decides to change its ios design again :-( ) .
>
> For Android, what would be the relevant classes ?
>
> Regards,
>
> Maurice
>
> -----Message d'origine-----
> De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de OmPrakash
Muppirala Envoyé : dimanche 3 novembre 2013 21:36 À :
dev@flex.apache.orgObjet : Re: IOS7 status bar management (
FLEX-33860)
>
>
RE: IOS7 status bar management ( FLEX-33860)
Posted by Maurice Amsellem <ma...@systar.com>.
Hi,
Unfortunately, Capabilities.os on Android returns the Linux kernel version, not the Android version.
http://stackoverflow.com/questions/11293236/how-can-i-detect-the-android-os-version-in-adobe-air
The workaround is to get the info form a system file called /system/build.prop
As described in:
https://github.com/funky-monkey/Android-Native-Device-Info
These is no licencing information associated with the code.
Possibilities:
- contact the author and ask for donation of the code to AF
- "borrow" the idea (reading system/build.prop) and re-implement the parse code, shouldn't be that difficult.
What do you think?
Note: of course, getting the version of Android is not required for managing iOS7 status bar.
I am raising this issue because Om once mentioned that css media query os-version would be useful for Android as well, to apply different skins to different versions of Android.
It's also required for completeness, so that os-version returns consistent results on Android as well.
Maurice
-----Message d'origine-----
De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
Envoyé : samedi 30 novembre 2013 21:43
À : dev@flex.apache.org
Objet : RE: IOS7 status bar management ( FLEX-33860)
I discovered in CSS Media specs the 'min' and 'max' operators, so IOS version categories are not needed anymore.
I have added a new css media property called 'os-version' of type Number.
And this is how to condition styles for IOS6 and IOS7:
ISO6:
@media (os-platform: 'IOS') and (max-os-version: 6.5)
IOS7:
@media (os-platform: 'IOS') and (min-os-version: 7.0)
It would work the same for Android...
Maurice
-----Message d'origine-----
De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
Envoyé : samedi 30 novembre 2013 16:11
À : dev@flex.apache.org
Objet : RE: IOS7 status bar management ( FLEX-33860)
Back to this issue.
I am working on adding os-version capability to MediaQueryParser.
My first intention was to implement it that way:
os-version >= 7.0
But it appears that CSS Media only support equality operator ( : ) , so version should be a category rather than a figure.
For iOS, it would be more like :
os-version: 'ios6-' | 'ios7+'
ios6- = ios 6 or less
ios7+ = ios 7 or more
(until Apple decides to change its ios design again :-( ) .
For Android, what would be the relevant classes ?
Regards,
Maurice
-----Message d'origine-----
De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de OmPrakash Muppirala Envoyé : dimanche 3 novembre 2013 21:36 À : dev@flex.apache.org Objet : Re: IOS7 status bar management ( FLEX-33860)
RE: IOS7 status bar management ( FLEX-33860)
Posted by Maurice Amsellem <ma...@systar.com>.
I discovered in CSS Media specs the 'min' and 'max' operators, so IOS version categories are not needed anymore.
I have added a new css media property called 'os-version' of type Number.
And this is how to condition styles for IOS6 and IOS7:
ISO6:
@media (os-platform: 'IOS') and (max-os-version: 6.5)
IOS7:
@media (os-platform: 'IOS') and (min-os-version: 7.0)
It would work the same for Android...
Maurice
-----Message d'origine-----
De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
Envoyé : samedi 30 novembre 2013 16:11
À : dev@flex.apache.org
Objet : RE: IOS7 status bar management ( FLEX-33860)
Back to this issue.
I am working on adding os-version capability to MediaQueryParser.
My first intention was to implement it that way:
os-version >= 7.0
But it appears that CSS Media only support equality operator ( : ) , so version should be a category rather than a figure.
For iOS, it would be more like :
os-version: 'ios6-' | 'ios7+'
ios6- = ios 6 or less
ios7+ = ios 7 or more
(until Apple decides to change its ios design again :-( ) .
For Android, what would be the relevant classes ?
Regards,
Maurice
-----Message d'origine-----
De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de OmPrakash Muppirala Envoyé : dimanche 3 novembre 2013 21:36 À : dev@flex.apache.org Objet : Re: IOS7 status bar management ( FLEX-33860)
RE: IOS7 status bar management ( FLEX-33860)
Posted by Maurice Amsellem <ma...@systar.com>.
Back to this issue.
I am working on adding os-version capability to MediaQueryParser.
My first intention was to implement it that way:
os-version >= 7.0
But it appears that CSS Media only support equality operator ( : ) , so version should be a category rather than a figure.
For iOS, it would be more like :
os-version: 'ios6-' | 'ios7+'
ios6- = ios 6 or less
ios7+ = ios 7 or more
(until Apple decides to change its ios design again :-( ) .
For Android, what would be the relevant classes ?
Regards,
Maurice
-----Message d'origine-----
De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de OmPrakash Muppirala
Envoyé : dimanche 3 novembre 2013 21:36
À : dev@flex.apache.org
Objet : Re: IOS7 status bar management ( FLEX-33860)
Re: IOS7 status bar management ( FLEX-33860)
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Nov 3, 2013 12:13 PM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>
> Hi Team,
>
> iOS7 manages the status bar differently than iOS 6.1: application is
displayed in full screen and the status bar is displayed on top of the app,
either in black or white font color (depending on some setting).
>
> Current flex apps running on iOS7 will have the status bar partly
covering the top navigation bar buttons and text.
>
> The usual workaround is to increase ActionBar paddingTop to remove the
overlap.
>
> (see : https://issues.apache.org/jira/browse/FLEX-33860)
>
> I would like to discuss the different approaches for a permanent fix of
this issue in the Flex SDK.
>
> There are two points to discuss: how to provide room for the status bar,
and how to determine/control when to do it:
>
>
> Point #1: how to provide room for the status Bar:
>
> Option 1) increase the top ActionBar paddingTop, to leave space for the
status bar.
>
> Note that the top padding must be applied to the top ActionBar only, not
to the other ActionBars.
> This is easy for ViewNavigatorApplication, but not obvious when the
ActionBar(s) are added indirectly, for example through SplitViewNavigator.
> This could be done eg. by testing the ActionBar stage y, and add the
padding if < 10
>
> Option 2) modify the various mobile ApplicationSkin classes
(ApplicaitonSkin, TabbedViewNavigatorApplicationSkin,
ViewNavigatorApplicationSkin) to leave 20 px space for the status bar.
> This space could be filled with application background color, instead of
being black.
I prefer option 2. Sounds like a cleaner approach.
>
> ----
>
> Point #2: How to determine when to add the top padding:
>
> Option 1)
> - Dynamically determine that application is running on iOS7 (based on
Capabilities.version and Capabilities.os)
> - Size the padding top accordingly ( set if IOS7, not set if not IOS7)
>
> ⇨ Simple, but not flexible.
>
> Option 2)
> - Introduce a new numerical os-version @media selector
>
> Eg.
>
> @media (application-dpi: 160) AND (os-platform:"IOS") AND (os-version >=
7) {
> statusBarHeight: 20;
> }
>
> Pros: opens up new possilibilities, for example to provide iOS7 specific
skins.
> Cons: much more difficult to implement.
>
Again option 2 sounds better. This will also help us with the Android 4.x
specific skins we are planning to add as well.
Thanks,
Om
>
> _____
>
> What do you think ?
>
> Maurice