November 2014 - Pharo-dev - lists.pharo.org

contributing to Pharo testing effort

by sheridan＠sheridan-mahoney.com

Hi there, I am interested in helping out with writing tests in Pharo, and was wondering where would be a good place to start. I am familiar with Smalltalk from working at GemStone Systems in their QA department some years ago, but am somewhat new to Pharo. Any advice would be very appreciated. Best regards, Sheridan Mahoney

Nov. 23, 2014

Re: [Pharo-dev] About RBCompiler

by Marcus Denker

> On 23 Nov 2014, at 17:37, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > On Sun, Nov 23, 2014 at 10:13 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >>> On 22 Nov 2014, at 18:17, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: >>> >>> I'm trying to port QuasiQuote package from Lukas Renggli to Pharo 3.0/4.0. >>> This package use the RBCompiler class from the AST-Compiler package >>> available here: >>> http://source.lukas-renggli.ch/helvetia >>> >>> If I understand RBCompiler, this is a Compiler that use RB parser nodes. >>> I guess this is something that is no more relevant with the new Opal compiler ? >>> >> >> Yes, this is the PetitParser based Smalltalk parser that created RB ParseNodes. >> >> Opal has a pluggable architecture for the parser, right now it just uses the hand-written >> RB Parser that came with the refactoring browser. > > > Ok, thank you for the explanation, Markus. > I'm able to parse Smalltalk code containing QuasiQuote and generate an > RB parsenodes AST. > How I can plug my AST tree to generate IR and bytecodes ? You can just as it to generate a CompileMethod with #compiledMethod (if you access e.g. ivars and the method was not compiled for a specific class yet, you might need to #doSemanticAnalysisIn: before) Marcus

Nov. 23, 2014

Re: [Pharo-dev] About RBCompiler

by Serge Stinckwich

On Sun, Nov 23, 2014 at 10:13 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> On 22 Nov 2014, at 18:17, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: >> >> I'm trying to port QuasiQuote package from Lukas Renggli to Pharo 3.0/4.0. >> This package use the RBCompiler class from the AST-Compiler package >> available here: >> http://source.lukas-renggli.ch/helvetia >> >> If I understand RBCompiler, this is a Compiler that use RB parser nodes. >> I guess this is something that is no more relevant with the new Opal compiler ? >> > > Yes, this is the PetitParser based Smalltalk parser that created RB ParseNodes. > > Opal has a pluggable architecture for the parser, right now it just uses the hand-written > RB Parser that came with the refactoring browser. Ok, thank you for the explanation, Markus. I'm able to parse Smalltalk code containing QuasiQuote and generate an RB parsenodes AST. How I can plug my AST tree to generate IR and bytecodes ? -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Nov. 23, 2014

Re: [Pharo-dev] [ANN] Nireas - a theme manager for Pharo 4

by kilon alios

yeap as I said I am still learning it but I think at least now I get the basics. My problem is that my class even though it was only 6 buttons and 6 morphs has a lot more methods and I dont know if I do this the best way possible. But there is no rush, I will go back to reading all the available documentation and study closely the source code of Spec. On Sun, Nov 23, 2014 at 2:19 PM, stepharo <stepharo(a)free.fr> wrote: > Cool. > I have on my huge todo to revisit the SPec chapter and clean the api too > :). > So it is nice to get more people using Spec. > > stef > Le 23/11/14 13:11, kilon alios a Ã©crit : > > Hello pharoers , I would like to present to you my latest project and a >> good excuse to learn Spec. First I would like to thank Nicolai for his help >> and all other people who helped me out understand Spec. Of course I am >> still learning :) >> >> So , Nireas is a theme manager for Pharo 4. What this means is that >> Nireas takes the dark theme and by presenting you with an easy to use gui >> allows you to change the colors on the fly to adjust the theme to your own >> preferences and habits. >> >> This is an example >> >> https://www.dropbox.com/s/w3c72lz0r81v4iv/Screenshot% >> 202014-11-23%2013.53.01.png?dl=0 >> >> you can see the Nireas GUI on the bottom, the Nautilus on the left has >> the default dark theme colors, the one on the right has the color selected >> by Nireas. >> >> You can find instructions on how to install Nireas and how to use here >> >> https://github.com/kilon/Nireas >> >> Unfortunately the last one the scroll bar color seems to have no effect, >> I will have to look into it, but the other options work fine. Please note >> also that you will have refresh issues so its advisable to close existing >> windows and reopen them so they update properly to the new colors. >> >> Please try this tool inside a new fresh pharo 4 image, this code is very >> experimental and has been known to crash Morphic. So use with caution. >> >> Nireas implements its own theme subclassing the dark theme, the big >> diffirence here is that it defines color to be independent and dynamic so >> the theme can be , well, .... themable :D >> >> Nireas does not change anything inside Pharo so it can be installed >> safely. >> >> I would like to take this tool further to allow of course deeper >> customisations that goes beyond just customising colors, meaning change the >> look and feel of Pharo. But this means unfortunately/fortunately that some >> things will have to change inside Pharo and Pharo will have to become much >> more dynamic GUI wise to make dynamic themes much easier to implement. >> >> Nireas is part of my Ephestos project, so this is why it appears inside >> an Ephestos menu and hopefully I will keep working it as customising Pharo >> GUI is something that I find really interesting and fun, >> >> As always comments, insults, worship and rage is more than welcomed. >> > > >

