March 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.3] #13094

by StÃ©phane Ducasse

13094 ----- - Issue 3792: PluggableListMorph with a wrapper for display. Thanks Benjamin van Ryseghem. S.

March 18, 2011

Re: [Pharo-project] Issue 3792 in pharo: PluggableListMorph with a wrapper for display

by pharo＠googlecode.com

Updates: Status: Closed Comment #4 on issue 3792 by stephane...(a)gmail.com: PluggableListMorph with a wrapper for display http://code.google.com/p/pharo/issues/detail?id=3792 in 13094

March 18, 2011

Re: [Pharo-project] [ANN 1.2] prebuilt core 1.2 final

by StÃ©phane Ducasse

lukas Can you tell us where? What method is doing a problem? The point of simpleMorphic is that there is a value in it and if we do not give a chance to people to have a look at it then the money spent by esug is lost (of course esug was not paying for simpleMorphic but this is like that). Stef On Mar 18, 2011, at 7:07 AM, Lukas Renggli wrote: > Ahh, looks like SimpleMorphic has some (probably unintentional) > overrides of core methods. Unloading the package pretty much breaks > everything :-( > > Lukas > > On 18 March 2011 07:02, Lukas Renggli <renggli(a)gmail.com> wrote: >>> Very good! We then can release the 1.2 Full soon, too. >>> I wonder if we should adopt your OB codebase for that? Or do >>> we wait for 1.2.1? >> >> I would wait a bit. I noticed that the debugger is quite broken. I >> only get the pre-debug window, but clicking on any button opens >> another pre-debug window. I don't have time to investigate, is this >> also in core or some side-effect of loading/unloading packages? The >> method #topView seems to be missing. >> >> Lukas >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch >

March 18, 2011

Re: [Pharo-project] Porting Visual Works to Pharo

by Schwab,Wilhelm K

I have used SIF to move a lot of code from Dolphin to Pharo. Attached is the most recent version I have seen. In some cases, I heavily edited the .sif (text) after export and before import. Be sure to make backups and go for it. ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Guillermo Polito [guillermopolito(a)gmail.com] Sent: Thursday, March 17, 2011 10:30 PM To: Pharo Development Subject: [Pharo-project] Porting Visual Works to Pharo Maybe this question is out of the scope of this list, but probably someone can help :). As described in some threads, I want to use what's described in: http://scg.unibe.ch/wiki/howtos/portingfromvisualworkstosqueak But when I try to load FileOut30 It doesn't load the Squeak Compatibility classes because it seems I lack the refactoring browser. I've already tried to load some Refactoring Browser from different stores, but it screws my image :). I'm using the community edition of Visual works in windowze. Can someone point me in the right direction? (Let's say I'm not very used to VisualWorks) Thanks! Guille

March 18, 2011

Re: [Pharo-project] [ANN 1.2] prebuilt core 1.2 final

by StÃ©phane Ducasse

Lukas Marcus is RIGHT. How can we make progress without adding temporarily new libraries and migrating? How can we make progress if people do not use the release candidate phase as it should be? Tell me because we are all ears opened. Stef >> I would not unload packaged. >> >> Everything not tested is broken, and so if you do things like that I am >> sure you will have problems. >> >> And nobody ever unloaded anything from Core. > > You must be joking right? In the mission you say "stable and small > core", but the numbers say something entirely different: PharoCore 1.0 > is 11 MB, PharoCore 1.1 is 14 MB, PharoCore 1.2 is 16 MB. I mentioned > it before in this list, but I already had to unload stuff in PharoCore > 1.1. Honestly, I don't really see the point of a PharoCore image if it > contains more and more not unloadable non-core code. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch >

March 18, 2011

Re: [Pharo-project] [ANN 1.2] prebuilt core 1.2 final

by StÃ©phane Ducasse

+1 > > I would not unload packaged. >>> >>> Everything not tested is broken, and so if you do things like that I am >>> sure you will have problems. >>> >>> And nobody ever unloaded anything from Core. >> >> You must be joking right? In the mission you say "stable and small >> core", but the numbers say something entirely different: PharoCore 1.0 >> is 11 MB, PharoCore 1.1 is 14 MB, PharoCore 1.2 is 16 MB. I mentioned >> it before in this list, but I already had to unload stuff in PharoCore >> 1.1. Honestly, I don't really see the point of a PharoCore image if it >> contains more and more not unloadable non-core code. >> > Size of the image comes in part from ever growing MC history. The only > other big thing should be the Minimal Morphic code, which is in there > temporarily. > > Else: People are welcome to help. > > We do what we do and then we do a release even if it is imperfect. > Perfection is death, and delaying the release forever "because we could do better" > will not mean that we do better, just that we don't release ever. > > Pharo 1.2 is *not* a goal in itself. It is just a snapshot on the way to a goal. Therefore > it's just a mess that is tested for some month so it does not have any obvious bugs. > Nothing else. > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

