Hi Dave,To do things "properly", a commercial installer is probably the easiest way.
That's well and good if I am distributing a complete application; but when I'm designing a database library to be used & distributed by others, I have to provide a path to any db stack opened by the calling stack. So far it seems specialFolderPath is the only way to accomplish this, and that means files must be forced into particular (though generically addressed) locations on every platform...
and that means an installer is needed on every platform and by every developer who uses my library.
It's not a solution I like very much; but what's the alternative?
--
Rob Cozens
CCW, Serendipity Software Company
http://www.oenolog.com/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)
_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution
