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

Re: [Pharo-project] Issue 3423 in pharo: Debugger little usability enh

by pharo＠googlecode.com

Comment #1 on issue 3423 by stephane.ducasse: Debugger little usability enh http://code.google.com/p/pharo/issues/detail?id=3423 When a method changes out from under your feet in the Debugger (e.g., you remove an instvar triggering a recompile of a method through which you've stepped), the Debugger blanks out contents. In the UI, this manifests as a blank code pane. This change resets the contents ivar by setting it to the new, recompiled, CompiledMethod as a side effect of calling self selectedMessage. This version is Eliot Miranda's improved version of my (fbs) initial submission. =============== Diff against Tools-ul.282 =============== Item was changed: ----- Method: Debugger>>contents (in category 'accessing') ----- contents "Depending on the current selection, different information is retrieved. Answer a string description of that information. This information is the method in the currently selected context." + ^contents ifNil: + [self selectedContext + ifNotNil: [self selectedMessage] + ifNil: [String new]] ! - contents == nil ifTrue: [^ String new]. - ^ contents copy!

Dec. 14, 2010

Re: [Pharo-project] Issue 3237 in pharo: If MessageTally is not in memory

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3237 by marcus.denker: If MessageTally is not in memory http://code.google.com/p/pharo/issues/detail?id=3237 So the code in Pharo is correct. There is no "ifPresentAndInMemory" anymore in Pharo

Dec. 14, 2010

[Pharo-project] Issue 3423 in pharo: Debugger little usability enh

by pharo＠googlecode.com

Status: FixedWaitingToBePharoed Owner: stephane.ducasse Labels: Milestone-1.3 New issue 3423 by stephane.ducasse: Debugger little usability enh http://code.google.com/p/pharo/issues/detail?id=3423 Name: Tools-fbs.283 Author: fbs Time: 1 December 2010, 3:09:44.682 pm UUID: 810789fa-9417-a340-a578-0df71274f43d Ancestors: Tools-ul.282 When a method changes out from under your feet in the Debugger (e.g., you remove an instvar triggering a recompile of a method through which you've stepped), the Debugger blanks out contents. In the UI, this manifests as a blank code pane. This change resets the contents ivar by setting it to the new, recompiled, CompiledMethod as a side effect of calling self selectedMessage. =============== Diff against Tools-ul.282 =============== Item was changed: ----- Method: Debugger>>contents (in category 'accessing') ----- contents "Depending on the current selection, different information is retrieved. Answer a string description of that information. This information is the method in the currently selected context." + contents == nil ifTrue: [^ self selectedMessage]. - contents == nil ifTrue: [^ String new]. ^ contents copy!

Dec. 14, 2010

[Pharo-project] Issue 3422 in pharo: Use UIManager instead of Workspace

by pharo＠googlecode.com

Status: Fixed Owner: stephane.ducasse Labels: Milestone-1.3 Difficulty-Easy New issue 3422 by stephane.ducasse: Use UIManager instead of Workspace http://code.google.com/p/pharo/issues/detail?id=3422 viewGZipContents "View the contents of a gzipped file" | stringContents | self binary. stringContents := self contentsOfEntireFile. stringContents := Cursor wait showWhile: [(GZipReadStream on: stringContents) upToEnd]. stringContents := stringContents asString withSqueakLineEndings. UIManager default edit: stringContents label: 'Decompressed contents of: ', self localName

Dec. 14, 2010

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

by StÃ©phane Ducasse

