November 2012 - Pharo-users

Re: [Pharo-users] Recovering Changes from a broken image

by Chris

On 08/11/2012 20:54, Sven Van Caekenberghe wrote: > On 08 Nov 2012, at 21:37, Chris <cpmbailey(a)btinternet.com> wrote: > >> I always thought class create and method delete worked fine. > I don't see them in my .changes file in Pharo 2.0 > > I also thought these were recorded as simple doits. Yes you're right. Just tried it in 1.4 and 2.0 and it only seems to be working in the former.

Nov. 8, 2012

Re: [Pharo-users] Recovering Changes from a broken image

by Sven Van Caekenberghe

On 08 Nov 2012, at 21:37, Chris <cpmbailey(a)btinternet.com> wrote: > I always thought class create and method delete worked fine. I don't see them in my .changes file in Pharo 2.0 I also thought these were recorded as simple doits.

Nov. 8, 2012

Re: [Pharo-users] Recovering Changes from a broken image

by Chris

On 08/11/2012 20:15, Benjamin wrote: > On Nov 8, 2012, at 9:09 PM, StÃ©phane Ducasse wrote: > >> On Nov 8, 2012, at 9:03 PM, Sven Van Caekenberghe wrote: >> >>> Hi, >>> >>> One of the cool things of Smalltalk's images/changes file is that you can do a World Menu > Tools > Recover lost changesâ¦ to get back most [1] of your code in case your image/OS/machine suddenly crashed or you forgot to save your image or commit your Monticello packages. >>> >>> But we all have encountered the situation where the image is broken, saved in such a state that it no longer starts up properly. In that case your code might seem lost forever. >>> >>> No, it is not ! >>> >>> Two days ago I had this problem myself and I remembered something Marcus said some time ago: you can access the changes file of one (in casu your broken image) from another (working) image to select/recover the changes you want. It worked perfectly. >>> >>> The easiest procedure it to copy the .changes file from the broken image and rename its extension to .cs and then open it from a World Menu > Tools > File Browser and open a Changes browser on it. >> We should add a recover from another image shortcut. >>> I found this very useful. This is a really important technique to be aware of. >>> >>> Sven >>> >>> [1] Sadly, not everything is logged in the changes file: creation of new classes, method deletions are not recorded. >> Yes we should change that. >> Ezequiel started to work on a new description of changes. > I though they were logged as "do it" , am i wrong ? > > Ben I always thought class create and method delete worked fine. There are a few issues with the current system that would be great to see addressed; instance variables created from the source code itself, class renames, repackaging etc > >>> -- >>> Sven Van Caekenberghe >>> http://stfx.eu >>> Smalltalk is the Red Pill >>> >>> >>> >>> >> > >

Nov. 8, 2012

Re: [Pharo-users] Recovering Changes from a broken image

by Benjamin

On Nov 8, 2012, at 9:09 PM, StÃ©phane Ducasse wrote: > > On Nov 8, 2012, at 9:03 PM, Sven Van Caekenberghe wrote: > >> Hi, >> >> One of the cool things of Smalltalk's images/changes file is that you can do a World Menu > Tools > Recover lost changesâ¦ to get back most [1] of your code in case your image/OS/machine suddenly crashed or you forgot to save your image or commit your Monticello packages. >> >> But we all have encountered the situation where the image is broken, saved in such a state that it no longer starts up properly. In that case your code might seem lost forever. >> >> No, it is not ! >> >> Two days ago I had this problem myself and I remembered something Marcus said some time ago: you can access the changes file of one (in casu your broken image) from another (working) image to select/recover the changes you want. It worked perfectly. >> >> The easiest procedure it to copy the .changes file from the broken image and rename its extension to .cs and then open it from a World Menu > Tools > File Browser and open a Changes browser on it. > > We should add a recover from another image shortcut. >> >> I found this very useful. This is a really important technique to be aware of. >> >> Sven >> >> [1] Sadly, not everything is logged in the changes file: creation of new classes, method deletions are not recorded. > > Yes we should change that. > Ezequiel started to work on a new description of changes. I though they were logged as "do it" , am i wrong ? Ben > >> >> -- >> Sven Van Caekenberghe >> http://stfx.eu >> Smalltalk is the Red Pill >> >> >> >> > >

Nov. 8, 2012

Re: [Pharo-users] Recovering Changes from a broken image

by StÃ©phane Ducasse

