Possible activities for teamwork on R-Instat

[rdstern]

@ChrisMarsh82 I list some possibilities for teamwork. They inevitably involve a defined activity that affects multiple dialogues. They are not mutually exclusive.

1. @volloholic has been working for some time with @Ivanluv on returning from R code to the corresponding dialogue. Perhaps this process could be documented and then extended to further dialogues. At the same time, perhaps the code for those dialogues could be examined for quality and consistency and improved. They have started to consider this topic.
2. There is the beginning (somewhere) of technical documentation, designed to help newcomers to the R-Instat programming tasks. This could be improved and extended. Points that are made would be illustrated using particular dialogues, etc and others listed that make similar use of this point or code.
3. R-Instat has a range of its own functions, e.g. data_book_add_filter, data_book_drop_unused_levels, data_book_add_summary. I have, so far, listed over 30 of these functions. Most are wrappers round a particular R function, but there is currently no documentation on any of them. Could summary information on these functions be supplied to the documentation team who would then add this to the help file?
4. In our recent review two of the categories were "Label across many variables at once" and "Transform across many variables at once". We plan to do this though using our selects that @shadrackkibet is working on. The idea is to have an option to use a select (set of columns) in a single receiver. @lilyclements has started work on the label aspect (one dialogue), and the transform will affect a number of dialogues. Typically they are the dialogues that take a variable and produce another, e.g. non-numeric.
5. We will soon have html results in the output window. This (I hope) will affect all the dialogues that currently send results to a browser. We may still wish to keep that option, but having the results in the output window will be exciting, partly because I assume it includes some powerful dialogues, e.g. pivot-table and plotly as well as our recent tables, etc. Adapting and testing these dialogues would be the task in turn.
6. Finishing the find/replace string dialogues. I think they are better now, but they still need improvements. Being able to tidy the lateforwork data in different ways (particularly with-and-without regex) would be useful to pinpoint what still could usefully be done. And then documenting different ways, while finalising the dialogues would be useful.
7. Adding more to the data grid. I have been surprised how much I have been using it. There are various small items that could be added, none vital, but perhaps useful. e.g. jump to a particular page, include variable numbers and label in tooltip, have (optional) drop-down for entry of factor levels, even be able to enter factor by any component, etc. (And improving the other grids (column and data frame metadata) too.

.