Is Ext.Net dead?

Page 1 of 2 12 LastLast
  1. #1

    Is Ext.Net dead?

    I haven't seen updates for Ext.Net since May, 2014. The last version published is 2.5.2 (and supports JS 4.2.1).
    There are no versions for Ext.JS 4.2.2 & 4.2.3. Granted, Ext.JS 4.23 is kind of new, but what about Ext.JS 4.2.2? It's been on the market for a long time.
    Moreover, I don't see any signs that Ext.Net is going to be supporting Ext.JS 5.
    Other companies, have been more agile in updating their libraries to support the latest Ext.JS versions.
    So, my questions is: should I start looking somewere else, because the development on Ext.Net seems to be at an end?
  2. #2
    I'll try to answer your questions and respond to your statements.

    There are no versions for Ext.JS 4.2.2 & 4.2.3. Granted, Ext.JS 4.23 is kind of new, but what about Ext.JS 4.2.2? It's been on the market for a long time.
    Ext JS 4.2.2 and 4.2.3 are not public releases and are considered "Sencha Subscriber Only" releases. Sencha has directed us to not include "Subscriber Only" releases in Ext.NET. Even though we do not get the benefit of the Subscriber Only releases, we still put in a lot of effort to fix the Ext JS defects ourselves and include those updates in the Svn repo.

    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.

    Moreover, I don't see any signs that Ext.Net is going to be supporting Ext.JS 5.
    There must be at least a dozen threads here in the forums regarding Ext.NET 3.0 and Ext JS 5.0 support. The search box at the top of this page should help you find those threads.

    Other companies, have been more agile in updating their libraries to support the latest Ext.JS versions.
    Can you provide examples? Our friends at Bryntum (http://bryntum.com/) just yesterday released their first Beta with Ext JS 5 support.

    Unfortunately Sencha did not communicate the release date of Ext JS 5.0 to its partners, so we were all left in the dark and had to scramble once it was released earlier than expected. Layer on top of that, there are big changes once again to the API, and Ext.NET has a HUGE catalog of custom Components, Plugins and Ext JS Bug fix overrides... it takes time.

    So, my questions is: should I start looking somewere else
    It's your choice.

    Hope this helps answer your questions.
    Last edited by geoffrey.mcgill; Sep 27, 2014 at 5:44 AM.
    Geoffrey McGill
    Founder
  3. #3
    Correct me if I'm wrong, but from your answer I understand the following: Ext.Net is not based on Sencha Ext JS (as advertised on top of http://www.ext.net/ page). Instead, it is based on http://code.google.com/p/extjs-public/ (which btw is maintained by only 1 person).

    Understandably, as you've mention bellow, since that "public" codebase is so old (4.2.1 from 08/22/2013), you need to spend time fixing bug there.

    In the end, your customers end up with a CUSTOM EXT JS, which may or may not be in sync with the official Sencha Ext JS.

    You have to do this because you elected to include an Ext JS with your product.

    So, my question is: why can't you just base your releases on the official Sencha Ext JS releases? That is what Bryntum (http://bryntum.com/) is doing, and because of that they release a new version of their products every month (using the latest Ext JS).

    Regarding Ext JS 5: since you based your code on the public releases, are you going to wait until a 5.0 version is posted on http://code.google.com/p/extjs-public/ ? Or, are you going to duplicate the work that Sencha did and release your own 5.0 version?
    I imagine, either way, that is going to take a long time.

    I mean no disrespect, and I apologize if my post seems a little bit abrasive, but as a customer, I would very much like to have an answer.

    My opinion, if you want to take it into consideration, is that instead of wasting time fixing old, public Ext JS releases, you can make a better use of your time improving the .NET aspect.
  4. #4
    Correct me if I'm wrong, but from your answer I understand the following: Ext.Net is not based on Sencha Ext JS (as advertised on top ofhttp://www.ext.net/ page). Instead, it is based on http://code.google.com/p/extjs-public/ (which btw is maintained by only 1 person).
    No, we use official Sencha releases but public releases only (latest public release is 4.2.1 and 5.0.0). Just if our members report about ExtJS bugs then we fix it (fix is just override class) and commit to our repository


    In the end, your customers end up with a CUSTOM EXT JS, which may or may not be in sync with the official Sencha Ext JS.
    You have to do this because you elected to include an Ext JS with your product.
    As I mentioned above, we use official releases only (you can find ExtJS code in http://svn.ext.net/premium/trunk/Ext.../Ext.Net/extjs, it is official 4.2.1 release)

    So, my question is: why can't you just base your releases on the official Sencha Ext JS releases? That is what Bryntum (http://bryntum.com/) is doing, and because of that they release a new version of their products every month (using the latest Ext JS).
    If you open Bryntum online samples then you will see that examples are based on ExtJS 4.2.1
    Onece again, Ext.Net can use public releases only (4.2.2 and 4.2.3 are not public and cannot be included to Ext.Net)

    Regarding Ext JS 5: since you based your code on the public releases, are you going to wait until a 5.0 version is posted onhttp://code.google.com/p/extjs-public/ ? Or, are you going to duplicate the work that Sencha did and release your own 5.0 version?
    I imagine, either way, that is going to take a long time.
    We already working on Ext.Net 3.0 which is based on officail ExtJS 5 release

    My opinion, if you want to take it into consideration, is that instead of wasting time fixing old, public Ext JS releases, you can make a better use of your time improving the .NET aspect.
    Unfortuantelly, ExtJS has many opened bugs and we have to fix it ourselves because Sencha doesn't always fix it efficiently therefore we fix it (if possible) for our members
  5. #5
    Can you please list the links of the public Sencha releases you use? If they are public, they must be available for anyone to see.

    Don't point me to http://svn.ext.net/premium/trunk/Ext.../Ext.Net/extjs.
    They should not be considered Sencha because they reside in your repository, and also are not public because they are accessible only to your clients.

    With respect to Bryntum, all you need to do is go to their website (http://bryntum.com/), click on http://www.bryntum.com/products/gant...log/?id=2.2.25 (for example),and you'll see they support both Ext JS 4.2.1 and 4.2.2.

    You're correct, the examples on the website use Ext JS 4.2.1, because they had to chose one Ext JS version.

    However, I can tell you that I personally tested all Bryntum examples with Ext JS 4.2.2 and they work just fine, just as they advertise.
    Side note: I've also tested all their products using Ext JS 4.2.3, and the only problem I've noticed was on resizing events on Ext Scheduler examples. All Ext Gantt worked just fine even with Ext JS 4.2.3.
  6. #6
    Can you please list the links of the public Sencha releases you use? If they are public, they must be available for anyone to see.
    I am not sure what links do you mean. I gave you link already, you can ensure that it is official ExtJS 4.2.1 release is located there. It is what Ext.Net is used

    Don't point me to http://svn.ext.net/premium/trunk/Ext.../Ext.Net/extjs.
    They should not be considered Sencha because they reside in your repository, and also are not public because they are accessible only to your clients.
    I am not sure that correctly understood you. What kind version of ExtJS you need? That link contains ExtJS which is used in Ext.Net, anyone can download latest public Ext.Net (from download page) and that ExtJS version will be embedded to Ext.Net assembly

    However, I can tell you that I personally tested all Bryntum examples with Ext JS 4.2.2 and they work just fine, just as they advertise.
    Side note: I've also tested all their products using Ext JS 4.2.3, and the only problem I've noticed was on resizing events on Ext Scheduler examples. All Ext Gantt worked just fine even with Ext JS 4.2.3.
    You can use Ext.Net with own ExtJS version, we don't limit it (just all possible issues you should resolve yourself)
    May be Bryntum has agreements to use 4.2.2/4.2.3 in their products but we cannot use it due Sencha limitation
  7. #7
    Before we continue the discussion, we need to clarify some terms:
    Sencha Ext JS official releases (Geoffrey called them subscriber releases). These are Sencha releases and are available for download to anyone that has a subscription. As of now, the following releases are listed (copied the list from my subscription page)
    Ext JS 4.2.3 Sep 2nd, 2014
    Ext JS 5.0.1 Aug 7th, 2014
    Ext JS 5.0.0 Jun 1st, 2014
    Ext JS 3.4.2 Nov 19th, 2013
    Ext JS 4.2.2 Sep 23rd, 2013
    You'll notice, 4.2.1 is not even in the list, since is so old.

    A public Sencha release should mean a release that is made available to the public at large, by Sencha. The only Ext JS repository I was able to find that is public is https://code.google.com/p/extjs-public/. Vladimir points me to the ext.net repository, but that is not public, nor Sencha, because it is only available for Ext.Net clients.

    Geoffrey said that Ext.Net is allowed to ship their product only with public releases of Ext JS, not the official ones. What public releases? Where are they located?
    On the other hand, Vladimir is saying that you guys are fixing bugs and using official Sencha releases. If that is the case, why wasn't Ext.NET updated for Ext JS 4.2.2 (which was released 1 year ago). And btw, that was my original question.
    Am I missing something?
    Last edited by eugen; Sep 27, 2014 at 2:02 PM.
  8. #8
    Ext.Net can use public ExtJs releases, public means available for all
    Latest ExtJS public release is 4.2.1
    http://www.sencha.com/forum/showthread.php?264700
    Ext.Net 2 uses ExtJS 4.2.1

    4.2.2 and 4.2.3 is available for Sencha subscribers only (means that there is no public available links for download, no public CDN)
    http://www.sencha.com/forum/showthre...-Now-Available!
    http://www.sencha.com/forum/showthread.php?286532
    http://www.sencha.com/forum/showthread.php?273860

    Sencha Ext JS official releases (Geoffrey called them subscriber releases).
    No, public release is not subscriber release. Public is available for all, subscriber is available for subscribers only

    Ext.Net uses public only
  9. #9
    OK, now I understand: Ext.NET supports only GPL (GNU General Public License) Ext JS releases.
    Since those releases are refereed by Sencha as beta, and have quite a lot of bugs, they made then available to the general public.
    Once they fix the bugs, with the help of the general public, mind you, they close the codebase, and make them available only to subscribers.

    What I don't understand is why you guys at Ext.NET make yourself dependent on GPL (beta) releases of Ext JS.
    By doing so, you have to spend a lot of time fixing their bugs. Why not just rely on official Sencha releases? This way you'll have more time to focus on your real product, EXT.NET. All you have to do is let your customers know that an official Ext JS release is required by your product: this is what Bryntum does, and that is why they are able to release versions every month, and support the latest official Ext JS available.
    Last edited by eugen; Sep 27, 2014 at 5:59 PM.
  10. #10
    I only have a few minutes to post a response, but I'll try to respond in greater detail later today.

    What I don't understand is why you guys at Ext.NET make yourself dependent on GPL (beta) releases of Ext JS.
    We have nothing to do with the Sencha Ext JS GPL release. Please stop referring or associating Ext.NET to the Sencha GPL release(s).

    The reason Bryntum can update their code is because they do not ship the Ext JS libraries. With Ext.NET we re-distribute the Ext JS library, and are prevented from including the private subscriber only releases. Bryntum does not re-distribute Ext JS.
    Geoffrey McGill
    Founder
Page 1 of 2 12 LastLast

Similar Threads

  1. [CLOSED] It's totally dead when using new code from SVN
    By thchuong in forum 1.x Legacy Premium Help
    Replies: 3
    Last Post: Jan 13, 2011, 10:12 AM

Posting Permissions