Fwd: [Moose-dev] Re: ConfigurationOfMetacello and OB

Sorry, forgot to add the Pharo list ...

---------- Forwarded message ----------
From: Lukas Renggli <[hidden email]>
Date: 4 March 2010 20:13
Subject: Re: [Moose-dev] Re: ConfigurationOfMetacello and OB
To: Related to the development of Moose and other related tools
<[hidden email]>


I am looking into this. I reply to the Pharo list, I think the Moose
list is the wrong one.

The refactoring engine seems to work well. All tests pass.

OmniBrowser is more difficult. There are 7 tests failing, and there
are 8 errors.

There is a large number of deprecated code that OB is calling. What am
I supposed to do so that OB continues to work in Pharo 1.0 and 1.1?
Can I expect that people have the deprecated warnings disabled?

- How are menus registered? TheWorldMenu does not exist any longer.

- What is the replacement for #intialExtent?

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch



--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Also why are

  - Utilities changeStamp
  - Utilities timeStampForMethod:
  - SystemNavigation allMethodsNoDoitsSelect:

gone and what is their replacement?

All in all I noticed a huge performance boost. So this is really cool :-)

Lukas

On 4 March 2010 20:21, Lukas Renggli <[hidden email]> wrote:


--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

> I am looking into this. I reply to the Pharo list, I think the Moose
> list is the wrong one.

Indeed. Maybe a psy can tell why I always choose the wrong list.

> - How are menus registered? TheWorldMenu does not exist any longer.
>
> - What is the replacement for #intialExtent?

I also bump into this. I do not have a satisfactory solution however.

Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.






_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

>  - Utilities changeStamp
>  - Utilities timeStampForMethod:
>  - SystemNavigation allMethodsNoDoitsSelect:
>
> gone and what is their replacement?
>
> All in all I noticed a huge performance boost. So this is really  
> cool :-)

Indeed!

Alexandre

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.






_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

On 4 March 2010 20:27, Lukas Renggli <[hidden email]> wrote:
> Also why are
>
>  - Utilities changeStamp
>  - Utilities timeStampForMethod:
>  - SystemNavigation allMethodsNoDoitsSelect:
>
> gone and what is their replacement?

Ok, #allMethodsNoDoitsSelect: is easy to replace with
#allMethodsSelect: that works in Pharo 1.0 and 1.1 and should be ok,
because do-its are not added to a class any longer for quite a long
time.

The two methods #changeStamp and #timeStampForMethod: are however more
serious. They both break OB and the RB (however that is not covered by
tests) in subtle ways.

Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Lukas,

Doesn't this enter into the same territory that you are in with Seaside ... you are dealing with multiple platforms 1.0 and 1.1.

The code can to be partitioned into "platform-specific" and "common" packages or you can monkey-patch for one of the platforms (presumably 1.0 should be monkey patched) and then merge on a regular basis.

Metacello can be taught to distinguish between different Pharo versions, so the technicalities of having different sets of packages to load based on which version of Pharo you are running is straightforward (I do this for GemStone already).

Dale
----- "Lukas Renggli" <[hidden email]> wrote:

| Sorry, forgot to add the Pharo list ...
|
| ---------- Forwarded message ----------
| From: Lukas Renggli <[hidden email]>
| Date: 4 March 2010 20:13
| Subject: Re: [Moose-dev] Re: ConfigurationOfMetacello and OB
| To: Related to the development of Moose and other related tools
| <[hidden email]>
|
|
| I am looking into this. I reply to the Pharo list, I think the Moose
| list is the wrong one.
|
| The refactoring engine seems to work well. All tests pass.
|
| OmniBrowser is more difficult. There are 7 tests failing, and there
| are 8 errors.
|
| There is a large number of deprecated code that OB is calling. What
| am
| I supposed to do so that OB continues to work in Pharo 1.0 and 1.1?
| Can I expect that people have the deprecated warnings disabled?
|
| - How are menus registered? TheWorldMenu does not exist any longer.
|
| - What is the replacement for #intialExtent?
|
| Cheers,
| Lukas
|
| --
| Lukas Renggli
| http://www.lukas-renggli.ch
|
|
|
| --
| Lukas Renggli
| http://www.lukas-renggli.ch
|
| _______________________________________________
| Pharo-project mailing list
| [hidden email]
| http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

> Also why are
>
>  - Utilities changeStamp
>  - Utilities timeStampForMethod:

we forgot to deprecate them.... shame on us.
Probably in Date


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

>
> There is a large number of deprecated code that OB is calling. What am
> I supposed to do so that OB continues to work in Pharo 1.0 and 1.1?
> Can I expect that people have the deprecated warnings disabled?
>
> - How are menus registered? TheWorldMenu does not exist any longer.

alain will reply
have a look at the <worldmenu> pragma

menuCommandOn: aBuilder
        <worldMenu>
        (aBuilder group: #SystemChanges)
                parent: #CodeRecoveringTools;  
                with: [
                        (aBuilder item: #'Change Sorter')
                                action:[self new morphicWindow openInWorld];
                                icon: self taskbarIcon.
                        (aBuilder item: #'Recover lost changes...')
                                action: [ChangeList browseRecentLog]]

We should start writing a doc.

> - What is the replacement for #intialExtent?

defining it in the model ?

Stef

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

On Mar 4, 2010, at 8:27 PM, Lukas Renggli wrote:

> Also why are

Apparently looking at http://code.google.com/p/pharo/issues/detail?id=2015


>
>  - Utilities changeStamp

Author>>changeStamp

>  - Utilities timeStampForMethod:



StringHolder>>timeStamp

???

http://code.google.com/p/pharo/issues/detail?id=2110

>  - SystemNavigation allMethodsNoDoitsSelect:
>
> gone and what is their replacement?
>
> All in all I noticed a huge performance boost. So this is really cool :-)


I'm dead/exhausted going bed now.....pfff cloud of smoke stef disappear from office pffff reappear in bed....
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

El jue, 04-03-2010 a las 21:04 +0100, Stéphane Ducasse escribió:

> I'm dead/exhausted going bed now.....pfff cloud of smoke stef disappear from office pffff reappear in bed....

Hey, I want one of that instant-travel devices. Do they sell them on
Amazon? :)
--
Miguel Cobá
http://miguel.leugim.com.mx


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project