Nov. 23, 2014

Re: [Pharo-dev] Duration year

by James Foster

More precisely, 365.242199 (http://www.timeanddate.com/date/leapyear.html) > On Nov 22, 2014, at 3:03 AM, Hilaire <hilaire(a)drgeo.eu> wrote: > > I saw some discussion about Duration and year calculus in the list > > Given that it is impossible to determine the number of days in a year > without the calendar years, should not 365.25 be used in place of 365 to > minimize the error ? > > So it could look like: > > Duration class >> years: aNumber > ^ self days: (aNumber * 365.25) truncated seconds: 0 > > > Hilaire > > -- > Dr. Geo - http://drgeo.eu > iStoa - http://istoa.drgeo.eu > > >

Nov. 23, 2014

Re: [Pharo-dev] Listening for shift key pressed

by Ben Coman

Aliaksei Syrel wrote: > Hi, Nicolai > > Thanks for suggestion. I'm using Mac 10.10 and it doesn't show any > notifications for shift.. > I'll open an issue for this. > > Cheers, > Alex Hi Alex, Did you open an issue? I can't find it. I've made some progress getting it working and would like to document this for review. cheers -ben > > On Fri, Nov 21, 2014 at 10:20 PM, Nicolai Hess <nicolaihess(a)web.de > <mailto:nicolaihess@web.de>> wrote: > > If you look at KeyPrinterMorph you'll see that it indeed handles a > single shift key down. > > 2014-11-21 17:36 GMT+01:00 Aliaksei Syrel <alex.syrel(a)gmail.com > <mailto:alex.syrel@gmail.com>>: > > Hi Ben, > > If at the end of InputEventFetcher>>__waitForInput > you put "Transcript crShow: Time now" > and I think you'll be looking at as raw an event aas you can > get. > > > Now this exhibits some strange behaviour? Pushing <shift> > on its own does not produce an event, however pushing > <shift> fast multiple times does generate events. ??? > > It's maybe because you move mouse, or randomly touch touchpad. > > After some investigations and digging lower and lower till > primitive methods, I realized that VM itself doesn't queue an > event after user presses Shift. It's just a modifier bit, that > is applied on a real events, such as mouse moves or normal > keyboard events. > > Cheers, > Alex > > > >

Nov. 23, 2014

Re: [Pharo-dev] Duration year

by Mark Bestley

On 22/11/2014 11:03, Hilaire wrote: > I saw some discussion about Duration and year calculus in the list > > Given that it is impossible to determine the number of days in a year > without the calendar years, should not 365.25 be used in place of 365 to > minimize the error ? > > So it could look like: > > Duration class >> years: aNumber > ^ self days: (aNumber * 365.25) truncated seconds: 0 > > I think it depends :) What use do you want to make of the answer. If for loan, bank or mortgage calculations then you need the days and adjustments and other info. If for tens of years it might work If to know the number of days it needs to be an integer. There is no one correct solution -- Mark

Nov. 23, 2014

Re: [Pharo-dev] [ANN] Nireas - a theme manager for Pharo 4

by stepharo

