That answers my question exactly.
I think my head goes off of this statement;
If I can realistically say thisPropertyChanged and it would have an effect on something especially commitProperties() it is bindable.
I can also see the difference you are stating with tabIndex. There is no reason someone would OR need to bind to that property because it is more of a tracking property.
Configuration is a good rule word.
Peace, Mike
On 8/9/06, Peter Hall <[EMAIL PROTECTED]> wrote:
Most should probably be bindable. Things that I would consider "configuration" properties that are unlikely to change, might not need to be bindable. That category would include things like tabIndex, but not really very many others..
PeterOn 8/9/06, Michael Schmalle < [EMAIL PROTECTED]> wrote:Hi,
Anybody care to shed light on when you would consider a component property Bindable?
I understand obviously the effects of what a bindable property is but, Adobe, what are your guidlines for declaring a property bindable in your components?
At times my head says, most could be bindable.
Peace, Mike
--
What goes up, does come down.
--
What goes up, does come down. __._,_.___![]()
SPONSORED LINKS
Custom software development Database development software Embedded software development Offshore software development Software development
YAHOO! GROUPS LINKS
- Visit your group "flexcomponents" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
__,_._,___
- [flexcomponents] [Bindable] :: Making a component G-S P... Michael Schmalle
- Re: [flexcomponents] [Bindable] :: Making a compon... Peter Hall
- Re: [flexcomponents] [Bindable] :: Making a co... Dominick Accattato
- Re: [flexcomponents] [Bindable] :: Making ... Dominick Accattato
- Re: [flexcomponents] [Bindable] :: Making ... Michael Schmalle
- Re: [flexcomponents] [Bindable] :: Making a co... Michael Schmalle
Reply via email to
