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

Re: [Pharo-dev] could we stop to create spaghetti code?

by Esteban Lorenzano

On Thu, Dec 12, 2013 at 8:19 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > >> > > > > I think the idea here is that maybe a class should have an icon. > Independend of Nautilus.\ > > (either just icon or toolIcon). > > Yes we got the idea :) > Now we faced extensions management problems with pavel so we could not fix > it. > We did not want to produce more mess. But this is the next thing I want to > fix because > we cannot explore dependencies with a broken explorer. > > I think that if we are real about modularity. We should really focus on it > for a while in 4.0 > +1 (along with tools :) > Else if it will never happen. People just do not think about dependencies. > We should have a tool that check that. > > > Stef >

Dec. 12, 2013

Re: [Pharo-dev] MessageNotUnderstood: SmallInteger>>isEmpty

by Sven Van Caekenberghe

On 12 Dec 2013, at 10:33, Dario Trussardi <dario.trussardi(a)tiscali.it> wrote: > > Ciao, > >> I will promote the latest vm (latest before spur) as stable tomorrow morning. >> So I suppose he can try that :) >> >> Pharo-VM-mac-latest.zip >> > I download it, > > but now what i need to do with it ? > > How i can update my Pharo 2.0 environment with it ? You can/probably have multiple VM applications by now. Just double-clicking a .image will use a default one (you can change that). To mix/match vms/images, either drop a .image onto a VM, or open the VM and from there open the .image Sven > Thanks, > > Dario > > >> cheers, >> Esteban >> >

Dec. 12, 2013

[Pharo Trick: #0007] - Write UI prototype in a workspace

by Benjamin

----------------------------------------------------------------------------------- [Pharo Trick: #0007] - Write UI prototype in a workspace ----------------------------------------------------------------------------------- Works in: Pharo 2.0, 3.0, ... ----------------------------------------------------------------------------------- In Morphic, there is no way to quickly prototype a UI. But in Spec there is a Dynamic class supporting this, so one can try different things directly from a Workspace An example: m := DynamicComposableModel new. m instantiateModels: #( button ButtonModel list ListModel). m list items: #(1 2 3 4 5). m button label: 'Plip'; action: [ self halt ]. m openWithSpecLayout: (SpecLayout composed newColumn: [: c | c add: #list ; add: #button height: 26 ]; yourself). Ben

Dec. 12, 2013

Re: [Pharo-dev] MessageNotUnderstood: SmallInteger>>isEmpty

by Dario Trussardi

Ciao, > I will promote the latest vm (latest before spur) as stable tomorrow morning. > So I suppose he can try that :) > > Pharo-VM-mac-latest.zip > I download it, but now what i need to do with it ? How i can update my Pharo 2.0 environment with it ? Thanks, Dario > cheers, > Esteban >

Dec. 12, 2013

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

by Benjamin

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

[Pharo Trick: #0006] - Run code from a button window

by Torsten Bergmann

----------------------------------------------------------------------------------- [Pharo Trick: #0006] - Run code from a standalone button window ----------------------------------------------------------------------------------- Works in: Pharo 2.0, 3.0, ... ----------------------------------------------------------------------------------- In Pharo there is a class called ButtonModel - it is a model used for buttons when building UI's with the Spec framework. But it can be used also standalone to open a button window with an action block: |b| b := ButtonModel new. b openWithSpec; label: 'Run my code'; action: [ Transcript open ] So you just have to click to run some code.

Dec. 12, 2013

[Pharo Trick: #0005] - Pick up morphs that do not want to be picked up"

by phil＠highoctane.be

Usually one can deal with morphs by doing the alt-shift-click on them, so that we get the halos and do whatever. Now, some morphs do not want to let you do this (like the Pharo image on the desktop background) - or you just don't see them as they are leftovers from experiments. A shift click (on Windows) brings a "find window" popup where you can select what you want, no matter what. Try to pick the ImageMorph in there for the Pharo Logo. Phil

Dec. 12, 2013

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

by phil＠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 StÃ©phane Ducasse

I want more :) On 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

about the Pharo Catalog

by StÃ©phane Ducasse

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