> Also, I wasn't > sure how to handle the property tables either, in essence they're big, > global arrays. It works, a little awkard, and a bit messy. That's > probably not the best thing for a clean core/gui separation... but there > is such an immense number of properties, what else could/should we do?
The idea with the property tables was to make the code independent of the actual implementation of the property-data by specifying an API for access and change-notification. At some points the props are accessed directly in the code, but never across the gui/core boundary. Essentially you don't have to worry much about the properties once you have figured out a way to invoke other methods in the core and return values. A very simple form of this is implemented in the remote-console optional feature of gtk-gnutella (read only and not implemented for all property types). -- Richard Eckart <[EMAIL PROTECTED]> ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Gtk-gnutella-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
