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

Re: [Pharo-project] Issue 3177 in pharo: add sophie copyright

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.2 Milestone-1.3 Comment #2 on issue 3177 by stephane.ducasse: add sophie copyright http://code.google.com/p/pharo/issues/detail?id=3177 (No comment was entered for this change.)

Dec. 11, 2010

Re: [Pharo-project] Issue 2755 in pharo: Image Save loses Form's color [black becomes transparent]

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.2 Milestone-1.3 Comment #12 on issue 2755 by stephane.ducasse: Image Save loses Form's color [black becomes transparent] http://code.google.com/p/pharo/issues/detail?id=2755 (No comment was entered for this change.)

Dec. 11, 2010

Re: [Pharo-project] Issue 1213 in pharo: Unable to type some czech characters

by pharo＠googlecode.com

Updates: Status: Closed Comment #11 on issue 1213 by stephane.ducasse: Unable to type some czech characters http://code.google.com/p/pharo/issues/detail?id=1213 (No comment was entered for this change.)

Dec. 11, 2010

[Pharo-project] Issue 3403 in pharo: should remove addServices2:for:extraLines:

by pharo＠googlecode.com

Status: Accepted Owner: stephane.ducasse Labels: Milestone-1.3 New issue 3403 by stephane.ducasse: should remove addServices2:for:extraLines: http://code.google.com/p/pharo/issues/detail?id=3403 This method looks suspicious.

Dec. 11, 2010

[Pharo-project] Issue 3402 in pharo: SmalltalkEditor new raises an Error

by pharo＠googlecode.com

Status: Accepted Owner: stephane.ducasse Labels: Milestone-1.2 New issue 3402 by stephane.ducasse: SmalltalkEditor new raises an Error http://code.google.com/p/pharo/issues/detail?id=3402 SmalltalkEditor new

Dec. 11, 2010

[Pharo-project] SmalltalkEditor new -> DNU

by StÃ©phane Ducasse

Hi When I tried to open a browser in SimpleMorphic I got an infinite DNU Now the problem is not in SimpleMorphic but SmalltalkEditor new does not work. Stef

Dec. 11, 2010

Re: [Pharo-project] About using pragma for help like in setting

by Lukas Renggli

> On the chat, it seemed that the main objection was depending on an external > class. Since HelpSystem is now part of core, what is the problem there? > Isn't it just like Tests depending on TestCase? After running the tests, first thing I do in a Pharo 1.2 core image on my build server: ====================================== "Unload all tests" (MCWorkingCopy allManagers inject: Gofer new into: [ :gofer :each | ((each packageName endsWith: 'Test') or: [ each packageName endsWith: 'Tests' ]) ifTrue: [ gofer package: each packageName ]. gofer ]) unload. "Unload other packages" Gofer new package: 'FixUnderscores'; package: 'Glamour-Morphic-Theme'; package: 'HelpSystem-Core'; package: 'Announcements-Help'; package: 'Regex-Help'; unload. ====================================== That means that I cannot load any package that includes pages for the help system. Furthermore, this means that none of my packages will ever include help system text, even if I would love to include my blog articles (for example for PetitParser) somehow more accessible than in a class comment. In fact, I haven't seen a single non-core package providing help pages. On contrary, there are many packages providing settings. This does not introduce any dependencies. Maybe this is a hint? Lukas -- Lukas Renggli www.lukas-renggli.ch

Dec. 11, 2010

Re: [Pharo-project] About using pragma for help like in setting

by Igor Stasenko

On 11 December 2010 20:25, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > I'm trying to wrap my mind around the issue... > > > StÃ©phane Ducasse wrote: >> >> yesterday on the irc we got a discussion on the dependency introduced when >> using HelpSystem. >> > > On the chat, it seemed that the main objection was depending on an external > class. Â Since HelpSystem is now part of core, what is the problem there? > Isn't it just like Tests depending on TestCase? > > So, what the problem here? Put a 'HelpSystem' class var somewhere. And if its nil, do nothing, and then HelpSystem , when loading set this var to some object, responsible for handling requests. Then use self helpSystem instead of HelpSystem everywhere, and you don't have external dependencies. > StÃ©phane Ducasse wrote: >> >> Some proposed to used pragmas... and we can also browse help with >> implementors. >> > > Again, if HelpSystem is in core, how does it help to browse with > implementors? > > Sean > -- > View this message in context: http://forum.world.st/About-using-pragma-for-help-like-in-setting-tp3078978… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Best regards, Igor Stasenko AKA sig.

Dec. 11, 2010

Re: [Pharo-project] Ring - model infrastructure for Pharo

by Igor Stasenko

CompiledMethod>>#methodNode is a conversion method and as any conversion i would prefer it be prefixed with 'as' , i.e. #asMethodNode #stringVersion is used only in MessageTrace in my image. Concerning #stringVersion: i really don't have an idea what this stuff doing there? Why a method reference allows putting an arbitrary data (strings) there by various tools? Then maybe better call it 'annotation' , and correspondingly #defaultAnnotation, so we will know that this field used for annotations by different tools? About #isMeta and friends: they serve nothing , but introducing a lot of ad-hoc logic with code branches all over the places. We should learn how to use message dispatching better :) IMO, the 'theClass' ivar should be capable answering this message, along with #name, which gives the name of a class. Method reference in its 'theClass' ivar instead of symbol, should hold either real class object (or metaclass object), or a proxy (in same way as method reference is a proxy by itself). -- Best regards, Igor Stasenko AKA sig.

Dec. 11, 2010

Re: [Pharo-project] good news of the year

by Sean P. DeNigris

Very exciting! Good luck & congrats, Igor. I can't wait to bask in all the improvements :) Sean -- View this message in context: http://forum.world.st/good-news-of-the-year-tp3083142p3083625.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 11, 2010