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

Re: [Pharo-dev] Who changed the meaning of command-click on class names ?

by Torsten Bergmann

Not unimportant side note: >From what I see from Nicolai's high activity in bug tracker and here on the list he is someone who closely watches the included changes and fixes/reviews issues. This quickly helps making progress. @Nicolai: big thanks from my side! Â Bye T.Â Gesendet:Â Dienstag, 16. Juni 2015 um 10:44 Uhr Von:Â "Nicolai Hess" <nicolaihess(a)web.de> An:Â "Pharo Development List" <pharo-dev(a)lists.pharo.org> Betreff:Â Re: [Pharo-dev] Who changed the meaning of command-click on class names ? Â Â 2015-06-16 10:15 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>:Hi, In Pharo 5, the meaning of command-click (apple-click) on class names changed from 'Browse class' to 'References to class'. On selectors it still is 'Implementors'. Why was this done ? Was this done intentionally or by accident, as a side effect of some other change ? Â By accident, please open an issue. (caused by 15575 AST syntax highlight: clean up variable resolving a bit ) Â I rely on it a lot and I think the old behaviour should be restored. Sven Â

June 16, 2015

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

by Henrik Johansen

> On 16 Jun 2015, at 9:58 , Matthieu Lacaton <matthieu.lacaton(a)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 16, 2015

Re: [Pharo-dev] Who changed the meaning of command-click on class names ?

by Sven Van Caekenberghe

> On 16 Jun 2015, at 12:05, Stephan Eggermont <stephan(a)stack.nl> wrote: > > On 16-06-15 10:15, Sven Van Caekenberghe wrote: >> In Pharo 5, the meaning of command-click (apple-click) on class names changed from 'Browse class' to 'References to class'. On selectors it still is 'Implementors'. > > Interesting. How and where exactly is that supposed to work? On Linux, that works in neither Pharo 4 nor 5. Are you sure ? Did you try ctrl and alt with a click ? Maybe something with shift ? > We have way too much hidden functionality Yes we do. But it is still better to have the functionality ;-) > Stephan Sven

June 16, 2015

Re: [Pharo-dev] Who changed the meaning of command-click on class names ?

by Stephan Eggermont

On 16-06-15 10:15, Sven Van Caekenberghe wrote: > In Pharo 5, the meaning of command-click (apple-click) on class names changed from 'Browse class' to 'References to class'. On selectors it still is 'Implementors'. Interesting. How and where exactly is that supposed to work? On Linux, that works in neither Pharo 4 nor 5. We have way too much hidden functionality Stephan

June 16, 2015

Location of SDL2 library

by Matthieu Lacaton

Hello, I am currently using Archlinux and I don't have the SDL2 library loaded into my system. Yesterday I downloaded the latest Pharo 5 vm and image thanks to the zeroconf scripts. When I tried to call "OSSDL2Driver hasPlugin" the return was "false" with the following message console : > ioLoadModule(.../pharo-vm/libSDL2DisplayPlugin.so): > libSDL2-2.0.so.0: cannot open shared object file: No such file or directory The library itself (libSDL2-2.0.so.0) is located in the pharo-vm folder, however it seems that the vm is looking for it somewhere else because after copying the file in /usr/lib32/ the VM was able to find it correctly. I was wondering : shouldn't the vm only rely on the SDL2 library inside pharo-vm folder ? Thanks, Matthieu

June 16, 2015

Re: [Pharo-dev] Who changed the meaning of command-click on class names ?

by Sven Van Caekenberghe

> On 16 Jun 2015, at 10:44, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > 2015-06-16 10:15 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > Hi, > > In Pharo 5, the meaning of command-click (apple-click) on class names changed from 'Browse class' to 'References to class'. On selectors it still is 'Implementors'. > > Why was this done ? Was this done intentionally or by accident, as a side effect of some other change ? > > By accident, please open an issue. (caused by 15575 AST syntax highlight: clean up variable resolving a bit ) https://pharo.fogbugz.com/f/cases/15778/The-meaning-of-command-click-apple-… Thanks for the quick response. > I rely on it a lot and I think the old behaviour should be restored. > > Sven > > >

June 16, 2015

Re: [Pharo-dev] Who changed the meaning of command-click on class names ?

by Nicolai Hess

2015-06-16 10:15 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > Hi, > > In Pharo 5, the meaning of command-click (apple-click) on class names > changed from 'Browse class' to 'References to class'. On selectors it still > is 'Implementors'. > > Why was this done ? Was this done intentionally or by accident, as a side > effect of some other change ? > By accident, please open an issue. (caused by 15575 AST syntax highlight: clean up variable resolving a bit ) > > I rely on it a lot and I think the old behaviour should be restored. > > Sven > > >

June 16, 2015

Who changed the meaning of command-click on class names ?

by Sven Van Caekenberghe

Hi, In Pharo 5, the meaning of command-click (apple-click) on class names changed from 'Browse class' to 'References to class'. On selectors it still is 'Implementors'. Why was this done ? Was this done intentionally or by accident, as a side effect of some other change ? I rely on it a lot and I think the old behaviour should be restored. Sven

June 16, 2015

Question about API / Backend

by Matthieu Lacaton

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

June 16, 2015

Tour de Spur

by Torsten Bergmann

There is a tour through the Spur code with Eliot, Craig and Matthias via a skype meeting on Wednesday morning (9am PST). It will be recorded but maybe you want to connect directly. Read more on the vm-dev list thread http://lists.squeakfoundation.org/pipermail/vm-dev/2015-June/018819.html Bye T.

June 16, 2015