Hi, Milan,

Yes, this is easy to do.  Just have make certain that the change-set 
that is "current" in the project bears the code changes that you want 
to have "travel" with the project.  Use a change-sorter for this, if 
necessary, to copy the additional changes you want into the Demo 
project's change-set before publishing it.

If, upon publishing, a project's change-set is found to be non-empty, 
you are presented with a prompt asking whether you want those changes 
included in the .pr file; simply answer yes.

Each time a user opens a project using the browser plugin, it 
involves a fresh launch of the squeak VM, retrieving a fresh, clean 
copy of the plug-in image from disk, so you don't need to worry about 
a project's errant code changes corrupting anything other than the 
project itself.

Cheers,

   -- Scott


At 8:16 PM -0500 12/21/04, Milan Zimmermann wrote:
>As a follow-up, I'd like to ask how to do following: Let's say I have a
>project Demo.pr that I want to publish on the web, but I know it uses a
>changeset that I imported to an image from which Demo.pr was exported ("Saved
>on File").
>
>Is there a way, during Project->Save On File, to ensure that changeset will be
>exported along with Demo.pr? (I assume that inside the browser plugin this
>would be implemented by copying the image as to not allow ill-constructed
>projects to damage the "Browser Plugin image")