February 2015 - Pharo-users

Re: [Pharo-users] get them while they are young

by Sven Van Caekenberghe

Nice! > On 11 Feb 2015, at 08:58, Martin BÃ¤hr <mbaehr(a)email.archlab.tuwien.ac.at> wrote: > > here is the reaction of a student preparing for a GSoC project for which the > student needs to learn smalltalk: > > "I have installed Pharo v4.0 and started the book Pharo By Example as > suggested by you .... I just wanted to say that I am in the initial stages > and loving it already :)" > > greetings, martin. > > -- > eKita - the online platform for your entire academic life > -- > chief engineer eKita.co > pike programmer pike.lysator.liu.se caudium.net societyserver.org > secretary beijinglug.org > mentor fossasia.org > foresight developer foresightlinux.org realss.com > unix sysadmin > Martin BÃ¤hr working in china http://societyserver.org/mbaehr/ >

Feb. 11, 2015

get them while they are young

by Martin BÃ¤hr

here is the reaction of a student preparing for a GSoC project for which the student needs to learn smalltalk: "I have installed Pharo v4.0 and started the book Pharo By Example as suggested by you .... I just wanted to say that I am in the initial stages and loving it already :)" greetings, martin. -- eKita - the online platform for your entire academic life -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net societyserver.org secretary beijinglug.org mentor fossasia.org foresight developer foresightlinux.org realss.com unix sysadmin Martin BÃ¤hr working in china http://societyserver.org/mbaehr/

Feb. 11, 2015

Re: [Pharo-users] SmaCC: First steps

by kilon alios

Ok so after rereading the tutorial and testing again and again , I think I have finally managed to understand how SmaCC really works and I was succesful into converting simple python litsts to pharo arrays and ordered collections. The tricky part now is to apply this knowledge to complex python types like multi dimensional lists, tuples and dictionaries. I understand that the visitor allows me to visit a specific object instances each time they are found in the AST . But because I want to walk the AST in order to build multi dimensional ordered collections I need something more, or maybe my understanding of the visitor pattern is flawed. The problem I am having here is that each time I parse a python type that python type is not necessarily represented by different kind of node. For example whether its a list or a tuple or a dictionary the same class is used PyAtomNode. In order to differentiate between those diffirent python types PyAtomNode has instance variables for right and left bracket, parantheses, and curly. So my initial thinking is to check those instance variables to see if they are nil and from that I can conclude which python type I am parsing. So I can preform simple ifs that check that the instance variable is Nil or not but the question is if my strategy is a good one or a bad one. I could define my own syntax to simplify the AST tree including different nodes for different python types , because from the looks of it , it seems it is a bit too verbose for my needs but On the other hand I am not so sure because in the future my needs may become more verbose too. So I am very close and ready to create my full python types converter for pharo but I wanted some good advice before wasting time on something that is not efficient. By the way Thierry I have to agree with you Smacc is a very capable parser, also I like the use of regex syntax, makes it uglier compared Pettit Parser but I prefer the compact regex syntax to having to define and browse tons of classes and send tons of messages. Also the Python support is very good and I am impressed how easily SmaCC can parse whole python applications since some of the test are very complex. Well done great work! On Sat, Jan 31, 2015 at 12:04 AM, kilon alios <kilon.alios(a)gmail.com> wrote: > thank for your congratulations, because at times I fear I ask too obvious > questions. I have to say I find this parsing very complex but very > fascinating too :) Time to experiment with the visitor. > > On Fri, Jan 30, 2015 at 11:49 PM, Thierry Goubier < > thierry.goubier(a)gmail.com> wrote: > >> >> >> 2015-01-30 14:04 GMT+01:00 kilon alios <kilon.alios(a)gmail.com>: >> >>> Ok thanks for the info, I am still however curious about these "tests" >>> are just tests (which may or may not happen) that determine the AST, for >>> example which node to use ? >>> >> >> 'tests' is just there because, in the grammar, there is this at a certain >> point: >> >> testlist: >> test 'test' "," testlist >> | test 'test' comma_opt >> ; >> >> I have named this use of test 'test', so SmaCC has deduced that testlist >> will be a list of test(s) nodes (or maybe other stuff such as atoms, >> depending on the productions for test).. so, SmaCC, in each rule where >> testlist is found, it will add a 'tests' instance variable. >> >> So, basically, the grammar rules explain how each node can be decomposed >> in sub-nodes, and the additional annotations (the 'test' naming and the >> {{}} or {{}}) drive how the classes for the nodes you want to keep are >> generated. In that testlist case, no node will be generated, but everywhere >> testlist appear on the right of the rule, then it will add a 'tests' >> instance variable. >> >> >>> >>> Or are they tests related to unit testing class PythonParserTests ? >>> >> >> Not at all :) >> >> >>> >>> Also you said I need to use the visitor created by PythonParser I assume >>> you mean PyRootNodeVisitor ? Just as it is explained in the AST chapter of >>> the documentation. >>> >>> In my case this simple python list will need me to subclass it and >>> override method visitListmaker , the aListmaker passed as argument to the >>> method should I assume it is PyListmakerNode ? >>> >> >> In my experience, what you need to do is you have a look at the ast >> generated and see if you can recognize the elements. From what I see in >> your simple example, the key to your list is that PyAtomNode instance with >> something in list. Once you have that, you know that you need to visit >> PyAtomNode (and check that it has the [ ] tokens). >> >> Looking into what is listmaker in atom in the grammar (congratulations by >> the way, you have seen it :) ), you'll see that it creates a listmaker node >> only in the first case: test followed by a list_for, otherwise it falls >> back to testlist... >> >> Thierry >> >> >> >>> >>> On Fri, Jan 30, 2015 at 10:50 AM, Thierry Goubier < >>> thierry.goubier(a)gmail.com> wrote: >>> >>>> Hi kilon, >>>> >>>> The tests instance variable is linked to the python grammar: top level >>>> items in an expression are probably tests, and, through the grammar, tests >>>> can be just atoms. >>>> >>>> So the tests instance variable doesn't means it is testing anything :) >>>> >>>> Thierry >>>> Le 30 janv. 2015 09:23, "kilon alios" <kilon.alios(a)gmail.com> a Ã©crit : >>>> >>>> Ok so I tried to parse a very simple list like >>>>> >>>>> [ 67,12342,5 ] >>>>> >>>>> using Parse and explore , I can find these number by following this >>>>> AST (for example 67) >>>>> >>>>> PyFileInputNode>>statements: -> 1: PySimpleStmNode>>stmts: -> 1: >>>>> PyExprStmtNode>>tests: ->1: PyPowerNode>>atom: -> PyAtomNode>>list: -> 1: >>>>> PyPowerNode>>atom: -> PyPowerNode>>numberToken -> numberToken>>value -> 67 >>>>> >>>>> quite a structure, but the one thing I dont get is "tests" , why >>>>> "tests" ? >>>>> >>>>> Does it tests something and if yes what ? >>>>> >>>> >>> >> >

