re-evaluate default file handler

[GoogleCodeExporter]

I think the way the default file handler currently works, while convenient,
is a bit too "magical" at the moment. Because every file handler instance
displays every library in the system, you have no opportunity to set up
different handlers with different setting (security for example) in the
same image.

At very least, we should make the file handler a bit more generic and have
the Environment package set up a default that behaves like the current
system. WALibrary class>>urlOf:handler: could be implemented and then the
existing #urlOf: could be moved into the Environment package as a class
extension and it could get the default file handler as it currently does or
from the environment somewhere.

At least that way people would have the option, when not using our
environment, to build up their own file handlers with only specific
libraries in them.

Or maybe this should be changed even more to get rid of the concept of a
"default" entirely. Or maybe you should be able to configure a default file
handler for your application in its configuration.

I'm not sure... we should discuss.

(this came out of comments in Issue 187)

Original issue reported on code.google.com by jfitz...@gmail.com on 28 Sep 2008 at 2:47