Talk:Cutecash
Cutecash Discussion
Thanks for your input!
Multi-user mode
As a user of GnuCash I see an odd behavior when opening the data file. When double clicked it opens nicely, but if you move the data file and double click the program opens up but doesn't know where the data is, even though the double click on the datafile started up GnuCash!
The reason this is relevant to the software is that for ease of use, the data file should be moveable to wherever the user wants, even after using it in one place for a while. For multiple users, which is the case for me, my wife and I both use GnuCash. You will want to decide if there are some preferences that are for everyone that opens the file, or if each user can set their own preferences. You don't need to make this software open for concurrent access, but the data should be accessible by multiple people on the same computer each logging in with different accounts, keeping their own preferences.
Mac OS X has a preferences system that you might want to take advantage of, or emulate on non-MacOS X implementations.
--Kd4ttc 15:59, 27 August 2011 (EDT)
- Your question obviously refers to "gnucash", not "cutecash". The latter is an experimental other software. Also, asking user or bug questions here in wiki pages is not good - please either file a bug in Bugzilla or ask by sending a message to the gnucash-user Mailing List. Thanks. --Cstim 16:56, 27 August 2011 (EDT)
- Let me rephrase: Cutecash should have behavior which allows smooth use with multiple users. For example, if several users on a computer decide to move the datafile around, just clicking on the datafile should open it directly. This should also include symlinks to point to the data file. The program itself should not be locked into one data file. Secondly, preferences should be allowed to be saved by different users as independent preferences. -- Kd4ttc 15:21, 28 August 2011 (EDT)
Command-line options
There is a command-line parser, part of libQxt suite, named QxtCommandOptions (for some reason, it doesn't appear in 0.6 documentation, though it is part of the source...)
