On Wednesday 09 May 2001 01:42, Joseph Frippiat wrote:
> 1) I see that my "*.changes" file is getting bigger and bigger.  Does the
> size of this file affect the performance of Squeak?

No. New methods are appended to the end of the file, but that doesn't take 
any longer if the file is large than if it isn't (assuming you have an OS 
with a reasonably efficient file system).

Compiled methods have a pointer into the changes file so that you can see the 
source code without the code having to reside in the image.

Of course, if the size of the changes file gets beyond the size of a 
SmallInteger, bad things might happen (or they might not; I'm not sure). 
However, you don't have to worry about this until your changes file is in the 
gigabyte range.

> 2) I want to use Squeak for real work.  So, for drawing flowchart, I load
> the project NK-ConnectorDemo in my image, then I create my own project, do
> some drawings, save my project and quit Squeak without saving. 

You have excellent taste <g>.

> If I look
> in the "*.changes" file I see that the source code for the NK-ConnectorDemo
> project is there at the end of the file.  Why ?

Because you loaded the change set with my code in it; your Squeak compiled 
that code and appended it to the end of the changes file.

> 3) Is it possible to reduce safely the size of the "*.changes" file ?

You could try
	Smalltalk condenseChanges.

> I have found the menu "changes/recently logged changes..." but I haven't got
> enough information to use it.  Is it possible to find some documentation on
> what I can do with the "changes..." menu ?

Well, there's the balloon help:

file out current change set	Write the current change set out to a file whose 
name reflects the change set name and the current date & time.

create new change set...	Create a new change set and make it the current one.

browse changed methods	Open a message-list browser showing all methods in the 
current change set

check change set for slips	Check the current change set for halts, references 
to the Transcript, etc., and if any such thing is found, open up a 
message-list browser detailing all possible slips.

simple change sorter	Open a 3-paned changed-set viewing tool

dual change sorter	Open a change sorter that shows you two change sets at a 
time, making it easy to copy and move methods and classes between them.

find a change sorter (C)	Brings an open change sorter to the front, creating 
one if necessary, and makes it the active window

browse recent submissions	Open a new recent-submissions browser. A 
recent-submissions browser is a message-list browser that shows the most 
recent methods that have been submitted.  If you submit changes within that 
browser, it will keep up-to-date, always showing the most recent submissions.

find recent submissions (R)	Make an open recent-submissions browser be the 
front-window, expanding a collapsed one or creating a new one if necessary.  
A recent-submissions browser is a message-list browser that shows the most 
recent methods that have been submitted, latest first. If you submit changes 
within that browser, it will keep up-to-date, always showing the most recent 
submissions at the top of the browser.

recently logged changes...	Open a change-list browser on the latter part of 
the changes log.

recent log file...	Create a file holding the logged changes (going as far 
back as you wish), and open a window on that file.

save world as morph file	Save a file that, when reloaded, reconstitutes the 
current World.

isolate changes of this project	Isolate this project and its subprojects from 
the rest of the system. Changes to methods here will be revoked when you 
leave this project.

-- 
Ned Konz
currently: Stanwood, WA
email:     ned at bike-nomad.com
homepage:  http://bike-nomad.com