- Pharo-dev - lists.pharo.org

method return-typing (was Re: Date&Time api)

by Ben Coman

> On Tue, Aug 18, 2015 at 1:21 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >> Hi, >> >> there are some weird things around the data & time API. So time-related >> classes are using methods like #asNanoSeconds. And numbers do not implements >> it. But they do implement methods as #nanoSeconds, #milliSeconds, #seconds >> and #asSeconds. Of course "5 nanoSecondsâ are nicer than â5 asNanoSecondsâ. >> Maybe we can do something to maintain polymorphism? >> >> Uko On Wed, Aug 19, 2015 at 3:21 AM, Chris Cunningham <cunningham.cb(a)gmail.com> wrote: > To, #asNanoSeconds converts the time into the umber of nanosecond that the > time represents. > #nanoSeconds (and the others) create a duration that is to be added to the > time or DateAndTime. The two do not end with the same things 0 and > shouldin't. > > The first tells you how many they represent; the second builds duration. > > Probably not ideal names - but the intents are definitely different. > > -cbc That is a fine distinction, and relatively hidden from someone reading application code. So the follow up question is how to make such distinction visible to an application developer. It would be nice to hover over a message send to get a popup showing the "type" returned and messages available. From time to time I consider what Smalltalk might be like where the return-type of a method is specified (i.e. only the method return type, still not typing variables). Anyone know of a programming language like that? Return-typing might facilitate: * Static analysis making a return-type hover popup simple. * Static analysis of cascade message sends. * Definition of global conventions that a particular message always returns a particular type, with automatic checking. Runtime violations might be logged full-time, or only when running unit tests. The message return-type effectively becomes an interface definition and the methods the implementation. A return type might be: * a class * a trait * a more narrowly defined "protocol" subset of messages, which might help with static analysis for modularisation and minimising the bootstrap. cheers -ben btw, I notice... * Number>>nanoSeconds returns a Duration, * Duration>>nanoSeconds returns an Integer. Should the latter be renamed #asNanoSeconds, or perhaps #nanos in line with its instance variable? Indeed, perhaps all #asNanoSeconds should be renamed #nanos, since its not converting to a NanoSeconds class. If its being converted to a raw integer, presumably the context of its usage will remain apparent plus the developer will have to subsequently mange that.

Aug. 19, 2015

[Smalltalks 2015] --- Invitation

by Andres Valloud

The FundaciÃ³n Argentina de Smalltalk proudly invites you to one of the premier Smalltalk conferences in the world. Let's meet at Buenos Aires, November 11-13! For more details, see the invitation here: http://www.fast.org.ar/Smalltalks2015-invitation.pdf

Aug. 19, 2015

Re: [Pharo-dev] Nautilus questions

by HernÃ¡n Morales Durand