Feb. 11, 2015

Re: [Pharo-users] Spotter vs Spotlight was: [Re: Cleaning code completition's namespace]

by Ben Coman

On Wed, Feb 11, 2015 at 1:25 PM, Laura Risani <laura.risani(a)gmail.com> wrote: > >> Also at some point i started to get an #inform: msg saying "WorldState > interCyclePause failed". > > > Thats not GTSpotter. That was my fault since build 40477 integrated Issue 14669. This should be fixed since Issue 40874 was integrated into build 40486 . cheers -ben

Feb. 11, 2015

Re: [Pharo-users] Spotter vs Spotlight was: [Re: Cleaning code completition's namespace]

by Laura Risani

> What do you mean about all existing menus in the image? Right now, the > default Spotter searches for the top level entries in the World menu and > then lets you dive if you want. It can also be made easily to search for > all menu entries from the World menu. Is that what you have in mind? > At that moment i thought of searching on all existing menu entries, for example if Spotter-search for "Browse" menu-category results will include "Browse scoped" (an entry of a menu you get for classes on the ClassBrowser). Yet at this moment i'm not sure of how useful it could be. > In this mail alone you list 4 different search tools: Finder, > MessageBrowser, Spotlight, Search in Nautilus. Each of these behaves > radically different without much of an added value. > > The whole philosophy of Smalltalk revolves around a minimal and uniform > model that can be used to express elegantly any action. For example, > Smalltalk has a simple syntax, and yet you can explain with that simple > syntax all things for which other languages require lots of hardcoded > constructs. The same rigor should be applied to the user interface. With > Spotter we strive to reach such a simple model that can be infinitely > moldable to fit custom needs. > > Now, besides elegance, if any, what else is there? Given that search is > such a pervasive action, before I start anything I first want to find an > entry point. That can be a method, a class, a file, or whatever other > object. To this end, first people think of what tool to use and then of how > to find the interesting object inside that tool. With Spotter we want to > eliminate the first step: we just open Spotter and start searching for what > we want. It's not quite there, but I think it is amazingly close to this > goal. > > I liked a lot these paragraphs in theirself and also as a motivation for Spotter. 2) Not having the regular features of a window that are useful depending on >> the case, for shortcuting i would like volatile but for browsing results i >> could depending on the case prefer persistency . >> > > Certainly. The current solution focuses on search. Creating a persistent > list of objects is still a work in progress but it is out of scope at the > moment. > > If at the method GTSpotterGlobalShortcut>>openGlobalSpotter one changes #openInWorld by #openInWindow , one gets the persistent behavior (it also includes the preview if opened). So now i can open a volatile or persistent Spotter, i'm going to have a keycombination for each one. In addition i get all the regular window behavior i in some cases want. This makes me really happy :) Only one little keybordian issue, Cmd+w doesn't close the window as usual, the same happens with GTPlayground. It would be nice if these come implemented so one doesn't have to add them. > This already works. As explained before, something like: > d #i > > will give you only the implementors of "d". So, # will search for the name > of the category. This feature is not yet complete in that it does not > highlight properly the results, but could you try to see if this fits what > you have in mind? > I've just read about that, and also the last bit on custom categories on the blog. So now i will define a category for classes+selectors and map a keycombination to open a volatile Spotter on ti, and remove the 5 results limit (how do i do this?). This gives me my wanted "selector/class shortcut" Spotlight provided me, improving the annoying deficiency Spotlight has of showing no-longer defined names (i asked about it in a recent mail to the list). Having a shortcut (Cmd+Shift+ArrowUp/ArrowDown) to jump through categories, then why to limit the number of results in each category to 5? Why not to show them all to avoid the need of going into the category? > Did you try compiling the method that I sent in the previous mail > (basically just copy paste that method in the GTSpotter class)? It should > provide the behavior of Spotlight. Please try and let me know if it works > for you. > > Yes, it works at some degree. I face this issue, if i type 'openIn' i get only 1/1 selector #openeningDelimiters, and only if i continue to type 'openInW' i get 5/28 selectors. Also at some point i started to get an #inform: msg saying "WorldState interCyclePause failed". So additions i would like to see built by default Cmd+w to close on GTSpotter and GTPlayground. Remove/know-how-to remove the 5 limit on results. Selectors category. Font size configured at SystemBrowser to have effect on GTSpotter both on search results and preview. To summarize i love Spotter and it will be the tool i use the most (in number of openings). Love, Laura

Feb. 11, 2015

Re: [Pharo-users] Problems evaluating message sends in run-time arrays

by Ben Coman

I'm away from my Pharo computer to double-check, but is it just that is how a Color object displays itself ? Maybe have a look at Color>>printOn: cheers -ben On Wed, Feb 11, 2015 at 9:38 AM, Andy Burnett < andy.burnett(a)knowinnovation.com> wrote: > I would like to create an array with a collection of colour values. > > I tried both: > > colorList := {Color blue} > and > colourList := {Color named: #blue.}. > > In both cases it evaluates to 'Color blue' rather than the Color object. > > What surprised me was that: > > charList := {Character digitValue:35. Character digitValue:33.}. > > Does evaluate to an array of two characters. What is going on? > > Cheers > Andy > á§ >

Feb. 11, 2015

Re: [Pharo-users] Problems evaluating message sends in run-time arrays

by Sean P. DeNigris

Andy Burnett wrote > In both cases it evaluates to 'Color blue' rather than the Color object. 'Color blue' is the Color object you created and put in your array. It is aColor object. It's print string is 'Color blue'. See Color>>#printOn: for more info. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Problems-evaluating-message-sends-in-run-time-arrays-… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 11, 2015

Re: [Pharo-users] Problems evaluating message sends in run-time arrays

by Ignacio Sniechowski

or | colorList | colorList := { Color blue class }. *Lic. Ignacio Sniechowski, MBA* *Prosavic SRL* *Tel: (011) 4542-6714* On Tue, Feb 10, 2015 at 10:38 PM, Andy Burnett < andy.burnett(a)knowinnovation.com> wrote: > I would like to create an array with a collection of colour values. > > I tried both: > > colorList := {Color blue} > and > colourList := {Color named: #blue.}. > > In both cases it evaluates to 'Color blue' rather than the Color object. > > What surprised me was that: > > charList := {Character digitValue:35. Character digitValue:33.}. > > Does evaluate to an array of two characters. What is going on? > > Cheers > Andy > á§ >

Feb. 11, 2015

Re: [Pharo-users] Problems evaluating message sends in run-time arrays

by Ignacio Sniechowski

| colorList | colorList := [ Color blue class ] value. *Lic. Ignacio Sniechowski, MBA* *Prosavic SRL* *Tel: (011) 4542-6714* On Tue, Feb 10, 2015 at 10:38 PM, Andy Burnett < andy.burnett(a)knowinnovation.com> wrote: > I would like to create an array with a collection of colour values. > > I tried both: > > colorList := {Color blue} > and > colourList := {Color named: #blue.}. > > In both cases it evaluates to 'Color blue' rather than the Color object. > > What surprised me was that: > > charList := {Character digitValue:35. Character digitValue:33.}. > > Does evaluate to an array of two characters. What is going on? > > Cheers > Andy > á§ >

Feb. 11, 2015

Problems evaluating message sends in run-time arrays

by Andy Burnett

I would like to create an array with a collection of colour values. I tried both: colorList := {Color blue} and colourList := {Color named: #blue.}. In both cases it evaluates to 'Color blue' rather than the Color object. What surprised me was that: charList := {Character digitValue:35. Character digitValue:33.}. Does evaluate to an array of two characters. What is going on? Cheers Andy á§

Feb. 11, 2015