v3: deprecate ajax: name
v3: deprecate ajax: name
tacman1123
Posts: 235Questions: 52Answers: 1
since jQuery is gone, the 1-to-1 mapping of ajax: is not longer necessary. What do you think about modernizing the property name? e.g. fetch? or remote:
admittedly, very little value. Just an idea.
Replies
Hi,
Yes, well worth thinking about this sort of thing! I'm inclined to say that the term "Ajax" is synonymous with async remote requests, regardless of what the underlying API is, so I think I'm okay with
ajaxremaining as it is (in fact, I'd guess a lot of Javascript devs don't know what the acronym is for any more!).I'd be concerned that renaming could potentially cause confusion as well since a lot of the old forum posts would be out of date as all of the documentation would need to be updated.
So yes, worth thinking about and discussing, but I think I'll keep it as it is for now.
Allan
makes sense. the other term I remember being confused about was serverSide: true and how that was different. but you explained it and I got it working.
My api-grid-bundle now uses 3.0 beta. It was bittersweet removing the searchPanes code, as it was the most complicated part of the code and looked great. I'll use another search tool or wait for searchPanes 3 when I need it. I hope to post a demo repo very soon.
Maybe ColumnControl will do what you want.
Kevin
Indeed, I've integrated that, and quite like it. I miss the counts, I always thought that was a big bonus. It became a reporting system while searching! But there are other tools for reporting.
SearchPanes will make a comeback. It needs a total rewrite and there is no point in updating the current code for DT3 and removing jQuery, then doing the rewrite (double the work!).
Allan