- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 2451 in pharo: Make Algernon work in Pharo 1.1.
by pharo＠googlecode.com Dec. 14, 2010

Dec. 14, 2010

Updates: Labels: -Milestone-1.1-DevImage Comment #6 on issue 2451 by marcus.denker: Make Algernon work in Pharo 1.1. http://code.google.com/p/pharo/issues/detail?id=2451 (No comment was entered for this change.)

1 0

[Pharo-project] Fwd: [Pharo-users] "Making ToolSet more flexible", any taker?
by Igor Stasenko Dec. 14, 2010

Dec. 14, 2010

On 14 December 2010 09:21, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Hi guys. I am out of time, but if someone wants to do a nice and not so > difficult contribution to Pharo, is to improve the ToolSet support. > > Issue is here: http://code.google.com/p/pharo/issues/detail?id=1915 > > And discussion is here: > http://forum.world.st/Questions-about-ToolSet-td1460544.html > Actually it's a much more older Â - 2 years http://lists.gforge.inria.fr/pipermail/pharo-project/2008-October/002872.ht… Here is what i proposed to this: http://www.mail-archive.com/pharo-project@lists.gforge.inria.fr/msg02869.ht… > Cheers > > Mariano > -- Best regards, Igor Stasenko AKA sig.

1 0

Re: [Pharo-project] Ring - model infrastructure for Pharo
by Marcus Denker Dec. 14, 2010

Dec. 14, 2010

On Dec 10, 2010, at 2:33 PM, Veronica Isabel Uquillas Gomez wrote: > Dear all, > > I am currently working on the Ring, an unifying and foundational model infrastructure for Pharo. > The goals are: > - Provide a common API at structural and runtime level > - Allow tools to interact and integrate directly with the host environment (Pharo) > - Support history analysis > > I started comparing the APIs of RB, MethodReference, Pseudo classes, MC, Smalltalk itself and Ginsu, as a basic to build the Ring. > So far I have implemented the main classes including the ones that should replace MethodReference and the Pseudo classes. > > An unified API will imply changes in most of the ones mentioned above (as most of them are non-polymorphic). > As a first step, I would like to have your opinion about the proposal for replacing MethodReference (attached file). > #stringVersionDefault has just one sender (#markMatchingClasses in SelectorBrowser). Do we need that? In general, #stringVersion in MethodReference seems to be strange... stringVersion: 'Class>>selector:' format why is there an iVar for this? Can't this just use the selector and class an build it? Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

4 3

[Pharo-project] "Making ToolSet more flexible", any taker?
by Mariano Martinez Peck Dec. 14, 2010

Dec. 14, 2010

Hi guys. I am out of time, but if someone wants to do a nice and not so difficult contribution to Pharo, is to improve the ToolSet support. Issue is here: http://code.google.com/p/pharo/issues/detail?id=1915 And discussion is here: http://forum.world.st/Questions-about-ToolSet-td1460544.html Cheers Mariano

1 0

Re: [Pharo-project] TODO for 1.2...
by Marcus Denker Dec. 14, 2010

Dec. 14, 2010

On Dec 14, 2010, at 2:35 AM, Guillermo Polito wrote: > Marcus, > > Here we have a "blue" build: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/11/ > How did you manage that? :P > Did you remove the test run from the build? > yes... I was wondering where exactly the process was failing (but then, one can see that fom the console)... Next step: remove the deprecated calls (or change deprecation warning setting) then I will turn on the tests again. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3411 in pharo: FileDIrectory - search methods - unnecessary code & unclear use of read only
by pharo＠googlecode.com Dec. 14, 2010

Dec. 14, 2010

Status: New Owner: ---- New issue 3411 by rhaw...@plymouth.ac.uk: FileDIrectory - search methods - unnecessary code & unclear use of read only http://code.google.com/p/pharo/issues/detail?id=3411 In FileDirectory, category 'search', the method: withAllFilesDo: fileStreamBlock andDirectoriesDo: directoryBlock - has a line that I think does nothing: directoryBlock value: dir. - inexplicably makes reference to read only files for reasons that are not encapsulated in the method title, and which appear to be irrelevant to the purpose. (Well, I can't see the point!) That method is called from the method: filesContaining: searchString caseSensitive: aBoolean - but that is apparently unused (there are no senders).

1 0

[Pharo-project] Is SmallInteger a really too dangerous class?
by Mariano Martinez Peck Dec. 13, 2010

Dec. 13, 2010

Hi folks. Sorry for the cross-post, I am not sure if it is image or vm problem. If I implement this: SmallInteger >> initialize self addInstVarName: 'Zaraza'. I have the error: 'SmallInteger cannot be changed' This is because SmallInteger is in the ClassBuilder >> tooDangerousClasses and the error is in ClassBuilder >> name: className inEnvironment: env subclassOf: newSuper type: type instanceVariableNames: instVarString classVariableNames: classVarString poolDictionaries: poolString category: category unsafe: unsafe Now....since this is Smalltalk, I can just comment something, continue, or any other kind of hack so that I can add class variables to SmallInetger. For my CompiledMethod proxies stuff, I am using SmallIntegers and I have some crashes (one is due to a corrupt heap and Eliot said something about sizes)...I wonder if this is related to this...So the question is: is really SMallInteger a too dangerous class so that it cannot be changed? not even adding a class variable??? does the VM assume that the class SmallInetger has a fixed size? if true, where? Thanks in advance Mariano

2 3

[Pharo-project] Issue 3288 in pharo: OB does not work with editor changes
by pharo＠googlecode.com Dec. 13, 2010

Dec. 13, 2010

Status: Accepted Owner: marcus.denker Labels: Milestone-1.2 New issue 3288 by marcus.denker: OB does not work with editor changes http://code.google.com/p/pharo/issues/detail?id=3288 To recreate: "Refactoring" Gofer new squeaksource: 'rb'; package: 'AST-Core'; package: 'Refactoring-Core'; package: 'Refactoring-Changes'; package: 'Refactoring-Critics'; package: 'Refactoring-Environment'; load. "OmniBrowser" Gofer new renggli: 'omnibrowser'; package: 'OmniBrowser'; package: 'OB-Standard'; package: 'OB-Morphic'; package: 'OB-Refactory'; load. then open an OB browser.

1 6

Re: [Pharo-project] Issue 2928 in pharo: Trying to change the category of traits method -> DNU
by pharo＠googlecode.com Dec. 13, 2010

Dec. 13, 2010

Updates: Status: Fixed Comment #2 on issue 2928 by marcus.denker: Trying to change the category of traits method -> DNU http://code.google.com/p/pharo/issues/detail?id=2928 (No comment was entered for this change.)

2 3

[Pharo-project] Issue 3367 in pharo: PopupChoiceDialogWindow>>handlesKeyboard: fails with empty label list
by pharo＠googlecode.com Dec. 13, 2010

Dec. 13, 2010

Status: Accepted Owner: aplantec Labels: Milestone-1.2 New issue 3367 by aplantec: PopupChoiceDialogWindow>>handlesKeyboard: fails with empty label list http://code.google.com/p/pharo/issues/detail?id=3367 For example, dnu when trying to add a category to a Trait from the browser

1 5