August 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] RB API

by Lukas Renggli

>>> Let me ask maybe a better question - how would you do the following >>> programmatically? >> >> I would crete a rewriter for each case, instantiate a RBNamespace, iterate >> over all methods within, and apply the rewriters if necessary, then review >> the changeset, and apply it. > > This is one of the best things which i seen in OB. But even by > watching your screencasts i found it hard to use. > I remember i tried to rewrite some code using it but then i failed and > lost in space (too much windows open, no clear visibility in what > context they might work and > why it fails for me, but works for you etc etc), so i abandoned > attempts to master refactoring-fu using OB. It is complicated to expose the complete refactoring engine API through an UI and in many cases it is not even easily usable, in fact the original Refactoring Browser only supported a much smaller sub-set. Now what I think is quite simple is: (1) open a scoped browser, (2) trigger a refactoring, and (3) edit the proposed change-list. That fact that the change-list is editable might not be obvious, but in fact any proposed change can be removed (ctrl+x) and outside diff mode you can even edit proposed change. Furthermore there is full multi-level undo-redo support in OB with the refactoring engine loaded, *any* refactoring (as well as any class/method deletion/redefinition/addition in OB) can be undone. > And of course, since most of the times i hunting bugs in core image(s) > of past , OB was not there and these features was not available to me, > as developer > (that's again, another reason to have single image for everyone). It is really easy to load refactoring engine into a core image, perform the refactoring, commit the changes, and load the refactored code into a core image again. This is especially true if Hudson always provides up-to-date images. > I would really like to have it in our _default_ images to empower > developers. I think it is a very bad idea to integrate the refactoring engine into the system, but I guess we don't have to discuss that again. > because you know, for you , as an author (and/or maintainer) of it > things look pretty straightforward, but for people who only get > started they apparently not. No, the refactoring engine is not an easy piece of software. It took me many years to fully understand it before I could start to fix and improve it. Lukas -- Lukas Renggli www.lukas-renggli.ch

Aug. 31, 2011

Re: [Pharo-project] Pharo 1.3 release

by Sven Van Caekenberghe

On 31 Aug 2011, at 18:29, Igor Stasenko wrote: > Update (for the impatient) > > Marcus and i made a beta version of one-click image, which can be > downloaded from here: > > https://gforge.inria.fr/frs/download.php/28922/Pharo-1.3-OneClick.zip > > works on: mac, ubuntu, windoze Super! Some small remarks (we want this to be perfect, don't we): on Mac OS X, the About menu should be changed to 'About Pharo', the Help menu should be changed to 'Pharo Help'; some items on the World menu have no icon, most notably the System Browser and Transcript. Also, I think that it would be very cool if a normal user like me can take the image and run all unit tests and be amazed that they all pass: that would really inspire new users and instill a quality feeling. Now, is there a way to get more feedback (like on the Transcript or some log file) when running all tests ? Right now, the Test Runner hangs and there seems to be no way to find out at which test. Sven

Aug. 31, 2011

[Pharo-project] PLEASE HELP testing Pharo 1.3 One Click [WAS] Pharo 1.3 release

by Mariano Martinez Peck

On Wed, Aug 31, 2011 at 6:29 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Update (for the impatient) > > Marcus and i made a beta version of one-click image, which can be > downloaded from here: > > https://gforge.inria.fr/frs/download.php/28922/Pharo-1.3-OneClick.zip > > So...this is the last pending thing for Pharo 1.3. Can you help us and test it ? > works on: mac, ubuntu, windoze > > > > -- > Best regards, > Igor Stasenko AKA sig. > > -- Mariano http://marianopeck.wordpress.com

Aug. 31, 2011

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

by Alexandre Bergel

Thanks for your help. Alexandre On 31 Aug 2011, at 14:15, Jimmie Houchin wrote: > On 8/31/2011 11:04 AM, Alexandre Bergel wrote: >> >> hi! >> >> Is there a way to open a text in a window in Pharo? >> Doing: Workspace openContents: 'hello world' >> shows >> <Mail Attachment.png> >> >> Is there a way to remove the syntax highlighting? >> > > I have recently been using > ws := Workspace openLabel: 'A Nice Label'. > ws contents: '"', 'my contents', '"'. > > ie: wrapping the contents with doubles quotes which simply make the contents a comment in the workspace. > > This is what I noticed was being used for the workspaces opened in in new image. > > I do wish we had a simple text box to receive such content which was not necessarily meant for syntax highlighting. > > I am using Workspace in my situation to provide progress updates on background processes which take hours to accomplish their task. > > I don't know if any of the recent work towards improving Transcript helps here. For me I would want an independent Transcript which I label and control. Not the general Transcript. > > Hope this helps. > > Jimmie -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 31, 2011

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

by Jimmie Houchin

On 8/31/2011 11:04 AM, Alexandre Bergel wrote: > 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? > I have recently been using ws := Workspace openLabel: 'A Nice Label'. ws contents: '"', 'my contents', '"'. ie: wrapping the contents with doubles quotes which simply make the contents a comment in the workspace. This is what I noticed was being used for the workspaces opened in in new image. I do wish we had a simple text box to receive such content which was not necessarily meant for syntax highlighting. I am using Workspace in my situation to provide progress updates on background processes which take hours to accomplish their task. I don't know if any of the recent work towards improving Transcript helps here. For me I would want an independent Transcript which I label and control. Not the general Transcript. Hope this helps. Jimmie

Aug. 31, 2011

Re: [Pharo-project] Gofer/Metacello problem in 1.4 [WAS] Re: DBXTalk and Pharo 1.4

by Dale Henrichs

Ah, a successful distributed bug hunt completed!:) Dale ----- Original Message ----- | From: "Mariano Martinez Peck" <marianopeck(a)gmail.com> | To: Pharo-project(a)lists.gforge.inria.fr | Cc: dbxtalk(a)googlegroups.com | Sent: Wednesday, August 31, 2011 3:21:10 AM | Subject: Re: [Pharo-project] Gofer/Metacello problem in 1.4 [WAS] Re: DBXTalk and Pharo 1.4 | | | | | On Tue, Aug 30, 2011 at 11:26 PM, Dale Henrichs < dhenrich(a)vmware.com | > wrote: | | | Mariano, | | I think that addVersion: is very old gofer/metacello code ... not | fancy new code. It sounds like an old version of Metacello is being | loaded/bootstrapped. #addVersion: isn't sent from the current code | base ... At a minimum, you should have these packages loaded: | | 'Metacello-Base-DaleHenrichs.19' | 'Metacello-Core-DaleHenrichs.455' | 'Metacello-MC-DaleHenrichs.505' | | | | Wow. This is weird. The versions that are being loaded are: | Metacello-Core-dkh.302 | Metacello-MC-dkh.258 | ... | | So...terribly old. Of course, the problem was that out | #ensureMetacello was very old. But how we didn't discovered before | doing the release? of course, because we used Pharo images that | already come with Metacello hahahha. | | I have just commited the fix. I took the latest #ensureMetacello from | here: http://code.google.com/p/metacello/wiki/EnsureMetacello | I hope this is correct. | | Thanks Dale for the help and thanks Laszlo for the report! | | | if the bootstrapping process is working. | | Keep in mind that pharo1.4.x has not yet been defined in Metacello | (see Issue 4613[1]), so there will be other Metacello issues in 1.4 | for the moment ... the proposed bugfix in 4613 would mean that a new | version of Metacello would no longer be needed to define the | platform specific attributes ... | | Dale | | [1] http://code.google.com/p/pharo/issues/detail?id=4613 | | | | | ----- Original Message ----- | | From: "Mariano Martinez Peck" < marianopeck(a)gmail.com > | | To: dbxtalk(a)googlegroups.com , "Pharo Development" < | | pharo-project(a)lists.gforge.inria.fr > | | Sent: Tuesday, August 30, 2011 2:00:26 PM | | Subject: [Pharo-project] Gofer/Metacello problem in 1.4 [WAS] Re: | | DBXTalk and Pharo 1.4 | | | | | | | | | | On Tue, Aug 30, 2011 at 9:14 PM, Laszlo Zsolt Kiss < | | lzskiss(a)gmail.com > wrote: | | | | | | | | | | hi. | | first i load the ConfigurationOfOpenDBX and the 1.4 version is | | missing from the spec.: | | | | | | | | stable: spec | | <symbolicVersion: #stable> | | | | spec for: #'pharo1.2.x' version: '1.0'. | | spec for: #'pharo1.3.x' version: '1.0'. | | | | | | then i added the next line to the spec: | | | | | | spec for: #'pharo1.4.x' version: '1.0'. | | | | | | then i probally do it this: | | | | | | (((Smalltalk globals at: #ConfigurationOfOpenDBXDriver) perform: | | #project) perform: #version: with: #stable) load. | | | | | | i gived back a warring: | | | | | | | | "The method Gofer addVersion: has been deprecated. | | Instead of #addVersion: simply use #version: | | | | Hi. Yes, I can reproduce this problem :( | | | | | | | | | | | | | | | | | | Select Proceed to continue, or close this window to cancel the | | operation." | | | | | | I proceed this warrning. | | | | | | Then gived back an error message, I think this error came from the | | Metacello. | | | | I attached the PharoDebug file. | | | | | | | | | | The error is in the method #updateProject where it does: | | | | (GoferPackageReference name: mgr packageName repository: mgr | | repositoryGroup) versionReference. | | | | GoferPackageReference dnu #name:repository: instead, it is | | implemented in GoferResolvedReference | | | | | | Dale any idea? | | | | Versions: Gofer-Core-StephaneDucasse.135. | | Metacello version is ...... ConfigurationOfMetacello project | | currentVersion raises dnu #setName | | | | So...I guess Pharo 1.4 is using a very new version of Gofer, which | | brings lot of changes that break Metacello ? | | | | Thanks! | | | | | | | | | | | | | | | | | | Byte | | Laszlo Zsolt | | | | | | Ps: the image is clean #14112 and the CogVM is the last.. | | | | | | inez Peck < marianopeck(a)gmail.com > | | | | | | | | | | | | | | | | | | | | On Tue, Aug 30, 2011 at 9:53 AM, Laszlo Zsolt Kiss < | | lzskiss(a)gmail.com > wrote: | | | | | | Hi Developers! | | | | | | Can I use any way this combination: DBXTalk with Pharo 1.4? | | | | Hi. Yes, sure. Did you try it? You shouldn't have any problem. | | Please let us know if you do have. | | | | | | -- | | Mariano | | http://marianopeck.wordpress.com | | | | | | | | | | | | -- | | Mariano | | http://marianopeck.wordpress.com | | | | | | | | | -- | Mariano | http://marianopeck.wordpress.com | |

