ActiveWidgets - Development too slow?
But that vision is disappearing fast. Other toolkits, which were not better than ActiveWidgets in the beginning have not only overcome all their shortcomings but have moved on to create better abstractions in code.
[edit: links to the competing toolkits deleted (Alex)]
My COMPLAINT is that while ActiveWidgets had a competitive edge over both these libraries, its losing it rapidly by its slow development pace. <b>How long ActiveWidgets Developers (including me) have to put up with incomplete documentation, incomplete or missing GUI Widgets (Tree, TreeGrid, Calendar, Progress etc...) and an exorbitant price tag?</b>
If you think that I'm evaluating ActiveWidgets harshly, then just check out the above two libraries to understand what the competition is like. And if noone copes up with these shortcomings now, it would only mean a furthur eroding of ActiveWidgets community when developers switch to other tookits.
I have a lot of respect for developers of other toolkits and I understand too well how difficult this task is, so their achievements are absolutely fantastic. However I still see that each new toolkit emerging in the previous months is very different from the others and each has its own niche.
Is there a niche for ActiveWidgets? - I am sure there is and the development does not stop where we are now.
I'm not trying to advertise/sell any other toolkits but rather trying to put myself in the shoes of a developer evaluating current AJAX toolkits before committing development towards one platform.
Thanks for reading my post and I'm happy that giving these concerns a thought.
I would appreciate your input regarding in what direction ActiveWidgets should evolve. Personally I always had a preference for speed and simplicity rather than trying to do too many things, however I still see large areas where ActiveWidgets could be improved, for example, integration with the server side code, or new data layer or tree/tree grid.
Honestly, when I compare it with other toolkits, we don't even have complete documentation yet and I remember countless hours at AW forums trying to find workarounds. The treegrid has been requested many times, the tree implementation is not yet complete, other essential widgets still don't feature on the schedule etc.
Why do you base this toolkit around a single product - the Grid? I think the grid has evolved to a fairly decent level and probably the time is to concentrate on filling the gaps. But my concern is if that's not done fairly soon, then it'll be quite difficult to make a case to use AW in a enterprise environment. I really want this product to break out in the open and not restricted to some niche areas.
Just my 2 cents.
This topic is archived.
Back to support forum
Version 2Looking for AW 2.6 ?
The old site is here.