-
10 Dec 2009 7:08 PM #1
ExtCore and ExtJS have different APIs like this?
ExtCore and ExtJS have different APIs like this?
Todays SVN
ExtCore:
Ext.Element.select = function(selector, root)
ExtJS:
Ext.Element.select = function(selector, unique, root) ...
I would have thought that ExtJS would just add an extra param to the end, not change the order of the parameters.
-
10 Dec 2009 7:21 PM #2
This isn't a bug, moving to general discussion.
Evan Trimboli
Sencha Developer
Twitter - @evantrimboli
Don't be afraid of the source code!
-
10 Dec 2009 7:24 PM #3
The reason it's like this is because CompositeElement (ie. the unique operator) isn't included in Ext Core. As such, there's no reason to have it.
Evan Trimboli
Sencha Developer
Twitter - @evantrimboli
Don't be afraid of the source code!
-
11 Dec 2009 11:08 AM #4
It would seem that these kind of minor inconsistencies could be a source of debugging headaches for users migrating from one product to the other and/or developing using both libraries for various products.
Tim Ryan
Read BEFORE posting a question / BEFORE posting a Bug
Use Google to Search - API / Forum
API Doc (4.x | 3.x | 2.x | 1.x) / FAQ / 1.x->2.x Migration Guide / 2.x->3.x Migration Guide
-
11 Dec 2009 4:55 PM #5Sencha - Community Support Team
- Join Date
- Jan 2009
- Location
- Palo Alto, California
- Posts
- 1,941
- Vote Rating
- 6
Agreed, we need to do everything we can to keep these APIs consistent
Ext JS Senior Software Architect
Personal Blog: http://edspencer.net
Twitter: http://twitter.com/edspencer
Github: http://github.com/edspencer
-
13 Dec 2009 8:24 AM #6


Reply With Quote