Aug. 31, 2011

Re: [Pharo-project] RB API

by Igor Stasenko

On 31 August 2011 18:34, Lukas Renggli <renggli(a)gmail.com> wrote: >>> Note that the classes contain actually excellent documentation. >>> >> Do you have any particular one in mind? > > You asked about the AST nodes. > >> 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. > > That's a private internal class, you are not supposed to instantiate it. You > find documentation about the rewrite engine in the first link I sent you. > >>> 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 couldn't guess that. > >> 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. > > A few more clicks and you have a refactoring scope on any method set you > want. > >> Let me ask maybe a better question - how would you do the following >> programmatically? > > I would crete a rewriter for each case, instantiate a RBNamespace, iterate > over all methods within, and apply the rewriters if necessary, then review > the changeset, and apply it. > This is one of the best things which i seen in OB. But even by watching your screencasts i found it hard to use. I remember i tried to rewrite some code using it but then i failed and lost in space (too much windows open, no clear visibility in what context they might work and why it fails for me, but works for you etc etc), so i abandoned attempts to master refactoring-fu using OB. And of course, since most of the times i hunting bugs in core image(s) of past , OB was not there and these features was not available to me, as developer (that's again, another reason to have single image for everyone). I would really like to have it in our _default_ images to empower developers. And with nice documentation (HelpSystem maybe?) because you know, for you , as an author (and/or maintainer) of it things look pretty straightforward, but for people who only get started they apparently not. > Cheers, > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > -- Best regards, Igor Stasenko AKA sig.

Aug. 31, 2011

Re: [Pharo-project] Pharo 1.3 release

by StÃ©phane Ducasse

tx! On Aug 31, 2011, at 6:29 PM, Igor Stasenko wrote: > Update (for the impatient) > > Marcus and i made a beta version of one-click image, which can be > downloaded from here: > > https://gforge.inria.fr/frs/download.php/28922/Pharo-1.3-OneClick.zip > > works on: mac, ubuntu, windoze > > > > -- > Best regards, > Igor Stasenko AKA sig. >

Aug. 31, 2011

Re: [Pharo-project] DrGeo release 11.08

by Dennis Schetinin

When will it available on iPad? 2011/8/31 Hilaire Fernandes <hilaire.fernandes(a)edu.ge.ch> > 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 > > > > > -- Dennis Schetinin

Aug. 31, 2011

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

by Igor Stasenko

On 31 August 2011 18:28, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > 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). ahaa! you seem to be facing same problems as we had :) Nothing. I found no reliable way to detect that image are running headless, there is no VM api for exposing that. And this is sad. The way how pharo images detecting it currently is to check a command-line arguments passed to VM. See SmalltalkImage isHeadless in pharo 1.3 - 1.4 images. it is ugly, but i think this is better than detecting via Display, because its more direct. We should fix that. either by adding a new primitive , or adding new system attribute.. But my personal preference is to let image control the headless mode, i.e. instead of making VM decide whether image should be forced to run headless or not, an image should check a command line, and then instruct VM to create a window or not. This IMO would be the best solution to the problem. VM should provide access to features and/or facilities, and image should decide whether use them or not. Even if VM decides to not allow UI, then it should report to an image that given facility is not available, and play with it in nice manner, but not like today when image has no idea what happens and leaving it without any clues in what environment it running. -- Best regards, Igor Stasenko AKA sig.

Aug. 31, 2011