- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Trip to Pharo land
by GÃ¶ran Krampe May 31, 2010

May 31, 2010

Hi! CCing Pharo list, this was regarding: http://goran.krampe.se/blog/Squeak/eblankett-dev.rdoc On 05/30/2010 12:00 PM, Stephan Eggermont wrote: > Hello GÃ¶ran, > > Is there a special reason you tried Pharo 1.0? Your improvements are of Nope, just (wrongly I agree) thought it was fairly up to date since it was just released. But you are right, depending on release process that does indeed not necessarily correlate. > course > in 1.1. Feature freeze for 1.0 was long ago. If you're willing to use > the bleeding edge > in squeak, why not do it in pharo too? Again, not a conscious choice. I can use bleeding edge in Pharo too, is there an easy place to start? Earlier I used some core + Renggli scripts to get a decent image. > Which peek bugfix is in Squeak? The 2010-1-13 solution is wrong. > See http://code.google.com/p/pharo/issues/detail?id=1813. I will check it out, gotta work on the house now :) > Groetjes, > Stephan Eggermont Thanks for the feedback, GÃ¶ran

6 16

[Pharo-project] Change Author full name prompt text in PharoCore 1.1
by Miguel Enrique CobÃ¡ Martinez May 31, 2010

May 31, 2010

I have changed the text of the message prompt and the text of the setting for author full name in PharoCore 1.1 so that is similar (shorter) to the text of PharoCore 1.0. Issue: http://code.google.com/p/pharo/issues/detail?id=2491 fixed in PharoInbox in: SLICE-rewriteAuthorMessageText-MiguelCoba.2 Ready for verification and integration. Cheers -- Miguel CobÃ¡ http://miguel.leugim.com.mx

2 1

[Pharo-project] [update 1.1] #11380
by StÃ©phane Ducasse May 30, 2010

May 30, 2010

11380 ----- - Issue 2484: Verify Number of FFI argument. Squeak trunk - Issue 2486: Pixel values for depth 32 is off for some colors. Thanks Henrik. - Issue 2337: Fix decompilation not to truncate very long decompiled methods. - Issue 2449: Help Browser should provide task bar icon - Issue 2470: runSimulated behaviour fixed. Tx eliot I recompile the complete image and got no problem so far. STef

1 0

Re: [Pharo-project] how to add an entry in World Menu (was: CommandShell)
by laurent laffont May 30, 2010

May 30, 2010

See http://book.pharo-project.org/book/TipsAndTricks/WorldMenuRegistration Can someone write a little example on how to add Settings ? I need this :) <http://book.pharo-project.org/book/TipsAndTricks/WorldMenuRegistration> Cheers, Laurent On Thu, May 27, 2010 at 9:56 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > On Thu, May 27, 2010 at 4:45 PM, David T. Lewis <lewis(a)mail.msen.com>wrote: > >> On Thu, May 27, 2010 at 09:04:37AM +0200, laurent laffont wrote: >> > Hi Dave, >> > >> > I've managed to make it running in Pharo (remove all isMorphic ifFalse >> ... >> > stuff, change menu registration, a little work is needed to adapt to >> Pharo >> > new settings system). It works (I can publish a package when back at >> home). >> > >> > Now I suppose you want to keep it running on Squeak, I don't know how to >> > handle differences on world menu and preferences. >> > >> > For the MVC part, is there some value in keeping it ? >> >> Hi Laurent, >> >> Thanks, I would be very interested in seeing your changes, especially the >> menu registration fixes. >> > > For menu registration, add > > CommandShell class>>#menuCommandOn: aBuilder > <worldMenu> > (aBuilder item: #'Command Shell') > parent: #Tools; > action:[self open]; > help: 'Smalltalk simulation of a Unix command shell '. > > and comment / remove Preferences in CommandShell class>>#initialize. > > > Laurent > > > >> >> I do want to keep this working on MVC and on other Squeak images. What >> I really need to do is repackage CommandShell and OSProcess so that >> everything is not all in two giant packages. I originally "packaged" >> these many years ago before Squeak had real packages and Monticello, >> so I basically separated things into two completely separate SAR packages >> that could be independently maintained (even though CommandShell and >> OSProcess were intended to work together). That was quite a project >> at the time, but it is badly out of date now, so I need to go back >> and make this stuff work properly with Metacello configurations. >> >> Dave >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >

