On Mon, Apr 19, 2004 at 09:00:21AM -0700, Ted Gould wrote:
Since we don't want to constrain an extension's UI (or choice of toolkits) unnecessarily, perhaps the best way to achieve this would be to provide a GtkSocket (http://developer.gnome.org/doc/API/2.0/gtk/GtkSocket.html) in the save dialog in which the currently selected extension can embed its preferences window.
Hmmm, I like the idea. The one thing that I was trying to preserve was the idea that a external script could have it's own preferences. But, I don't think that is worth saving, and it adds other complications like setting extension parameters externally. I think that if we just make it so that scrips have to use a generated interface, then we can do this, and not have the parameters problem.
That's the way that I'm going to go - any other thoughts?
This may be related to the work I'm doing on the print dialog. There is an interface to put "other" config options into the gnomeprintui dialog, but I wasn't sure how to handle it with the extensions.
Should I just let the extension work directly on the dialog using this GtkSocket? (Or am I misunderstanding how this should work?)