On Nov 8, 2012, at 9:03 PM, Sven Van Caekenberghe wrote: > Hi, > > One of the cool things of Smalltalk's images/changes file is that you can do a World Menu > Tools > Recover lost changesâ¦ to get back most [1] of your code in case your image/OS/machine suddenly crashed or you forgot to save your image or commit your Monticello packages. > > But we all have encountered the situation where the image is broken, saved in such a state that it no longer starts up properly. In that case your code might seem lost forever. > > No, it is not ! > > Two days ago I had this problem myself and I remembered something Marcus said some time ago: you can access the changes file of one (in casu your broken image) from another (working) image to select/recover the changes you want. It worked perfectly. > > The easiest procedure it to copy the .changes file from the broken image and rename its extension to .cs and then open it from a World Menu > Tools > File Browser and open a Changes browser on it. We should add a recover from another image shortcut. > > I found this very useful. This is a really important technique to be aware of. > > Sven > > [1] Sadly, not everything is logged in the changes file: creation of new classes, method deletions are not recorded. Yes we should change that. Ezequiel started to work on a new description of changes. > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > > >

Nov. 8, 2012

Recovering Changes from a broken image

by Sven Van Caekenberghe

Hi, One of the cool things of Smalltalk's images/changes file is that you can do a World Menu > Tools > Recover lost changesâ¦ to get back most [1] of your code in case your image/OS/machine suddenly crashed or you forgot to save your image or commit your Monticello packages. But we all have encountered the situation where the image is broken, saved in such a state that it no longer starts up properly. In that case your code might seem lost forever. No, it is not ! Two days ago I had this problem myself and I remembered something Marcus said some time ago: you can access the changes file of one (in casu your broken image) from another (working) image to select/recover the changes you want. It worked perfectly. The easiest procedure it to copy the .changes file from the broken image and rename its extension to .cs and then open it from a World Menu > Tools > File Browser and open a Changes browser on it. I found this very useful. This is a really important technique to be aware of. Sven [1] Sadly, not everything is logged in the changes file: creation of new classes, method deletions are not recorded. -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Nov. 8, 2012

Re: [Pharo-users] [Pharo-consortium] Pharo consortium agreement

by StÃ©phane Ducasse

On Nov 8, 2012, at 4:03 AM, Igor Stasenko wrote: > On 6 November 2012 15:36, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> Very good that there is progress on this front ! >> >> Even better news about Igor ;-) >> > i always asking myself, if this horse worth its bets. > Thank you, Stephane & others for putting trust in me more than i do :) As a thank, write a tutorial and doc on FFI and NativeBoost with a lot of documented examples ;D > >> Indeed: thank you INRIA for sponsoring Pharo. >> >> I will read the document this evening. >> >> -- >> Sven Van Caekenberghe >> http://stfx.eu >> Smalltalk is the Red Pill >> >> >> >> On 06 Nov 2012, at 17:24, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> Dear Pharoers >>> >>> Here is the result of the work we did around the consortium for Pharo for about 2 years. We took into account all your remarks over the years >>> and we think that the result is good and corresponds to what the community can support. >>> This consortium is important for Pharo's future and it will help us to deliver a system to help you making business. >>> Our goal is to be able to collect fundings to pay at least one full time engineer. >>> >>> The idea is that all the consortium members will sign the same agreement. We will not handle modifications per partners. >>> Now since we are starting the process if you spot some glitches on the form let us know. We can discuss and fully stabilize one version. >>> >>> We suggest to read the document. >>> - If you agree to sign it and send it to us (in two copies if you do it by surface mail at >>> INRIA - S. Ducasse - Pharo, 40, avenue Halley, Parc Scientifique de la Haute Borne, >>> BÃ¢t.A, Park Plaza, Villeneuve d'Ascq, FR-59650, France.), so that we sign it too. >>> - Don't forget to complete your legal mention on first page and your contact details on article 14 before signing. :) >>> >>> We will launch soon two web sites: >>> - one for the Pharo user association and >>> - one for the Pharo consortium. >>> >>> >>> A side note: we will communicate about it later and separately but Inria decided to support the consortium by paying one extra year to Igor Stasenko. >>> This is around 60 Keuros in addition to the year of Esteban Lorenzano and previous years of Igor. >>> >>> I really want to thank Inria for the constant support and the work of S. Karpf, P. Moreau and S. Perin. >>> >>> Stef >>> >>> <2012-11-06-consortium PHARO.pdf> >>> >>> >>> >>> >>> ------------------------ >>> Dr. StÃ©phane Ducasse -- Directeur de Recherche (Senior Researcher) >>> INRIA - USTL - CNRS UMR 8022 >>> stephane.ducasse(a)inria.fr >>> http://stephane.ducasse.free.fr >>> http://rmod.lille.inria.fr/ >>> **NEW ***Tel 00 33 (0)3 59 35 87 52 - Fax 33 3 59 57 78 50 >>> >>> 40, avenue Halley, Parc Scientifique de la Haute Borne, >>> BÃ¢t.A, Park Plaza, Villeneuve d'Ascq, FR-59650, France. >>> >>> >>> >>> >>> >>> >>> >> >> > > > > -- > Best regards, > Igor Stasenko. > > _______________________________________________ > Pharo-consortium mailing list > Pharo-consortium(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-consortium

