<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000"><br></font>That's fine too. I honestly don't care, I just need *some* mechanism.<br><br></div></blockquote></div><br><div>My SimplestThing approach for managing ReadMe file content within the image is described in the following discussion, and it uses class comments for simple in-image storage. In cuis class comments aren't styled so they look a bit plain, but do the job.</div><div><br></div><div><a href="http://smalltalkers.pbworks.com/System-Info">http://smalltalkers.pbworks.com/System-Info</a></div><div><br></div><div>We used to have a bob task that opens all the .text files it could find in workspaces. We added file handling capabilities to MC as well, so that you could have a Readme-ar.1.mcz. There is also a fix in mantis which allows workspaces to know the file they belong to, and save on accept, revert and so forth. (Search for "Workspace convenience methods" if that is of interest)</div><div><br></div><div>My current solution is that the default behavior of InstallSeries is to open any *.text files in a workspace. So any readme's that a package or patch wants to display are added to the updates stream like so e.g. 0020/Readme.text</div><div><br></div><div>Keith</div></body></html>