loosing versions of method after deleting and creating new

Hi,

sometimes I have got the following situation:

1) I delete a method
2) I recognize uhhhh, I need it! it was wrong to delete it!
3) I re-write it (or get it from changes file or old image)
4) now, the versions of the method are lost

I would have the following wishes for this situation:
a) it should be easier for me to get back the deleted method (easier as searching the changes file or load old version of image)
b) after re-writing the method, I want the versions of this method back.

Perhaps there is another way to handle this and I did not know it.
For a while I was renaming methods (e.g. from "methodname" to "methodnameOLD") instead of deleting it but this is not the way it should be imho.

I was used to have this functionality in envy.

What do you think about this?

Regards
Sabine

On Aug 13, 2013, at 4:34 PM, Sabine Knöfel <[hidden email]> wrote:

> Hi,
>
> sometimes I have got the following situation:
>
> 1) I delete a method
> 2) I recognize uhhhh, I need it! it was wrong to delete it!
> 3) I re-write it (or get it from changes file or old image)
> 4) now, the versions of the method are lost

Yes this is bug and nobody took the time to look at it.
Martin is working on a new change management system.


> I would have the following wishes for this situation:
> a) it should be easier for me to get back the deleted method (easier as
> searching the changes file or load old version of image)
> b) after re-writing the method, I want the versions of this method back.

us too.

> Perhaps there is another way to handle this and I did not know it.
> For a while I was renaming methods (e.g. from "methodname" to
> "methodnameOLD") instead of deleting it but this is not the way it should be
> imho.
>
> I was used to have this functionality in envy.

Us too in Pharo but a bug was introduced.

> What do you think about this?

we want more time

Hi Sabine,

There is a method version inspector which uses gitfiletree [1] doesn't loose the old versions of the methods, and it will show versions older than the image (i.e. all versions stored in the git repository holding the package). It's packaged with the AltBrowser [2].

Thierry

[1] https://github.com/dalehenrich/filetree
[2] https://github.com/ThierryGoubier/AltBrowser

________________________________________
De : Pharo-dev [[hidden email]] de la part de Sabine Knöfel [[hidden email]]
Date d'envoi : mardi 13 août 2013 16:34
À : [hidden email]
Objet : [Pharo-dev] loosing versions of method after deleting and creating      new

Hi,

sometimes I have got the following situation:

1) I delete a method
2) I recognize uhhhh, I need it! it was wrong to delete it!
3) I re-write it (or get it from changes file or old image)
4) now, the versions of the method are lost

I would have the following wishes for this situation:
a) it should be easier for me to get back the deleted method (easier as
searching the changes file or load old version of image)
b) after re-writing the method, I want the versions of this method back.

Perhaps there is another way to handle this and I did not know it.
For a while I was renaming methods (e.g. from "methodname" to
"methodnameOLD") instead of deleting it but this is not the way it should be
imho.

I was used to have this functionality in envy.

What do you think about this?

Regards
Sabine







--
View this message in context: http://forum.world.st/loosing-versions-of-method-after-deleting-and-creating-new-tp4703492.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.