June 2015 - Pharo-dev - lists.pharo.org

Wrong parent in RBProgramNode after a #copy

by Jan Vrany

Hi, while writing some code transformation code, I found out that in many implementations of RBProgramNode & co. the #copy message makes a sort of deep copy, copying also it's child nodes. However, it does NOT sets it's parent to the copy, so for copied nodes, following does not hold: someNode children anyOne parent == someNode This seems to br wrong to me. In other implementations I can simply use #deepCopy and works fine, but I cannot do this in Pharo because #deepCopy fails. The reason is that in Pharo RBProgramNodes are infested with OpalCompiler stuff which apparently keeps BlockClosures which cannot be deep-copied. The tree I'm trying to copy is obtained using BlockClosure>>sourceNode. Question: Is there a way how to copy the parse tree with parents set properly? If not, I'm inclined to fix #copy so it sets parent node properly If that's not desirable for one reason or another, no problem, I'll do it differently (but not-so-nicely :-) Best, Jan

June 18, 2015

Re: [Pharo-dev] We want to remove historyNavigation from Nautilus...

by Sean P. DeNigris

camille teruel wrote > Horizontal scrolling events are converted to right/left keypress events. Holy #@$! I could never figure out what was going on. Maybe I will finish implementing the "better hack for horizontal scrolling" in the VM and possibly eradicate this one until we have a proper solution with SDL... or maybe that is right around the corner? ----- Cheers, Sean -- View this message in context: http://forum.world.st/We-want-to-remove-historyNavigation-from-Nautilus-tp4… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 18, 2015

Re: [Pharo-dev] How to download Woden?

by Alexandre Bergel

Hi Natalia, Which error do you get? I have the following problem: Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jun 17, 2015, at 6:42 PM, Natalia Tymchuk <natalia.tymchuk(a)unikernel.net> wrote: > > Hello. > > As I understand, no one works on improving Roassal3d, so all people who work with 3d graphics need to use Woden. > Iâm using Woden during the month. I like Woden. And Iâm sorry, but and it seems to me that it creates more troubles with downloading after each next downloading. > At the beginning I could download it from CI server. Now I cannot. > Then I used long script from smalltalkhub and downloaded it into moose5 image. Now I cannot. > Then I used the same script to download it into pharo4 image and after a couple of tries I was successful. Now I am not. > > I understand that Woden is complicated and huge, but please tell me how should I download it? > > Sorry for so criticizing letter. > Best regards, > Natalia > > > > >

June 17, 2015

How to download Woden?

by Natalia Tymchuk

Hello. As I understand, no one works on improving Roassal3d, so all people who work with 3d graphics need to use Woden. Iâm using Woden during the month. I like Woden. And Iâm sorry, but and it seems to me that it creates more troubles with downloading after each next downloading. At the beginning I could download it from CI server. Now I cannot. Then I used long script from smalltalkhub and downloaded it into moose5 image. Now I cannot. Then I used the same script to download it into pharo4 image and after a couple of tries I was successful. Now I am not. I understand that Woden is complicated and huge, but please tell me how should I download it? Sorry for so criticizing letter. Best regards, Natalia

June 17, 2015

Fwd: [pharo-project/pharo-core] fbbe9e: 50118

by Nicolai Hess

---------- Forwarded message ---------- From: GitHub <noreply(a)github.com> Date: 2015-06-17 19:03 GMT+02:00 Subject: [Pharo-dev] [pharo-project/pharo-core] fbbe9e: 50118 To: pharo-dev(a)lists.pharo.org 15787 Improving rubric https://pharo.fogbugz.com/f/cases/15787 Now, a printIt popup in GTPlayground does not work anymore, it stays up and you can not paste the content

June 17, 2015

Re: [Pharo-dev] Question about API / Backend

by stepharo

