- Pharo-dev - lists.pharo.org

Re: [Pharo-project] petitparser
by Tudor Girba March 11, 2011

March 11, 2011

Hi, The slides I used for today's tutorial on PetitParser can be found here: http://www.slideshare.net/girba/petitparser-at-the-deep-into-smalltalk-scho… Cheers, Doru On 10 Mar 2011, at 12:39, Tudor Girba wrote: > Hi, > > To participate in the PetitParser tutorial to take place this afternoon at the Deep into Smalltalk school, you should: > - find one or two partners to code with, and > - download the latest Moose image containing PetitParser: > http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/… > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Value is always contextual." > > > -- www.tudorgirba.com "What is more important: To be happy, or to make happy?"

2 2

Re: [Pharo-project] petitparser
by Tudor Girba March 10, 2011

March 10, 2011

Hi, The slides I used for today's tutorial on PetitParser can be found here: http://www.slideshare.net/girba/petitparser-at-the-deep-into-smalltalk-scho… Cheers, Doru On 10 Mar 2011, at 12:39, Tudor Girba wrote: > Hi, > > To participate in the PetitParser tutorial to take place this afternoon at the Deep into Smalltalk school, you should: > - find one or two partners to code with, and > - download the latest Moose image containing PetitParser: > http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/… > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Value is always contextual." > > > -- www.tudorgirba.com "What is more important: To be happy, or to make happy?"

1 0

[Pharo-project] [COTDC] 28 - ImmAbstractPlatform
by laurent laffont March 10, 2011

March 10, 2011

Today: ImmAbstractPlatform Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

2 4

Re: [Pharo-project] Pharo compiler
by Marcus Denker March 10, 2011

March 10, 2011

On Mar 10, 2011, at 2:37 PM, Alexandre Bergel wrote: > Hi Folks! > > What are the different optimizations Pharo compiler offers? Is there more than a mere message inlining (class, ifTrue:ifFalse:, timesRepeat:, to:do:) ? > As Pharo uses right now the standard or Squeak compiler, this is exactly the same. (And this will be true for the new one, too). MessageNode>>#initialize has: MacroSelectors := #( ifTrue: ifFalse: ifTrue:ifFalse: ifFalse:ifTrue: and: or: whileFalse: whileTrue: whileFalse whileTrue to:do: to:by:do: caseOf: caseOf:otherwise: ifNil: ifNotNil: ifNil:ifNotNil: ifNotNil:ifNil:). What else do you mean? There is of course the special bytecode (send plus...) Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

[Pharo-project] Issue 3796 in pharo: Remove '.pr' references
by pharo＠googlecode.com March 10, 2011

March 10, 2011

Status: Fixed Owner: stephane...(a)gmail.com Labels: Milestone-1.3 New issue 3796 by stephane...(a)gmail.com: Remove '.pr' references http://code.google.com/p/pharo/issues/detail?id=3796 directoryNames | dirNames projectNames entries | "Return a collection of names for the subdirectories of this directory but filter out project directories." entries := self entries. dirNames := (entries select: [:entry | entry isDirectory]) collect: [:entry | entry name]. projectNames := Set new. entries do: [:entry | ((entry isDirectory) not and: ['*.pr' match: entry name]) ifTrue: [projectNames add: (entry name copyFrom: 1 to: entry name size-3)]]. ^dirNames reject: [:each | projectNames includes: each] => directoryNames "Return a collection of names for the subdirectories of this directory." ^ (self entries select: [:entry | entry isDirectory]) collect: [:entry | entry name].

1 1

[Pharo-project] Issue 3728 in pharo: Changed MenuMorph references to go through UIManager default menuClass
by pharo＠googlecode.com March 10, 2011

March 10, 2011

Status: New Owner: ---- New issue 3728 by fernando...(a)gmail.com: Changed MenuMorph references to go through UIManager default menuClass http://code.google.com/p/pharo/issues/detail?id=3728 the attached changeset replaces all the refs to the class MenuMorph by the usage of UIManager default menuClass. 9 uses remain, mostly due to #isKindOf: senders. Attachments: menuMorphReferences.1.cs 51.7 KB

1 15

[Pharo-project] New widget
by Benjamin March 10, 2011

March 10, 2011

Hello everyone, I've done a new Morphic widget, that allow to easily switch from a categorized view to a "all elements" view (quite hard to explain, let me give you an example ^^) Gofer new squeaksource: 'SwitchableTreeWidget'; package: 'SwitchableTreeWidget'; load. SwitchableCategoriesTreeExample new openInWorld. If you click on the button or just double click on the tree, you will switch the view :) I wrote that widget to integrate it in a new browser (and if I succeed, to create a new Glamour widget) Thanks in for your feedback :) Ben

5 7

[Pharo-project] Pharo compiler
by Alexandre Bergel March 10, 2011

March 10, 2011

Hi Folks! What are the different optimizations Pharo compiler offers? Is there more than a mere message inlining (class, ifTrue:ifFalse:, timesRepeat:, to:do:) ? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

[Pharo-project] Issue 3802 in pharo: A strange superclasses if Canvas
by pharo＠googlecode.com March 10, 2011

March 10, 2011

Status: Accepted Owner: siguc...(a)gmail.com New issue 3802 by siguc...(a)gmail.com: A strange superclasses if Canvas http://code.google.com/p/pharo/issues/detail?id=3802 Imagine that you can do something like: Object new drawOnCanvas: World assuredCanvas no, don't imagine. You can do that! :) At least it is supposed to work, because Canvas inherits from some strange things (NullEncoder, FlattenEncoder), so you can actually instruct any object to draw itself on canvas.. which is makes some sense (sort of): Canvas>>draw: anObject ^anObject drawOn: self Object>>drawOnCanvas:aStream self flattenOnStream:aStream. But as to me, Object should NOT implement #drawOnCanvas:, nor #drawOn:. Period. The real users of protocols placed in NullEncoder and FlattenEncoder is PostscriptCanvas which are not included into core images. So, the proposal is to remove the extra noise by making Canvas to be the subclass of Object. And for things which do care about serializing drawing commands onto some stream (like PostScriptCanvas do), make a subclass and introduce this behavior later.

1 0

Re: [Pharo-project] Issue 3801 in pharo: FSystemNavigation>>#methodHierarchyBrowserForClass
by pharo＠googlecode.com March 10, 2011

March 10, 2011

Updates: Summary: FSystemNavigation>>#methodHierarchyBrowserForClass Status: Accepted Comment #1 on issue 3801 by Benjamin...(a)gmail.com: FSystemNavigation>>#methodHierarchyBrowserForClass http://code.google.com/p/pharo/issues/detail?id=3801 Yep, but it come from SystemNavigation ... SystemNavigation default methodHierarchyBrowserForClass: Boolean selector: #ifTrue:.

1 0