thanks I will have a look. I was blocked in an airport yesterday night so ... no way to check internet On Dec 14, 2010, at 12:14 PM, Torsten Bergmann wrote: > > Stef wrote on Mon Dec 13 10:02:56 (see [1]): >> Now what I want is that people can type >> ... >> <help> >> > > I already gave exactly such an example to Lukas already back in > May. Again - PLEASE have a look at it (just load the code in [2] > and run > > HelpBrowser openOn: PragmaHelp > > The code is small and simple: > > - beside the existing help builders it just introduces a > "PragmaHelpBuilder" that uses the pragma <help> to > collect the help data > > - a Foo and Bar class is included to demonstrate > how you define help with this new builder (similar to > the way Stef/Lukas wanted) > > As I said adding "pragma help" is just a new "help builder" > to define and one can easily add it. > > Think of another scenario: maybe one doesnt care about > the "class to book mapping" or a "pragma approach". > > He wants to define his help contents completely different > in external text files. Same pattern: he introduces a new > HelpBuilderFromExternalTextFile that converts his custom > (external) format into help topics. Nothing more. > > So the real work is in thinking about/defining how and in what > format you want to write the help contents itself. > > The problem: there are MANY ways to define the contents - > and as Stef showed us with the TWO "pragma" descriptions > examples in his mail [2] that we are currently NOT SURE > about the "pragma description" format to use. > But if we want pragma help in the help system we have to > find ONE and it should be simple and fit best. > > To say it in simple words: if we want to use pragmas > we have to find a way to use pragmas to define nestable > and extensible books (with pages and page order). > > I once requested this from Lukas but regarding extensible > books his simple answer was: > > "I would not make the books extensible themselves, > that complicates things and is rarely needed in practice." > > This answer is not satisfying to me since extensible books > ARE EASILY POSSIBLE with the "class to book mapping" that > the help system already have. And I use them. > > We can use "pragmas" but we should have the same possibilities > and not use pragmas because they are "modern" or they are > used by the Settings framework. > > And I agree with him that it may be hard to do with pragmas ... > especially since I already experimented on this with pragmas > But maybe we all can find a solution here together. > > In the end I switched to the "use classes and the class hierarchy" > approach since it is more natural (at least to me) and easy to > use/understand. > > Stef further wrote: >> and that if the help is loaded we can see it in help. > > A registration mechanism to mark which custom help builders > are included in the standard browser is on my todo list. > Currently it is only one and hard coded (see HelpBrowser>>defaultRoot) > > If the above pragma help builder is in good shape we > can add it too as one of the defaults - but a registration > mechanism is better in the long run. > > But again: > The problem I have with this simple pragma approach > > foo: myBuidler > <help> > myBuilder ... > > is that with this you can easily describe a page with a > title and text - but it is hard to describe a complete > book with structure and even extensible books. > > So we have to clearly think about the builder part of > this approach to keep the help contents definitions > simple. And this is what I requested you all to do if > we want to move on here... > > Just use my simple code example [2] to experiment and > find the "pragma" description format we want to introduce. > > Stef may answer: use the one that I showed you. But if > one uses pragmas we may want to describe the whole book. > Not just a simple <help> tag to describe a single page > with a title! > > Thx > T. > > [1] http://lists.gforge.inria.fr/pipermail/pharo-project/2010-December/037545.h… > > [2] http://lists.gforge.inria.fr/pipermail/pharo-project/attachments/20100505/c… > > -- > GMX DSL Doppel-Flat ab 19,99 €/mtl.! Jetzt auch mit > gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl >

Dec. 14, 2010

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

by Torsten Bergmann

Stef wrote on Mon Dec 13 10:02:56 (see [1]): >Now what I want is that people can type >... > <help> > I already gave exactly such an example to Lukas already back in May. Again - PLEASE have a look at it (just load the code in [2] and run HelpBrowser openOn: PragmaHelp The code is small and simple: - beside the existing help builders it just introduces a "PragmaHelpBuilder" that uses the pragma <help> to collect the help data - a Foo and Bar class is included to demonstrate how you define help with this new builder (similar to the way Stef/Lukas wanted) As I said adding "pragma help" is just a new "help builder" to define and one can easily add it. Think of another scenario: maybe one doesnt care about the "class to book mapping" or a "pragma approach". He wants to define his help contents completely different in external text files. Same pattern: he introduces a new HelpBuilderFromExternalTextFile that converts his custom (external) format into help topics. Nothing more. So the real work is in thinking about/defining how and in what format you want to write the help contents itself. The problem: there are MANY ways to define the contents - and as Stef showed us with the TWO "pragma" descriptions examples in his mail [2] that we are currently NOT SURE about the "pragma description" format to use. But if we want pragma help in the help system we have to find ONE and it should be simple and fit best. To say it in simple words: if we want to use pragmas we have to find a way to use pragmas to define nestable and extensible books (with pages and page order). I once requested this from Lukas but regarding extensible books his simple answer was: "I would not make the books extensible themselves, that complicates things and is rarely needed in practice." This answer is not satisfying to me since extensible books ARE EASILY POSSIBLE with the "class to book mapping" that the help system already have. And I use them. We can use "pragmas" but we should have the same possibilities and not use pragmas because they are "modern" or they are used by the Settings framework. And I agree with him that it may be hard to do with pragmas ... especially since I already experimented on this with pragmas But maybe we all can find a solution here together. In the end I switched to the "use classes and the class hierarchy" approach since it is more natural (at least to me) and easy to use/understand. Stef further wrote: >and that if the help is loaded we can see it in help. A registration mechanism to mark which custom help builders are included in the standard browser is on my todo list. Currently it is only one and hard coded (see HelpBrowser>>defaultRoot) If the above pragma help builder is in good shape we can add it too as one of the defaults - but a registration mechanism is better in the long run. But again: The problem I have with this simple pragma approach foo: myBuidler <help> myBuilder ... is that with this you can easily describe a page with a title and text - but it is hard to describe a complete book with structure and even extensible books. So we have to clearly think about the builder part of this approach to keep the help contents definitions simple. And this is what I requested you all to do if we want to move on here... Just use my simple code example [2] to experiment and find the "pragma" description format we want to introduce. Stef may answer: use the one that I showed you. But if one uses pragmas we may want to describe the whole book. Not just a simple <help> tag to describe a single page with a title! Thx T. [1] http://lists.gforge.inria.fr/pipermail/pharo-project/2010-December/037545.h… [2] http://lists.gforge.inria.fr/pipermail/pharo-project/attachments/20100505/c… -- GMX DSL Doppel-Flat ab 19,99 €/mtl.! Jetzt auch mit gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl

Dec. 14, 2010

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

by Geert Claes

StÃ©phane Ducasse wrote: > > yes monticelloHub > I like :) -- View this message in context: http://forum.world.st/good-news-of-the-year-tp3083142p3086850.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 14, 2010

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

by laurent laffont

On Tue, Dec 14, 2010 at 11:52 AM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > yes monticelloHub > Cool name :) Laurent > > On Dec 14, 2010, at 10:03 AM, Geert Claes wrote: > > > > > > > StÃ©phane Ducasse wrote: > >> > >> For SqueakSource, ESUG is paying the iliad guys to show that their > >> technology is cool and they will rewrite from scratch. We are > negociating > >> since a couple of months with inria to have a web-dav server so that we > >> can host all the monticello related host. > >> > > > > More great news then! Since its a complete re-write and assuming it will > > serve for both Squeak and Pharo projects alike, I am wondering if its > just > > me but I reckon it could do with a nice new name too :) If so it > probably > > deserves a separate thread > > > > -- > > View this message in context: > http://forum.world.st/good-news-of-the-year-tp3083142p3086645.html > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > >

Dec. 14, 2010

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

by StÃ©phane Ducasse

yes monticelloHub On Dec 14, 2010, at 10:03 AM, Geert Claes wrote: > > > StÃ©phane Ducasse wrote: >> >> For SqueakSource, ESUG is paying the iliad guys to show that their >> technology is cool and they will rewrite from scratch. We are negociating >> since a couple of months with inria to have a web-dav server so that we >> can host all the monticello related host. >> > > More great news then! Since its a complete re-write and assuming it will > serve for both Squeak and Pharo projects alike, I am wondering if its just > me but I reckon it could do with a nice new name too :) If so it probably > deserves a separate thread > > -- > View this message in context: http://forum.world.st/good-news-of-the-year-tp3083142p3086645.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Dec. 14, 2010

Re: [Pharo-project] Issue 3413 in pharo: WeakFinalizersTest.testNewFinalizationSupported fails on Hudson builder

by pharo＠googlecode.com

Comment #1 on issue 3413 by siguctua: WeakFinalizersTest.testNewFinalizationSupported fails on Hudson builder http://code.google.com/p/pharo/issues/detail?id=3413 Yes we do. :) But of course its not critical.

Dec. 14, 2010