April 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] ConfigurationOfPharo

by Alexandre Bergel

Hi! I am curious to see how Pharo1.1 can be produced from Core1.1. I loaded ConfigurationOfPharo from MetacelloRepository, and evaluated in a workspace: ConfigurationOfPharo project This triggered many loads, to end with an error: 'Name not found: ArchiveViewer'. I removed the reference of ArchiveViewer in the baseline. I then had to do some modifications: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Getting Pharo 1.1 from PharoCore 1.1 - add <worldMenu> in: SHWorkspace class>>open - changed asSortedArray into "asArray sort" OBMetagraphBuilder>>execute () OBAllMethodCategoryNode>>methodReferences OBSelectorNode>>implementors OBMethodNode>>messageSelectors OBMethodNode>>implementorsOf: OBSelectorNode>>senders ORCommand>>instanceVariables - fix in OCompletionTable class>>initializeWithPackages (FillInTheBlank) NSAbstractDataStream class>>initialize (isInMemory) SHParserST80>>resolvePartial: (hasBindingThatBeginsWith: is not defined in SystemDictionary anymore) - Registration in the WorldMenu: In Moose PetitGUI MoosePanel -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= I would like to see Pharo1.1 Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 27, 2010

[Pharo-project] Fwd: [ANN] SwaLint Code Critics 2.0.0-beta.1 available

by StÃ©phane Ducasse

Begin forwarded message: > From: Tobias Pape <das.linux(a)gmx.de> > Date: April 27, 2010 2:57:08 PM GMT+02:00 > To: pharo-project-owner(a)lists.gforge.inria.fr > Subject: Re: [ANN] SwaLint Code Critics 2.0.0-beta.1 available > > Dear Mailinglist Admin. > > This post is an announcement of Software that works in pharo. > however, since pharo is not my main Development environment, > i did not subscribe to the pharo ML. Please allow this one post. > > So Long, > -Tobias > > Am 2010-04-27 um 14:47 schrieb pharo-project-owner(a)lists.gforge.inria.fr: > >> You are not allowed to post to this mailing list, and your message has >> been automatically rejected. If you think that your messages are >> being rejected in error, contact the mailing list owner at >> pharo-project-owner(a)lists.gforge.inria.fr. >> >> >> Von: Tobias Pape <Das.Linux(a)gmx.de> >> Datum: 27. April 2010 14:47:03 MESZ >> An: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org>, pharo-project(a)lists.gforge.inria.fr >> Betreff: [ANN] SwaLint Code Critics 2.0.0-beta.1 available >> >> >> Dear Smalltalkers, >> >> I'm pleased to announce that SwaLint, an extensible code critics tool, >> is available again, now working in Squeak >= 4.1 and Pharo >= 1.0. >> >> You can obtain SwaLint Code Critics 2.0.0-beta.1: >> â¢ Via SqueakMap >> â¢ By a Metacello Configuration at SwaLint on SqueakSource. >> >> The configuration is used by the SqueakMap installation, as well. >> You can use the SqueakMap-Script directly: >> http://map.squeak.org/accountbyid/50d39e2b-7bd5-472a-ac94-cd1572a0bbdc/file… >> >> The accompanying wiki is not yet available. >> >> If you have installed any of >> â¢ OB-Refactory, >> â¢ Seaside-Slime, >> â¢ Grease-Slime, >> SwaLint can automatically make use of them. >> Howerver, invocation of SwaLint from within a browser >> has not been a target yet. >> >> I'll happily answer your questions, if any. >> >> So Long, >> -Tobias >> > >

April 27, 2010

Re: [Pharo-project] How to copy some nice UI bits from Squeak4.1 (e.g. get rid of the fat buttons in OB)

by Henrik Johansen

On Apr 27, 2010, at 2:42 10PM, Tim Mackinnon wrote: > > Looking a bit closer - I have tried setting the System Font for Window Title - to be 10pt instead of 11 (and that looks a bit better to my mind). However - even when you do this, if you compare the title bar of a classes browser to the title bar of pharo (e.g. "Pharo 1.0 - Image") - you do notice that the classes browser has a few more pixels either side of the close/collapse/expand buttons as compared to the native pharo window. > > Thanks again. > > Tim I agree, for windows the button spacing should be independent of title height derived from font height. At the moment, it just happens to be just about right with a pt10 size font :) Would be nice if the title height also took button size into account actually, with a small font-size the title becomes too narrow to display the full height of the button. Cheers, Henry

April 27, 2010

Re: [Pharo-project] [Pharo-users] RB AST serialization

by StÃ©phane Ducasse

On Apr 27, 2010, at 2:33 PM, Lukas Renggli wrote: >> what theo d hondt told us a while ago is that pascal or oberon >> they did not store bytecode but compressed ast and it was shorter than bytecode > > Sounds strange (imagine if you have comments in your code). Are there > any references on this? No I know that marcus read some papers on slim binaries Stef > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 27, 2010

