Today I learned that you can actually lose code in Pharo because the record is not always added to the changes file.
Also using the tool is quite a lot of pain, so if you want to recover your changes you have to do a lot of archaeology. I've added several issues and marked most of them as '2 - Really Important', because I think they are (especially for students etc that like to break things), but maybe you don't want it for Pharo 5. Peter |
I hadn't used Recover Changes for a while, but recently found that it
had lost a lot of power. Particularly not being able to filter to show only the most recent updates. Its tedious to manually search for the latest version of several methods. cheers -ben On Fri, Mar 18, 2016 at 6:30 AM, Peter Uhnák <[hidden email]> wrote: > Today I learned that you can actually lose code in Pharo because the record > is not always added to the changes file. > > Also using the tool is quite a lot of pain, so if you want to recover your > changes you have to do a lot of archaeology. > > I've added several issues and marked most of them as '2 - Really Important', > because I think they are (especially for students etc that like to break > things), but maybe you don't want it for Pharo 5. > > https://pharo.fogbugz.com/f/cases/17840/ChangesBrowser-selectAll-DNU > https://pharo.fogbugz.com/f/cases/17841/Creating-a-class-from-a-debugger-during-compilation-doesn-t-create-a-record-in-changes-file > https://pharo.fogbugz.com/f/cases/17842/Recover-lost-changes-doesn-t-recover-class-creation > https://pharo.fogbugz.com/f/cases/17843/Changes-Browser-doesn-t-recover-changes-in-correct-order > > Peter > > |
Yes because we have epicea to replace it but epicea shows us some nice
bugs underneath. So we decided to postpone. Now this is just that maintaining two systems is always a pain and we are sorry. Stef Le 18/3/16 00:33, Ben Coman a écrit : > I hadn't used Recover Changes for a while, but recently found that it > had lost a lot of power. Particularly not being able to filter to > show only the most recent updates. Its tedious to manually search for > the latest version of several methods. > > cheers -ben > > On Fri, Mar 18, 2016 at 6:30 AM, Peter Uhnák <[hidden email]> wrote: >> Today I learned that you can actually lose code in Pharo because the record >> is not always added to the changes file. >> >> Also using the tool is quite a lot of pain, so if you want to recover your >> changes you have to do a lot of archaeology. >> >> I've added several issues and marked most of them as '2 - Really Important', >> because I think they are (especially for students etc that like to break >> things), but maybe you don't want it for Pharo 5. >> >> https://pharo.fogbugz.com/f/cases/17840/ChangesBrowser-selectAll-DNU >> https://pharo.fogbugz.com/f/cases/17841/Creating-a-class-from-a-debugger-during-compilation-doesn-t-create-a-record-in-changes-file >> https://pharo.fogbugz.com/f/cases/17842/Recover-lost-changes-doesn-t-recover-class-creation >> https://pharo.fogbugz.com/f/cases/17843/Changes-Browser-doesn-t-recover-changes-in-correct-order >> >> Peter >> >> > |
In reply to this post by Peter Uhnak
thanks for the report.
We should fix them. We can try to fix one together today. Le 17/3/16 23:30, Peter Uhnák a écrit : > Today I learned that you can actually lose code in Pharo because the > record is not always added to the changes file. > > Also using the tool is quite a lot of pain, so if you want to recover > your changes you have to do a lot of archaeology. > > I've added several issues and marked most of them as '2 - Really > Important', because I think they are (especially for students etc that > like to break things), but maybe you don't want it for Pharo 5. > > https://pharo.fogbugz.com/f/cases/17840/ChangesBrowser-selectAll-DNU > https://pharo.fogbugz.com/f/cases/17841/Creating-a-class-from-a-debugger-during-compilation-doesn-t-create-a-record-in-changes-file > https://pharo.fogbugz.com/f/cases/17842/Recover-lost-changes-doesn-t-recover-class-creation > https://pharo.fogbugz.com/f/cases/17843/Changes-Browser-doesn-t-recover-changes-in-correct-order > > Peter > > |
In reply to this post by stepharo
On Fri, Mar 18, 2016 at 7:45 AM, stepharo <[hidden email]> wrote:
> Yes because we have epicea to replace it but epicea shows us some nice bugs > underneath. > So we decided to postpone. Postpone after 5.0 ? -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/ |
yes, Epicea will be integrated “first week of Pharo 6”, so we can iterate and fix :)
> On 18 Mar 2016, at 08:52, Serge Stinckwich <[hidden email]> wrote: > > On Fri, Mar 18, 2016 at 7:45 AM, stepharo <[hidden email]> wrote: >> Yes because we have epicea to replace it but epicea shows us some nice bugs >> underneath. >> So we decided to postpone. > > Postpone after 5.0 ? > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > |
On Fri, Mar 18, 2016 at 8:58 AM, Esteban Lorenzano <[hidden email]> wrote: yes, Epicea will be integrated “first week of Pharo 6”, so we can iterate and Well we still need to fix it, we can't leave Pharo 5 for a year without a proper recovery. We'll try to fix something today with Stef. Peter |
12 hours later all the bugs are fixed. And that's why I love Pharo and everyone here. :) Thanks! On Fri, Mar 18, 2016 at 10:53 AM, Peter Uhnák <[hidden email]> wrote:
|
THANK YOU !!
(but you had a secret French special agent, right ;-) > On 18 Mar 2016, at 12:26, Peter Uhnák <[hidden email]> wrote: > > 12 hours later all the bugs are fixed. > > And that's why I love Pharo and everyone here. :) > > Thanks! > > On Fri, Mar 18, 2016 at 10:53 AM, Peter Uhnák <[hidden email]> wrote: > On Fri, Mar 18, 2016 at 8:58 AM, Esteban Lorenzano <[hidden email]> wrote: > yes, Epicea will be integrated “first week of Pharo 6”, so we can iterate and > > Well we still need to fix it, we can't leave Pharo 5 for a year without a proper recovery. > We'll try to fix something today with Stef. > > Peter > |
Actually the thanks here goes to Latsabben ( that fixed most of it before I could even start looking at the code. :) Peter On Fri, Mar 18, 2016 at 12:30 PM, Sven Van Caekenberghe <[hidden email]> wrote: THANK YOU !! |
Ah, that is a secret Norwegian agent !
> On 18 Mar 2016, at 12:34, Peter Uhnák <[hidden email]> wrote: > > Actually the thanks here goes to Latsabben ( that fixed most of it before I could even start looking at the code. :) > > Peter > > On Fri, Mar 18, 2016 at 12:30 PM, Sven Van Caekenberghe <[hidden email]> wrote: > THANK YOU !! > > (but you had a secret French special agent, right ;-) > > > On 18 Mar 2016, at 12:26, Peter Uhnák <[hidden email]> wrote: > > > > 12 hours later all the bugs are fixed. > > > > And that's why I love Pharo and everyone here. :) > > > > Thanks! > > > > On Fri, Mar 18, 2016 at 10:53 AM, Peter Uhnák <[hidden email]> wrote: > > On Fri, Mar 18, 2016 at 8:58 AM, Esteban Lorenzano <[hidden email]> wrote: > > yes, Epicea will be integrated “first week of Pharo 6”, so we can iterate and > > > > Well we still need to fix it, we can't leave Pharo 5 for a year without a proper recovery. > > We'll try to fix something today with Stef. > > > > Peter > > > > > |
In reply to this post by Peter Uhnak
Thanks henrik you were faster than us...
I had to finish an exercise for the mooc. Stef Le 18/3/16 10:53, Peter Uhnák a écrit :
|
In reply to this post by Ben Coman
Hi
> On Mar 17, 2016, at 4:33 PM, Ben Coman <[hidden email]> wrote: > > I hadn't used Recover Changes for a while, but recently found that it > had lost a lot of power. Particularly not being able to filter to > show only the most recent updates. Its tedious to manually search for > the latest version of several methods. Also the middle button menu in the change list (which can also be used to import source files) has been reduced to just two items, rendering the tool much less powerful. A colleague and I were importing code from squeak the other day and were missing "select unchanged definitions", and others. Watching my colleague use the tool manually was painful. Someone should really put this functionality back. Look at the squeak tool for the most immediate reference. Look at VisualWorks for something more powerful still. Don't let it be said of Pharo: Don't it always seem to go That you don't know what you've got Til its gone They paved paradise And put up a parking lot ;-) _,,,^..^,,,_ (phone) Eliot > > cheers -ben > >> On Fri, Mar 18, 2016 at 6:30 AM, Peter Uhnák <[hidden email]> wrote: >> Today I learned that you can actually lose code in Pharo because the record >> is not always added to the changes file. >> >> Also using the tool is quite a lot of pain, so if you want to recover your >> changes you have to do a lot of archaeology. >> >> I've added several issues and marked most of them as '2 - Really Important', >> because I think they are (especially for students etc that like to break >> things), but maybe you don't want it for Pharo 5. >> >> https://pharo.fogbugz.com/f/cases/17840/ChangesBrowser-selectAll-DNU >> https://pharo.fogbugz.com/f/cases/17841/Creating-a-class-from-a-debugger-during-compilation-doesn-t-create-a-record-in-changes-file >> https://pharo.fogbugz.com/f/cases/17842/Recover-lost-changes-doesn-t-recover-class-creation >> https://pharo.fogbugz.com/f/cases/17843/Changes-Browser-doesn-t-recover-changes-in-correct-order >> >> Peter > |
In reply to this post by Sven Van Caekenberghe-2
> Ah, that is a secret Norwegian agent ! Yes the french spies is unsharpen these days working on mooc (yes again continuously and teaching) > >> On 18 Mar 2016, at 12:34, Peter Uhnák <[hidden email]> wrote: >> >> Actually the thanks here goes to Latsabben ( that fixed most of it before I could even start looking at the code. :) >> >> Peter >> >> On Fri, Mar 18, 2016 at 12:30 PM, Sven Van Caekenberghe <[hidden email]> wrote: >> THANK YOU !! >> >> (but you had a secret French special agent, right ;-) >> >>> On 18 Mar 2016, at 12:26, Peter Uhnák <[hidden email]> wrote: >>> >>> 12 hours later all the bugs are fixed. >>> >>> And that's why I love Pharo and everyone here. :) >>> >>> Thanks! >>> >>> On Fri, Mar 18, 2016 at 10:53 AM, Peter Uhnák <[hidden email]> wrote: >>> On Fri, Mar 18, 2016 at 8:58 AM, Esteban Lorenzano <[hidden email]> wrote: >>> yes, Epicea will be integrated “first week of Pharo 6”, so we can iterate and >>> >>> Well we still need to fix it, we can't leave Pharo 5 for a year without a proper recovery. >>> We'll try to fix something today with Stef. >>> >>> Peter >>> >> >> > > |
Free forum by Nabble | Edit this page |