The problem with ScriptManager is that it's graphical. It's small, 1 class, but graphical. If I'm working on a package which does not depend on a graphical framework, it would be cool to not add a dependency just for the README. What I suggest is a method on Object or Class which prints its argument to the Transcript by default. Then, ScriptManager can override this method. It's not that clean but it's the only solution I found currently.
26 Feb 2007 14:44:05 -0500, Lex Spoon lex@lexspoon.org:
"Damien Cassou" damien.cassou@gmail.com writes:
20 Feb 2007 18:32:27 -0500, Lex Spoon lex@lexspoon.org:
Damien Cassou damien.cassou@laposte.net writes:
There is ScriptManager to do that I think. I use it for the squeak-dev image and it is very interesting. Would be cool if a system like that is integrated into Squeak so that packages could just do a:
self addReadmeTitled: 'Dynamic Protocols' containing: '...'
Ohh, nice.
Of course, in a package-universes image, you can depend-on the ScriptManager package, and then do exactly the above in your package's post-load code.
But it would be better to have that message in the base image even if ScriptManager is not loaded. Then, the image would display a Workspace if such a class exist or would put everything in the transcript.
If your package depends on ScriptManager, then ScriptManager will always be available by the time your package loads.
Assuming ScriptManager is small, it should be no big deal to depend on it. If ScriptManager is big, then it would be better to have a small subsystem just for managing these readmes. This could initially be a separate package, and could later be included in the standard image if enough people use it.
-Lex