I like this idea too because it makes clear that you are using an back-end specific behavior. Le 16/6/15 12:15, Henrik Johansen a Ã©crit : > >> On 16 Jun 2015, at 9:58 , Matthieu Lacaton >> <matthieu.lacaton(a)gmail.com <mailto:matthieu.lacaton@gmail.com>> wrote: >> >> Hello everybody, >> >> The question I have concerns OSWindow and its backend : SDL. However, >> even if I'll speak about these two, i think the question is quite >> general and can apply to every API. >> >> There are some functions that we are sure we will find in every >> backend possible (for instance the possibility to create a new >> window, to resize it etc.) and for these ones it is totally fine to >> abstract the backend from the user because you know that even if the >> backend has to change the API will be usable the same way. >> >> But there are some functions that are quite specific to a certain >> backend and you cannot always find it in others. But this function is >> cool so it would be a shame not to implement it just for the sake of >> uniformity. >> In this case I see two options : >> >> 1) You abstract these functions exactly the same way you did for the >> others and the user is not informed at all. In this case the risk is >> that if the backend changes it may break the API for the user because >> he won't be able to use this function anymore.And he may feel a bit >> sad because he was not warned about it. >> >> 2) You make *something* to let the user know that this or that >> function is specific to this or that backend. By doing so the user >> knows that there is a small risk that he won't be able to use this >> function anymore if the backend changes. He has been warned. >> >> Now I prefer the second option but I wanted to ask you about that >> "something". What is the best way to warn the user ? >> >> - Should I let the name of the backend in the name of the method ? >> "SDL_MySpecificMethod" >> - Should I put all these methods in a specific package and name / >> comment that package accordingly ? >> - Some other things ? >> >> Basically my question is : what is the best way to let the user know >> he is dealing with a specific function for a specific backend ? >> >> Thanks, >> >> Matthieu > > A recent idea I had, translated to your case, was doing this by > providing accessors to specific backend extension classes. > Personally, I'd prefer to use a class separate from that which > implements the common interface, so one doesn't accidentally end up > doing common calls on only specific backends, here's a purely > theoretical example of how that may look: > > window := OSWindow new. > window title: 'Test window'. > "With SDL, we support making window unbordered" > window SDL bordered: false. > window openInWorld. > > With a few example implementations: > OSWindow >> #SDL > "Could cache in instvar, but that would not as modular, as you can't > package that with the rest of the backend, with methods all you need > is *SDL-Windows categorization" > currentBackEnd isSDL > ifTrue: [SDL_ExtWindow target: self] > ifFalse: [NoopWindow target: self] > > SDLExtendedWindow >> #bordered: aBoolean > <primitive: #primitiveNativeCall module: #NativeBoostPlugin error: > errorCode> > ^ self nbCall: #( int SDL_SetWindowBordered ( SDL_Window * target , > SDL_bool aBoolean ) ) > > Haven't actually used this pattern yet, but at least to me, it yields > a clear distinction between what is common between backends, and what > will only work on some. > SDL is of course a somewhat special case, at it itself is an > abstraction over different backends, and there's little functionality > there that could not be part of a standard window API... > > Cheers, > Henry

June 17, 2015

Re: [Pharo-dev] External interfacing with Pharo on Pi

by Attila Magyar

I use OSProcess to play video files with omxplayer (the built in video player in raspbian), and it works fine. -- View this message in context: http://forum.world.st/External-interfacing-with-Pharo-on-Pi-tp4832762p48328… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 17, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50118 Home: https://github.com/pharo-project/pharo-core

June 17, 2015

