Re: [Uriana Framework] Documentation updated
Hello again Scott, did you have time to take a look to the framework? I would love to get some feedback around. Thanks in advance. Carlos. 2013/4/8 Carlos Velasco > Hi Scott, > > I have started the documents for the mobile library, you should take a > look at it to figure out if Uriana could help you with your current > developments. > > Cheers, > Carlos. > > > 2013/4/8 Carlos Velasco > >> It seems to me that you've been working on the same path that Uriana goes >> (same methodology). >> >> The point with Uriana is that when developping for IPAD you will use >> mobile library instead of application library, which simplifies the >> application-module architecture exchanging it for a simplified Sections and >> views within a section architecture, but in the end you change some >> components and extend Mobile based ones to get everything done. >> >> I find it quite simple to work with, and I hope it will fit your purposes >> well. >> >> Thanks for your interest. >> >> Cheers, >> Carlos. >> >> >> 2013/4/8 Scott Matheson >> >>> Carlos >>>my project is a simple MVC application designed to teach dyslexic >>> to read, >>> we have used standard MXML and AS and a few events with modules to keep >>> every thing nice and clean >>> >>> There is only 2 developers on the project, so we try and keep the project >>> simple with out lots of over heads >>> >>> We will port to iPad etc later this year >>> >>> I will try and understand you work, it may save us a lot of time >>> >>> Scott >>> >>> >>> >>> >>> >>> On 4/8/13 3:16 PM, "Carlos Velasco" >>> wrote: >>> >>> >Hi Scott, and thanks for your comments. I have planned the site as a >>> 'how >>> >does it work' rather than a 'this is the wtf framework for' as I am just >>> >sharing it with the world instead of selling it, but I will try to show >>> >its >>> >benefits in the how to's part, well at this point any advice is of value >>> >:). >>> > >>> >I can point some of the 'Why to use it' staff in advance: >>> > >>> >- Standarized methodology for Web, desktop and mobile projects. >>> >- Makes software easy to understand and maintain. >>> > >>> >- Standard linkage between pieces in a program (Event or direct access >>> >based as desired). >>> >- Pre-built framework pieces to simplify handling common resources, lot >>> of >>> >them are to handle mobile staff. (Let's say, views are provided of a >>> >localization manager to handle locales, a logger to write log lines and >>> >so... you don't need to add them to start working) >>> >- Resource cleaning is ensured by the framework (and also stablishes >>> >points >>> >for manual cleaning when desired). >>> >- Abstracts dispatchers and listeners staff through the application. >>> >- It's extensible to handle any resources or third party libraries. >>> >- I think it's quite lightweight. >>> > >>> >And in my opinion the most important ones: >>> > >>> >- It's very confortable working with it. >>> >- It implements much more logic than the pureMVC framework (so I don't >>> >need >>> >to code it again and again). >>> >- The workflow is very simple (resource - Event - Mediator - Event - >>> Rest >>> >of the world through Controllers). >>> > >>> >I don't know what you are working at right now or if Uriana is the best >>> >solution for your problems, but I can say I would help with whatever you >>> >need in case you find it interesting for your projects or were >>> interested >>> >in colaborating to improve the Uriana capabilities. >>> > >>> >Cheers, >>> >Carlos. >>> > >>> > >>> >2013/4/8 Scott Matheson >>> > >>> >> Hi >>> >>So this may be more an issue about me, and maybe this group is not >>> >>for >>> >> me, I am a business developed that hacks at code and make stuff work, >>> >> >>> >> When I read a page I am trying to understand the benefits, what will >>> >>this >>> >> do for me >>> >> >>> >> When I read this WiKi I do not get the sense of the value, so I have >>> no >>> >> idea if this will be of benefit to the business problems I am >>> challenged >>> >> with >>> >> >>> >> As I said this may have more to do with my ability to decode what >>> >> information is provided, no offense ment >>> >> >>> >> >>> >> Scott >>> >> >>> >> >>> >> >>> >> On 4/8/13 1:02 PM, "Carlos Velasco" >>> >> wrote: >>> >> >>> >> >I have extended the Application Library documentation: >>> >> > >>> >> >https://www.assembla.com/spaces/uriana/wiki/Application_Library >>> >> > >>> >> >But at the moment I have not received feedback, questions or so from >>> >>the >>> >> >community. Is anyone testing Uriana out there? >>> >> > >>> >> >Cheers, Carlos. >>> >> > >>> >> > >>> >> >2013/4/5 Carlos Velasco >>> >> > >>> >> >> I have recently updated documentation wiki pages for Uriana's >>> >> >>application >>> >> >> library: >>> >> >> >>> >> >> https://www.assembla.com/spaces/uriana/wiki/Application_Library >>> >> >> >>> >> >> I will be working to complete these documentation pages and create >>> >>the >>> >> >> Mobile library ones in the next days. >
GridColumn sortField
I've noticed that spark datagrid when it tries to sort based on a column, when it finds no sortFunction it asks the GridColumn about the sortField. Within the method public function get sortField():SortField I've noticed it uses ObjectUtil to compare 2 items. Shouldn't it rely on the default locale and set the locale style on the sortField? -- João Fernandes
Papervision3D replacment
Can anyone on here suggest a good replacement for papervision3D. I want to look at replacing some papervision3D content that is currently loaded to display a 3D model. It's a very large existing project so I can't easily really cut a hole in the app to allow to see the display object at position zero where stage 3D is rendered. Any one got a good work around or project I've not heard of that allows me to place 3D content in a Flex container? Thanks Mark
Re: Papervision3D replacment
I've tried to get Minko to work inside Flex but failed and ended up resorting to an ActionScript project. I'm pretty sure all the recent 3D stuff uses Stage3D. Can you use a mask to reveal it below the other display objects. I've done loads of other Stage3D stuff in Flex: my blog may help: http://flexmonkey.blogspot.co.uk/search/label/Stage3D Simon _ +44 (0) 7973 669691 sglad...@gmail.com http://flexmonkey.blogspot.com/ On 12 Apr 2013, at 15:09, "Mark Line" wrote: > Can anyone on here suggest a good replacement for papervision3D. I want to > look at replacing some papervision3D content that is currently loaded to > display a 3D model. > > > > It's a very large existing project so I can't easily really cut a hole in > the app to allow to see the display object at position zero where stage 3D > is rendered. > > > > Any one got a good work around or project I've not heard of that allows me > to place 3D content in a Flex container? > > > > Thanks > > > > Mark >
RE: Papervision3D replacment
Thanks Simon, I stumbled upon your blog a month ago while playing with starling and then looking at shaders. Some useful stuff you have shared. I kinda thought that would be the case, but it's probably worth the effort as I'd like to get rid of the 1-2 seconds freeze when papervision initialises. Plus the project targets fp 11.5 so may as well use the stage3D. Was just hoping for a quicker solution/lazy programmer -Original Message- From: Simon Gladman [mailto:sglad...@gmail.com] Sent: 12 April 2013 15:29 To: users@flex.apache.org Cc: Subject: Re: Papervision3D replacment I've tried to get Minko to work inside Flex but failed and ended up resorting to an ActionScript project. I'm pretty sure all the recent 3D stuff uses Stage3D. Can you use a mask to reveal it below the other display objects. I've done loads of other Stage3D stuff in Flex: my blog may help: http://flexmonkey.blogspot.co.uk/search/label/Stage3D Simon _ +44 (0) 7973 669691 sglad...@gmail.com http://flexmonkey.blogspot.com/ On 12 Apr 2013, at 15:09, "Mark Line" wrote: > Can anyone on here suggest a good replacement for papervision3D. I > want to look at replacing some papervision3D content that is currently > loaded to display a 3D model. > > > > It's a very large existing project so I can't easily really cut a hole > in the app to allow to see the display object at position zero where > stage 3D is rendered. > > > > Any one got a good work around or project I've not heard of that > allows me to place 3D content in a Flex container? > > > > Thanks > > > > Mark >
Re: Papervision3D replacment
Hi Mark, You should try http://away3d.com/ as it supports Stage3D -Fred -Message d'origine- From: Mark Line Sent: Friday, April 12, 2013 4:09 PM To: users@flex.apache.org Subject: Papervision3D replacment Can anyone on here suggest a good replacement for papervision3D. I want to look at replacing some papervision3D content that is currently loaded to display a 3D model. It's a very large existing project so I can't easily really cut a hole in the app to allow to see the display object at position zero where stage 3D is rendered. Any one got a good work around or project I've not heard of that allows me to place 3D content in a Flex container? Thanks Mark
RE: Papervision3D replacment
I thought away3d would have the same issue as it uses stage3d, so it will appear behind all the "normal"/flex/flash display list? I'll check it though, maybe I misread something. Thanks -Original Message- From: Frédéric THOMAS [mailto:webdoubl...@hotmail.com] Sent: 12 April 2013 15:57 To: users@flex.apache.org Subject: Re: Papervision3D replacment Hi Mark, You should try http://away3d.com/ as it supports Stage3D -Fred -Message d'origine- From: Mark Line Sent: Friday, April 12, 2013 4:09 PM To: users@flex.apache.org Subject: Papervision3D replacment Can anyone on here suggest a good replacement for papervision3D. I want to look at replacing some papervision3D content that is currently loaded to display a 3D model. It's a very large existing project so I can't easily really cut a hole in the app to allow to see the display object at position zero where stage 3D is rendered. Any one got a good work around or project I've not heard of that allows me to place 3D content in a Flex container? Thanks Mark
Application Scale
Hi Not sure if this is the correct place, I will ask anyway In my Main.mxml I have a simple code this.scaleX = this.scaleX – 0.1 this.scaleY = this,scaleY –0.1 This works fine for the main container, but not the Application, so I end up with scroll bars How do I scale the application not the first container Scott Disclaimer: This electronic mail and any attachments are confidential and may be privileged. If you are not the intended recipient, please notify the sender immediately by replying to this email, and destroy all copies of this email and any attachments. Thank you.
Re: Papervision3D replacment
set backgroundAlpha="0" to your flex application -Fred -Message d'origine- From: Mark Line Sent: Friday, April 12, 2013 5:07 PM To: users@flex.apache.org Subject: RE: Papervision3D replacment I thought away3d would have the same issue as it uses stage3d, so it will appear behind all the "normal"/flex/flash display list? I'll check it though, maybe I misread something. Thanks -Original Message- From: Frédéric THOMAS [mailto:webdoubl...@hotmail.com] Sent: 12 April 2013 15:57 To: users@flex.apache.org Subject: Re: Papervision3D replacment Hi Mark, You should try http://away3d.com/ as it supports Stage3D -Fred -Message d'origine- From: Mark Line Sent: Friday, April 12, 2013 4:09 PM To: users@flex.apache.org Subject: Papervision3D replacment Can anyone on here suggest a good replacement for papervision3D. I want to look at replacing some papervision3D content that is currently loaded to display a 3D model. It's a very large existing project so I can't easily really cut a hole in the app to allow to see the display object at position zero where stage 3D is rendered. Any one got a good work around or project I've not heard of that allows me to place 3D content in a Flex container? Thanks Mark
Re: Application Scale
Is this mx:Application or s:Application? Why are you trying to adjust the scale? I would think that would make your app look a bit "fuzzy" as things won't be on pixel boundaries. You might be better off with a main container offset within the application. If the main container isn't also "shrinkable", that might be what causes the scroll bars. On 4/12/13 8:10 AM, "Scott Matheson" wrote: > Hi > Not sure if this is the correct place, I will ask anyway > > In my Main.mxml I have a simple code > > this.scaleX = this.scaleX 0.1 > this.scaleY = this,scaleY 0.1 > > This works fine for the main container, but not the Application, so I end up > with scroll bars > > How do I scale the application not the first container > > Scott > > > > > Disclaimer: This electronic mail and any attachments are confidential and may > be privileged. If you are not the intended recipient, please notify the sender > immediately by replying to this email, and destroy all copies of this email > and any attachments. Thank you. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Application Scale
Hi
Some good points, we are developing for 1024 x 768, as most screen are
larger than this, however with the browser URL etc on some devices you end
up with score bars, all graphics are vectors so we think these will scale
well, that’s what our limited testing has shown, the screen are very
simple with lost of space, so we could scale the design down
This was a v3 app we upgraded, to V4 I also implemented a Main and AppBase
class, looks like I may not have updated all mx: to S;
Should is change the base imports ?
===
=
AppBase.AS
package baseclasses
{
import com.peach.uofs.services.LoadCenters;
import flash.events.IEventDispatcher;
import mx.core.Application;
import mx.core.FlexGlobals;
import mx.events.FlexEvent;
import mx.events.StyleEvent;
import mx.styles.IStyleManager2;
public class AppBase extends Application
===
==
Main.mxml
http://ns.adobe.com/mxml/2009";
xmlns:mx="library://ns.adobe.com/flex/mx"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:baseclasses="baseclasses.*"
xmlns:components="com.peach.uofs.components.*"
xmlns:skins="skins.*"
creationComplete="init()" >
On 4/12/13 5:12 PM, "Alex Harui" wrote:
>Is this mx:Application or s:Application?
>
>Why are you trying to adjust the scale? I would think that would make
>your
>app look a bit "fuzzy" as things won't be on pixel boundaries. You might
>be
>better off with a main container offset within the application.
>
>If the main container isn't also "shrinkable", that might be what causes
>the
>scroll bars.
>
>
>On 4/12/13 8:10 AM, "Scott Matheson" wrote:
>
>> Hi
>> Not sure if this is the correct place, I will ask anyway
>>
>> In my Main.mxml I have a simple code
>>
>> this.scaleX = this.scaleX 0.1
>> this.scaleY = this,scaleY 0.1
>>
>> This works fine for the main container, but not the Application, so I
>>end up
>> with scroll bars
>>
>> How do I scale the application not the first container
>>
>> Scott
>>
>>
>>
>>
>> Disclaimer: This electronic mail and any attachments are confidential
>>and may
>> be privileged. If you are not the intended recipient, please notify the
>>sender
>> immediately by replying to this email, and destroy all copies of this
>>email
>> and any attachments. Thank you.
>
>--
>Alex Harui
>Flex SDK Team
>Adobe Systems, Inc.
>http://blogs.adobe.com/aharui
>
Disclaimer: This electronic mail and any attachments are confidential and may
be privileged. If you are not the intended recipient, please notify the sender
immediately by replying to this email, and destroy all copies of this email and
any attachments. Thank you.
Re: Application Scale
On 4/12/13 10:07 AM, "Scott Matheson" wrote:
> Hi
>Some good points, we are developing for 1024 x 768, as most screen are
> larger than this, however with the browser URL etc on some devices you end
> up with score bars, all graphics are vectors so we think these will scale
> well, that¹s what our limited testing has shown, the screen are very
> simple with lost of space, so we could scale the design down
If you scale too far, fonts will get too small to read. But in general,
scaling causes lines/edges that were on pixel boundaries to no longer be on
pixel boundaries and then anti-aliasing kicks in and the colors change or
edges look fuzzy. Quite frankly, I never notice unless told to look, but
some folks have a sensitivity to this sort of thing.
>
> This was a v3 app we upgraded, to V4 I also implemented a Main and AppBase
> class, looks like I may not have updated all mx: to S;
>
> Should is change the base imports ?
I think Flex 4 has different scaling behavior than Flex 3, and Spark does
not show scrollbars by default, so probably worth trying.
>
> ===
> =
>
> AppBase.AS
>
>
> package baseclasses
> {
> import com.peach.uofs.services.LoadCenters;
>
>
> import flash.events.IEventDispatcher;
>
>
> import mx.core.Application;
> import mx.core.FlexGlobals;
> import mx.events.FlexEvent;
> import mx.events.StyleEvent;
> import mx.styles.IStyleManager2;
>
>
>
> public class AppBase extends Application
>
>
>
> ===
> ==
>
> Main.mxml
>
> layout="absolute"
> xmlns:fx="http://ns.adobe.com/mxml/2009";
> xmlns:mx="library://ns.adobe.com/flex/mx"
> xmlns:s="library://ns.adobe.com/flex/spark"
> xmlns:baseclasses="baseclasses.*"
> xmlns:components="com.peach.uofs.components.*"
> xmlns:skins="skins.*"
> creationComplete="init()" >
>
>
>
>
>
>
>
>
>
>
>
>
> On 4/12/13 5:12 PM, "Alex Harui" wrote:
>
>> Is this mx:Application or s:Application?
>>
>> Why are you trying to adjust the scale? I would think that would make
>> your
>> app look a bit "fuzzy" as things won't be on pixel boundaries. You might
>> be
>> better off with a main container offset within the application.
>>
>> If the main container isn't also "shrinkable", that might be what causes
>> the
>> scroll bars.
>>
>>
>> On 4/12/13 8:10 AM, "Scott Matheson" wrote:
>>
>>> Hi
>>> Not sure if this is the correct place, I will ask anyway
>>>
>>> In my Main.mxml I have a simple code
>>>
>>> this.scaleX = this.scaleX 0.1
>>> this.scaleY = this,scaleY 0.1
>>>
>>> This works fine for the main container, but not the Application, so I
>>> end up
>>> with scroll bars
>>>
>>> How do I scale the application not the first container
>>>
>>> Scott
>>>
>>>
>>>
>>>
>>> Disclaimer: This electronic mail and any attachments are confidential
>>> and may
>>> be privileged. If you are not the intended recipient, please notify the
>>> sender
>>> immediately by replying to this email, and destroy all copies of this
>>> email
>>> and any attachments. Thank you.
>>
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>
>
>
>
>
> Disclaimer: This electronic mail and any attachments are confidential and may
> be privileged. If you are not the intended recipient, please notify the sender
> immediately by replying to this email, and destroy all copies of this email
> and any attachments. Thank you.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: Application Scale
Hi, I am using the following function, and it works like a charm to me.
First I designed the interface for 1280*800 (using phtoshop) and then
positioned the elements in pixels (no anchors, or relative position). It
scales great to any phone, tablet even desktop. Hope it helps.
//escalar al dispositivo (se diseñó para 1280*800)
xScaleFactor=this.width/1280;
yScaleFactor=this.height/800;
ScaleFactor=Math.min(xScaleFactor,yScaleFactor);
trace("ancho del dispositivo:
"+FlexGlobals.topLevelApplication.width);
trace("dpi del dispositivo:
"+FlexGlobals.topLevelApplication.applicationDPI);
trace("scalar por "+ ScaleFactor);
//scalar para el dispositivo
FlexGlobals.topLevelApplication.scaleX=ScaleFactor
FlexGlobals.topLevelApplication.scaleY=ScaleFactor;
2013/4/12 Alex Harui
>
>
>
> On 4/12/13 10:07 AM, "Scott Matheson" wrote:
>
> > Hi
> >Some good points, we are developing for 1024 x 768, as most screen
> are
> > larger than this, however with the browser URL etc on some devices you
> end
> > up with score bars, all graphics are vectors so we think these will scale
> > well, that¹s what our limited testing has shown, the screen are very
> > simple with lost of space, so we could scale the design down
> If you scale too far, fonts will get too small to read. But in general,
> scaling causes lines/edges that were on pixel boundaries to no longer be on
> pixel boundaries and then anti-aliasing kicks in and the colors change or
> edges look fuzzy. Quite frankly, I never notice unless told to look, but
> some folks have a sensitivity to this sort of thing.
> >
> > This was a v3 app we upgraded, to V4 I also implemented a Main and
> AppBase
> > class, looks like I may not have updated all mx: to S;
> >
> > Should is change the base imports ?
> I think Flex 4 has different scaling behavior than Flex 3, and Spark does
> not show scrollbars by default, so probably worth trying.
> >
> >
> ===
> > =
> >
> > AppBase.AS
> >
> >
> > package baseclasses
> > {
> > import com.peach.uofs.services.LoadCenters;
> >
> >
> > import flash.events.IEventDispatcher;
> >
> >
> > import mx.core.Application;
> > import mx.core.FlexGlobals;
> > import mx.events.FlexEvent;
> > import mx.events.StyleEvent;
> > import mx.styles.IStyleManager2;
> >
> >
> >
> > public class AppBase extends Application
> >
> >
> >
> >
> ===
> > ==
> >
> > Main.mxml
> >
> > > layout="absolute"
> > xmlns:fx="http://ns.adobe.com/mxml/2009";
> > xmlns:mx="library://ns.adobe.com/flex/mx"
> > xmlns:s="library://ns.adobe.com/flex/spark"
> > xmlns:baseclasses="baseclasses.*"
> > xmlns:components="com.peach.uofs.components.*"
> > xmlns:skins="skins.*"
> > creationComplete="init()" >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On 4/12/13 5:12 PM, "Alex Harui" wrote:
> >
> >> Is this mx:Application or s:Application?
> >>
> >> Why are you trying to adjust the scale? I would think that would make
> >> your
> >> app look a bit "fuzzy" as things won't be on pixel boundaries. You
> might
> >> be
> >> better off with a main container offset within the application.
> >>
> >> If the main container isn't also "shrinkable", that might be what causes
> >> the
> >> scroll bars.
> >>
> >>
> >> On 4/12/13 8:10 AM, "Scott Matheson" wrote:
> >>
> >>> Hi
> >>> Not sure if this is the correct place, I will ask anyway
> >>>
> >>> In my Main.mxml I have a simple code
> >>>
> >>> this.scaleX = this.scaleX 0.1
> >>> this.scaleY = this,scaleY 0.1
> >>>
> >>> This works fine for the main container, but not the Application, so I
> >>> end up
> >>> with scroll bars
> >>>
> >>> How do I scale the application not the first container
> >>>
> >>> Scott
> >>>
> >>>
> >>>
> >>>
> >>> Disclaimer: This electronic mail and any attachments are confidential
> >>> and may
> >>> be privileged. If you are not the intended recipient, please notify the
> >>> sender
> >>> immediately by replying to this email, and destroy all copies of this
> >>> email
> >>> and any attachments. Thank you.
> >>
> >> --
> >> Alex Harui
> >> Flex SDK Team
> >> Adobe Systems, Inc.
> >> http://blogs.adobe.com/aharui
> >>
> >
> >
> >
> >
> > Disclaimer: This electronic mail and any attachments are confidential
> and may
> > be privileged. If you are not the intended recipient, please notify the
> sender
> > immediately by replying to this email, and destroy all copies of this
> email
> > and any attachments. Thank you.
>
> --
> Alex Harui
> Flex SDK Team
>
Re: Application Scale
Hi all,
david, one question, did you do a jpg? And where did you put the code you wrote?
Thx?
Sent from my
On Apr 12, 2013, at 20:18, atauri wrote:
> Hi, I am using the following function, and it works like a charm to me.
> First I designed the interface for 1280*800 (using phtoshop) and then
> positioned the elements in pixels (no anchors, or relative position). It
> scales great to any phone, tablet even desktop. Hope it helps.
>
>//escalar al dispositivo (se diseñó para 1280*800)
>xScaleFactor=this.width/1280;
>yScaleFactor=this.height/800;
>ScaleFactor=Math.min(xScaleFactor,yScaleFactor);
>
>trace("ancho del dispositivo:
> "+FlexGlobals.topLevelApplication.width);
>trace("dpi del dispositivo:
> "+FlexGlobals.topLevelApplication.applicationDPI);
>trace("scalar por "+ ScaleFactor);
>
>//scalar para el dispositivo
>FlexGlobals.topLevelApplication.scaleX=ScaleFactor
>FlexGlobals.topLevelApplication.scaleY=ScaleFactor;
>
>
> 2013/4/12 Alex Harui
>
>>
>>
>>
>> On 4/12/13 10:07 AM, "Scott Matheson" wrote:
>>
>>> Hi
>>> Some good points, we are developing for 1024 x 768, as most screen
>> are
>>> larger than this, however with the browser URL etc on some devices you
>> end
>>> up with score bars, all graphics are vectors so we think these will scale
>>> well, that¹s what our limited testing has shown, the screen are very
>>> simple with lost of space, so we could scale the design down
>> If you scale too far, fonts will get too small to read. But in general,
>> scaling causes lines/edges that were on pixel boundaries to no longer be on
>> pixel boundaries and then anti-aliasing kicks in and the colors change or
>> edges look fuzzy. Quite frankly, I never notice unless told to look, but
>> some folks have a sensitivity to this sort of thing.
>>>
>>> This was a v3 app we upgraded, to V4 I also implemented a Main and
>> AppBase
>>> class, looks like I may not have updated all mx: to S;
>>>
>>> Should is change the base imports ?
>> I think Flex 4 has different scaling behavior than Flex 3, and Spark does
>> not show scrollbars by default, so probably worth trying.
>> ===
>>> =
>>>
>>> AppBase.AS
>>>
>>>
>>> package baseclasses
>>> {
>>>import com.peach.uofs.services.LoadCenters;
>>>
>>>
>>>import flash.events.IEventDispatcher;
>>>
>>>
>>>import mx.core.Application;
>>>import mx.core.FlexGlobals;
>>>import mx.events.FlexEvent;
>>>import mx.events.StyleEvent;
>>>import mx.styles.IStyleManager2;
>>>
>>>
>>>
>>>public class AppBase extends Application
>> ===
>>> ==
>>>
>>> Main.mxml
>>>
>>> >>layout="absolute"
>>>xmlns:fx="http://ns.adobe.com/mxml/2009";
>>>xmlns:mx="library://ns.adobe.com/flex/mx"
>>>xmlns:s="library://ns.adobe.com/flex/spark"
>>>xmlns:baseclasses="baseclasses.*"
>>>xmlns:components="com.peach.uofs.components.*"
>>>xmlns:skins="skins.*"
>>>creationComplete="init()" >
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On 4/12/13 5:12 PM, "Alex Harui" wrote:
>>>
Is this mx:Application or s:Application?
Why are you trying to adjust the scale? I would think that would make
your
app look a bit "fuzzy" as things won't be on pixel boundaries. You
>> might
be
better off with a main container offset within the application.
If the main container isn't also "shrinkable", that might be what causes
the
scroll bars.
On 4/12/13 8:10 AM, "Scott Matheson" wrote:
> Hi
>Not sure if this is the correct place, I will ask anyway
>
> In my Main.mxml I have a simple code
>
> this.scaleX = this.scaleX 0.1
> this.scaleY = this,scaleY 0.1
>
> This works fine for the main container, but not the Application, so I
> end up
> with scroll bars
>
> How do I scale the application not the first container
>
> Scott
>
>
>
>
> Disclaimer: This electronic mail and any attachments are confidential
> and may
> be privileged. If you are not the intended recipient, please notify the
> sender
> immediately by replying to this email, and destroy all copies of this
> email
> and any attachments. Thank you.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
>>>
>>>
>>>
>>>
>>> Disclaimer: This electronic mail and any attachments are confidential
>> and may
>>> be privileged. If you are not
Re: Application Scale
We had a similar solution. We created a Group that is a child of the
application. This allows us to have different applications but thesame
main group. The reason is we can then use different CSS style sheets
for different application targets.
Then in the application resize we check for the minimum width:
protected function application1_resizeHandler(event:ResizeEvent):void
{
resizeApplication();
}
protected function resizeApplication():void {
if (!systemManager) return;
var visibleWidth:Number =
systemManager.getVisibleApplicationRect().width;
var visibleHeight:Number =
systemManager.getVisibleApplicationRect().height;
// if the visible area is less than our content then scale down
if (visibleHeight < ApplicationModel.APPLICATION_MIN_HEIGHT ||
visibleWidth < ApplicationModel.APPLICATION_MIN_WIDTH) {
var smallestScale:Number =
Math.min(visibleHeight/ApplicationModel.APPLICATION_MIN_HEIGHT,
visibleWidth/ApplicationModel.APPLICATION_MIN_WIDTH);
parentGroup.scaleX = smallestScale;
parentGroup.scaleY = smallestScale;
}
else {
parentGroup.scaleY = 1;
parentGroup.scaleX = 1;
}
}
On Fri, Apr 12, 2013 at 1:18 PM, atauri wrote:
> Hi, I am using the following function, and it works like a charm to me.
> First I designed the interface for 1280*800 (using phtoshop) and then
> positioned the elements in pixels (no anchors, or relative position). It
> scales great to any phone, tablet even desktop. Hope it helps.
>
> //escalar al dispositivo (se diseñó para 1280*800)
> xScaleFactor=this.width/1280;
> yScaleFactor=this.height/800;
> ScaleFactor=Math.min(xScaleFactor,yScaleFactor);
>
> trace("ancho del dispositivo:
> "+FlexGlobals.topLevelApplication.width);
> trace("dpi del dispositivo:
> "+FlexGlobals.topLevelApplication.applicationDPI);
> trace("scalar por "+ ScaleFactor);
>
> //scalar para el dispositivo
> FlexGlobals.topLevelApplication.scaleX=ScaleFactor
> FlexGlobals.topLevelApplication.scaleY=ScaleFactor;
>
>
Re: Application Scale
Hi Angelo, the function goes in the app xml, the ini fuction. import
mx.core.FlexGlobals;
http://ns.adobe.com/mxml/2009";
xmlns:s="library://ns.adobe.com/flex/spark"
firstView="views.videoView"
backgroundColor="#00"
width="1280"
height="800"
xmlns:myClasses="myClasses.*"
initialize="ini()"
>
then my interface (views.videoView") looks like
all sizes in pixels.
I used photoshop to draw an d position elements and measure distances in
pixels.
Good luck
2013/4/12 Angelo Lazzari
> Hi all,
> david, one question, did you do a jpg? And where did you put the code you
> wrote?
>
> Thx?
>
> Sent from my
>
> On Apr 12, 2013, at 20:18, atauri wrote:
>
> > Hi, I am using the following function, and it works like a charm to me.
> > First I designed the interface for 1280*800 (using phtoshop) and then
> > positioned the elements in pixels (no anchors, or relative position). It
> > scales great to any phone, tablet even desktop. Hope it helps.
> >
> >//escalar al dispositivo (se diseñó para 1280*800)
> >xScaleFactor=this.width/1280;
> >yScaleFactor=this.height/800;
> >ScaleFactor=Math.min(xScaleFactor,yScaleFactor);
> >
> >trace("ancho del dispositivo:
> > "+FlexGlobals.topLevelApplication.width);
> >trace("dpi del dispositivo:
> > "+FlexGlobals.topLevelApplication.applicationDPI);
> >trace("scalar por "+ ScaleFactor);
> >
> >//scalar para el dispositivo
> >FlexGlobals.topLevelApplication.scaleX=ScaleFactor
> >FlexGlobals.topLevelApplication.scaleY=ScaleFactor;
> >
> >
> > 2013/4/12 Alex Harui
> >
> >>
> >>
> >>
> >> On 4/12/13 10:07 AM, "Scott Matheson" wrote:
> >>
> >>> Hi
> >>> Some good points, we are developing for 1024 x 768, as most screen
> >> are
> >>> larger than this, however with the browser URL etc on some devices you
> >> end
> >>> up with score bars, all graphics are vectors so we think these will
> scale
> >>> well, that¹s what our limited testing has shown, the screen are very
> >>> simple with lost of space, so we could scale the design down
> >> If you scale too far, fonts will get too small to read. But in general,
> >> scaling causes lines/edges that were on pixel boundaries to no longer
> be on
> >> pixel boundaries and then anti-aliasing kicks in and the colors change
> or
> >> edges look fuzzy. Quite frankly, I never notice unless told to look,
> but
> >> some folks have a sensitivity to this sort of thing.
> >>>
> >>> This was a v3 app we upgraded, to V4 I also implemented a Main and
> >> AppBase
> >>> class, looks like I may not have updated all mx: to S;
> >>>
> >>> Should is change the base imports ?
> >> I think Flex 4 has different scaling behavior than Flex 3, and Spark
> does
> >> not show scrollbars by default, so probably worth trying.
> >>
> ===
> >>> =
> >>>
> >>> AppBase.AS
> >>>
> >>>
> >>> package baseclasses
> >>> {
> >>>import com.peach.uofs.services.LoadCenters;
> >>>
> >>>
> >>>import flash.events.IEventDispatcher;
> >>>
> >>>
> >>>import mx.core.Application;
> >>>import mx.core.FlexGlobals;
> >>>import mx.events.FlexEvent;
> >>>import mx.events.StyleEvent;
> >>>import mx.styles.IStyleManager2;
> >>>
> >>>
> >>>
> >>>public class AppBase extends Application
> >>
> ===
> >>> ==
> >>>
> >>> Main.mxml
> >>>
> >>> >>>layout="absolute"
> >>>xmlns:fx="http://ns.adobe.com/mxml/2009";
> >>>xmlns:mx="library://ns.adobe.com/flex/mx"
> >>>xmlns:s="library://ns.adobe.com/flex/spark"
> >>>xmlns:baseclasses="baseclasses.*"
> >>>xmlns:components="com.peach.uofs.components.*"
> >>>xmlns:skins="skins.*"
> >>>creationComplete="init()" >
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> On 4/12/13 5:12 PM, "Alex Harui" wrote:
> >>>
> Is this mx:Application or s:Application?
>
> Why are you trying to adjust the scale? I would think that would make
> your
> app look a bit "fuzzy" as things won't be on pixel boundaries. You
> >> might
> be
> better off with a main container offset within the application.
>
> If the main container isn't also "shrinkable", that might be what
> causes
> the
> scroll bars.
>
>
> On 4/12/13 8:10 AM, "Scott Matheson"
> wrote:
>
> > Hi
> >Not sure if this is the correct place, I will ask anyway
> >
> > I
