Scalability issue

Hi,

thanks for your feedback!

Yes, this is a nagging and I would really like to fix it TablePress! Unfortunately, I haven’t yet found a good and easy implementation for this, yet ??
Now, TablePress has made a lot of progress, in that the “Edit” screen is now no longer reloaded when changes are saved, as that is done via AJAX now. However, the initial load might still be slow with many textareas, and this might still cause issues in browsers.

Now, after seeing how cool the new Media Manager in WP 3.5 turned out, with just a JavaScript-based implementation, I’m currently looking into using a similar development model in TablePress. Hopefully, this will help to finally fix this issue in the future.

Even though I don’t have good news about this yet, I still hope that you like TablePress ??

Best wishes,
Tobias

Hi Tobias,
nice to hear from you again!
mmm, look if this library could come in help for backend data editing:
https://jquery-datatables-editable.googlecode.com/svn/trunk/index.html

Another couple of ideas:
* an ecologic improvement that shouldn’t result in a drastic disruption for the current codebase is to implement a final render caching layer, beeing the render an HTML fragment, a json data structure or whatever…
looking at server load and client wait times seems that data is queried on the database and arranged in the HTML presentation every time, with RAM and CPU resources used even if data has not been changed from the last render…

* thinking of a possible ajaxification please consider to don’t disrupt the current frontend behaviour to have the data printed in HTML on the public site, as real HTML can be be good for SEO and a JS progressive enhancement is enough.
Otherwise to eventually allow publishing huge tables on the public site an ajax chunked data loading could be a must, but on my tests up to about 25.000 rows HTML is still an alternative, please leave an option for it! ??

Cheers for TablePress!
–htrex;

Hi,

thanks for the link to the DataTables Editable script. I’m not yet sure that this will work in TablePress, but I’ll check it out!

About the other two points:
– TablePress does cache the final/rendered table HTML code, actually. (That’s on the frontend though, I don’t think that this is helpful for the “Edit” screen.)

– 25.000 rows is really a lot. Have you thought about implementing this via a custom PHP/mySQL solution, where you directly use the AJAX loading methods that the DataTables library offers?

Best wishes,
Tobias