Coding an RR refreshing tool
Dear all,
Currently we use several tools for a group of experts to work on our databases online, See this document for more information : https://docs.google.com/document/d/1AAlNh3SgoMlp4rYlQLETDqvAK_B6Z11OJGPAZ1Quny0/edit?usp=sharing
We are quite stuck with some problems with the caching, so we will finance the coding of a tool to make things easier. Currently, once you have got a first image, you stick with it, even if the underlying data changed or if you changed the height / width. The only options are to change your R script, or to refresh tiki caches. Not very handy.
We need some strong tool in order to perform :
- Manual refresh with a simple click on a button located in the page to empty cached pictures and reload the page
- Refresh on a per-page basis : dumps the pictures and reloads the whole page (optioning to a per-graph basis : only dumps some cached pictures before the reload)
- An auto cache dumper / refresher time-based : each day, week, ..., it dumps the cache and the first user to load the page will create it for the others
- Has to work with R, RR, spiralstatsfilter and potential other tools of the R family
- Enable/disable cache per user or manage other caching options : no caching, caching...
- Option to output the date of the picture at the bottom of the graph.
A R stats refresher plugin
The idea would be to create an independant plugin (R_stats_refresh) which basically provides a button to click to dump the old pictures of all R-type instances and to reload the page.
Then some options would be great :
- Dumping the pictures based on their time-stamp : for instance, before or after page load, dumps the cached pictures too old (compares the date of the picture to the date of the last database extraction)
- Refreshes only the image before the plugin - see if it can spot a cached picture, depending on time and naming...
An other option could be to include the code in RR to make it an option of RR. That would make simpler the per-image refreshing. But a per-page refresh is more essential. We won't ask our user to refresh the page as many times that there are pictures in it...
So what do you think of this ?