Re: [flexcomponents] [Bindable] :: Making a component G-S Property bindable :: When?

[Dominick Accattato]

Also, I think you'd get a compiler error, but it should be noted that internal components should not be [Bindable].

 

right?

 

On 8/9/06, Dominick Accattato <[EMAIL PROTECTED]> wrote:

Remember to keep your bindable properties inline with your public interface.

 

A few more to be excluded from [Bindable]:

 

Constants

private properties should only be bindable through getters.

temporary vars (counter, i, j, k, etc) <-- obvious

and as Peter mentioned.. any internals (configs and such)

 

anything else?

 

Dominick Accattato, CTO

New View Networks

www.newviewnetworks.com

 

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..

Peter

On 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.

__._,_.___

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.

---

__,_._,___