Ext Core

[Lloyd K]

Will you be creating a seperate forum group for Ext Core?

[aconran]

We've thought about it.... What does the community think?

I think it would be a bad idea because then knowledge that was applicable to both Ext JS and Ext Core would be split apart rather than found at the same place. Since everything that applies to Ext Core will also apply to Ext JS.

I think it is a good idea because then people responding and trying to assist other members know what possible features/methods are available. For example, that addClassOnOver is not available on Ext.Element or that XTemplate's looping/conditional constructs are not available.

[VinylFox]

...speaking of addClassOnOver not being available...

http://content.screencast.com/users/VinylFox/folders/Jing/media/9960d867-d5e2-4371-ba6e-9e4b50c230c6/2009-04-06_0948.png

im sure you know about it already, but that error comes up on all the forum pages.

[Lloyd K]

That was my thoughts too, I guess they could just do [Core] in the titles which would help but not a lot of people adhere to those things (including myself sometimes).

[mabello]

I would expect that Ext.Element in Ext.core and in Ext 3.0 possibly contain mainly the same code (if not exactly the same!).
I mean, Ext core in my opinion should be the base library also for Ext 3.0 which build all the other "packages" on top of that.
So for example the core folder both in Ext 3.0 and Ext core contain the same Element.js file (same code), but of course Ext 3.0 contains also a "core extension" folder in which Element is extended with other functionalities...
Maintaining the code this way should be simpler and the code is more consistent.

[aconran]

mabello -

We took a very similar approach as what you've suggested. The Ext JS Element has just added several additional methods to the Ext Core Element.

[mabello]

@aconran

Thanks for your quick reply.
I like that :)

[mjlecomte]

We've thought about it.... What does the community think?

I think it would be a bad idea because then knowledge that was applicable to both Ext JS and Ext Core would be split apart rather than found at the same place. Since everything that applies to Ext Core will also apply to Ext JS.

I think it is a good idea because then people responding and trying to assist other members know what possible features/methods are available. For example, that addClassOnOver is not available on Ext.Element or that XTemplate's looping/conditional constructs are not available.

A separate thread has been created for manual/api doc bugs.

The bugs thread people can/should put [3.x CORE] if it's core specific.

So no new forum needed for above two points.

As to general help, maybe let the issue fester a bit and see if it becomes a problem.

It's not too often that questions related to core type methods have come up before. Even if you create a separate forum I suspect people will mispost anyway.

[mabello]

I agree with mjlecomte.
It's also likely that if a developer uses just the Ext core finds the same bugs of a developer using the whole ext, mainly because Ext itself is based on the core...we will end up replicating lot of questions, bugs and requests...

[deanna]

I think 1 forum will work better, but there probably needs to be a sticky for core components that have extra functionality added in extjs to avoid confusion.

[syscobra]

Well, maybe a sub-forum can do the job...

Just enter the ExtJS Forum and there you found a Sub forum for Extcore only...

Just a suggestion

[dawesi]

any chance of getting tags on posts? or perhaps you can click a checkbox to add meta? Whatever you do with the 3.x forums of any kind, please allow them to be searched on versions?

[ ] ExtJS 2.x [ ] - ExtJS GWT 2.x - [ ] ExtJS 3.x - [ ] ExtJS 3.x Core - [ ] ExtJS 3.x GWT