Dialogs in library organization

[Rob Cozens]

>I'm planning some libraries.  At the time, I think some will need 
>some setup help in the form of setup windows.  Maybe these can be 
>designed as stacks.  (For example, if the application calls a 
>function to initialize a humdinger with no parameters, the library 
>might bring up a dialog box and use the parameters from that.)
>
>How do I organize this?
>
>My initial thought is to put these into the same stackfile as the 
>library stack, that is, as substacks to the library.

That's what I do with Serendipity Library.

>
>Or am I modeling this all wrong?  Is it silly to have libraries 
>bring up windows?

If it is, I'm silly as well as a foole.

A.  If a handler in the library needs a dialog or setup stack, what 
better place for that stack than inside the library?

B.  If a dialog or setup stack is used by several applications that 
also use the library, ditto?

Bottom line: a library stack can be a repository for resources other 
than handlers (eg: images, clips, graphics(?), and dialogs).  Unless 
a setup window is specific to a single standalone, why not maintain a 
single instance of it in a library?
-- 

Rob Cozens
CCW, Serendipity Software Company
http://www.oenolog.net/who.htm

"And I, which was two fooles, do so grow three;
Who are a little wise, the best fooles bee."

from "The Triple Foole" by John Donne (1572-1631)