David Prieto <[email protected]> writes: > Hi, > > I'm pretty new to accounting and taking an accounting course where we're > being taught a proprietary solution. I have chosen to take the chance to > practice using Gnucash, too, which has this far been pretty impressive for > every task we've had to work on. > > There is a suggestion I'd like to make, though: When I try to find certain > elements (customers, invoices, jobs, vendors, bills, employees and expenses) > I only have two options: create a new one, or search an existing one. > > Why not offer *a list* of the existing elements in these categories so that > the user can keep track of the whole list? Why not use the search as a > filter, so that if it's left blank you get the whole list instead of not > getting any results? Why not have that list as a tab (e.g. a customers tab), > same as you have an accounts tab? > > I think that particular part of the program would be much easier to use that > way.
When it was originally designed it was designed to scale, and I was thinking about down the road having hundreds or thousands of entries in the "list". At that quantity having a list vs. a search is most definitely the wrong thing. The plan at the time was to have a search with a dynamic list based off a partial input. As this is the devel list, patches are always welcome! I look forward to seeing your implementation! :-D > Thanks for your attention, > > David Prieto. > _______________________________________________ > gnucash-devel mailing list > [email protected] > https://lists.gnucash.org/mailman/listinfo/gnucash-devel -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH [email protected] PGP key available _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
