On Mon, Feb 16, 2009 at 05:32:33PM -0000, Gary Chambers wrote:
So, for new browser it needs to be decided what information to show as this will affect the pragma. For instance, do we still want categories, "project specific" (probably not) etc.
I expect we will want a Preference class either way to model each preference in the browser. Making a new browser is quite an undertaking given the different types of preference (boolean, text, one-of-many, colour, font etc.).
I think Magritte is the proper solution. It already handles UI metadata like this. Regarding preferences being optional, I think just a few tweaks to the MC loader would work: If the Preferences Browser is not loaded, MC will not compile the methods that return the Magritte metadata. If this is done properly, as in MC1.5, these methods will hang out uncompiled in the orphanage until you load the preferences package, at which point they will be loaded into the image. Out-of-order package loading is nice. -- Matthew Fulmer -- http://mtfulmer.wordpress.com/