Josh Phillips wrote:
Sqlite can easily be embedded into an application and provides an easy and intuitive means for storing and retrieving properties and other user settings and when embedded takes only 250kb or so.
Yes, but [to me, anyway] that still seems a bit heavyweight (or overkill) for this task - both in terms of file/memory footprint and "excess" functionality/API...
Don't get me wrong - SQLite seems like a good mix of size, features and performance, and I have been waiting for a while for something cool to use it on - but presumably more than simple accessing and persistence of app options. :)
It might also make for an easy implementation for property sheets rather than having the user required to manually edit a configuration file. The same could be used for calltips etc.
I am not following you here - the "barrier" to having more graphical ways of dealing with options has always been the programming of the GUI itself - or so I thought... or is there some tool one uses with SQLite that magically generates well laid-out property sheets directly from your DB schema?
Robert Roessler [EMAIL PROTECTED] http://www.rftp.com _______________________________________________ Scintilla-interest mailing list [email protected] http://mailman.lyra.org/mailman/listinfo/scintilla-interest