3 5

[Pharo-project] List of pending items for 1.1
by StÃ©phane Ducasse May 30, 2010

May 30, 2010

Hi all I did a fast list of items it would make sense to close for 1.1: Can you help us? I'm going over the issues and sort them - FFI/Alien? - http://code.google.com/p/pharo/issues/detail?id=2481 Issue 2481: Fix code gen infinite recursion - Issue 2446: Method lookup bug when evaluating code in a ParagraphEditor. http://code.google.com/p/pharo/issues/detail?id=2446 - Issue 2436: Compiler outofScopeNotification - Issue 2470: runSimulated behaviour http://code.google.com/p/pharo/issues/detail?id=2470 - Issue 1450: Displaying block content in inspector, debugger Stef

1 0

[Pharo-project] [update 1.1] #11379
by StÃ©phane Ducasse May 30, 2010

May 30, 2010

11379 ----- - Issue 1832: remove unnecessary halt or convert them into error Now as part of the integration process I will do a little Compiler recompileAll to see if we catch some problems with source. Stef

1 0

[Pharo-project] How do I install seaside in Pharo 1.0?
by magique poter May 30, 2010

May 30, 2010

Hello, I have problem installing Seaside on Pharo 1.0. Evaluate ConfigurationOfSeaside >> workspace did not work. I have also tryed this code: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside'; load. ((Smalltalk at: #ConfigurationOfSeaside ) project latestVersion) load it did not work to. Why does the code DEVImageWorkspaces openExternalProjectWorkspace did not show an easy way to install Seaside (it was the case before)? Cordialy

2 3

[Pharo-project] trait composition conflict autoresolution
by aizcorbe May 30, 2010

May 30, 2010

Hi all, I'm doing some work with traits, and I found something like this case: Trait T1>>m1 ^self requirement Trait T2>>m1 doSomeStuff Class C1 uses: T1 + T2 [note, i'm not excluding m1 from T1 in the T1 + T2 composition.] And the resulting: C1>>m1 doSomeStuff It is just ok, since the other m1 is just a mark for a requiredMethod, but I find this a little weird, since do not follow the Trait definition. (at least the one I read, maybe it changed!). Wouldn't be better to automatically add the exclusion at the composition? Class C1 uses: T1 - {#m1} + T2 In this way the definition would be followed without any exception (and it will be explicit with what is going on). This is just a suggestion, anyway it works great! btw... why there are two requirement marks?: Object>>requirement self error: 'Implicitly required method' Object>>explicitRequirement self error: 'Explicitly required method' the question is, if I use #requirement, I'm explicitly requiring that method. Is there any situation where I should use #requirement? Cheers -- View this message in context: http://forum.world.st/trait-composition-conflict-autoresolution-tp2235790p2… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 3

[Pharo-project] [ANN] Camp Smalltalk London filling up
by Julian Fitzell May 29, 2010

May 29, 2010

Much to our delight, there seems to be a lot of interest in the Camp Smalltalk event in London. We originally estimated our capacity at 30, and those slots have already filled up in less than 4 days! We are just now discussing what our actual maximum capacity is. We'll be able to handle a few more people, we're just now sure yet how many. So if you're interested in coming and haven't signed up yet, please head over to cslondon2010.eventbrite.com and add yourself to the waiting list. That will really help us understand how many more people still want to attend. Note that joining the waiting list does not commit you to attending, so if you're still on the fence, you might want to sign yourself up anyway. We'll open up some more spots next week and then see how it goes. Thanks for your enthusiastic participation! Julian

1 0

May 29, 2010

11378 ----- - Issue2458: ChooseColorDefaults - Issue 2182: Part one. http://code.google.com/p/pharo/issues/detail?id=2182 This slice adds a class ObsoleteTest that tests the various flavor of isObsolete (on classes, metaclasses and traits). Furthermore, it adds some very useful methods: Trait class>>named:, Class>>subclass:uses:

1 0