Is there a compatibility package for migrating Spec application from Pharo 6.1 to Pharo 7 ?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Is there a compatibility package for migrating Spec application from Pharo 6.1 to Pharo 7 ?

Julien
Hello,

In Pharo 7, Spec’s *Model classes were renamed following the pattern *Presenter, which is better.

The original classes names (*Model) are still usable but their usage is deprecated in Pharo 7.

I wonder if someone did a package for Pharo 6.1 that does the opposite: provide *Presenter classes in
Pharo 6.1 to allow to prepare applications for the migration to Pharo 7 *but* allowing to keep them compatible
with Pharo 6.1 until Pharo 7 is released (and eventually after...)? The implementation would be quite easy :
create an empty subclass using the pattern *Presenter for the name for each *Model class of spec.

Thanks in advance,

Julien

---
Julien Delplanque
Doctorant à l’Université de Lille
Bâtiment B 40, Avenue Halley 59650 Villeneuve d'Ascq
Numéro de téléphone: +333 59 35 86 40

Reply | Threaded
Open this post in threaded view
|

Re: Is there a compatibility package for migrating Spec application from Pharo 6.1 to Pharo 7 ?

Peter Uhnák
ComposableModel withAllSubclasses do: [ :cls | cls subclass: ((cls name withoutSuffix: 'Model'), 'Presenter') asSymbol ] + move all the classes in Undeclared package.

Haven't run it... but it should work more or less.

A backport might not be a bad idea.

Peter

On Wed, May 30, 2018 at 2:44 PM, Julien <[hidden email]> wrote:
Hello,

In Pharo 7, Spec’s *Model classes were renamed following the pattern *Presenter, which is better.

The original classes names (*Model) are still usable but their usage is deprecated in Pharo 7.

I wonder if someone did a package for Pharo 6.1 that does the opposite: provide *Presenter classes in
Pharo 6.1 to allow to prepare applications for the migration to Pharo 7 *but* allowing to keep them compatible
with Pharo 6.1 until Pharo 7 is released (and eventually after...)? The implementation would be quite easy :
create an empty subclass using the pattern *Presenter for the name for each *Model class of spec.

Thanks in advance,

Julien

---
Julien Delplanque
Doctorant à l’Université de Lille
Numéro de téléphone: +333 59 35 86 40


Reply | Threaded
Open this post in threaded view
|

Re: Is there a compatibility package for migrating Spec application from Pharo 6.1 to Pharo 7 ?

EstebanLM
https://github.com/pharo-contributions/Spec70Compatibility

On 30 May 2018, at 15:48, Peter Uhnák <[hidden email]> wrote:

ComposableModel withAllSubclasses do: [ :cls | cls subclass: ((cls name withoutSuffix: 'Model'), 'Presenter') asSymbol ] + move all the classes in Undeclared package.

Haven't run it... but it should work more or less.

A backport might not be a bad idea.

Peter

On Wed, May 30, 2018 at 2:44 PM, Julien <[hidden email]> wrote:
Hello,

In Pharo 7, Spec’s *Model classes were renamed following the pattern *Presenter, which is better.

The original classes names (*Model) are still usable but their usage is deprecated in Pharo 7.

I wonder if someone did a package for Pharo 6.1 that does the opposite: provide *Presenter classes in
Pharo 6.1 to allow to prepare applications for the migration to Pharo 7 *but* allowing to keep them compatible
with Pharo 6.1 until Pharo 7 is released (and eventually after...)? The implementation would be quite easy :
create an empty subclass using the pattern *Presenter for the name for each *Model class of spec.

Thanks in advance,

Julien

---
Julien Delplanque
Doctorant à l’Université de Lille
Numéro de téléphone: +333 59 35 86 40



Reply | Threaded
Open this post in threaded view
|

Re: Is there a compatibility package for migrating Spec application from Pharo 6.1 to Pharo 7 ?

Julien
Cool, this is what I was looking for.

Thanks.

Julien

---
Julien Delplanque
Doctorant à l’Université de Lille
Bâtiment B 40, Avenue Halley 59650 Villeneuve d'Ascq
Numéro de téléphone: +333 59 35 86 40

Le 30 mai 2018 à 15:59, Esteban Lorenzano <[hidden email]> a écrit :

https://github.com/pharo-contributions/Spec70Compatibility

On 30 May 2018, at 15:48, Peter Uhnák <[hidden email]> wrote:

ComposableModel withAllSubclasses do: [ :cls | cls subclass: ((cls name withoutSuffix: 'Model'), 'Presenter') asSymbol ] + move all the classes in Undeclared package.

Haven't run it... but it should work more or less.

A backport might not be a bad idea.

Peter

On Wed, May 30, 2018 at 2:44 PM, Julien <[hidden email]> wrote:
Hello,

In Pharo 7, Spec’s *Model classes were renamed following the pattern *Presenter, which is better.

The original classes names (*Model) are still usable but their usage is deprecated in Pharo 7.

I wonder if someone did a package for Pharo 6.1 that does the opposite: provide *Presenter classes in
Pharo 6.1 to allow to prepare applications for the migration to Pharo 7 *but* allowing to keep them compatible
with Pharo 6.1 until Pharo 7 is released (and eventually after...)? The implementation would be quite easy :
create an empty subclass using the pattern *Presenter for the name for each *Model class of spec.

Thanks in advance,

Julien

---
Julien Delplanque
Doctorant à l’Université de Lille
Numéro de téléphone: +333 59 35 86 40