December 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo Trick: #0001] - Simple TODO list

by Serge Stinckwich

Nice idea Torsten, this kind of tricks ;-) Maybe we can save them online somewhere ? gists.github.com ? On Wed, Dec 11, 2013 at 12:16 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi, > > the mailinglist, stackoverflow and other Pharo related medias are typically used > in the "here is a question to problem" followed by an "answer from community" style. > > But lets also think the other way around: if we already have a solution for a > problem that others may have too or may have in the future we should share the > answer/solution as well. > > I'm sure many of you have some tricks that make developing with Pharo much easier > and others can profit from these tricks if we share them here on the list. > > Be it > - a simple and useful script > - a simple key combination other may not yet know of > - a package one can use or how you use it > - a link to a nice description on the web related on how to use Pharo > - a custom tool that makes development easier > - an algorithm or something that you think was solved very elegant > - a way you solved a common problem easily in your app > - ... > > Then just describe it in a few lines and post it. Also write in which Pharo > version you tried it - this makes it easier for others to see in which > version the trick/solution is known to work. > > The idea goes like this: if you have a trick to share then send a mail with > subject "Pharo Trick: #xxxx] - Short Description" to the Pharo dev AND Pharo user > list (see http://lists.pharo.org) Make sure to increase the trick counter xxxx. > > Using this special subject one can later easily get the tricks from the > mailinglist archive. Also others can refer to the trick if it solves a common > problem other may ask for on the list. > > Lets see if we are able to reach the goals of 100, 1000 or more Pharo tricks ;) > > Bye > T. > > > I will start with something easy but useful: > > ----------------------------------------------------------------------------------- > [Pharo Trick: #0001] - Simple TODO > ----------------------------------------------------------------------------------- > Works in: Pharo3.0 Latest update: #30635 but should work in other versions too > ----------------------------------------------------------------------------------- > > If you develop an app with Pharo you may not yet fully implement all features. > Some kind of marker for future "ToDo's" is often needed. Using a pragma on a method is > the easiest solution here: > > foo > <todo: 'Add world later'> > "That method is not yet fully implemented" > > Transcript show: 'Hello' > > > Using a simple expression in the workspace you can browse all the TODOs for your > project afterwards in a window: > > SystemNavigation default browseAllSendersOf: #todo: > > You can even query the system for the todo descriptions if you need the full > list of things to work on: > > (PragmaCollector filter: [:prg | prg keyword = 'todo:']) > reset; > collect: [:each| each arguments first ] > > As the pragma keyword #todo: is very common and may be used by others too > it may be wise to use a custom one like "myappplicationTodo:" or similar. > ----------------------------------------------------------------------------------- > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Dec. 12, 2013

