I'm trying to figure out the most elegant way of bringing meteor and extjs together.
Obviously Ext has its own Ext.data.Store and Proxies to handle REST backends. Meteor has a publish/subscribe model which pushes updates automatically.
My first thought would be do write a custom "MeteorProxy" and to handle all the update events there. I'm not sure though this is wise in terms of filtering or sorting data. Ideally filtering should take place on the Meteor side because data sorts/filters ideally should persist across to other (non-ext) views of the data.
Would using MemoryProxy + some glue code be a better alternative?
Or are there newer ones as of ExtJS 5?
For being over a decade old, Ext JS is still a good platform to develop many enterprise-grade (think intranet) applications.
Ext JS is a popular JavaScript framework which provides rich UI for building web applications with cross-browser functionality. Ext JS is basically used for creating desktop applications. It supports all the modern browsers such as IE6+, FF, Chrome, Safari 6+, Opera 12+, etc.
Requires - All classes required to be defined for the class to be instantiated. Uses - A list of classes potentially used by the class at some point in its lifecycle, but not necessarily requried for the class to initially be instantiated. Subclasses - Classes that extend the current class.
It's been two years. Are you still looking at ExtJS specifically, or are you open to ExtJS alternatives?
If the latter is the case, check out my Meteor + Webix integration. Webix is a UI widgets library similar to ExtJS, but leaner, mobile friendly, and faster.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With