Re: [Pharo-project] In Smalltalk you can't loose code... hum
On Sep 25, 2010, at 9:25 PM, François Tanguy wrote:
Hi,
the statement is true when the code is saved in the browser. But in a workspace or in the script manager that is not true.
Actually it is a feature request: You can't loose code even when you are working in the script browser.
check if you can find a way and I'm sure that the maintainer of scriptmanager will integrate it. I always prefer to define methods so I never use script or workspace to write anything useful.
Because in the script manager has a save capability, would it be difficult to write the changes into the changes files ?
the problem is that the change files logic is old and it works 'well' for what it should but extending it will break other part. This is why slowly we will have to think to get something better.
Francois _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Sat, Sep 25, 2010 at 12:53 PM, Stéphane Ducasse < stephane.ducasse@inria.fr> wrote:
On Sep 25, 2010, at 9:25 PM, François Tanguy wrote:
Hi,
the statement is true when the code is saved in the browser. But in a workspace or in the script manager that is not true.
Actually it is a feature request: You can't loose code even when you are working in the script browser.
check if you can find a way and I'm sure that the maintainer of scriptmanager will integrate it. I always prefer to define methods so I never use script or workspace to write anything useful.
Because in the script manager has a save capability, would it be
difficult to write the changes into the changes files ?
the problem is that the change files logic is old and it works 'well' for what it should but extending it will break other part. This is why slowly we will have to think to get something better.
Do you mean improving the change scanner parsing or throwing away and going for something different?
Francois _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Le 25 sept. 2010 à 21:53, Stéphane Ducasse a écrit :
On Sep 25, 2010, at 9:25 PM, François Tanguy wrote:
Hi,
the statement is true when the code is saved in the browser. But in a workspace or in the script manager that is not true.
Actually it is a feature request: You can't loose code even when you are working in the script browser.
check if you can find a way and I'm sure that the maintainer of scriptmanager will integrate it. I always prefer to define methods so I never use script or workspace to write anything useful.
In my case, I wrote some crap and got an endless loop... Had to quit the image and lost some code. But I kind of like the script manager to write codes that build models or examples to remind me how to do some stuff. I will have a look at the script manager and hope we can come up with a solution. At least when Cmd + S is pressed, the minimum would be to save the code.
Because in the script manager has a save capability, would it be difficult to write the changes into the changes files ?
the problem is that the change files logic is old and it works 'well' for what it should but extending it will break other part. This is why slowly we will have to think to get something better.
Francois _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
participants (3)
-
Eliot Miranda -
François Tanguy -
Stéphane Ducasse