2015-08-18 17:49 GMT-03:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > Actually two buttons I miss from Squeak is implementers and senders which > I found super useful. > > Absolutely, visible senders and implementors buttons are fundamental. HernÃ¡n > On Tue, Aug 18, 2015 at 11:00 PM Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > >> Hi, >> >> maybe I'm too picky, but I have couple of questions/remarks regarding >> current Nautilus UI. >> Now, I'm happy that new features were added/reorganized, but it does feel >> it is a little bit chaotic right now. >> >> >> I would expect the left/right history buttons being right next to the >> History Navigator selector. That way history-related controls are together >> and the purpose of the buttons is obvious >> >> "Hier.", "Com."... abbreviating button labels? Really? >> >> âAnd finally, why was part of the buttons moved up? And part stayed down? >> I know that you wanted to distinguish "Scoped", because it opens a new >> browser, and Variables, because they have intermediate menu (and later open >> another menu). >> But I think the fact that Variables are tied to a particular selected >> class would make much more sense to place the button beside hierachy/class >> button. >> >> And opening Scoped can be denoted with an appropriate icon ( >> https://www.google.com/search?site=&tbm=isch&source=hp&biw=&bih=&q=new+wind… >> ) >> >> Placing them all on a single line would also save up vertical space, >> which considering we've added QualityAssistant and Rubric adds another line >> is quite valuable. >> >> (And finally the width of the buttons should perhaps match more closely >> the actual needs of the label, because now it's bit cramped.) >> >> >> â >> And finally, code-wise I've never really interacted with Morphic and >> stayed in Spec, so when I was digging through code it seems that the way >> Morphs are composed are through these "addMorph:fullFrame: (LayoutFrame >> identity rightFraction: 0.10; yourself);" constructs sprinkled haphazardly >> throughout the code. Is there nothing like SpecLayout? Maybe it wasn't so >> hard once you get used to Morphic, because I spent probably more time doing >> elementary changes to layout than learning half of Spec... (Also since Spec >> can interoperate with Morphic, maybe the layout could also be adapted? Or >> slowly migrate Nautilus to Spec (if there are even plans like that)?) >> >> Now as I've mentioned I'm not an UI/UX expert, but you don't need to be a >> chef to tell when food isn't great (which is of course amplified by >> personal tastes). >> >> So unless I am the only person bothered by this, I would like to raise a >> discussion (or send a slice, but the way I've done the layout weirds me >> out, so I still want to look into that regardless). >> >> Cheers, >> Peter >> >>

Aug. 19, 2015

Re: [Pharo-dev] WhatsUp from: 2015-08-17 until: 2015-08-31

by Merwan Ouddane

On 18/08/2015 23:00, Dimitris Chloupis wrote: > 1) bringing more Python support for Pharo, now I have added support > for python and blender types to be automagically converted to pharo > objects . Used and learn SmaCC. > 2) Gave a deep reading on Pharo auto completion. > 3) Study how Playgrounds draws its GUI to improve it by making far > more flexible. > 4) Study a new programming language Nim , for making dynamic libraries > for pharo , replacing C/C++. Possible scenario of porting SqueakNim to > Pharo. > > To Do > > 1) Improve my blue theme (Nireas) > 2) Create an API for Blender for Pharo Blender ? This one: https://www.blender.org/features/ ? > 3) Create my own custom Playground which will be more powerful > 4) Integrate Nim with Pharo > > On Tue, Aug 18, 2015 at 6:23 PM Sean P. DeNigris > <sean(a)clipperadams.com <mailto:sean@clipperadams.com>> wrote: > > ### Here's what I've been up to since the last WhatsUp: > - Ported Moose issue tracker to GitHub > - GT extension for presentations semi-auto-generated from Magritte > descriptions > - data, label, etc pre-filled by default > - Magritte actions appear as e.g. presentation list selection > context menu > - Magritte > - extension for above > - many little fixes and enhancements > - [WIP]: Created Glamour browsers from presentations > - Glamour/GT patches > - GSoC Mentoring for sQuick Smalltalk project > > ### What's next, until 2015-08-31 (*): > - Camp Smalltalk Portland! > > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/WhatsUp-from-2015-08-17-until-2015-08-31-tp4843391p48… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. >

Aug. 18, 2015

Re: [Pharo-dev] WhatsUp from: 2015-08-17 until: 2015-08-31

by Dimitris Chloupis

1) bringing more Python support for Pharo, now I have added support for python and blender types to be automagically converted to pharo objects . Used and learn SmaCC. 2) Gave a deep reading on Pharo auto completion. 3) Study how Playgrounds draws its GUI to improve it by making far more flexible. 4) Study a new programming language Nim , for making dynamic libraries for pharo , replacing C/C++. Possible scenario of porting SqueakNim to Pharo. To Do 1) Improve my blue theme (Nireas) 2) Create an API for Blender for Pharo 3) Create my own custom Playground which will be more powerful 4) Integrate Nim with Pharo On Tue, Aug 18, 2015 at 6:23 PM Sean P. DeNigris <sean(a)clipperadams.com> wrote: > ### Here's what I've been up to since the last WhatsUp: > - Ported Moose issue tracker to GitHub > - GT extension for presentations semi-auto-generated from Magritte > descriptions > - data, label, etc pre-filled by default > - Magritte actions appear as e.g. presentation list selection context > menu > - Magritte > - extension for above > - many little fixes and enhancements > - [WIP]: Created Glamour browsers from presentations > - Glamour/GT patches > - GSoC Mentoring for sQuick Smalltalk project > > ### What's next, until 2015-08-31 (*): > - Camp Smalltalk Portland! > > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/WhatsUp-from-2015-08-17-until-2015-08-31-tp4843391p48… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Aug. 18, 2015