Nov. 8, 2012

Re: [Pharo-users] Pharo consortium agreement

by Igor Stasenko

On 6 November 2012 15:36, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Very good that there is progress on this front ! > > Even better news about Igor ;-) > i always asking myself, if this horse worth its bets. Thank you, Stephane & others for putting trust in me more than i do :) > Indeed: thank you INRIA for sponsoring Pharo. > > I will read the document this evening. > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > > > On 06 Nov 2012, at 17:24, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Dear Pharoers >> >> Here is the result of the work we did around the consortium for Pharo for about 2 years. We took into account all your remarks over the years >> and we think that the result is good and corresponds to what the community can support. >> This consortium is important for Pharo's future and it will help us to deliver a system to help you making business. >> Our goal is to be able to collect fundings to pay at least one full time engineer. >> >> The idea is that all the consortium members will sign the same agreement. We will not handle modifications per partners. >> Now since we are starting the process if you spot some glitches on the form let us know. We can discuss and fully stabilize one version. >> >> We suggest to read the document. >> - If you agree to sign it and send it to us (in two copies if you do it by surface mail at >> INRIA - S. Ducasse - Pharo, 40, avenue Halley, Parc Scientifique de la Haute Borne, >> BÃ¢t.A, Park Plaza, Villeneuve d'Ascq, FR-59650, France.), so that we sign it too. >> - Don't forget to complete your legal mention on first page and your contact details on article 14 before signing. :) >> >> We will launch soon two web sites: >> - one for the Pharo user association and >> - one for the Pharo consortium. >> >> >> A side note: we will communicate about it later and separately but Inria decided to support the consortium by paying one extra year to Igor Stasenko. >> This is around 60 Keuros in addition to the year of Esteban Lorenzano and previous years of Igor. >> >> I really want to thank Inria for the constant support and the work of S. Karpf, P. Moreau and S. Perin. >> >> Stef >> >> <2012-11-06-consortium PHARO.pdf> >> >> >> >> >> ------------------------ >> Dr. StÃ©phane Ducasse -- Directeur de Recherche (Senior Researcher) >> INRIA - USTL - CNRS UMR 8022 >> stephane.ducasse(a)inria.fr >> http://stephane.ducasse.free.fr >> http://rmod.lille.inria.fr/ >> **NEW ***Tel 00 33 (0)3 59 35 87 52 - Fax 33 3 59 57 78 50 >> >> 40, avenue Halley, Parc Scientifique de la Haute Borne, >> BÃ¢t.A, Park Plaza, Villeneuve d'Ascq, FR-59650, France. >> >> >> >> >> >> >> > > -- Best regards, Igor Stasenko.

Nov. 8, 2012

Re: [Pharo-users] [Pharo-consortium] Pharo consortium agreement

by StÃ©phane Ducasse

