Search Type: Posts; User: TizianoF
Search: Search took 0.01 seconds.
Is it possibile to get a better change log, like the one we used to (subdivided by component)?
The current one is practically impossible to read.
So you are releasing a new version with known open bugs??? I understood that right?
One the road map is reported as early march. So I expect it any day now (if they don't want to miss a deadline again...)
10 Feb 2010 10:46 PM
Ext documentation has to be put on a webserver (it cannot be read just opening the documentation page with a browser, like, for example, javadocs). I really never understood why they dropped the...
Just wondering, if big bugs are found in version 3.1.1 (considering how much you are changing this is likely to happen), what will we have to do? We will have to wait for 3.2 to see them fixed?
3 Feb 2010 3:34 AM
The problem is that while using version 2.x dragging a window on IE7 uses around 20% cpu, on 3.1 it uses 100%.
Try it yourself the 2.x desktop sample and 3.1 one and watch the cpu.
3 Feb 2010 3:08 AM
Is this problem fixed in the 3.1.1-rc?
This problem makes all complex application completely unusable on IE7, it must have high priority!!!
29 Jan 2010 5:44 AM
Is there any news on this problem?
Even in the desktop sample, when you drag a window cpu usage goes to 100% and the movement is not fluid.
Doing the same with version 2.2.1 (again desktop...
21 Dec 2009 4:04 AM
As we thought, Ext 3.1 released with all the bug fixed in 3.0.3 and no 3.0.4 version for those not interested in the new 3.1 features (that obviously will add new bugs).
So, no stable version if...
I'd like to add a similar behaviour to my application. My idea is to extend Ext.Window, so that it doesn't show on the current page but on a new browser window.
Do you believe it's something that...
This doesn't mean that 3.1.0 will have the same fixes included in the latest 3.0.X release. Instead 3.1.0 will have new fixes not included in any 3.0.X release.
So there won't be anymore a stable...
Please read again Abe's post:
"All of the support releases that lead up to 3.1 will be available".
He has not written that the latest 3.0.X support release will have the same bug fixes that...
So there will be a new 3.0.X release with all the bugs fixed included in 3.1 and not shipped in 3.0.3? Abe has not stated this...
There's a big difference.
ExtJS will never releases all the known bug fixes, i.e. for version 3.0.
3.0.3 will still miss the bug fixes between version 3.0.3 and 3.1.0, while 3.1.0 will have new...
2 Nov 2009 12:46 AM
What about the bug fixed between version 3.03 and 3.1?
We obviously won't get them...
18 Oct 2009 11:35 PM
Abe, please don't fool the people who bought Ext licenses. Up to a few months ago overiddes were posted on the bug forum for most of the bugs. So, with some time, you could fix the most important...
16 Oct 2009 1:23 AM
15 Oct 2009 7:37 AM
You are wrong.
You get the next version, that has a lot of more changes than the sum of 3.0.1+3.0.2 bug fixes. It is quite different that a bug fix release.
15 Oct 2009 4:25 AM
I know, but when even the example doesn't work that's not acceptable... that means the code was not even tested.
And in the last year this happened on every release from what I have seen.
15 Oct 2009 4:15 AM
Your release plan is nice, but you are missing an important point. Ext has an history of bugged releases.
From what I have seen in the last year, every new release introduced new bugs on existing...
15 Oct 2009 1:11 AM
What's next then? Release buggy versions just to get more people to buy a maintenance release to get the bugs fixed?
And another question came to my mind. What if I get the point release without...
14 Oct 2009 11:54 PM
So that means that if you do not pay you won't ever have a stable release. It's sure that the new features in version 3.1 will introduce new bugs...
This decision by ext makes no sense to me :-?
For instance this problem affects also IE6, I've just tested it.
Any chance to get a bug fix release for those that have paid for the license?
Results 1 to 25 of 61