On May 5, 2010, at 3:24 PM, Torsten Bergmann wrote:
Hi Lukas,
"it is a design flaw" "Being forced to have strong references ... " "makes it impossible to just include some documentation" "This doesn't encourage me at all" "..."
So many negative statements in one post, look like you had a bad day today ;)
PhD stress :)
....
Attached is a simple (rough)example that it is easy to extend the help system the way you may want (with a builder similar to system settings and your above example)
Good this is what I want. I want to leverage the tests we have. Since we can remove tests anyway.
Just load it into an up to date core 1.1. image and evaluate:
HelpBrowser openOn: PragmaHelp
Look at class Foo and Bar to see that there is no dependency and PragmaHelp/PragmaHelpBuilder to see how it is done.
HelpSystem is flexible, you can also have external help sources as I've shown with the IRC example. It just depends on how you want to describe and structure your documentation...
Bye Torsten
P.S: I'm still in favour of well structured books in separate packages than mixed code/docu in one package since you may wish to unload docu for deployment/runtime scenarios.
-- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 <HelpSystemWithPragmaHelp.1.cs>_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project