Re: new namespace convention

Re: new namespace convention

Can you use the Java package convention instead ? ie ext.BasicDialog instead of Ext.BasicDialog?

I prefer anything that follows a more or less strict convention, and if the convention is "namespaces and classes start with uppercase", it's probably better to use Ext.

Btw, I see the Ext namespace as a move to drop the YAHOO namespace one day. Is this correct? I think this would make sense. Yes, it would break compatibility but it is a find & replace operation to put everything working again.

Also, it would be nice to have a "code conventions" page on the wiki (I'm sorry but I'm in a rush this month due to a release, but when things calm down I'll be back and contribute with some wiki pages ;-)).

I would love to use ext instead of Ext, but it may clash with local variables. Ext is already pushing it but I doubt there will be variables named Ext (at least I am hoping). Package names should be lowercase (and all sub packages will be) but the root namespace has to be capital to prevent conflicts with local variables.

Btw, I see the Ext namespace as a move to drop the YAHOO namespace one day. Is this correct? I think this would make sense. Yes, it would break compatibility but it is a find & replace operation to put everything working again.

Yes the YAHOO namespace is going away. I can't wait! It will remain backwards compatible though, as I will alias Ext as YAHOO.ext and keep code working.

Btw, I see the Ext namespace as a move to drop the YAHOO namespace one day. Is this correct? I think this would make sense. Yes, it would break compatibility but it is a find & replace operation to put everything working again.

Yes the YAHOO namespace is going away. I can't wait! It will remain backwards compatible though, as I will alias Ext as YAHOO.ext and keep code working.

Since YUI-ext is morphing into a full blown library which uses some YUI classes / concenpts rather than an extension of YUI, does a package name "Ext" make that much sense? It's kinda a general non defining namespace. Have you considered coming up with a real name for this project? If not, does "YuiX" have a better ring than "Ext"? Just thinking out loud.

Since YUI-ext is morphing into a full blown library which uses some YUI classes / concenpts rather than an extension of YUI, does a package name "Ext" make that much sense? It's kinda a general non defining namespace. Have you considered coming up with a real name for this project? If not, does "YuiX" have a better ring than "Ext"? Just thinking out loud.

I was thinking about this yesterday, Sanjiv, and after questioning the meaning of the name I concluded that "Ext" could actually be a good name, unless there is already a javascript library with a similar name. Because YUI-ext provides a series of tools to extend Javascript itself and our power to make nice looking applications. Well, I think that Ext is fine, sexy and short. Unless there was some other very nice name (like "Koopaloopa" :lol, how would we call it?

just my 0.02. ;-)

PS: remember that YuiX still makes reference to YUI, so I guess this is not an option.

I'm with moraes, I really like Ext. It's short and sweet. Also, I think it allows the existing "brand" awareness for yui-ext to not be completely destroyed.

Like moraes noted, the meaning is a little different than "Extensions". The idea is to have a new tag line along the lines of "Extending the web experience" or "Extended JavaScript Components" or "Extend your web application" (I am open to suggestions).