On 9/30/06, Yen-Ju Chen <[EMAIL PROTECTED]> wrote:
With the experimental GtkMozEmbed on hand, I would like to have some discussion about the BookmarkKit. Frankly, the most important question I have is what kind of storage we should use ? We can go for one bookmark per file (as Mac OSX), single file (property list), or system-wide database (CoreData/sqlite3). OSX switch to per-file based system because of the indexing. And it is indeed the best situation for LuceneKit. But since this kind of data is structured, a system-wide database is not a bad solution considering sqlite3 does offer searching. If we can decide the storage system, we can also use it for AddessesKit, and probably Grr. And if the CoreData is ready, it is not a bad idea to integrate everything together.
The other issue is how do we organize the bookmark ? The storage backend is responsible for store each record (bookmark). But on the user interface, bookmarks are organized as group, and group may have another group inside, just like what NSOutlineView is designed to display. Actually, the whole system is very similar to AddressesKit. We have ADPerson as single record and ADGroup for organization. Maybe we can just abstract AddressesKit for BookmarkKit. And a lot of applications use this type of organization, such is bookmark on web browser or AddressManager. The only issue is how big a record is too big to store in this kind of system if we use database as backend. Say Grr. RSS is not very big unless an image is included. So it will also benefit by this system. But GNUMail may not because an email may be very big due to the attachment. So if we have a system which can store structured data and organize them in a tree-like structure, it will be very useful for many applications. I would say it is like NSUserDefaults, but more organized. Yen-Ju [snip]
Have fun. Yen-Ju
_______________________________________________ Etoile-discuss mailing list [email protected] https://mail.gna.org/listinfo/etoile-discuss
