Re: [Pharo-users] recover lost changes
Norbert wrote:
Am 10.02.2015 um 20:59 schrieb stepharo <[hidden email]>:
Yes this should be fixed.
You mean fix the current implementation or swap it for epicea?
The current implementation. It is a significant barrier to entry for new smalltalkers and gives a very bad impression. The epicea swap is a high-impact change, that is likely to affect stability for some time. Stephan
Am 11.02.2015 um 09:33 schrieb Stephan Eggermont <stephan@stack.nl>:
Norbert wrote:
Am 10.02.2015 um 20:59 schrieb stepharo <[hidden email]>:
Yes this should be fixed.
You mean fix the current implementation or swap it for epicea?
The current implementation. It is a significant barrier to entry for new smalltalkers and gives a very bad impression. The epicea swap is a high-impact change, that is likely to affect stability for some time.
Yes but resources are still sparse. I'm usually arguing the same way like you. But at the moment I have the feeling we postpone the integration of too much too long. If the release is postponed until july I'd vote for integrating it now and iron it out. Otherwise it might be never integrated and that is our poor history of good projects dying because. my 2 cents, Norbert
Yes but resources are still sparse. I'm usually arguing the same way like you. But at the moment I have the feeling we postpone the integration of too much too long. If the release is postponed until july I'd vote for integrating it now and iron it out. Otherwise it might be never integrated and that is our poor history of good projects dying because. my 2 cents, Norbert +1 Stef
Stephan Eggermont wrote
The current implementation
+1. It is really bad, especially for new users, that we've let it go on this long. It should have been fixed and backported to 3.0. ----- Cheers, Sean -- View this message in context: http://forum.world.st/recover-lost-changes-tp4804929p4805140.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
On 11 Feb 2015, at 16:31, Sean P. DeNigris <sean@clipperadams.com> wrote:
Stephan Eggermont wrote
The current implementation
+1. It is really bad, especially for new users, that we've let it go on this long. It should have been fixed and backported to 3.0.
The issue is here: https://pharo.fogbugz.com/f/cases/13290/Recover-lost-changes-doesn-t-recover... <https://pharo.fogbugz.com/f/cases/13290/Recover-lost-changes-doesn-t-recover...> Marcus
Marcus Denker-4 wrote
The issue is here
And the solution is right there in the comment! Pharo Issue Tracker wrote
ChangesLog default is not registered for the SystemAnnouncer. Reinitializing it should help: ChangesLog reset;default.
Works on both 3.0 and 4.0. I made a parent issue 14916 and an issue for 4.0 14918 (13290 was about 3.0). ----- Cheers, Sean -- View this message in context: http://forum.world.st/recover-lost-changes-tp4804929p4805160.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
Can I get the link to this change set. On Wed, Feb 11, 2015 at 10:05 PM, Sean P. DeNigris <sean@clipperadams.com> wrote:
Marcus Denker-4 wrote
The issue is here
And the solution is right there in the comment!
Pharo Issue Tracker wrote
ChangesLog default is not registered for the SystemAnnouncer. Reinitializing it should help: ChangesLog reset;default.
Works on both 3.0 and 4.0. I made a parent issue 14916 and an issue for 4.0 14918 (13290 was about 3.0).
----- Cheers, Sean -- View this message in context: http://forum.world.st/recover-lost-changes-tp4804929p4805160.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
Is Epicea able to run parallel with the exiting changes framework, do we have to rip the latter out first? cheers -ben On Thu, Feb 12, 2015 at 10:38 PM, S Krish <krishnamachari.sudhakar@gmail.com
wrote:
Can I get the link to this change set.
On Wed, Feb 11, 2015 at 10:05 PM, Sean P. DeNigris <sean@clipperadams.com> wrote:
Marcus Denker-4 wrote
The issue is here
And the solution is right there in the comment!
Pharo Issue Tracker wrote
ChangesLog default is not registered for the SystemAnnouncer. Reinitializing it should help: ChangesLog reset;default.
Works on both 3.0 and 4.0. I made a parent issue 14916 and an issue for 4.0 14918 (13290 was about 3.0).
----- Cheers, Sean -- View this message in context: http://forum.world.st/recover-lost-changes-tp4804929p4805160.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
On 12 Feb 2015, at 17:36, Ben Coman <btc@openInWorld.com> wrote:
Is Epicea able to run parallel with the exiting changes framework, do we have to rip the latter out first?
I works in parallel now. The idea is to remove the other mechanism in a second step. Marcus
So is the plan to integrate Epicea for Pharo 4 Release as the default mechanism, and leave removal of the existing mechanism until Pharo 5? cheers -ben On Fri, Feb 13, 2015 at 12:44 AM, Marcus Denker <marcus.denker@inria.fr> wrote:
On 12 Feb 2015, at 17:36, Ben Coman <btc@openInWorld.com> wrote:
Is Epicea able to run parallel with the exiting changes framework, do we have to rip the latter out first?
I works in parallel now. The idea is to remove the other mechanism in a second step.
Marcus
no. in the best case it will be in pharo4 as preview. (to remove/disable the old mechanism is going to take more time and complicationsâ¦) cheers, Esteban
On 12 Feb 2015, at 18:07, Ben Coman <btc@openInWorld.com> wrote:
So is the plan to integrate Epicea for Pharo 4 Release as the default mechanism, and leave removal of the existing mechanism until Pharo 5? cheers -ben
On Fri, Feb 13, 2015 at 12:44 AM, Marcus Denker <marcus.denker@inria.fr <mailto:marcus.denker@inria.fr>> wrote:
On 12 Feb 2015, at 17:36, Ben Coman <btc@openInWorld.com> wrote:
Is Epicea able to run parallel with the exiting changes framework, do we have to rip the latter out first?
I works in parallel now. The idea is to remove the other mechanism in a second step.
Marcus
On Fri, Feb 13, 2015 at 2:30 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote:
no. in the best case it will be in pharo4 as preview. (to remove/disable the old mechanism is going to take more time and complicationsâ¦)
Isn't that what I said? :) Since both are tools selected from the method, they would really be on equal footing wrt priority. cheers -ben
On 12 Feb 2015, at 18:07, Ben Coman <btc@openInWorld.com> wrote:
So is the plan to integrate Epicea for Pharo 4 Release as the default mechanism, and leave removal of the existing mechanism until Pharo 5? cheers -ben
On Fri, Feb 13, 2015 at 12:44 AM, Marcus Denker <marcus.denker@inria.fr> wrote:
On 12 Feb 2015, at 17:36, Ben Coman <btc@openInWorld.com> wrote:
Is Epicea able to run parallel with the exiting changes framework, do we have to rip the latter out first?
I works in parallel now. The idea is to remove the other mechanism in a second step.
Marcus
S Krish wrote
Can I get the link to this change set.
Which change set? You just have to DoIt: "ChangesLog reset;default" ----- Cheers, Sean -- View this message in context: http://forum.world.st/recover-lost-changes-tp4804929p4805417.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
Le 11/2/15 09:33, Stephan Eggermont a écrit :
Norbert wrote:
Am 10.02.2015 um 20:59 schrieb stepharo <[hidden email]>:
Yes this should be fixed.
You mean fix the current implementation or swap it for epicea? The current implementation.
Yes
It is a significant barrier to entry for new smalltalkers and gives a very bad impression. The epicea swap is a high-impact change, that is likely to affect stability for some time.
No it is stable. We postponed it because martin was doing override in MC instead of adding notification to MC and registering to them. It will be fixed. Stef
Stephan
participants (8)
-
Ben Coman -
Esteban Lorenzano -
Marcus Denker -
Norbert Hartl -
S Krish -
Sean P. DeNigris -
Stephan Eggermont -
stepharo