[pharo-project/pharo-core] fbbe9e: 50118

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: fbbe9e3fbef08dab20e46b3b72c3e3f80e9d0057 https://github.com/pharo-project/pharo-core/commit/fbbe9e3fbef08dab20e46b3b… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-06-17 (Wed, 17 Jun 2015) Changed paths: M ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/symbolic versions/stable_.st A ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/versions/version126_.st A ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/versions/version134_.st A ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/versions/version135_.st R Glamour-Morphic-Theme.package/GLMThemeIcons.class/class/icons/radioSelectedForm.st R Glamour-Morphic-Theme.package/GLMThemeIcons.class/class/icons/radioSelectedFormContents.st R Glamour-Morphic-Theme.package/GLMThemeIcons.class/class/icons/radioUnselectedForm.st R Glamour-Morphic-Theme.package/GLMThemeIcons.class/class/icons/radioUnselectedFormContents.st M Glamour-Rubric-Presentations.package/GLMSegmentWithHelpAndMouseUpActionExample.class/instance/accessing/presentation.st A Rubric.package/RubAbstractTextArea.class/instance/accessing text/textFont_.st M Rubric.package/RubAbstractTextArea.class/instance/event handling/mouseDown_.st A Rubric.package/RubAbstractTextArea.class/instance/event handling/takeKeyboardFocus.st A Rubric.package/RubAbstractTextArea.class/instance/testing/isReadOnly.st M Rubric.package/RubAbstractTextArea.class/instance/testing/takesKeyboardFocus.st M Rubric.package/RubAdornmentDisplayer.class/instance/drawing/drawOn_.st M Rubric.package/RubCursor.class/instance/accessing/actualCursorColor.st A Rubric.package/RubGhostTextDisplayer.class/instance/accessing/font_.st R Rubric.package/RubGhostTextDisplayer.class/instance/event handling/textAreaGotFocus_.st R Rubric.package/RubGhostTextDisplayer.class/instance/event handling/textAreaLostFocus_.st R Rubric.package/RubGhostTextDisplayer.class/instance/initialize-release/initialize.st M Rubric.package/RubGhostTextDisplayer.class/instance/private/showHideGhostText.st M Rubric.package/RubGhostTextDisplayer.class/instance/submorphs-accessing/noteNewOwner_.st A Rubric.package/RubScrolledTextMorph.class/instance/configure/configureGhostText_.st A Rubric.package/RubScrolledTextMorph.class/instance/defaults/defaultGhostTextMorph.st A Rubric.package/RubScrolledTextMorph.class/instance/testing/isReadOnly.st A Rubric.package/RubTextFieldMorph.class/instance/configure/configureGhostText_.st A Rubric.package/RubTextFieldMorph.class/instance/defaults/defaultGhostTextMorph.st M Rubric.package/RubTextFieldMorph.class/instance/geometry/textFieldHeight.st M Rubric.package/RubTextScrollPane.class/instance/drawing/drawSubmorphsOnAthensCanvas_.st M Rubric.package/RubTextScrollPane.class/instance/drawing/drawSubmorphsOn_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50117.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50118.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50117.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50118.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Core.package/LabelModel.class/definition.st A Spec-Core.package/LabelModel.class/instance/api/emphasis.st M Spec-Core.package/LabelModel.class/instance/api/emphasis_.st M Spec-Core.package/LabelModel.class/instance/initialization/initialize.st M Spec-MorphicAdapters.package/MorphicLabelAdapter.class/instance/factory/buildWidget.st Log Message: ----------- 50118 15771 spotter dive into class from senders/implementors result list https://pharo.fogbugz.com/f/cases/15771 15304 LabelModel emphasis: doesnt work before the model is opened https://pharo.fogbugz.com/f/cases/15304 15787 Improving rubric https://pharo.fogbugz.com/f/cases/15787 http://files.pharo.org/image/50/50118.zip

June 17, 2015

Re: [Pharo-dev] Detecting the context/producer of code change announcements

by Martin Dias

Thanks for the discussion. I'm considering the ideas; I want to propose something concrete very soon. If I understand well, the two positions are: * to extend Job with a 'description' object; * to extend system announcements, so they know their 'parent' announcement; in both cases, the subscriber can lookup into the hierarchy of "tasks" that produced an announcement. MartÃn On Sat, Jun 13, 2015 at 8:06 AM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Hi Eliot, > > Le 13/06/2015 06:54, Eliot Miranda a Ã©crit : > >> Hi Thierry, >> >> On Jun 11, 2015, at 8:16 AM, Thierry Goubier <thierry.goubier(a)gmail.com >> <mailto:thierry.goubier@gmail.com>> wrote: >> >> >>> >>> 2015-06-11 16:49 GMT+02:00 Ben Coman <btc(a)openinworld.com >>> <mailto:btc@openinworld.com>>: >>> >>> >>> Just a *very* divergent thought that I'm not sure is a good idea... >>> maybe the parent announcement could hold the announcer of its >>> children. >>> >>> >>> The problem is then that all tools which are not interested in the >>> parent announcement because they only deal with the low level stuff >>> (system browser, RPackageOrganizer and friends: MessageList, Spotter, >>> Critics browser, Finder, Versionner, Inspector, anything which listen >>> to a code change basically) have to still listen to the parent and, on >>> reception, subscribe to the low-level announcement, and then >>> unsubscribe on the parent end announcement. >>> >> >> It seems to me that with Ben's suggestion there need only be the >> low-level announcement, and that subscribers interested in the >> higher-level context could fetch it by asking the announcement for its >> context. >> > > I reacted to the fact Ben said announcer, not announcement... > Reregistering announcers in code-aware tools is not something you do often > [1] > > One aspect I forgot is the performance issues linked with announcements. > On package loads, a huge number of announcements is generated, and just > simple things like tracking those to refresh the display of a system > browser needs to be optimised to avoid degrading performance significantly. > > Thierry > > [1] > https://github.com/ThierryGoubier/AltBrowser/blob/pharo5/Alt-Browser.packag… > >

June 17, 2015