Yes every package will have a manifest where we store first rules result then naturally the documentation. I would like to use a subset of SmallUML to describe some parts too. Stef On Dec 1, 2012, at 3:13 PM, Sebastian Nozzi wrote:
Dear Pharoers,
by chance I read recently a comment from Stef that comments for Packages are planned.
Is this true?
Would be a very welcome feature :-)
Sometimes I load a package, or series of packages, from Monticello, but have a hard time figuring out where to start. Through intuition, trial and error I find the "core" package and then the "core" class and then at the class side maybe there are examples, or look in the documentation. But a better starting point would be of course documentation (just a few lines) in the core package.
Long story short, we need a way to compensate for the lack of "README.txt" that file-based solutions have ;-)
Also related: is there a way to execute a command after a class/package is loaded by Monticello? Like opening a Workspace with initial documentation?
Thanks!
Sebastian