March 18, 2011

Re: [Pharo-project] [ANN 1.2] prebuilt core 1.2 final

by Marcus Denker

On Mar 18, 2011, at 8:24 AM, Marcus Denker wrote: > > On Mar 18, 2011, at 8:16 AM, Lukas Renggli wrote: > >>> I would not unload packaged. >>> >>> Everything not tested is broken, and so if you do things like that I am >>> sure you will have problems. >>> >>> And nobody ever unloaded anything from Core. >> >> You must be joking right? In the mission you say "stable and small >> core", but the numbers say something entirely different: PharoCore 1.0 >> is 11 MB, PharoCore 1.1 is 14 MB, PharoCore 1.2 is 16 MB. I mentioned >> it before in this list, but I already had to unload stuff in PharoCore >> 1.1. Honestly, I don't really see the point of a PharoCore image if it >> contains more and more not unloadable non-core code. >> > Size of the image comes in part from ever growing MC history. 1.2 Core is 15.6MB MCVersionInfo allInstances do: [ :each | each instVarNamed: 'ancestors' put: nil ]. --> 11.8 MB Delete ScriptLoader class in addition: --> 9.8MB Starting with 1.2Core, doing ScriptLoader new cleanUpForProduction --> 7.5 MB (With MinimalMorphic) So it's not that bad. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 18, 2011

Re: [Pharo-project] [ANN 1.2] prebuilt core 1.2 final

by Marcus Denker

On Mar 18, 2011, at 8:16 AM, Lukas Renggli wrote: >> I would not unload packaged. >> >> Everything not tested is broken, and so if you do things like that I am >> sure you will have problems. >> >> And nobody ever unloaded anything from Core. > > You must be joking right? In the mission you say "stable and small > core", but the numbers say something entirely different: PharoCore 1.0 > is 11 MB, PharoCore 1.1 is 14 MB, PharoCore 1.2 is 16 MB. I mentioned > it before in this list, but I already had to unload stuff in PharoCore > 1.1. Honestly, I don't really see the point of a PharoCore image if it > contains more and more not unloadable non-core code. > Size of the image comes in part from ever growing MC history. The only other big thing should be the Minimal Morphic code, which is in there temporarily. Else: People are welcome to help. We do what we do and then we do a release even if it is imperfect. Perfection is death, and delaying the release forever "because we could do better" will not mean that we do better, just that we don't release ever. Pharo 1.2 is *not* a goal in itself. It is just a snapshot on the way to a goal. Therefore it's just a mess that is tested for some month so it does not have any obvious bugs. Nothing else. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 18, 2011

Re: [Pharo-project] [COTDC] - 33 StrikeFontSet

by laurent laffont

On Fri, Mar 18, 2011 at 8:05 AM, Henrik Sperre Johansen < henrik.s.johansen(a)veloxit.no> wrote: > On 18.03.2011 08:03, Henrik Sperre Johansen wrote: > >> On 18.03.2011 07:48, laurent laffont wrote: >> >>> Nobody know this stuff ? >>> >>> Laurent >>> >> >> Know it? Sort of. >> Enough to not write a correct comment? Getting there would probably induce >> extreme frustration in the process, which I in no way need. >> Sorry. >> >> Cheers, >> Henry >> >> Maybe: > "This is not something you will understand completely just by looking at > the code for 30+ minutes" :) > I spent 10 mn only ... big class ... :( Laurent > > Cheers, > Henry > >

March 18, 2011

Re: [Pharo-project] [ANN 1.2] prebuilt core 1.2 final

by Lukas Renggli

> I would not unload packaged. > > Everything not tested is broken, and so if you do things like that I am > sure you will have problems. > > And nobody ever unloaded anything from Core. You must be joking right? In the mission you say "stable and small core", but the numbers say something entirely different: PharoCore 1.0 is 11 MB, PharoCore 1.1 is 14 MB, PharoCore 1.2 is 16 MB. I mentioned it before in this list, but I already had to unload stuff in PharoCore 1.1. Honestly, I don't really see the point of a PharoCore image if it contains more and more not unloadable non-core code. Lukas -- Lukas Renggli www.lukas-renggli.ch

March 18, 2011