Shouldnt there be static definition for borderlayout -- SOUTH, NORTH, WEST, EAST ?

[seymores]

What do you guys think?

Just like Ext.Msg.ERROR, Ext.Msg.YESNO, ... etc , should there be something like Ext.Layout.NORTH, Ext.Layout.SOUTH, ...

If not for catching misspelling bug then at least for consistency sake.

:-)

Cheers

[jay@moduscreate.com]

what would prevent anyone from mistyping that? at least w/ the string method they can force it to lower case.

[seymores]

Hmmm you are right, this is no Java pre-compile checking.

However having a static definition should help in those auto-complete Javascript IDE right?

[jay@moduscreate.com]

i suppose. but you're assuming everyone uses an IDE with an Ext plugin.

[seymores]

I use Vim, but I get your point. ;-)

[jay@moduscreate.com]

vim pwns!

[loeppky]

seymores: I think you have a valid question. There is some inconsistency between when strings are passed verses a reference to a static variable. I assume passing strings around though is the more accepted behavior because it is less cumbersome than Ext.Layout.NORTH for example. If one ever needed to find all instances of using the north layout region, they could be confident doing a search for Ext.Layout.NORTH but not as confident searching for 'north'.

[evant]

The same could be said about other things, xtypes for instance.

[jack.slocum]

I'd rather save the bytes. If there were statics for everything it would be another 10k+ on the library. Let's use that for something useful.