- Pharo-dev - lists.pharo.org

[Pharo-project] what's the standard way of finding out from Smalltalk if one is running headless?

by Eliot Miranda

I thought to test things like Display extent & DisplayScreen actualScreenDepth but these either fall back to values in the pre-headless image or don't fail and answer the actual display depth, even though the VM is running headless (at least on Mac they do). -- best, Eliot

Aug. 31, 2011

Re: [Pharo-project] opening a text in a window

by Max Leske

Don't know if this helps: The workspace used by the help system to interactively edit the help texts allows deactivation of the syntax highlighting via the menu in the top right corner of the workspace. Max On 31.08.2011, at 18:04, Alexandre Bergel wrote: > hi! > > Is there a way to open a text in a window in Pharo? > Doing: Workspace openContents: 'hello world' > shows > <Screen Shot 2011-08-31 at 13.03.06.png> > > Is there a way to remove the syntax highlighting? > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

Aug. 31, 2011

Re: [Pharo-project] opening a text in a window

by Benjamin

I got the same problem in the debugger :) May Alain save us again ^^ Ben On Aug 31, 2011, at 6:04 PM, Alexandre Bergel wrote: > hi! > > Is there a way to open a text in a window in Pharo? > Doing: Workspace openContents: 'hello world' > shows > <Screen Shot 2011-08-31 at 13.03.06.png> > > Is there a way to remove the syntax highlighting? > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

Aug. 31, 2011

[Pharo-project] opening a text in a window

by Alexandre Bergel

hi! Is there a way to open a text in a window in Pharo? Doing: Workspace openContents: 'hello world' shows Is there a way to remove the syntax highlighting? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 31, 2011

[Pharo-project] DrGeo release 11.08

by Hilaire Fernandes

I am pleased to announce release 11.08 of DrGeo for GNU-Linux/Windows/Mac OSX. As always the application is distributed under the form of an unique universal portable bundle for the three systems. http://www.ofset.org/drgeo ChangeLog * Release 11.08 - Thanks to the Pharo Smalltalk community for its continuous support - Special greeting to Henrik. * #2929 Simplify the way to load a sketch: now the user selects the sketch to open from a preview list * User can open sketch from an examples repository or from its own 'MySketches' repository. Change accordingly the load and save file operation. * In the toolbar, new icon button to create a blank sketch, keep or open an existing sketch * DrGeo is now touchpad friendly for a better user experience on tablet PC * #13010 Secure the edited free value * #12785 undo/redo angle: lost arc * #12782 Use smaller font to print 3 points angle * #12786 label should be selectable first * #12784 Assist to name object * Rendering speed improvements * Properly save sketch as UTF-8 file

Aug. 31, 2011

Re: [Pharo-project] #deprecate: & #deprecate:in: will be deprecated in 1.4

by Damien Cassou

On Wed, Aug 31, 2011 at 3:53 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > http://code.google.com/p/pharo/issues/detail?id=4718 > I put a fix in the inbox that updates all existing calls to use > #deprecate:on:in: can we say it is a meta-deprecation? -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Aug. 31, 2011

Re: [Pharo-project] The Keys to the Kingdom

by Dennis Schetinin

"Pure" TDD (or, BDD as it's reincarnation) makes tests a documentation automatically. Unfortunately, it's not easy to find TDD examples in Smalltalk (nearly all, not just Pharo) code. Not to say, this approach would resolve a lot of other problems, if adopted just a bit widerâ¦ Just complaining :) 2011/8/31 Sean P. DeNigris <sean(a)clipperadams.com> > IMHO, the biggest room for improvement is with Tests. What I loved about > BDD > coming from Ruby is that it forces you to write tests from the perspective > of a user of the API. Often in Squeak/Pharo, I go to the tests and still > have no idea how to use the classes because the tests focus on > implementation details. > > -- > View this message in context: > http://forum.world.st/The-Keys-to-the-Kingdom-tp3780556p3780712.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Dennis Schetinin

Aug. 31, 2011

Re: [Pharo-project] RB API

by Sean P. DeNigris

Lukas Renggli wrote: > > Note that the classes contain actually excellent documentation. > Do you have any particular one in mind? I traced OB's execution to RBStringReplaceRule and then looked up the hierarchy finding basic few-sentence descriptions, but nothing in-depth about how to search and replace. Lukas Renggli wrote: > > Actually you can do it with a few clicks: Select #deprecated:, click > on "Refactor method > Add parameter" and follow the instructions. > Notice I asked about the API, not about the OB GUI. I needed to programmatically change each one depending on the sender's timeStamp and the collections of what was deprecated in which version. Also, there are already methods in the system with the name I'm changing to, so OB just mentions that and fails. Let me ask maybe a better question - how would you do the following programmatically? For each method that sends #deprecated: (except for certain excluded ones) change the send to #deprecated:on:in: where the second argument is the calling method's timeStamp and the third is 'Pharo1.3' or 'Pharo1.4' depending on which pre-made list it appears on. Cheers, Sean -- View this message in context: http://forum.world.st/RB-API-tp3781019p3781179.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Aug. 31, 2011

Re: [Pharo-project] RB API

by StÃ©phane Ducasse

I would love to have a real and nice documentation/tutorial because this is a great tool. Stef On Aug 31, 2011, at 4:17 PM, Lukas Renggli wrote: >> Is there any documentation on using AST & RB? > > http://www.refactory.com/RefactoringBrowser/index.html > http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.91.9246&rep=rep1&t… > >> I didn't find anything enlightening via google, the tests, or the >> class/method comments. > > Note that the classes contain actually excellent documentation. > >> In trying to replace all calls to #deprecate: and >> #deprecate:in: to #deprecate:on:in: (Issue 4718), it took me hours to step >> through OB's refactoring and learn the syntax. >> >> In case anyone else can benefit, I eventually ended up with: >> RBParseTreeRewriter new >> replace: '``@object deprecated: ``@arg1 ' >> with: '``@object deprecated: ``@arg1 on:(''', dateString, ''') >> in:(''Pharo', versionNumber asString, ''')'. > > Actually you can do it with a few clicks: Select #deprecated:, click > on "Refactor method > Add parameter" and follow the instructions. > > The rewrite engine takes a while to master. It is the infrastructure > that runs most of the refactorings and it is typically not necessary > for basic refactorings like this one. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch >

Aug. 31, 2011

Re: [Pharo-project] RB API

by Lukas Renggli

> Is there any documentation on using AST & RB? http://www.refactory.com/RefactoringBrowser/index.html http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.91.9246&rep=rep1&t… > I didn't find anything enlightening via google, the tests, or the > class/method comments. Note that the classes contain actually excellent documentation. > In trying to replace all calls to #deprecate: and > #deprecate:in: to #deprecate:on:in: (Issue 4718), it took me hours to step > through OB's refactoring and learn the syntax. > > In case anyone else can benefit, I eventually ended up with: > Â Â Â Â RBParseTreeRewriter new > Â Â Â Â Â Â Â Â replace: '``@object deprecated: ``@arg1 ' > Â Â Â Â Â Â Â Â with: '``@object deprecated: ``@arg1 on:(''', dateString, Â ''') > in:(''Pharo', versionNumber asString, ''')'. Actually you can do it with a few clicks: Select #deprecated:, click on "Refactor method > Add parameter" and follow the instructions. The rewrite engine takes a while to master. It is the infrastructure that runs most of the refactorings and it is typically not necessary for basic refactorings like this one. Lukas -- Lukas Renggli www.lukas-renggli.ch

Aug. 31, 2011