Smalltalk › Pharo › Pharo Smalltalk Developers

Help needed with case 19236

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

6 messages Options

Denis Kudriashov

Help needed with case 19236

Hi all.

We need help how to better manage issue 19236.

Generally: we have class Tab which is morph related to tabs widget. It conflicts with key mapping class variable and some similar stuff from Xtreams.

So this issue made rename of morph classes from tabs widget to add them ~Morph suffix.

I think it is good change. But it leads to incompatibility for old images. So any tools which use tabs will be not working in Pharo6.

How to better manage this problem? Could we integrate this change?

stepharo

Re: Help needed with case 19236

Hi all.

We need help how to better manage issue 19236.

Generally: we have class Tab which is morph related to tabs widget. It conflicts with key mapping class variable and some similar stuff from Xtreams.

So this issue made rename of morph classes from tabs widget to add them ~Morph suffix.

I think it is good change.

But it leads to incompatibility for old images.

If people use Spec and we update spec = no problem :)

So any tools which use tabs will be not working in Pharo6.

How to better manage this problem? Could we integrate this change?

Class renaming without keeping the old name is difficult.
What we did with gustavos was more for deprecating.

stef

Nicolas Cellier

Re: Help needed with case 19236

2016-11-02 20:03 GMT+01:00 stepharo <[hidden email]>:

Hi all.

We need help how to better manage issue 19236.

Generally: we have class Tab which is morph related to tabs widget. It conflicts with key mapping class variable and some similar stuff from Xtreams.

So this issue made rename of morph classes from tabs widget to add them ~Morph suffix.

I think it is good change.

+1

But it leads to incompatibility for old images.

If people use Spec and we update spec = no problem :)

So any tools which use tabs will be not working in Pharo6.

How to better manage this problem? Could we integrate this change?

Class renaming without keeping the old name is difficult.
What we did with gustavos was more for deprecating.

stef

Undeclared at: #Tab put: TabMorph ? Just for a transition period...

kilon.alios

Re: Help needed with case 19236

well Tab is a terrible name for a class anyway. Says nothing about the class itself.

Denis Kudriashov

Re: Help needed with case 19236

In reply to this post by stepharo

2016-11-02 20:03 GMT+01:00 stepharo <[hidden email]>:

But it leads to incompatibility for old images.

If people use Spec and we update spec = no problem :)

Yes Spec is updated by this.

And now it is fix to include

stepharo

Re: Help needed with case 19236

Super cool.

Stef

Le 3/11/16 à 13:26, Denis Kudriashov a écrit :

2016-11-02 20:03 GMT+01:00 stepharo <[hidden email]>:

But it leads to incompatibility for old images.

If people use Spec and we update spec = no problem :)

Yes Spec is updated by this.

And now it is fix to include