111–120 of 134 posts
Can anyone recommend a stable, well documented alternative to Ext JS grids? I am currently developing with React, and would like to replace our internal tables with something as fully featured as Ext JS. (Features like remote filtering, inline editing, custom components, custom queries, etc).
Can anyone recommend a stable, well documented alternative to Ext JS grids? I am currently developing with React, and would like to replace our internal tables with something as fully featured as Ext JS. (Features like remote filtering, inline editing, custom components, custom queries, etc).
Earlier quoted context omitted.
It's quite possible they did do that. For example, Angular parses your source to perform Dependency Injection based on argument names.
Well thanks for that. Now I know what not to use.
This article misses a point as to why the community was outraged at the license change from LGPL to GPL. I was testing switching an application to EXT JS at the time, and I was really liking it. The prototype worked so well that we were preparing to get the commercial license, and then the license change happened. After the change was announced, a number of people said they would fork and maintain the LGPL versions.…
As a solo freelancer, I have developed and maintained an internal management web app for a small wine importing company from 2012 to this day: a huge portion of its 15+ KLOCs codebase is ExtJS 4 (the rest is the Python backend) and I have mixed feelings about it.. Given the heavy use of complex widgets and layouts (the Grid component in particular does about everything you could ever imagine, and probably more), I of…
>the Grid component in particular does about everything >you could ever imagine, and probably more Is there anything available comparable with open license?
[0] https://bvaughn.github.io/react-virtualized/#/components/Lis...
As a developer of some "popular" widgets, I owe a great deal to ExtJS because it taught me that encapsulation, especially in JavaScript, a scripted language with defacto accessible source code, is just absurd. A simple thing like that reminded me of functional programming and the rest is history. Extending a dropdown component meant that i had to copy some closure just to change a number in a wrapped function, and th…
Building the DOM via JS wasn't going to work for us. We had to re-learn how make simple things and we were at the mercy of the Ext API. The resulting DOM was incredibly bloated, different in IE, and was a nightmare to style.
Template-driven apps like Angular, JSX in React, Vue, etc are much easier to use overall. Less to learn, faster adoption for new developers, cleaner separation, better portability, and small, clean, and consistent output.
To be fair, the original authors of our application had little idea what they were doing either and misused/abused Ext, which made everything 100x worse.
Our later rewrite in Angular was more structured, though I do admit at least some of that is because it was much of the same team who were now more experienced (and also no longer treated it as an afterthought to the backend), and it being the second time round.
Also much like the Angular 1 -> 2 change, Ext 3 -> 4 was a very large change, and while it was a change for the better (providing many of the features of our homegrown framework in the core), it was still difficult to upgrade.
I developed Ext-JS applications from 2011 till 2017, and during the ExtJS 4 time, it was great. I loved the quality of their documentation, and most importantly: the ability to comment on each class/method/property etc. This contained invaluable hints and insights. The community was really good. Then they upgraded ExtJS (can't remember if it was to Ext5 or 4.x) and deleted all the comments as 'no longer relevant'. Th…
It was a monster from day one.