Ext JS 4.1 Beta 2 is Now Available

[dongryphon]

Moving from 4.0.6 to 4.1b2 I was not happy when I started switching one app as many things didn't work out of the box. But ... as I could identify and remove one hurdle after the other ... a pretty much faster app reveals ... I am starting to like 4.1 ... and so will the endusers if I succeed in removing the remaining hurdles ... thumbs up on 4.1 :-)

Glad to hear things are looking up.

Outside of the issues discussed elsewhere (http://www.sencha.com/forum/showthre...29-API-Changes), our goal is to be backwards compatible with 4.0x. So, if you are hitting compatibility issues, we'd love to hear about them so that we can address them for GA. That would also probably be of value to others.

Thanks for the feedback!

[ashaihullin]

Does anybody have problems with tree in opera? I already wrote about this bug there http://www.sencha.com/forum/showthre...Panel-in-Opera, but i thought it have been repaired in next beta, but now I have this problems with b2, too. Any advise?

[KajaSheen]

I keep testing the MVC example app from the learning center, that is also included as the app/simpe example in the code. Since Beta-1 (and now in Beta-2 as well) the updating from the form to the grid does not work the same anymore.

The original controller/Users.js::updateUser function in the example is as follows:

    updateUser: function(button) {
        var win    = button.up('window'),
            form   = win.down('form'),
            record = form.getRecord(),
            values = form.getValues();

        record.set(values);
        win.close();
        this.getUsersStore().sync();
    } 

When I use the following method instead it works as expected:

    updateUser: function(button) {
        var win    = button.up('window');
        form   = win.down('form');  
            
        record = form.getRecord();
        form.getForm().updateRecord(record);

        win.close();
        this.getUsersStore().sync();
    } 

It seems that record.set(values) does not force an update on the grid anymore (when clicking the table row again the correctly changed values from the prior edit are shown.

Also to make this example work, the data/updateUsers.json has to return the same data as changed in the form, i.e.

{
    success: true,
    users: [
        {id: 1, name: 'Eddy',    email: 'ed@sencha.com'}
    ]    
} 

Otherwise looking forward to the final release.

[silcreval]

AWESOME job guys. This worked out of the box on a very complex app for me. There were a few minor glitches, but compared to b1 this is a massive move forward - at least for my app.

Icons still dont appear in Firefox by the way on the 'kitchen sink' demo.

[slemmon]

I'm having trouble moving forward in testing B2. The issues that I'm seeing are at times only showing up when deployed on our Windows 2008R2 webserver using IIS7. 2.2, 3.x, and 4.0.7 projects are working fine on the same platform. Is anyone else having difficulty with Beta publishing on a Windows platform?

I have reported some issues/anomalies here:
http://www.sencha.com/forum/showthre...-layout-in-IE8
http://www.sencha.com/forum/showthre...dows-webserver
http://www.sencha.com/forum/showthre...n-a-web-server
http://www.sencha.com/forum/showthre...ed-from-shadow

I know on a B1 report that Evant wasn't able to reproduce the issue with the treepanel's horizontal scrollbar. And I wasn't able to either on my file system or when I deployed the sample code to my Apache server, but can't escape it in our production Windows webservers.

[BulletzBill]

Any chance you guys could include a scoped version of the gray theme in 4.1 and future releases?

[mystix]

It seems that record.set(values) does not force an update on the grid anymore (when clicking the table row again the correctly changed values from the prior edit are shown.

that's caused by this bug:
http://www.sencha.com/forum/showthre...FieldNames-arg

[ashaihullin]

What happend with button's borders?
How to remove this extra styles:

<div id="button-1023" class="x-btn x-btn-default-small x-noicon x-btn-noicon x-btn-default-small-noicon" style="padding-top: 8px; padding-right: 8px; padding-bottom: 8px; padding-left: 8px; margin-right: auto; margin-left: auto; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; "><em id="button-1023-btnWrap"><button id="button-1023-btnEl" type="button" class="x-btn-center" hidefocus="true" role="button" autocomplete="off" style="width: 84px; "><span id="button-1023-btnInnerEl" class="x-btn-inner" style="width: 84px; ">Text</span><span id="button-1023-btnIconEl" class="x-btn-icon "></span></button></em></div>

[jvdwiel]

Does anyone else get this error in firefox :

default = fields.get("default"), ext-all-dev.js (line 638)

function = fields.get("function"), ext-all-dev.js (line 640)



default = fields.get("default"), ext-all-debug.js (line 462, col 4)

function = fields.get("function"),ext-all-debug.js (line 464, col 4)

in Chrome :

Uncaught SyntaxError: Unexpected token default ext-all-debug.js:454
Uncaught SyntaxError: Unexpected token function ext-all-debug.js:454

[dongryphon]

Does anyone else get this error in firefox :

default = fields.get("default"), ext-all-dev.js (line 638)

function = fields.get("function"), ext-all-dev.js (line 640)



default = fields.get("default"), ext-all-debug.js (line 462, col 4)

function = fields.get("function"),ext-all-debug.js (line 464, col 4)

in Chrome :

Uncaught SyntaxError: Unexpected token default ext-all-debug.js:454
Uncaught SyntaxError: Unexpected token function ext-all-debug.js:454

The issue is with the new optimizations for data reading. Internally, a generated function uses field names to hold values but if the field names are reserved JS keywords, you'll have this kind of error. This is a high priority bug for us to get fixed.