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

Wed, 09 Aug 2006 08:16:13 -0700

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

That also makes perfect sense. :)

Seems like that is a good rule if the public interface is thought out.

I don't think you can bind static or const anyway.? Seems to me this is not implemented. I remember trying to bind to a static property in an mxml component and it didn't work. Compiler complained.

Peace, Mike

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





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



__,_._,___

Reply via email to