Re: [Pharo-dev] Nautilus questions

by Dimitris Chloupis

I agree with your post about the buttons. Personally I have never used scoped or really need it as feature , I dont think I would be needing variables either. Actually two buttons I miss from Squeak is implementers and senders which I found super useful. On Tue, Aug 18, 2015 at 11:00 PM Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Hi, > > maybe I'm too picky, but I have couple of questions/remarks regarding > current Nautilus UI. > Now, I'm happy that new features were added/reorganized, but it does feel > it is a little bit chaotic right now. > > > I would expect the left/right history buttons being right next to the > History Navigator selector. That way history-related controls are together > and the purpose of the buttons is obvious > > "Hier.", "Com."... abbreviating button labels? Really? > > âAnd finally, why was part of the buttons moved up? And part stayed down? > I know that you wanted to distinguish "Scoped", because it opens a new > browser, and Variables, because they have intermediate menu (and later open > another menu). > But I think the fact that Variables are tied to a particular selected > class would make much more sense to place the button beside hierachy/class > button. > > And opening Scoped can be denoted with an appropriate icon ( > https://www.google.com/search?site=&tbm=isch&source=hp&biw=&bih=&q=new+wind… > ) > > Placing them all on a single line would also save up vertical space, which > considering we've added QualityAssistant and Rubric adds another line is > quite valuable. > > (And finally the width of the buttons should perhaps match more closely > the actual needs of the label, because now it's bit cramped.) > > > â > And finally, code-wise I've never really interacted with Morphic and > stayed in Spec, so when I was digging through code it seems that the way > Morphs are composed are through these "addMorph:fullFrame: (LayoutFrame > identity rightFraction: 0.10; yourself);" constructs sprinkled haphazardly > throughout the code. Is there nothing like SpecLayout? Maybe it wasn't so > hard once you get used to Morphic, because I spent probably more time doing > elementary changes to layout than learning half of Spec... (Also since Spec > can interoperate with Morphic, maybe the layout could also be adapted? Or > slowly migrate Nautilus to Spec (if there are even plans like that)?) > > Now as I've mentioned I'm not an UI/UX expert, but you don't need to be a > chef to tell when food isn't great (which is of course amplified by > personal tastes). > > So unless I am the only person bothered by this, I would like to raise a > discussion (or send a slice, but the way I've done the layout weirds me > out, so I still want to look into that regardless). > > Cheers, > Peter > >

Aug. 18, 2015

Re: [Pharo-dev] World Menu associated mouse click

by Dimitris Chloupis

and what about the existing right click menu for selecting morphs ? On Tue, Aug 18, 2015 at 8:09 PM Ben Coman <btc(a)openinworld.com> wrote: > Opened issue with fix - https://pharo.fogbugz.com/default.asp?16265 > > On Wed, Aug 19, 2015 at 12:13 AM, Ben Coman <btc(a)openinworld.com> wrote: > >>>>> -----Message d'origine----- > >>>>> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la > part de > >>>>> Ben Coman > >>>>> A while back on reddit someone complained about the World Menu being > >>>>> associated with left-mouse-click. I have come to agree. The World > Menu > >>>>> provides the actions available in the context of the World, i.e. > >>>>> the World's context-menu - but its not invoked by the usual > convention > >>>>> for context menus, which is the right-mouse-click. > >>>>> > >>>>> By way of example, in a fresh image and open one Playground. > >>>>> > >>>>> * First right-click the Playground. Up comes the Playground's > >>>>> context-menu as expected per industry wide conventions. > >>>>> > >>>>> * Then right-click the background. Doh! Its not consistent, thats not > >>>>> the World's context-menu. "WTH is that?" says a newbie in surprise. > >>>>> (Btw, who uses that list of open windows ? I *never* do and might > >>>>> suggest that function be moved to a meta-mouse-click.) > >>>>> > >>>>> So can we discuss changing the World Menu to be invoked by the > >>>>> context-click (i.e. right-click) ? > >>>>> > >>>>> cheers -ben > >

Aug. 18, 2015

Nautilus questions

by Peter UhnÃ¡k

Hi, maybe I'm too picky, but I have couple of questions/remarks regarding current Nautilus UI. Now, I'm happy that new features were added/reorganized, but it does feel it is a little bit chaotic right now. I would expect the left/right history buttons being right next to the History Navigator selector. That way history-related controls are together and the purpose of the buttons is obvious "Hier.", "Com."... abbreviating button labels? Really? âAnd finally, why was part of the buttons moved up? And part stayed down? I know that you wanted to distinguish "Scoped", because it opens a new browser, and Variables, because they have intermediate menu (and later open another menu). But I think the fact that Variables are tied to a particular selected class would make much more sense to place the button beside hierachy/class button. And opening Scoped can be denoted with an appropriate icon ( https://www.google.com/search?site=&tbm=isch&source=hp&biw=&bih=&q=new+wind… ) Placing them all on a single line would also save up vertical space, which considering we've added QualityAssistant and Rubric adds another line is quite valuable. (And finally the width of the buttons should perhaps match more closely the actual needs of the label, because now it's bit cramped.) â And finally, code-wise I've never really interacted with Morphic and stayed in Spec, so when I was digging through code it seems that the way Morphs are composed are through these "addMorph:fullFrame: (LayoutFrame identity rightFraction: 0.10; yourself);" constructs sprinkled haphazardly throughout the code. Is there nothing like SpecLayout? Maybe it wasn't so hard once you get used to Morphic, because I spent probably more time doing elementary changes to layout than learning half of Spec... (Also since Spec can interoperate with Morphic, maybe the layout could also be adapted? Or slowly migrate Nautilus to Spec (if there are even plans like that)?) Now as I've mentioned I'm not an UI/UX expert, but you don't need to be a chef to tell when food isn't great (which is of course amplified by personal tastes). So unless I am the only person bothered by this, I would like to raise a discussion (or send a slice, but the way I've done the layout weirds me out, so I still want to look into that regardless). Cheers, Peter

Aug. 18, 2015

Re: [Pharo-dev] Date&Time api

by Chris Cunningham

To, #asNanoSeconds converts the time into the umber of nanosecond that the time represents. #nanoSeconds (and the others) create a duration that is to be added to the time or DateAndTime. The two do not end with the same things 0 and shouldin't. The first tells you how many they represent; the second builds duration. Probably not ideal names - but the intents are definitely different. -cbc On Tue, Aug 18, 2015 at 1:21 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Hi, > > there are some weird things around the data & time API. So time-related > classes are using methods like #asNanoSeconds. And numbers do not > implements it. But they do implement methods as #nanoSeconds, > #milliSeconds, #seconds and #asSeconds. Of course "5 nanoSecondsâ are nicer > than â5 asNanoSecondsâ. Maybe we can do something to maintain polymorphism? > > Uko >

Aug. 18, 2015

Re: [Pharo-dev] World Menu associated mouse click

by Ben Coman

Opened issue with fix - https://pharo.fogbugz.com/default.asp?16265 On Wed, Aug 19, 2015 at 12:13 AM, Ben Coman <btc(a)openinworld.com> wrote: >>>>> -----Message d'origine----- >>>>> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de >>>>> Ben Coman >>>>> A while back on reddit someone complained about the World Menu being >>>>> associated with left-mouse-click. I have come to agree. The World Menu >>>>> provides the actions available in the context of the World, i.e. >>>>> the World's context-menu - but its not invoked by the usual convention >>>>> for context menus, which is the right-mouse-click. >>>>> >>>>> By way of example, in a fresh image and open one Playground. >>>>> >>>>> * First right-click the Playground. Up comes the Playground's >>>>> context-menu as expected per industry wide conventions. >>>>> >>>>> * Then right-click the background. Doh! Its not consistent, thats not >>>>> the World's context-menu. "WTH is that?" says a newbie in surprise. >>>>> (Btw, who uses that list of open windows ? I *never* do and might >>>>> suggest that function be moved to a meta-mouse-click.) >>>>> >>>>> So can we discuss changing the World Menu to be invoked by the >>>>> context-click (i.e. right-click) ? >>>>> >>>>> cheers -ben

Aug. 18, 2015