Re: [Pharo-dev] [Pharo Trick: #0004] - Run code using a key command to speedup development

by Guillermo Polito

The world morph was initially intended to handle the global system shortcuts, taking advantage of the event bubbling. However, that posed the fact that the global shortcuts have less priority than other shortcuts. The bubbling will activate a global shortcut only if it they key event did not activated a shortcut of its childs first. So we changed that, and there is another mechanism to install global shortcuts in the system. An example of it is installed in the system: SpotlightShortcuts On Thu, Dec 12, 2013 at 10:59 AM, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > BTW, no world binding has yet been initialized yet in Pharo 3.0 (but CMD+K) > Is it intentional? > see > http://stackoverflow.com/questions/17886061/switch-between-open-windows-in-… > > > 2013/12/12 phil(a)highoctane.be <phil(a)highoctane.be> > > Very sweet indeed. >> >> Phil >> >> >> >> On Thu, Dec 12, 2013 at 9:42 AM, Max Leske <maxleske(a)gmail.com> wrote: >> >>> Nice! Didnât know about that one. >>> >>> >>> On 12.12.2013, at 09:35, Torsten Bergmann <astares(a)gmx.de> wrote: >>> >>> > >>> ----------------------------------------------------------------------------------- >>> > [Pharo Trick: #0004] - Run code using a key command to speedup >>> development >>> > >>> ----------------------------------------------------------------------------------- >>> > Works in: Pharo3.0 Latest update: #30637 but should work in other >>> 2.0/3.0 versions >>> > >>> ----------------------------------------------------------------------------------- >>> > >>> > If you have to run some code very often you typically have to evaluate >>> it >>> > from a workspace over and over again. >>> > But to speed up you can assign a global keymapping which allows to run >>> it with >>> > a simple keyboard shortcut: >>> > >>> > World >>> > on: $a shift command >>> > do: [ Object browse ]. >>> > >>> > Evaluate this once in a workspace. After that anytime you press SHIFT, >>> the >>> > command button (on Windows this is ALT) and A together the block gets >>> evaluated >>> > and your code runs easily. >>> > >>> > Background: >>> > =========== >>> > In Pharo there is a global morph called "World" representing the >>> desktop. >>> > One can assign a key combination to any morph including this world. >>> > If you are interested on the Keymappings then read >>> http://playingwithobjects.wordpress.com/2013/03/19/keymappings-101-for-phar… >>> > for more >>> > >>> >>> >>> >> >

Dec. 12, 2013

Re: [Pharo-dev] [Pharo Trick: #0004] - Run code using a key command to speedup development

by Guillermo Polito

Ahh a little detail! We are deprecating the usage of #on:do: for shortcuts so they are not mistaken with exception handling, nor announcement registration :). The right snippet would be World bindKeyCombination: $a shift command toAction: [ Object browse ]. Actually, if you see the #on:do: implementation in Morph, you'll notice it uses #bindKeyCombination:toAction: . Aaaand, we should probably remove/deprecate the old one. On Thu, Dec 12, 2013 at 10:02 AM, phil(a)highoctane.be <phil(a)highoctane.be>wrote: > Very sweet indeed. > > Phil > > > > On Thu, Dec 12, 2013 at 9:42 AM, Max Leske <maxleske(a)gmail.com> wrote: > >> Nice! Didnât know about that one. >> >> >> On 12.12.2013, at 09:35, Torsten Bergmann <astares(a)gmx.de> wrote: >> >> > >> ----------------------------------------------------------------------------------- >> > [Pharo Trick: #0004] - Run code using a key command to speedup >> development >> > >> ----------------------------------------------------------------------------------- >> > Works in: Pharo3.0 Latest update: #30637 but should work in other >> 2.0/3.0 versions >> > >> ----------------------------------------------------------------------------------- >> > >> > If you have to run some code very often you typically have to evaluate >> it >> > from a workspace over and over again. >> > But to speed up you can assign a global keymapping which allows to run >> it with >> > a simple keyboard shortcut: >> > >> > World >> > on: $a shift command >> > do: [ Object browse ]. >> > >> > Evaluate this once in a workspace. After that anytime you press SHIFT, >> the >> > command button (on Windows this is ALT) and A together the block gets >> evaluated >> > and your code runs easily. >> > >> > Background: >> > =========== >> > In Pharo there is a global morph called "World" representing the >> desktop. >> > One can assign a key combination to any morph including this world. >> > If you are interested on the Keymappings then read >> http://playingwithobjects.wordpress.com/2013/03/19/keymappings-101-for-phar… >> > for more >> > >> >> >> >

Dec. 12, 2013

Re: [Pharo-dev] [Pharo Trick: #0004] - Run code using a key command to speedup development

by Nicolas Cellier

BTW, no world binding has yet been initialized yet in Pharo 3.0 (but CMD+K) Is it intentional? see http://stackoverflow.com/questions/17886061/switch-between-open-windows-in-… 2013/12/12 phil(a)highoctane.be <phil(a)highoctane.be> > Very sweet indeed. > > Phil > > > > On Thu, Dec 12, 2013 at 9:42 AM, Max Leske <maxleske(a)gmail.com> wrote: > >> Nice! Didnât know about that one. >> >> >> On 12.12.2013, at 09:35, Torsten Bergmann <astares(a)gmx.de> wrote: >> >> > >> ----------------------------------------------------------------------------------- >> > [Pharo Trick: #0004] - Run code using a key command to speedup >> development >> > >> ----------------------------------------------------------------------------------- >> > Works in: Pharo3.0 Latest update: #30637 but should work in other >> 2.0/3.0 versions >> > >> ----------------------------------------------------------------------------------- >> > >> > If you have to run some code very often you typically have to evaluate >> it >> > from a workspace over and over again. >> > But to speed up you can assign a global keymapping which allows to run >> it with >> > a simple keyboard shortcut: >> > >> > World >> > on: $a shift command >> > do: [ Object browse ]. >> > >> > Evaluate this once in a workspace. After that anytime you press SHIFT, >> the >> > command button (on Windows this is ALT) and A together the block gets >> evaluated >> > and your code runs easily. >> > >> > Background: >> > =========== >> > In Pharo there is a global morph called "World" representing the >> desktop. >> > One can assign a key combination to any morph including this world. >> > If you are interested on the Keymappings then read >> http://playingwithobjects.wordpress.com/2013/03/19/keymappings-101-for-phar… >> > for more >> > >> >> >> >

Dec. 12, 2013

Re: [Pharo-dev] about the Pharo Catalog

by StÃ©phane Ducasse

Yes :) In the output of the catalog itself https://ci.inria.fr/pharo-contribution/job/PharoProjectCatalog/HTML_Report/? There is probably a typo in the generator catalogkeyClassesAndExample => catalogKeyClassesAndExample 1. Aconcagua Please define a class method named catalogDescription returning a paragraph of description in the configuration class. 1.1. Keywords Please define a class method named catalogKeywords returning an array of symbols in the configuration class. 1.2. Key classes and Implementations Notes Please define a class method named catalogkeyClassesAndExample returning a paragraph describing the most important classes of the project and relevant information such as an example. 1.3. Key change logs Please define a class method named catalogChangeLog returning a paragraph describing the most important changes in the configuration class. We suggest to use the following format: Version number - Date - topics ConfigurationOfXXX project version: 'xx' ) load or simply Version number - Date - topics Version number - Date - topics Version number - Date - topics On Dec 12, 2013, at 10:49 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > is there a place where I can see the metadata methods I need to implement? > > Esteban > > > On Thu, Dec 12, 2013 at 9:59 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > I really want to have an official catalog soon, so please add the missing metadata in your configurations. > In addition I was discussing with robert pergl from Prague and he told me that > when he has a problem with a package he does not know to whom he should report so > I would like to add a catalogContact section. > Any idea for improvement. > > Stef >

Dec. 12, 2013

Re: [Pharo-dev] Categories, packages, and tags [cont'd]

by StÃ©phane Ducasse

On Dec 12, 2013, at 10:47 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Stef means "RPackageOrganizer", not PackageOrganizer :) ok I thought the old one was removed and the new renamed > > Esteban > > > On Thu, Dec 12, 2013 at 8:37 AM, Roberto Minelli <roberto.minelli(a)usi.ch> wrote: > Thx Stef! > > I also found RPackage organizer packages ;) > > Cheers, > R > > On Dec 12, 2013, at 8:25 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > > > > On Dec 11, 2013, at 1:40 PM, Roberto Minelli <roberto.minelli(a)usi.ch> wrote: > > > >> Hi guys, > >> > >> I have a question about the new âPackageTreeModelââ¦ > >> > >> In a previous discussion (https://www.mail-archive.com/pharo-dev@lists.pharo.org/msg09271.html) we discussed about the new package model. Now I understood it but I am wondering one thing. > >> > >> Since Stef said that categories will be removed, i.e., the ByteSymbol representation of what I used to call packages, I am wondering how one could ask the system which are the installed packages, tags, etc. > >> > >> In short I want to know which is the best method to ask what used to be âSystemOrganization categoriesâ. > > > > > > PackageOrganizer default blblablabbleb packages > > >

Dec. 12, 2013

Re: [Pharo-dev] Using TreeModel>>selectAll

by StÃ©phane Ducasse

TreeMorph On Dec 12, 2013, at 10:27 AM, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > Of ? > > Ben > > On 12 Dec 2013, at 08:11, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> In the midterm >> >> would it not be better to start a new implementation? >> >> Stef >> On Dec 11, 2013, at 11:18 PM, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: >> >>> Thatâs the default behaviour >>> >>> I was thinking today of introducing a special one which act as you described >>> >>> Ben >>> >>> On 11 Dec 2013, at 21:49, Nicolai Hess <nicolaihess(a)web.de> wrote: >>> >>>> One thing I didn't understand is, are valueholders supposed to announce changes, even if >>>> the "value" didn't changed? >>>> >>>> |log node | >>>> log := OrderedCollection new. >>>> node:= >>>> TreeNodeModel new >>>> content: $a; >>>> whenSelectedChanged:[:item | self halt.log add:item]; >>>> selected: true; >>>> selected: true; >>>> selected: true. >>>> log >>>> >>>> will log three times, even the value (selected=true) didn't changed at all. >>>> (or at most one if "selected" is initialized with false). >>>> >>>> Nicolai >>>> >>>> >>>> >>>> 2013/12/9 Martin Dias <tinchodias(a)gmail.com> >>>> thanks for your help, Ben >>>> >>>> On Mon, Dec 9, 2013 at 11:15 AM, Benjamin >>>> <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: >>>> > I am still chasing why itâs executed three times >>>> > >>>> > Must be an issue in the info propagation. >>>> > >>>> > Ben >>>> > >>>> > On 09 Dec 2013, at 06:48, Martin Dias <tinchodias(a)gmail.com> wrote: >>>> > >>>> > Hi, I'm back with more annoying questions :) >>>> > >>>> > Using #whenSelectedItemsChanged:, I see that the block is evaluated a lot of >>>> > times: >>>> > >>>> > log := OrderedCollection new. >>>> > roots := #(1 2) collect: [ :each | >>>> > TreeNodeModel new >>>> > content: each; >>>> > selected: true; >>>> > yourself ]. >>>> > >>>> > TreeModel new >>>> > roots: roots; >>>> > multiSelection: true; >>>> > whenSelectedItemsChanged: [ :items | >>>> > log add: items ]; >>>> > openWithSpec. >>>> > log ---> an OrderedCollection(#() an OrderedCollection(1) an >>>> > OrderedCollection(1) an OrderedCollection(1 2) an OrderedCollection(1 2) an >>>> > OrderedCollection(1 2)) >>>> > >>>> > I'd expect only one evaluation... is it a bug or a feature? >>>> > >>>> > cheers, >>>> > MartÃn >>>> > >>>> > >>>> > On Sun, Dec 8, 2013 at 12:22 AM, Martin Dias <tinchodias(a)gmail.com> wrote: >>>> >> >>>> >> aha! thanks >>>> >> >>>> >> MartÃn >>>> >> >>>> >> On Sat, Dec 7, 2013 at 10:33 AM, Benjamin >>>> >> <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: >>>> >> > roots := #(1 2 3) collect: [ :e | TreeNodeModel new content: e ; >>>> >> > yourself ]. >>>> >> > >>>> >> > TreeModel new >>>> >> > roots: roots; >>>> >> > multiSelection: true; >>>> >> > openWithSpec. >>>> >> > >>>> >> > roots third >>>> >> > selected: true; >>>> >> > takeHighlight >>>> >> > >>>> >> > Ben >>>> >> > >>>> >> > On 07 Dec 2013, at 05:44, Martin Dias <tinchodias(a)gmail.com> wrote: >>>> >> > >>>> >> > ouch! thanks Ben. >>>> >> > >>>> >> > Another related question: is there any way of selecting an arbitrary >>>> >> > item? I tried (among others) with: >>>> >> > >>>> >> > TreeModel new >>>> >> > roots: #(1 2 3); >>>> >> > multiSelection: true; >>>> >> > openWithSpec; >>>> >> > selection: 3 >>>> >> > >>>> >> > without success. >>>> >> > >>>> >> > Cheers, >>>> >> > MartÃn >>>> >> > >>>> >> > >>>> >> > >>>> >> > On Thu, Dec 5, 2013 at 4:17 PM, Benjamin >>>> >> > <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: >>>> >> > >>>> >> > your tree here is single selection so it will not work >>>> >> > >>>> >> > TreeModel new >>>> >> > roots: #(1 2 3); >>>> >> > multiSelection: true; >>>> >> > openWithSpec; >>>> >> > selectAll >>>> >> > >>>> >> > Ben >>>> >> > >>>> >> > On 05 Dec 2013, at 15:38, Martin Dias <tinchodias(a)gmail.com> wrote: >>>> >> > >>>> >> > Hi, >>>> >> > >>>> >> > I'm not sure how this method should be used. I tried in different >>>> >> > ways, for example: >>>> >> > >>>> >> > TreeModel new >>>> >> > roots: #(1 2 3); >>>> >> > selectAll; >>>> >> > openWithSpec >>>> >> > >>>> >> > But always the items are unselected. Is it a bug? or I didn't find the >>>> >> > way to use it? >>>> >> > >>>> >> > Thanks, >>>> >> > MartÃn >>>> >> > >>>> >> > >>>> >> > >>>> >> > >>>> > >>>> > >>>> > >>>> >>>> >>> >> >

Dec. 12, 2013

Re: [Pharo-dev] Which tests should be run in CI?

by Tudor Girba

This is clearly an issue of Grease. And it is not essential either as there are no senders to it. So, I see no reason not to rename it in Grease. Cheers, Doru On Thu, Dec 12, 2013 at 8:28 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > +1 > I do not really get it because we mentioned that several times. > Grease maintainers should simply produce a new version and Seaside/users > should use this new version. > > > >> > > But *Grease* still is the problem: in the tradition of the wonderful > philosophy âLets keep all smalltalk crappy > > and provide some layer on topâ, it redefines #package and therefore > requires that no Smalltalk ever > > implements #packages on the class side to return the system concept of > package. > > > > What you need to find out: Why does Grease need a #package method? Is > there a GreasePackage class? > > What is itâs responsibility? wouldnât it be good enough to have a > #gpackage method? > > > > In general, you should evaluate Grease and put all the *concepts* it > adds into Pharo itself. This way even > > the Core system can use them and everything gets better. > > > > Marcus > > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 12, 2013

Re: [Pharo-dev] about the Pharo Catalog

by Esteban Lorenzano

is there a place where I can see the metadata methods I need to implement? Esteban On Thu, Dec 12, 2013 at 9:59 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Hi guys > > I really want to have an official catalog soon, so please add the missing > metadata in your configurations. > In addition I was discussing with robert pergl from Prague and he told me > that > when he has a problem with a package he does not know to whom he should > report so > I would like to add a catalogContact section. > Any idea for improvement. > > Stef >

Dec. 12, 2013

Re: [Pharo-dev] Categories, packages, and tags [cont'd]

by Esteban Lorenzano

Stef means "RPackageOrganizer", not PackageOrganizer :) Esteban On Thu, Dec 12, 2013 at 8:37 AM, Roberto Minelli <roberto.minelli(a)usi.ch>wrote: > Thx Stef! > > I also found RPackage organizer packages ;) > > Cheers, > R > > On Dec 12, 2013, at 8:25 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: > > > > > On Dec 11, 2013, at 1:40 PM, Roberto Minelli <roberto.minelli(a)usi.ch> > wrote: > > > >> Hi guys, > >> > >> I have a question about the new âPackageTreeModelââ¦ > >> > >> In a previous discussion ( > https://www.mail-archive.com/pharo-dev@lists.pharo.org/msg09271.html) we > discussed about the new package model. Now I understood it but I am > wondering one thing. > >> > >> Since Stef said that categories will be removed, i.e., the ByteSymbol > representation of what I used to call packages, I am wondering how one > could ask the system which are the installed packages, tags, etc. > >> > >> In short I want to know which is the best method to ask what used to be > âSystemOrganization categoriesâ. > > > > > > PackageOrganizer default blblablabbleb packages > > >

Dec. 12, 2013