18 Apr 2015 6:19 PM #1
What I like to have in future versions of ExtJS
What I like to have in future versions of ExtJS
Am not aware how sencha collects its feedback from customers to create its roadmap. I am sure they do it time to time, but for those of us who dont get to voice their openion/concerns, here is a thread.
I originally put this in another thread
where I got some upvotes and some concerns. Someone suggested to have it as a seperate thread and then discuss it over,
So here is a list what I like to See in next versions of ExtJs, you can agree/disagree add more, remove some
- Use HTML Modules for dependency management (and remove require style dependecy handling)
- Drop XTemplate and use HTML Template and String Templates
- May be their widgets can now be converted to WebComponents
- Remove callbacks and use promises / async functions
- Use TypeScript in source - Dont supply a definition file which is seperate from the source (I know some sencha forum manager hate it "personaly" but they need to visit their openion again, for me who often browse Ext sources to get deeper understanding having type definition will be an great help, also you dont need to create plugins for various IDEs)
- I like Sencha's Data package a lot. its much better than Ember-Data, Breeze.js or JS-Data but provide us a way to design adapters so that I can connect outside-data packages to Sencha widgets. (Some of these data packages are doing pretty rapid and innovative development like cloud sync and introducing new features more often, I am afraid sencha's data package may lag behind)
- Use more open source products in their tooling (for instance instead of creating their own SASS compiler - "Fashion" they could have used Stylus , I may be wrong here i dont know about "Fashion" it may be doing more than what stylus have to offer- but in that case they should produce it as open source so that we get community contributions )
- Use Gulp/Grunt instead of providing us Sencha Cmd (it will help me make use of so many plugins out there to automate/customize my builds, or keep the Sencha Cmd and switch over from ant to gulp/grunt enabling us to use community plugins )
- Provide open package management solution - JSPM, NPM etc
- Make ExtJS more porous to outside world rather than a monolithic framework and keep us locked inside their walled gardens
- Start thinking about unit testing solutions (provide a way for dependency injection)
- I dont know much on Sencha's 2-Way data binding but I what I read is that 2 Way data binding has more cons than pros
- Their SVG api needs some serious updates (its pretty much behind than some of the compititors)
- Some of the best thing that ilike to mention about sencha are
- Data Package
- Their API too is very nice or may be i got too comfortable with it that i dont like others
18 Apr 2015 11:56 PM #2
They are selling Sencha Cmd? They might not want to replace it with something they can't charge.
While learning I asked them when they are going to switch to TypeScript so that I can stop using this ugly syntax that tries to introduce class system through raping functions, and as I remember answer was that they have no intention.
I also asked why do I have to include every file instead of Sencha simply taking all the files in my directory. They said that this is not possible. This is of course not true since in Meteor you can do just that. But this is maybe because Meteor also includes server so server can pickup those files somehow.
I also asked about reactive data sources. As it stands now when you change data on list will get updated. But this doesn't work with forms in a way that form fields automatically change they values as their data sources change values. You have to program that yourself using events. Once again Meteor offers just data. Instead of event driven Meteor is Reactive - components react to changes in data source.
So some of the stuff I mentioned Sencha might not be able to implement since it has no control on server (is it theoretically possible that you install something on server to make this possible) but other stuff like using real class syntax and allowing other components and not just lists to be reactive is possible.
19 Apr 2015 12:18 AM #3
+1 for mrisan's proposals. Strongly agree.
Regarding to grunt/gulp. What do you think about brunch?
19 Apr 2015 1:30 AM #4
- Join Date
- Apr 2007
- Sydney, Australia
- Vote Rating
Would like to address some misconceptions here.
I also asked why do I have to include every file instead of Sencha simply taking all the files in my directory.
But this doesn't work with forms in a way that form fields automatically change they values as their data sources change values.Evan Trimboli
Twitter - @evantrimboli
Don't be afraid of the source code!
19 Apr 2015 5:02 AM #5
@evant Thanks for that example. While I have not done as much doc reading as I should, that is the 1st example of the use of the view model which opened my eyes as to how to use it.
I'd like more simple examples like this.
19 Apr 2015 10:42 AM #6
On Sencha widget's pack,
which is extreemly feature rich and top of the class in quality, i would like them to add some components which is geared more towards performance and less on the feature
I also have a thread on those lines and you can read about it here to know what i am talking about
By fayzan in forum Community DiscussionReplies: 2Last Post: 11 Feb 2015, 8:11 AM
By Yura.Luchkiv in forum Ext: Q&AReplies: 1Last Post: 2 Jan 2013, 8:24 AM
By tsouza in forum Community DiscussionReplies: 0Last Post: 22 Jun 2008, 11:47 AM