>
> >
> > right now is saving all the changes to the log. I saw something
> > about doit silent but I do not understand why a change should not be
> > save, why is that?
>
> because sometimes you want to install code without polluting the
> changes set
>        - halt
>        - breakpoint
>        and all kinds of trickery


I did not change anything of that. This fix saves class definition changes
(like add a variable, change a class category, rename a class, etc) and
method categorization changes. I did not modify anything related to changing
methods so this should work as before.
Now, about polluting the changes file (no the changes set, I think they are
two different things) I would not be so conservative, I mean disk space is
not a big issue now don't you think?
I think it is better to save all the necessary info in the changes file to
get back to what you have before a hang. That is how VisualWorks and
VisualAge works.


>
>
>  > I needed this fix becuase I lost a lot of work because pharo hanged
> > on me many times...
>
> argh. Let us know if you can reproduce that.
> I think that we changed a lot and pharo 1.0 may be less stable than
> Squeak3.9


yes, I did. Some were related to MouseOverHandler (I uploaded a new version
of that class to the pharo-inbox too), others to the inputsensor change.
But it is ok, I understand that pharo is getting better and it takes time to
have an stable system.

Bye,
Hernan.


> >
> >
> > Stef
> > >
> > > Bye,
> > > Hernan.
> > >
> > >
> > > _______________________________________________
> > > Pharo-project mailing list
> > > [email protected]
> > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> >
> >
> > _______________________________________________
> > Pharo-project mailing list
> > [email protected]
> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> >
> > _______________________________________________
> > Pharo-project mailing list
> > [email protected]
> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to