Stéphane Ducasse wrote:
I suggest that we avoid copy and paste.
Why not having everything in the web pharo-book since we
can
- browse it on the web
- generate latex and book for it
- query it via help
I do not see the point of having an ascii outdated version. We do not have the
manpower for doing that.
I'm already losing my time with svn since some people committed over my
changes....
Stef
I think this is a good approach ... right now I'm rethinking the
metacello and glassdb wikis based on google project ... it has been
convenient up to now, but I really think that having documentation that
is created/editted on the web and then spawned programatically for
inclusion as in image help is superior....
the advantage of in-image documentation is that doits can just be
executed without the need for copy and paste. Also the in-image
documentation will match the loaded code, while the online documentation
will constantly be moving forward ...
Dale
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
