[by WixSL]

THE BEST ASWER WAS #2 FROM "mitchellsimoens" NOT MY OWN RESPONSE.

Thank you so mutch, that will do it.
Sorry for not investigating well enough first in the docs.

[by WixSL]

I need to use a same Model definition, with dynamic fields.
Is there a way that I can pass a "fields" config object to a Model, and the Model takes it for each instance?

I found this in a post...

[by WixSL]

Just a sigestion, did you consider this thread:

http://www.sencha.com/forum/showthread.php?123787-Grid-performance-improvement-suggestion

[by WixSL]

That's what i thought.
Note: But i provide a test case with one of your examples.

[by WixSL]

1.- Open sample: http://dev.sencha.com/deploy/ext-4.1.0-gpl/examples/form/contact-form.html
and click on "Contact Us" Button

2.- Type an invalid e-mail address in the field "Your e-mail...

[by WixSL]

Ok. Thank you.

[by WixSL]

I want to know how to target a specific element or component when showing a Ext.MessageBox instead of targetting the page body.

Thanks.

[by WixSL]

Don't delete the filters, I need them for reuse:


Ext.ux.grid.GridFilters = Ext.extend(Ext.util.Observable, {
//...

/** @private */
constructor : function (config) {
...

[by WixSL]

Ok. I've solve it by defining a "fix" border layout skeleton and dynamically adding the components to the regions.

[by WixSL]

That's great.
Thank you so much.

I've mark mitchellsimoens answer as the best possible, witch in did it is.

But I still need an Ext 3.4.0 approach since most of my code is written with that...

[by WixSL]

Does Ext 4.1 allows adding dinamycally regions to a border layout.

If not, how can I solve he following type of situation:

For speed perseption reasons y create an Ext.Window and show it...

[by WixSL]

Try this:
As you doble click the button, move up and down the mouse pointer a little bit hovering the button.

Actually by doing this, you won't be able to make doble clicks, but clicking...

[by WixSL]

Just collapse the form's window, the borders remains visible.

31204

[by WixSL]

Border layout is easily breakable


Ext version tested:
Ext 4.1 beta 2

Browser versions tested against:
Google Chrome 16 IE6 Opera 12Alpha FF9.01 (firebug 1.9 installed) Safari 5

DOCTYPE...

[by WixSL]

Playing arround whith the border layout sample i get this.

31141

I was unable to put together a step by step bug reproduction, but i did it several times.

Always when collapsing and...

[by WixSL]

Ok, thank you very much for your reply.
Sorry for the insistance.

[by WixSL]

- Ext.String.repeat: This method dosn't work, "buf" variable is defined in the for() loop header, and is used after the loop (???).
- Ext.JSON: encodeArray: "newLine" argument never get used.
-...

[by WixSL]

Why this thread is marked as closed?
This are valid errors.

[by WixSL]

I realise lately, but yes is not a very legible style.
Thanks for the replay.

[by WixSL]

Fair enough.
I'll reduce the list to the errors if found:

- Ext.String.repeat: This method dosn't work, "buf" variable is defined in the for() loop header, and is used after the loop (???).
-...

[by WixSL]

Sorry, that may be the intended syntax.

[by WixSL]

Missed an "=" sign in the following if() statement:

if(me.maskRe || (me.vtype && me.disableKeyFilter !== true && (me.maskRe = Ext.form.field.VTypes[me.vtype+'Mask']))){

Is located in...

[by WixSL]

Some "Ext.String" method's arguments are treated as strings/arrays without being validated for their types, witch will lead to js errors:

From ext-all-debug.js:

- htmlDecodeReplaceFn:...

[by WixSL]

This seems incredible!
I didn't know it.
Thank you for the info.

[by WixSL]

I've send an e-mail to the FireBug mailing list reporting the following bug, but I thought it could be relevant letting you know about it since it involves a performance problem, and may help you in...