[Newbies] How to do a Image Upgrade?
Ron at USMedRec.com
Wed Sep 13 16:26:16 UTC 2006
You ask some good questions. Your first problem does sound like your
project was using something in Wonderland. There is a wond3d directory that
is created and used. You can find that directory in your 3.8 directory.
I'm no expert on the 3d stuff but it's possible that copying that directory
could fix your problem. Also you might consider reloading it from squeakmap
in 3.9 before trying your projects. Maybe someone with more experience
could help you. (They will be asking you for the actual error, which you
can find after your system crashes by grabbing some of the stack from the
file that is created in your squeak directory SqueakDebug.log)
To your questions:
a) The projects mentioned above. Are these image dependent?
Hopefully you will get a better answer then mine.
b) Should i do image(-version) regulary updates ?
I'm having some trouble understanding this question.
If you are asking should you move to 3.9 my answer is yes you
should, eventually. Now that 3.9 is semi-blessed it's a good idea for
everyone that does not have a working production system to move forward.
For those that do have a working production system it's a good idea to weigh
the benefits for future development, performance, or current maintenance
against the pain of upgrading. If there is no planned development or
problems with bugs or performance you should just stay where you are.
If you are asking should you regularly make sure that you code is
loadable in a new image. The answer is definitely yes. I only rarely save
an image. I do this when loading packages takes a really long time. What I
will do is start each day by loading my work into a clean image. I will
only save stable or released code into an image and then change the name of
the image to something like ron+mc+shout+USMRSv1.image. Or something like
that. This way I can ensure that I can always load code into a new image in
the future. Just recently I had an experience which helped show how
important this is. I added some pragma code which referenced a class that
also needed to be loaded. When I exited and came back in I couldn't load my
code because the pragma definition loaded before the class that it
referenced. It's a good idea to find a way to fix these load depended
problems as you go instead of finding out about them later.
If you are asking neither one of these questions please feel free to
c) What about on code changes in classes that came (new) with an image.
For example i add methods in magnitude classes. Should i do this in the
class hierachy (directly in/under Magnitude) or better in an own
hierachy that could be managed by monticello?
When you make changes to a base class like Magnitude you should set the
category of the class to one of your own packages. I have a package called
USMRS-OverrideBaseClasses. If I added a method to Magnitude I would set the
category of the method to *USMRS-OverrideBaseClasses. The asterisk (*)
tells Monticello to store this method in your package. When you save your
package it will save all of your methods to base classes. Later you can
load a new Magnitude class and then add all of your methods to Magnitude
(and other base classes) by loading your package.
Hope that helps!
President / Principal Software Engineer
US Medical Record Specialists
Ron at USMedRec.com
> From: Gerhard Brauer
> Sent: Wednesday, September 13, 2006 9:58 AM
> i'm running Squeak on Gentoo Linux. I want to try the GTK-Plugin and the
> author told me to use a 3.9 Image (i've got errors on my 3.8 iamge).
> Now i thougt about how to do such a upgrade the best way.
> In my old 3.8 image i have not much "new stuff".
> My own code is organized by monticello and file in/out.
> I was able to import my code into the new started 3.9 image.
> But the projects fail to load (these are mostly test projects, nothing
> important, nothing which i can't "restore" from my sources)
> The errors on project reloading points to some "Wonderland"
> classes/methodes, "Cameras"(?) which i never used in these projects.
> Now i would like to know if there's a recommend way to do a image
> ugrade. I searched (a little) in mailing lists and FAQs but i found
> nothing similar to a "walkthrough solution".
> My skills in Smalltalk are a antique (Smalltalk V/DOS) and the "world"
> (Squeak) changed a lot... ;-)
> Beside the generally way for an upgrade i have some special questions:
> a) The projects mentioned above. Are these image dependent?
> b) Should i do image(-version) regulary updates ?
> c) What about on code changes in classes that came (new) with an image.
> For example i add methods in magnitude classes. Should i do this in the
> class hierachy (directly in/under Magnitude) or better in an own
> hierachy that could be managed by monticello?
> If it's not clear what i mean (my english isn't the best): how to rescue
> my whole work from a current image to a new image?
> HAL is running Windows...
> Beginners mailing list
> Beginners at lists.squeakfoundation.org
More information about the Beginners