Sep 28, 2014, 1:40 AM
Then why don't you enlighten me and the community as to what version of Ext JS you guys are using.
Vladimir pointed me to the following link: http://www.sencha.com/forum/showthread.php?264700
If you read that page, you'll see the following:
The Commercial and GPL downloads are available here:
http://cdn.sencha.com/ext/commercial...commercial.zip
http://cdn.sencha.com/ext/gpl/ext-4.2.1-gpl.zip
The commercial link is out of the question because you previously admitted you only use public Ext JS releases.
GPL means General Public License, so I've concluded that you guys are using ext-4.2.1-gpl.zip.
Technically speaking, you're shipping a CUSTOM Ext JS version with Ext.NET. This is because you add your own bug fixes to Ext JS.
Moreover, branching someone else's code, changing it (bugs, what whatever), than distributing it to your clients as being the original (that is what you do on your website), is a very bad programming practice. Any junior software developer should be able to tell you that.
So, the claim on your website that Ext.NET supports Sencha Ext JS 4.2.1 is a bit dishonest: any developer that reads that will assume you support the official Sencha release.
I would like to suggest inform your clients on your website as to what version of Ext JS you use (public, commercial, custom, ...etc).
If you think I've misrepresented your development process, please don't hesitate to outline it in your own words.
I'm sure you think: why does he care what version we use? Well, for several reasons:
1. Division of responsibility. If I find a bug in your Ext JS, who do I call for support? You, Sencha?
2. The subsequent versions to Ext JS 4.2.1 (4.2.2 & 4.2.3) have a lot of official improvements and bug fixes. As an example 4.2.3 has more than 200 bug fixes.
3. If I want to use some of the improvements available only on the latest Ext JS releases, in addition to your Ext JS lib, I'll have to also load those as well.
One more thing Geoffrey. You mention in an earlier reply:
"I just checked Svn and we've made 60+ commits (mostly Ext JS bug fixes) to the main /trunk/ since the 2.5.2 release, including hitting our 6000th Svn commit earlier today."
Well this is nice and dandy, but how are we supposed to know about it? I don't see any announcement on your website!
Vladimir pointed me to the following link: http://www.sencha.com/forum/showthread.php?264700
If you read that page, you'll see the following:
The Commercial and GPL downloads are available here:
http://cdn.sencha.com/ext/commercial...commercial.zip
http://cdn.sencha.com/ext/gpl/ext-4.2.1-gpl.zip
The commercial link is out of the question because you previously admitted you only use public Ext JS releases.
GPL means General Public License, so I've concluded that you guys are using ext-4.2.1-gpl.zip.
Technically speaking, you're shipping a CUSTOM Ext JS version with Ext.NET. This is because you add your own bug fixes to Ext JS.
Moreover, branching someone else's code, changing it (bugs, what whatever), than distributing it to your clients as being the original (that is what you do on your website), is a very bad programming practice. Any junior software developer should be able to tell you that.
So, the claim on your website that Ext.NET supports Sencha Ext JS 4.2.1 is a bit dishonest: any developer that reads that will assume you support the official Sencha release.
I would like to suggest inform your clients on your website as to what version of Ext JS you use (public, commercial, custom, ...etc).
If you think I've misrepresented your development process, please don't hesitate to outline it in your own words.
I'm sure you think: why does he care what version we use? Well, for several reasons:
1. Division of responsibility. If I find a bug in your Ext JS, who do I call for support? You, Sencha?
2. The subsequent versions to Ext JS 4.2.1 (4.2.2 & 4.2.3) have a lot of official improvements and bug fixes. As an example 4.2.3 has more than 200 bug fixes.
3. If I want to use some of the improvements available only on the latest Ext JS releases, in addition to your Ext JS lib, I'll have to also load those as well.
One more thing Geoffrey. You mention in an earlier reply:
"I just checked Svn and we've made 60+ commits (mostly Ext JS bug fixes) to the main /trunk/ since the 2.5.2 release, including hitting our 6000th Svn commit earlier today."
Well this is nice and dandy, but how are we supposed to know about it? I don't see any announcement on your website!
Last edited by eugen; Sep 28, 2014 at 1:58 AM.