Re: [Pharo-project] [ANN] NativeBoost source released

by Henrik Johansen

On Apr 27, 2010, at 9:50 31AM, Igor Stasenko wrote: > Hello all, > > For all interesting parties, i made an initial release of NativeBoost > plugin as well as language-side code. > > You can find an installation instructions on > > http://code.google.com/p/nativeboost/wiki/Installation > > You can also can find a couple of other descriptions on same wiki. > > I need your feedback! :) > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > Hi Igor! Would it be possible to upload a "ready-made" VM/Image combo to the google project? I'd really like to try it out, but I'd rather spend my time on exploring how to use AsmJit and using the primitive, than building the plugin and making an image with the needed packages ;) Cheers, Henry

April 27, 2010

Re: [Pharo-project] How to copy some nice UI bits from Squeak4.1 (e.g. get rid of the fat buttons in OB)

by Tim Mackinnon

> I don't know, the size of the title bar either comes from the > currently selected theme or your font choice. There is no such thing > as "native size" in Squeak or Pharo. I think my term native size was confusing - I meant compared to the size of windows outside of squeak/pharo (or indeed the OSX window of Pharo itself). Looking a bit closer - I have tried setting the System Font for Window Title - to be 10pt instead of 11 (and that looks a bit better to my mind). However - even when you do this, if you compare the title bar of a classes browser to the title bar of pharo (e.g. "Pharo 1.0 - Image") - you do notice that the classes browser has a few more pixels either side of the close/collapse/expand buttons as compared to the native pharo window. Still - its a minor thing and it doesn't bother me so much now you have fixed the buttons (awesome!). I did get a spurious walkback saying that a some button didn't understand #enabled: - however I haven't been able to reproduce that yet, so it could have been me playing with trying to set button heights? Thanks again. Tim

April 27, 2010

Re: [Pharo-project] [Pharo-users] RB AST serialization

by Lukas Renggli

> what theo d hondt told us a while ago is that pascal or oberon > they did not store bytecode but compressed ast and it was shorter than bytecode Sounds strange (imagine if you have comments in your code). Are there any references on this? Lukas -- Lukas Renggli www.lukas-renggli.ch

April 27, 2010

Re: [Pharo-project] [Pharo-users] RB AST serialization

by StÃ©phane Ducasse

what theo d hondt told us a while ago is that pascal or oberon they did not store bytecode but compressed ast and it was shorter than bytecode Stef On Apr 27, 2010, at 1:44 PM, Lukas Renggli wrote: >> So what I want to explore is to have a very compact representations of ASTs, but one >> that does not lose information *and* that allows the AST to be annotated with non-textual >> objects even when it's compressed. > > Indeed, annotations (or properties) get lost when serializing an AST > as source code. However I doubt that a different encoding of the AST > as a string is any more efficient than just storing the (compressed) > original source code (see the tests of AstSerializer). Also having a > "custom pretty printer" and a "custom parser" makes it kind of > difficult to have code that cannot be represented with the standard > AST, as this is for example the case in Helvetia. > > What about storing the annotations (or properties) separate the the > source string and map them back to the AST after parsing? > > Lukas > > > > > > >> >> Marcus >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 27, 2010

Re: [Pharo-project] I would like to have this kind of tool in pharo

by StÃ©phane Ducasse

Yes this would a nice idea. Stef On Apr 27, 2010, at 12:28 PM, Serge Stinckwich wrote: > It's open source and based on Seaside, so not to difficult to have > something similar for pharo hosted at : http://doc.pharo-project.org/ > > On Tue, Apr 27, 2010 at 4:03 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> http://philemonworks.wordpress.com/2009/11/13/soek-goodies-st-exploring-ope… >> >> >> Stef >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Serge Stinckwich > UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam > Every DSL ends up being Smalltalk > http://doesnotunderstand.org/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 27, 2010

Re: [Pharo-project] [Pharo-users] RB AST serialization

by Lukas Renggli

> So what I want to explore is to have a very compact representations of ASTs, but one > that does not lose information *and* that allows the AST to be annotated with non-textual > objects even when it's compressed. Indeed, annotations (or properties) get lost when serializing an AST as source code. However I doubt that a different encoding of the AST as a string is any more efficient than just storing the (compressed) original source code (see the tests of AstSerializer). Also having a "custom pretty printer" and a "custom parser" makes it kind of difficult to have code that cannot be represented with the standard AST, as this is for example the case in Helvetia. What about storing the annotations (or properties) separate the the source string and map them back to the AST after parsing? Lukas > > Â Â Â Â Marcus > > -- > Marcus Denker Â -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

April 27, 2010