Norbert after discussing with sophie, we will collect all details and produce a new version by beginning of new week. Stef On Nov 7, 2012, at 3:15 PM, Norbert Hartl wrote: > So, what's best. Wait to finalize the form or print and send? > > Norbert > > Am 06.11.2012 um 17:24 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >> Dear Pharoers >> >> Here is the result of the work we did around the consortium for Pharo for about 2 years. We took into account all your remarks over the years >> and we think that the result is good and corresponds to what the community can support. >> This consortium is important for Pharo's future and it will help us to deliver a system to help you making business. >> Our goal is to be able to collect fundings to pay at least one full time engineer. >> >> The idea is that all the consortium members will sign the same agreement. We will not handle modifications per partners. >> Now since we are starting the process if you spot some glitches on the form let us know. We can discuss and fully stabilize one version. >> >> We suggest to read the document. >> - If you agree to sign it and send it to us (in two copies if you do it by surface mail at >> INRIA - S. Ducasse - Pharo, 40, avenue Halley, Parc Scientifique de la Haute Borne, >> BÃ¢t.A, Park Plaza, Villeneuve d'Ascq, FR-59650, France.), so that we sign it too. >> - Don't forget to complete your legal mention on first page and your contact details on article 14 before signing. :) >> >> We will launch soon two web sites: >> - one for the Pharo user association and >> - one for the Pharo consortium. >> >> >> A side note: we will communicate about it later and separately but Inria decided to support the consortium by paying one extra year to Igor Stasenko. >> This is around 60 Keuros in addition to the year of Esteban Lorenzano and previous years of Igor. >> >> I really want to thank Inria for the constant support and the work of S. Karpf, P. Moreau and S. Perin. >> >> Stef >> >> <2012-11-06-consortium PHARO.pdf> >> >> >> >> >> ------------------------ >> Dr. StÃ©phane Ducasse -- Directeur de Recherche (Senior Researcher) >> INRIA - USTL - CNRS UMR 8022 >> stephane.ducasse(a)inria.fr >> http://stephane.ducasse.free.fr >> http://rmod.lille.inria.fr/ >> **NEW ***Tel 00 33 (0)3 59 35 87 52 - Fax 33 3 59 57 78 50 >> >> 40, avenue Halley, Parc Scientifique de la Haute Borne, >> BÃ¢t.A, Park Plaza, Villeneuve d'Ascq, FR-59650, France. >> >> >> >> >> >> >> >> _______________________________________________ >> Pharo-consortium mailing list >> Pharo-consortium(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-consortium >

Nov. 7, 2012

Re: [Pharo-users] [Pharo-consortium] Pharo consortium agreement

by StÃ©phane Ducasse

> So, what's best. Wait to finalize the form or print and send? so far it will only be c instead of C so wait 2 more days and this is ok Stef > > Norbert > > Am 06.11.2012 um 17:24 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >> Dear Pharoers >> >> Here is the result of the work we did around the consortium for Pharo for about 2 years. We took into account all your remarks over the years >> and we think that the result is good and corresponds to what the community can support. >> This consortium is important for Pharo's future and it will help us to deliver a system to help you making business. >> Our goal is to be able to collect fundings to pay at least one full time engineer. >> >> The idea is that all the consortium members will sign the same agreement. We will not handle modifications per partners. >> Now since we are starting the process if you spot some glitches on the form let us know. We can discuss and fully stabilize one version. >> >> We suggest to read the document. >> - If you agree to sign it and send it to us (in two copies if you do it by surface mail at >> INRIA - S. Ducasse - Pharo, 40, avenue Halley, Parc Scientifique de la Haute Borne, >> BÃ¢t.A, Park Plaza, Villeneuve d'Ascq, FR-59650, France.), so that we sign it too. >> - Don't forget to complete your legal mention on first page and your contact details on article 14 before signing. :) >> >> We will launch soon two web sites: >> - one for the Pharo user association and >> - one for the Pharo consortium. >> >> >> A side note: we will communicate about it later and separately but Inria decided to support the consortium by paying one extra year to Igor Stasenko. >> This is around 60 Keuros in addition to the year of Esteban Lorenzano and previous years of Igor. >> >> I really want to thank Inria for the constant support and the work of S. Karpf, P. Moreau and S. Perin. >> >> Stef >> >> <2012-11-06-consortium PHARO.pdf> >> >> >> >> >> ------------------------ >> Dr. StÃ©phane Ducasse -- Directeur de Recherche (Senior Researcher) >> INRIA - USTL - CNRS UMR 8022 >> stephane.ducasse(a)inria.fr >> http://stephane.ducasse.free.fr >> http://rmod.lille.inria.fr/ >> **NEW ***Tel 00 33 (0)3 59 35 87 52 - Fax 33 3 59 57 78 50 >> >> 40, avenue Halley, Parc Scientifique de la Haute Borne, >> BÃ¢t.A, Park Plaza, Villeneuve d'Ascq, FR-59650, France. >> >> >> >> >> >> >> >> _______________________________________________ >> Pharo-consortium mailing list >> Pharo-consortium(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-consortium >

Nov. 7, 2012