My 2 cents from from the user perspective: Being able to put user-defined strings into a record field is of very limited value if you are not able to search/find/analyze this data.
That's why, as I recently had built a GnuCash with my own split action list for myself, I additionally extended the transaction report to filter for specific split action values. (Still on my to-do-list: extending wiki with the description how to create lists of user defined strings, bind them to arbitrary key strokes or to a GUI menu in order to insert them into arbitrary input fields in arbitrary applications, e.g. in the split action field of GnuCash.) Best regards, Paul On 23.06.2018 18:12, John Ralls wrote: > >> On Jun 23, 2018, at 4:58 AM, Robert Fewell <[email protected]> wrote: >> >> There have been some enquiries about customising this list so I thought I >> would propose a possible solution that I may work. >> At the moment the static lists are based on register type in >> split-register.c and it looks to me there are two possible options. >> >> 1, Dynamicaly add to these lists based on past entries, probably there >> would be an overhead do so. >> 2, Allow the lists to be customised in some sort of config file. >> >> I think 2, is the better option and in the source it mentions about using a >> config file so I was thinking along those lines to basicly do... >> >> Create a new user key file probably in .config/gnucash called >> user-config.gcm >> >> On gnucash load, test for the file and if not present create it with the >> default list content of split-register.c, I assume this would populate the >> file with the translated entries. >> >> A section name would then have list keys for the entries, something like... >> >> [Action List] >> cash_register=Increase;Decrease;Buy;Sell >> asset_register=Buy;Sell;Fee >> >> Change gnc_split_register_config_action to read the key file content to >> populate the appropriate list. >> >> A missing register key would get a list of one entry with "Empty". >> >> This would allow the users, once the file is created to add or remove >> entries as required. >> >> Any thoughts, wrong approach ? >> >> This would probably be a master project. > Bob, > > User-edited “ini” files are so 1980s. Anything like this should have a GUI > interface. > > I suspect at least some users would want to be able to set this per-account, > but I think it more important to find out how many care at all and where it > fits in most users’ list of priorities for improvements. It might even be > that most users prefer the current pre-populated combo box that allows them > to put anything they like in there, or that most don’t even use it. > > Regards, > John Ralls > > _______________________________________________ > gnucash-devel mailing list > [email protected] > https://lists.gnucash.org/mailman/listinfo/gnucash-devel _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
