Iam trying to implement my applicaion in ext js 2.3 using mvc architecture.
Can someone suggest me the classes available in ext 2.3 version to implement MVC.
Any links to extjs 2.3 tutorials will be highly useful.
Thanks in advance.
MVC has never been implemented in Ext 2.3, as far as I know. I also think that it is not worth the effort as 2.3 is three versions back and it is really outdated today.
If you have a motivation and resources to upgrade the existing app then opt to update the app to Ext 5.x. It would be much better spent development time.
In Extjs4.x, the MVC appears for the first time. So it can't be used in previous versions. It becomes mvvm in Extjs5.x. I recommend you to learn Extjs4.x or Extjs5.x.
Related
I need to learn ExtJS 3.4 ( pretty older version) and could you please give me some document links. I searched in Google but I am getting most of the links to 4.0 version and above.
If any one having PDFs please share it with me.
Thanks
Since you mention the 3.4 version I assume you work with AEM which is built upon the ExtJS 3.4 version.
Check out this AEM ExtJS tutorial which is pretty old but quite useful.
We have a pretty complex application to be built. Planning to use EXTJS4. We have a team who is well versed with coding EXTJS3 style. We are researching on MVC feature of EXTJS4 and whether to go that way or not. Want to add that we will have really complex layouts and pages.
Can we use EXTJS4 without using MVC feature?
Yes, you can... however if the only reason you are avoiding MVC is that someone on your team is "well versed in Ext JS 3 style" then you are in for a world of hurt.
Ext JS 4 is very different from Ext JS 3, in about a hundred thousand ways. The latest version is Ext JS 6.0.1 -- and follows all of the paradigms introduced in Ext JS 4.
TL;DR -- if you are serious about using Ext JS for large projects, (1) use the paradigms for the framework and (2) use the latest version!
We want to convert our web app to angularjs, the problem is we need to support IE8 so only option is to stick with angularjs version 1.2. The question is it safe to go with this version? As 1.3 is already out and soon version 2.0 will be there too, so in near future (like 8-12 months) if we dropped IE8 support and then want to migrate to 1.3 or even 2 how much effort it will be?
Migration from Angular 1.2 to 1.3 is far more easier as compared to moving to Angular 2.0
There is even a migration guide to migrate from 1.2 to 1.3. So migrating would be possible to 1.3 or 1.4 or 1.x.
There is a bit of paradigm shift when it comes to Angular 2.0. The migration path is still not clear and we even don't know whether one is possible.
Update: This video from ngconf 2015, gives some useful insight into how build today with 1.3, that makes transition easy.
What are the risks associated with updating from ExtJS 3.x to Ext JS 4 Beta?
Would you expect that user extensions which work with Ext JS 3.x will work with Ext JS 4 Beta?
Would it be as simple as replacing Ext Js 3.x with ExtJs 4?
Should I update or wait until there is an official stable release?
What are the risks associated with
updating from ExtJS 3.x to Ext JS 4
Beta?
Ext 4 is not backwards-compatible to Ext 3. Expect to spend significant time upgrading and testing, depending on how large your existing application is. Once you see the impact on your specific app, you'll be able to evaluate your own specific risk. It all depends. There will be migration documentation, so hopefully that will mitigate the risk somewhat.
Would you expect that user extensions
which work with Ext JS 3.x will work
with Ext JS 4 Beta?
No, not by default. I would expect most will need to be upgraded, but again, it depends on the specific component.
Would it be as simple as replacing Ext
Js 3.x with ExtJs 4?
No. You might want to watch this thread on the Sencha forums.
I think this question isn't specific to ext js at all. I think the answer to the same for the following question: "Upgrade from <some library i'm using> to <Beta version of next release for library I'm using>?"
And the answer is a recommended no. Betas for 3rd party libs aren't like betas for websites. They could have major changes by the time the final release comes out and any code you write on top of a beta could become useless. To be honest, the most I would do with a beta release is just try and plug it in to my project to gauge how much work is going to be involved in upgrading once the final release comes out.
Currently in the system analysis phase and I am looking at developing a system that uses Kohana for the backend and extjs to display and render my data. How feasible is this? Is it the right approach to start with? Any good tutorials would be welcome.
Thanks
You can definitely use Kohana with ExtJS in your project. Kohana is just a HMVC framework for PHP. The feasibility factor is up to you. How complex your application is? Do you really need ExtJS or Is jQuery UI feasible? etc. You might want to read this post from Kohana forum to decide yourself.
ExtJS community also have a Kohana module (Ext.Direct module). You can download and use it as well if you plan to use Ext.Direct.