yes we should have done that
On Dec 9, 2010, at 11:44 PM, Tudor Girba wrote:
I said it before: just give the variable a different name. For example,
textStyle. That would solve all loading problems.
Doru
On 9 Dec 2010, at 22:49, Stéphane Ducasse wrote:
Thanks all for your time.
We
Yes
I think that this is the pattern that we are applying for packageInfo for
example
I said it before: This doesn't solve anything at all. In fact it is
much easier to remove the variable and fork the code. Renaming causes
a ripple effect to lots of methods and makes it impossible to merge
so, concerning the new editor changes, I would like to help because this
messy situation is partly my fault.
would it be helpful if I rename current TextEditor as TextEditor2, (give
me another name please ...),
current SmalltalkEditor as SmalltalkEditor2 and reintroduce the previous
No, don't waste time on reverting. I almost got it working.
My comment was ment for the future :-)
Lukas
On 10 December 2010 13:02, Alain Plantec alain.plan...@free.fr wrote:
so, concerning the new editor changes, I would like to help because this
messy situation is partly my fault.
would it
I wonder why the old editor functionality was removed instead of being
deprecated until the next release like this is normally done?
It is extremely difficult to get any GUI related stuff ported, because
the packages cannot simply be loaded. One has to fix part of the
package in the old image,
Hi lukas,
sorry for your frustration, that I can easily understand
I do not remember.
There are some changes that when deprecated get in our way.
I still think that we need a refactoring deprecate methods because just doing
all of them
by hand is not possible.
I believe that we need to have the
Hi Lukas, all
I guess I'm the one who made all this bad changes.
So sorry, sorry sorry.
Maybe we can come back to the old one.
No problem for me.
I can make a slice in that direction.
But frankly, what a catastrophic mail for people who are trying
to make the system cleaner.
do you know how much
On Thu, 9 Dec 2010, Lukas Renggli wrote:
I wonder why the old editor functionality was removed instead of being
deprecated until the next release like this is normally done?
It is extremely difficult to get any GUI related stuff ported, because
the packages cannot simply be loaded. One has to
And shout is kinda working too... i tried hard on OB just for fun but had no
luck.. i think i'd got meta meta confused :)
I would love to dedicate more time to it, but currently i'm very bussy.
Cheers,
Francisco
On Thu, Dec 9, 2010 at 5:24 PM, Levente Uzonyi le...@elte.hu wrote:
On Thu, 9
I guess I'm the one who made all this bad changes.
So sorry, sorry sorry.
I don't think so.
Maybe we can come back to the old one.
No problem for me.
I think the main problem is that the new editor model (which I really
like) was merged directly into the existing editor morphs, so
Thanks all for your time.
We should try to do it better in the future.
We should also change and improve our tools for helping us being better.
Now something important is how can we move this style variable in a way that we
can move it and also avoid to break.
this is just an example: let us do
Ducasse
[stephane.duca...@inria.fr]
Sent: Thursday, December 09, 2010 4:49 PM
To: Pharo-project@lists.gforge.inria.fr
Subject: Re: [Pharo-project] Why was the old Editor Functionality Removed?
Thanks all for your time.
We should try to do it better in the future.
We should also change and improve
I said it before: just give the variable a different name. For example,
textStyle. That would solve all loading problems.
Doru
On 9 Dec 2010, at 22:49, Stéphane Ducasse wrote:
Thanks all for your time.
We should try to do it better in the future.
We should also change and improve our tools
On Thu, 9 Dec 2010, Lukas Renggli wrote:
I guess I'm the one who made all this bad changes.
So sorry, sorry sorry.
I don't think so.
Maybe we can come back to the old one.
No problem for me.
I think the main problem is that the new editor model (which I really
like) was merged directly
On Thu, Dec 9, 2010 at 10:32 PM, Lukas Renggli reng...@gmail.com wrote:
I guess I'm the one who made all this bad changes.
So sorry, sorry sorry.
I don't think so.
Maybe we can come back to the old one.
No problem for me.
I think the main problem is that the new editor model (which I
I said it before: just give the variable a different name. For example,
textStyle. That would solve all loading problems.
I said it before: This doesn't solve anything at all. In fact it is
much easier to remove the variable and fork the code. Renaming causes
a ripple effect to lots of methods
16 matches
Mail list logo