Hello,
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? TIA Gerhard -- HAL is running Windows... _______________________________________________ Beginners mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/beginners |
Hi Gerhard,
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 ask again. 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! Happy coding, Ron Teitelbaum President / Principal Software Engineer US Medical Record Specialists [hidden email] > From: Gerhard Brauer > Sent: Wednesday, September 13, 2006 9:58 AM > > Hello, > > 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? > > TIA > Gerhard > -- > HAL is running Windows... > _______________________________________________ > Beginners mailing list > [hidden email] > http://lists.squeakfoundation.org/mailman/listinfo/beginners _______________________________________________ Beginners mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/beginners |
Hello!
* Ron Teitelbaum <[hidden email]> schrieb am [13.09.06 18:26]: > Hi Gerhard, > > 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. On linux i havn't this wond3d dir. There are only the virtual machine dir (here it's 3.9-7) and the source,changes and image files. But it could be possible that i've downloaded a developer image (i got it from http://ftp.squeak.org/3.9/ and it's 3.9gamma #7057) where some classes not included. > Also you might consider reloading it from squeakmap > in 3.9 before trying your projects. In squeakmap browser i'm not found anthing like Wonderland, only searching 3D puts me to something like Ballon3d... > To your questions: > > a) The projects mentioned above. Are these image dependent? > Hopefully you will get a better answer then mine. ;-) But when i think a little deeper, it could be that i've never understand the "project" behavior. I thougt these were "little images" or "applications" that could be filed and reloaded. For example in one project that i have saved were several open browsers, workspaces with "running objects", some morphs. I think reloading this in a "clean" image is not what projects should be for. > b) Should i do image(-version) regulary updates ? > I'm having some trouble understanding this question. No one makes me my english so fast after ;-) I break the grammar like a 7 years old child... > 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. Ah, that's a nice working-flow method. Maybe i think to statically about "the image". You use the image like a "versioning system" for the "here and now of the world". If a new world is build you simply merge your changes in this new. My problem (and sure the problem from every smalltalk newbie) is: i never had a real Gotcha! about the whole enviroment. I rediscover Smalltalk, and i jump between heaven and hell... It's the easiest language - and still complex. It's the easiest IDE - and still one of the complexed. I never coded something for real use, only for private use. And all languages/IDE's i tried it's a feeling of bliss to do it in something like squeak. My problems come later: what to do with my work? How and how much must i publish (refactory)? The strong break in programming paradigm makes me problems. > If you are asking neither one of these questions please feel free to > ask again. No, no, you won the price ;-) And give me some good hints. > Hope that helps! > Happy coding, > > Ron Teitelbaum Greetings Gerhard -- Dont't drink and root! _______________________________________________ Beginners mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/beginners |
Free forum by Nabble | Edit this page |