[flexcoders] 2 Questions abot TextField in ActionScript
1- Is it possible to create a translucent TextField (or whatever class that can be added to a DisplayObjectContainer to display) ? How? 2- The same question about a text with halo? Thanks
RE: [flexcoders] 2 Questions abot TextField in ActionScript
1. Yes. By default, flash.display.TextField does not have an opaque background; to get one, you have to set its background:Boolean property, and then you can set backgroundColor:uint to determine what color the background is. 2. Can you be more specific? What Halo component are you talking about? Label? Text? TextInput? TextArea? Gordon Smith Adobe Flex SDK Team From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of ACasualObserver Sent: Tuesday, May 12, 2009 12:53 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] 2 Questions abot TextField in ActionScript 1- Is it possible to create a translucent TextField (or whatever class that can be added to a DisplayObjectContainer to display) ? How? 2- The same question about a text with halo? Thanks
[flexcoders] 2 Questions
Hi all I want to design a menu banner with synchronous loading as u can see in this link http://www.emaar.com/misr/ when the page is loading and the second question is how to replace the setting word if right click in this page url with any word
Re: [flexcoders] 2 questions
On Thursday 02 November 2006 15:26, DJ Lift wrote: Question 1: Is it best to use States or ViewStacks to deal with changing app states? We use view stacks here, because so much changes between the two states. Question 2: Is it good practice to have components be able to talk and share information with one another? And if so, how do you keep them around and reference them if you're using viewstates? Yes, but you should do it by both of them talking to a third 'model' component that holds all your (shared) data. Have a look at Cairngorm's ModelLocator for an example. -- Tom Chiverton Helping to authoritatively enable attention-grabbing initiatives This email is sent for and on behalf of Halliwells LLP. Halliwells LLP is a limited liability partnership registered in England and Wales under registered number OC307980 whose registered office address is at St James's Court Brown Street Manchester M2 2JF. A list of members is available for inspection at the registered office. Any reference to a partner in relation to Halliwells LLP means a member of Halliwells LLP. Regulated by the Law Society. CONFIDENTIALITY This email is intended only for the use of the addressee named above and may be confidential or legally privileged. If you are not the addressee you must not read it and must not use any information contained in nor copy it nor inform any person other than Halliwells LLP or the addressee of its existence or contents. If you have received this email in error please delete it and notify Halliwells LLP IT Department on 0870 365 8008. For more information about Halliwells LLP visit www.halliwells.com. -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ * Your email settings: Individual Email | Traditional * To change settings online go to: http://groups.yahoo.com/group/flexcoders/join (Yahoo! ID required) * To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] * To unsubscribe from this group, send an email to: [EMAIL PROTECTED] * Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
RE: [flexcoders] 2 questions
The only time Ive used states is transitioning from two different contexts specifically from a login screen to the initial state of the application after login. (I wanted to animate the transition) As for components, my approach is to black box them and leverage the event model for communicating. As soon as one component knows about another, re-use is pretty much compromised. Your app itself can use listeners to catch and respond to these events and orchestrate things between components. HTH, Stace From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf Of Igor Costa Sent: Thursday, November 02, 2006 1:12 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] 2 questions better uses of viewStack On 11/2/06, DJ Lift [EMAIL PROTECTED]net wrote: Hi there, Have some questions about the best practice way of designing apps. I'm building a simple email server preferences application. And I've created two components. One for handling the login (which hits amfphp and ldap on the backend) and one for loading and changing/saving the user prefs (which also hits amfphp and ldap on the backend). There are really only two states, login handilng, and prefs changing. Question 1: Is it best to use States or ViewStacks to deal with changing app states? on to my second question... The login component is sorta self sufficient. It can handle good logins and bad ones. and if it's a good login can switch the current state to the preferences state (as viewstates are what i'm currently working with.) But when i get to the email preferences state, it wants to know things from the login component, like email and password. Question 2: Is it good practice to have components be able to talk and share information with one another? And if so, how do you keep them around and reference them if you're using viewstates? Thanks, mark -- Igor Costa www.igorcosta.com __._,_.___ -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com SPONSORED LINKS Software development tool Software development Software development services Home design software Software development company Your email settings: Individual Email|Traditional Change settings via the Web (Yahoo! ID required) Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe __,_._,___
[flexcoders] 2 questions
Hi there, Have some questions about the best practice way of designing apps. I'm building a simple email server preferences application. And I've created two components. One for handling the login (which hits amfphp and ldap on the backend) and one for loading and changing/saving the user prefs (which also hits amfphp and ldap on the backend). There are really only two states, login handilng, and prefs changing. Question 1: Is it best to use States or ViewStacks to deal with changing app states? on to my second question... The login component is sorta self sufficient. It can handle good logins and bad ones. and if it's a good login can switch the current state to the preferences state (as viewstates are what i'm currently working with.) But when i get to the email preferences state, it wants to know things from the login component, like email and password. Question 2: Is it good practice to have components be able to talk and share information with one another? And if so, how do you keep them around and reference them if you're using viewstates? Thanks, mark -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ * Your email settings: Individual Email | Traditional * To change settings online go to: http://groups.yahoo.com/group/flexcoders/join (Yahoo! ID required) * To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] * To unsubscribe from this group, send an email to: [EMAIL PROTECTED] * Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
Re: [flexcoders] 2 questions
better uses of viewStackOn 11/2/06, DJ Lift [EMAIL PROTECTED] wrote: Hi there, Have some questions about the best practice way of designing apps. I'm building a simple email server preferences application. And I've created two components. One for handling the login (which hits amfphp and ldap on the backend) and one for loading and changing/saving the user prefs (which also hits amfphp and ldap on the backend). There are really only two states, login handilng, and prefs changing. Question 1: Is it best to use States or ViewStacks to deal with changing app states? on to my second question... The login component is sorta self sufficient. It can handle good logins and bad ones. and if it's a good login can switch the current state to the preferences state (as viewstates are what i'm currently working with.) But when i get to the email preferences state, it wants to know things from the login component, like email and password. Question 2: Is it good practice to have components be able to talk and share information with one another? And if so, how do you keep them around and reference them if you're using viewstates? Thanks, mark -- Igor Costawww.igorcosta.com __._,_.___ -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com SPONSORED LINKS Software development tool Software development Software development services Home design software Software development company Your email settings: Individual Email|Traditional Change settings via the Web (Yahoo! ID required) Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe __,_._,___