Cool. I have on my huge todo to revisit the SPec chapter and clean the api too :). So it is nice to get more people using Spec. stef Le 23/11/14 13:11, kilon alios a Ã©crit : > Hello pharoers , I would like to present to you my latest project and > a good excuse to learn Spec. First I would like to thank Nicolai for > his help and all other people who helped me out understand Spec. Of > course I am still learning :) > > So , Nireas is a theme manager for Pharo 4. What this means is that > Nireas takes the dark theme and by presenting you with an easy to use > gui allows you to change the colors on the fly to adjust the theme to > your own preferences and habits. > > This is an example > > https://www.dropbox.com/s/w3c72lz0r81v4iv/Screenshot%202014-11-23%2013.53.0… > > you can see the Nireas GUI on the bottom, the Nautilus on the left has > the default dark theme colors, the one on the right has the color > selected by Nireas. > > You can find instructions on how to install Nireas and how to use here > > https://github.com/kilon/Nireas > > Unfortunately the last one the scroll bar color seems to have no > effect, I will have to look into it, but the other options work fine. > Please note also that you will have refresh issues so its advisable to > close existing windows and reopen them so they update properly to the > new colors. > > Please try this tool inside a new fresh pharo 4 image, this code is > very experimental and has been known to crash Morphic. So use with > caution. > > Nireas implements its own theme subclassing the dark theme, the big > diffirence here is that it defines color to be independent and dynamic > so the theme can be , well, .... themable :D > > Nireas does not change anything inside Pharo so it can be installed > safely. > > I would like to take this tool further to allow of course deeper > customisations that goes beyond just customising colors, meaning > change the look and feel of Pharo. But this means > unfortunately/fortunately that some things will have to change inside > Pharo and Pharo will have to become much more dynamic GUI wise to make > dynamic themes much easier to implement. > > Nireas is part of my Ephestos project, so this is why it appears > inside an Ephestos menu and hopefully I will keep working it as > customising Pharo GUI is something that I find really interesting and > fun, > > As always comments, insults, worship and rage is more than welcomed.

Nov. 23, 2014

Re: [Pharo-dev] cull: equivalent for valueWithArguments:

by stepharo

thanks sven I will digest that. One day I will have to avoid using block in my tiny language exercise. Stef Le 22/11/14 21:03, Sven Van Caekenberghe a Ã©crit : >> On 22 Nov 2014, at 20:50, stepharo <stepharo(a)free.fr> wrote: >> >> Hi guys >> >> What would be cull: equivalent for valueWithArguments:? >> >> I need to be able to specify an extra argument to valueWithArguments >> valueWithArgument:cull:? >> >> Stef > The different variants/counts of #cull: come down to specifying one to four arguments to block evaluation/execution where the actual arguments (the count of them) is defined by the block, right ? > > So I think it should be #cullWithArguments: where the number actually used is defined by the number accepted by the block. > > I see that we already have #valueWithEnoughArguments: > > [ :x :y | { x. y } ] valueWithEnoughArguments: #( 1 2 ). => #(1 2) > > [ :x | { x } ] valueWithEnoughArguments: #( 1 2 ). => #(1) > > [ ] valueWithEnoughArguments: #( 1 2 ). => nil > > Which seems to do the same thing. > > Sven > > >

Nov. 23, 2014

[ANN] Nireas - a theme manager for Pharo 4

by kilon alios

Hello pharoers , I would like to present to you my latest project and a good excuse to learn Spec. First I would like to thank Nicolai for his help and all other people who helped me out understand Spec. Of course I am still learning :) So , Nireas is a theme manager for Pharo 4. What this means is that Nireas takes the dark theme and by presenting you with an easy to use gui allows you to change the colors on the fly to adjust the theme to your own preferences and habits. This is an example https://www.dropbox.com/s/w3c72lz0r81v4iv/Screenshot%202014-11-23%2013.53.0… you can see the Nireas GUI on the bottom, the Nautilus on the left has the default dark theme colors, the one on the right has the color selected by Nireas. You can find instructions on how to install Nireas and how to use here https://github.com/kilon/Nireas Unfortunately the last one the scroll bar color seems to have no effect, I will have to look into it, but the other options work fine. Please note also that you will have refresh issues so its advisable to close existing windows and reopen them so they update properly to the new colors. Please try this tool inside a new fresh pharo 4 image, this code is very experimental and has been known to crash Morphic. So use with caution. Nireas implements its own theme subclassing the dark theme, the big diffirence here is that it defines color to be independent and dynamic so the theme can be , well, .... themable :D Nireas does not change anything inside Pharo so it can be installed safely. I would like to take this tool further to allow of course deeper customisations that goes beyond just customising colors, meaning change the look and feel of Pharo. But this means unfortunately/fortunately that some things will have to change inside Pharo and Pharo will have to become much more dynamic GUI wise to make dynamic themes much easier to implement. Nireas is part of my Ephestos project, so this is why it appears inside an Ephestos menu and hopefully I will keep working it as customising Pharo GUI is something that I find really interesting and fun, As always comments, insults, worship and rage is more than welcomed.

Nov. 23, 2014