1.7.4 comments

[Derek Atkins]

linas@linas.org (Linas Vepstas) writes:

> I used peachtree heavily for a while, and I remember that one of
> thethings I didn't like about it was that most tasks required you to go
> through the search dialog (and a huge pull-down of all accounts!),
> which got tedious and annoying pretty quick.  

I certainly can understand the frustration.  One thing that gnucash
allows you to do is work _from_ the search windows..  So you can start
from there instead of starting from, say, the invoice.

> So how about this for a suggested enhancement: If the sql database has
> less than e.g. 200 names, then  all the names *would* be cached in ram,
> and the usual type-ahead/matching/tab-completion would work.  Otherwise,
> if the list seems too big, then the search dialog is forced...  (yes, I
> know, don't remind me that I, too, can volunteer to code this up ...)

Feel free to file an RFE, but i dont have time to get this into 1.8.0.
I'm not against the model at all (however it doesn't scale well).  I
suppose I could just autocomplete on the locally-cached entries (which
means 'all' of them in XML, and 'whatever you've used so far' in a SQL
system).  Then the SQL Backend could cache whatever it wants when you
startup.

However, I'll pose the same question to you -- on what values do you
autocomplete?  Do you autocomplete on the Customer Name?  The Customer
Number?  The Customer Contact? 

I'll think about how to do this for a future release/enhancement
(unless someone provides me the code to do this sooner :)  But it's
not something I plan to finish (or even start) before 1.8.

> --linas

-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
       warlord@MIT.EDU                        PGP key available