Hi.
I've worked a bit with the new version lying in the background. When I
started, I have one manager called * SM-Loader. Now I have two identical
ones. How come?

How do you think DVS should relate to the FileContentsBrowser and to SM?
I'm currently only using it to create my packages, since I'm not
maintaining anything in CVS. So I just use a script to create a module
on my code, fileout, version by rename, gzip and upload to ftp.

When I want to compare what I've done in the last version (to write the
changes log), I usually use the FCB. I just tried, and the browse
changes option works pretty well, except it doesn't know what file to
use, since I add a ".N", where N=version count to keep history.

Hmm, maybe I should create an SMLoaderInfo class to keep track of this
renaming?

Daniel

Avi Bryant <avi at beta4.com> wrote:
> Hey,
> 
> A new version of DVS has been posted.  This (hopefully) addresses Daniel's
> concerns about lighter-weight package creation - the UI now tracks package
> instances instead of classes, and the simple "Add" button is back.
> However, custom PackageInfo subclasses are still fully supported.
> Also, there's a crude prelude/postscript mechanism: override #preludeText
> and #postscriptText to add arbitrary doits to the beginning and end of the
> file-out.
> 
> Available from SqueakMap:
> http://marvin.bluefish.se:8000/sm/package/100d59d0-bf81-4e74-a4fe-5a2fd0c6b4ec
> 
> Avi