Bryce Harrington wrote:
On Sun, Mar 13, 2005 at 04:19:50PM -0800, Jon Phillips wrote:
I agree that this should be removed. Then, just have the error messages sent to console and on windows, send them to the message window ishmal added...however, the message window should go behind the main Inkscape window so it doesn't startle users.
I think what would be even cooler is to implement an Extension Editor dialog, that provides a GUI view of the extension db, that shows each extension and its status, along with error messages, info about where to get the extension, etc. This way, the error info is easily available for users curious about it, but safely hidden from those who don't.
Perhaps a first start could be to create a function that iterates through the extension db and generates a string that summarizes the status of each extension, and then just put that into a text box in a dialog. That shouldn't be too hard to implement, and while it'd be ugly, it would be enough to be able to eliminate the error dialog on startup.
Bryce
Btw, Win32 still does not have the extension DLLs being built, and will likely not have them until we get the dependency-free export api done. DLLs have tougher binding requirements than Unix; our current build would require the entire Inkscape object blob to be linked with each DLL. This needs to be fixed, by separating Interface & Implementation, and/or by XPath, before this can be accomplished. An extension CANNOT know the internals of Inkscape, other than published interfaces.
Bob