Ext JS 4.0.2 RC released

[alphadogg]

Yeah, having issues with online RC docs too.

http://dev.sencha.com/deploy/ext-4.0...Ext.grid.Panel is stuck at loading content (although the object browser and title display fine).

[alphadogg]

Weird. I was clicking around and the top level items started working, now the Ext.grid.Panel shows too...

Never mind.

[westy]

Hi Ed,

Get lots of errors when building my CSS, missing images etc.
Probably another one for Robert, but thought would throw it out there...

Looks like how the config.rb is interpreted has changed.

My current config.rb:

# Grab the current dir
dir = File.dirname(__FILE__)

# Set our Ext path
$ext_path = '../../../lib/Ext/ext-4.0.2'   # This is our 'web' path
ext_filesystem_path = '../../../../ThirdPartyReferences/Ext/ext-4.0.2'

# We need to load in the Ext4 themes folder, which includes all it's default styling, images, variables and mixins
load File.join(dir, ext_filesystem_path, 'resources', 'themes')

# Sort out our SASS, CSS and images dirs
sass_path = dir
css_path = File.join(dir, "..", "css")
images_dir = File.join(dir, "..", "images")

# Specify the output style/environment
output_style = :expanded #:compressed
environment = :development #:production

As you can see, I have a web path ($ext_path) that seems to be what is put in the CSS file.

I also have a physical path to Ext (in a ThirdPartyReferences folder) that I put in so that the load statement worked, since that's a physical location on disk.

I want to avoid having to copy Ext to every single code repository, since that's the point of virtual directories on the web server (IIS in my case)...

If I change my config.rb to:

# Grab the current dir
dir = File.dirname(__FILE__)

# Set our Ext path
$ext_path = '../../../../ThirdPartyReferences/Ext/ext-4.0.2'

# We need to load in the Ext4 themes folder, which includes all it's default styling, images, variables and mixins
load File.join(dir, $ext_path, 'resources', 'themes')

# Sort out our SASS, CSS and images dirs
sass_path = dir
css_path = File.join(dir, "..", "css")
images_dir = File.join(dir, "..", "images")

# Specify the output style/environment
output_style = :expanded #:compressed
environment = :development #:production

Then I get no errors, but all of the image paths in my CSS are wrong.
Obviously I can post-process, but curious as to what has changed and why?

Remember we're not all on OSes that support symbolic or hard links properly (e.g. OSX), and is the norm rather than the exception I'm on Win7 x64 btw.

I'll hack my CSS for now so can give the release a whirl, but would welcome some support for those of us that want to have many repos and one copy of Ext.

Cheers,
Westy

[wsi2]

4.0.1 - scroller in infinite scrolling mode worked. 4.0.2 RC3 - scroller does not scroll rows at all

To clarify what doesn't work, the buffer-grid example can be used in Chrome 12.0.742.91:

1. Click once on the down scroll arrow, the grid will jump to records 31-50 instead of 2-21.
2. Now the grid cannot be scrolled above record 31.
3. Click 17 more times on the down scroll arrow. The grid will jump to records 56-75. Note the grid does not move at all during the previous 16 clicks.

More thorough bug-testing to come, including whether inserts/removes on buffered grids finally persist. Thanks for the fixes so far.

Update: Inserts, removes, and/or filtering on buffered grids still occur only on the currently paged segment. Scrolling to a different page, then scrolling back shows the additions, removals, and/or filtering do not persist.

[edspencer]

@ed,

Am setting it up now - thanks! Are there new SDK tools as part of this RC?

stevil

We actually have a separate release cycle for the SDK Tools but they're being worked on right now to address the image creation issues some people are seeing. I think we're also going to create some kind of notification system/release RSS feed that will inform you when new releases are put out.

[Animal]

Hi,
congratulation for the 4.0.2 release.
When first time click on a nested to the left menu, the items are shown partially. The second click goes OK.
Sorry for my bad English.
Attachment 26495

Well spotted. I'm fixing this right now.

[dorgan]

I still do not see any details on the grid configuration option for Ext.chart.Axis will this ever appear in the docs??

[edspencer]

I still do not see any details on the grid configuration option for Ext.chart.Axis will this ever appear in the docs??

I've asked one of our elite charts team to rectify this today

[fabio.parra]

I know that team is focused on improve performance in nested layouts, but a simple test creating 500 fields show almost same result as in 4.0.1.

Ext.ns('Automidia');

Automidia.Tester = {
    init : function(){
        this.panel = new Ext.form.FormPanel({
            title      : 'Performance Test',
            width      : 400,
            height     : 300,
            autoScroll : true,
            renderTo   : Ext.getBody(),
            buttons    : [{
                text    : 'Add',
                handler : this.onAddClick,
                scope   : this
            }]
        });
    },
    onAddClick : function(){
        var items = this.buildFields();
        var start = new Date();
        this.panel.add(items);
        this.panel.doLayout();
        var end = new Date();
        this.panel.setTitle((end - start) + ' miliseconds');
    },
    buildFields : function(){
        var items = [];
        for(var i=0;i<500;i++){
            items.push({
                xtype : 'textfield',
                fieldLabel : 'Campo ' + i
            });
        }
        return items;
    }

};


Ext.onReady(Automidia.Tester.init, Automidia.Tester);

4.0.2-rc3.jpg

[edspencer]

To clarify what doesn't work, the buffer-grid example can be used in Chrome 12.0.742.91:

1. Click once on the down scroll arrow, the grid will jump to records 31-50 instead of 2-21.
2. Now the grid cannot be scrolled above record 31.
3. Click 17 more times on the down scroll arrow. The grid will jump to records 56-75. Note the grid does not move at all during the previous 16 clicks.

More thorough bug-testing to come, including whether inserts/removes on buffered grids finally persist. Thanks for the fixes so far.

Update: Inserts, removes, and/or filtering on buffered grids still occur only on the currently paged segment. Scrolling to a different page, then scrolling back shows the additions, removals, and/or filtering do not persist.

I'm seeing the same behavior, will escalate this immediately for a fix. Thanks for reporting