Re: Ext Scheduler 2.1 alpha

[mats]

This is an alpha release based on Ext JS 4.1, tested only against Beta 3. It will not work with any Ext 4.0.x version. This release is not bug-free, and we would very much appreciate help in testing it and reporting anything you find.

The main goal of this 2.0 release is to upgrade to Ext JS 4.1 which brings better performance. Our initial tests show a 2x speed increase for the initial rendering.
We have also done some refactoring, and there is one breaking change: you must now use a new Sch.data.EventStore for your events.

For more details about known issues and things relating to our products and Ext JS please see our wiki: http://www.assembla.com/spaces/bryntum/wiki
or check the change log:
http://www.bryntum.com/products/scheduler/changelog/

The only thing you need to do to upgrade is replace code like this:

Code: Select all

 // Store holding all the events
            eventStore = Ext.create('Ext.data.JsonStore', {
                model : 'Sch.model.Event',
                data : [
                    {ResourceId : 'r1', PercentAllocated : 60, StartDate : new Date(2011, 0, 1, 10), EndDate: new Date(2011, 0, 1, 12)},
                    {ResourceId : 'r2', PercentAllocated : 20, StartDate : new Date(2011, 0, 1, 12), EndDate:new Date(2011, 0, 1, 13)},
                    {ResourceId : 'r3', PercentAllocated : 80, StartDate : new Date(2011, 0, 1, 14), EndDate:new Date(2011, 0, 1, 16)},
                    {ResourceId : 'r6', PercentAllocated : 100, StartDate : new Date(2011, 0, 1, 16),EndDate: new Date(2011, 0, 1, 18)}
                ]
            });


with:

Code: Select all

// Store holding all the events
            eventStore = Ext.create('Sch.data.EventStore', {
                data : [
                    {ResourceId : 'r1', PercentAllocated : 60, StartDate : new Date(2011, 0, 1, 10), EndDate: new Date(2011, 0, 1, 12)},
                    {ResourceId : 'r2', PercentAllocated : 20, StartDate : new Date(2011, 0, 1, 12), EndDate:new Date(2011, 0, 1, 13)},
                    {ResourceId : 'r3', PercentAllocated : 80, StartDate : new Date(2011, 0, 1, 14), EndDate:new Date(2011, 0, 1, 16)},
                    {ResourceId : 'r6', PercentAllocated : 100, StartDate : new Date(2011, 0, 1, 16),EndDate: new Date(2011, 0, 1, 18)}
                ]
            });

and exactly the same for Gantt, when replacing an Ext.data.Store with its model set to 'Gnt.model.Dependency', it should just be changed to Gnt.data.DependencyStore.

[rentconcept_kgr]

Hi Mats,

at first: nice job!
I have checked every day whether you released the 2.1
I have some Issues with the new Version but I have to analyse them first, then I will post here.

Sadly my biggest wish doesen't come true, a better performance when switching the ViewPreset.
I'm running my Scheduler with a HourDay View and a time span of 30 days.
With a slider you can switch between presets with different hour increments so you can display 1 to 4 days at once.

Maybe I can do something better or in an other way maybe with Sch.util.HeaderRenderers, but I nowhere found how to rerender the headers on the fly.

I added screenshots for a better understanding.

Kind regards,

Karol

[jakub]

Not sure if it's possible to do it faster, as changing viewPreset forces whole panel to re-render. We're currently working on zooming feature for timeline, so we're try to take a look into this also.

[rentconcept_kgr]

Cześć Kuba

thx for the fast answer.
The strange thing is that the re-rendering takes longer then the initial rendering.
e.g. in IE 7 it can be, that the browser aborts the rendering / excecuting of Javascript with the error message, that it takes to long.
You surely know this yes/no alert message to abort a Javascript routine that is running amok.


Kind regards,

Karol

[mats]

This is likely due to the large amount of columns you generate. I'd recommend using one/two columns and fill the headers with headerRenderers instead. This way you lose column lines but gain a lot in speed. Try it?

[rentconcept_kgr]

Hi Mats,

yes I know that the problem is caused by the amount of columns.
The dilemma is, that my customer (BMW Group) wants the ability to scroll trough the whole month.
In my first presentation I've used time spans of 1-4 days but the shifting trough the scheduler was to slow especially in IE 7.

I know that the performance is better now, but if you display the whole month with a scrollbar you have zero delay.
You also don't have to click the shift button few times to get the right day or open a datepicker to jump into the date you want etc.


It seems that it is hard to get both, switching the preset and have the whole month scrollable.

I've played around to reduce the columns as you proposed.
I use now DAY/DAY instead of DAY/HOUR presets and the dateCells function for the HeaderRenderer.

The speed is very better now!
But of course the hour column borders are gone now

Do you have any idea?
I could use background images for every day cell but that is botching imho.

kind regards,

Karol

[mats]

If your column width is fixed/known you could solve it using a background image with repeat? Or use Lines plugin populated with date lines?

[rentconcept_kgr]

I will try the solution with a background-image.
I will post whether it is a proper solution or not.
Should we move my problem to an other/new thread?
Because it's something general and has nothing to do with the new alpha version.

Thanks for your help.

Kind regards,

Karol

[mats]

Let's see how it goes first

[bartek.frontkiewicz]

Hi guys.

Great work on the alpha version - I can see really big speed improvement in rendering. I have some issues with dragging and dropping between schedulers though (the time hint is not showing and I always get red x, event though the event is dropped and saved correctly).

What are plans for the next version - one that will be working with rc1 instead of beta3?

Thanks

Bartek