- Pharo-dev - lists.pharo.org

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

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