- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] An ugly question about menu and domain objects

by StÃ©phane Ducasse

yes so far I added menus "ugly just to brainstorm and get something working now" ^ #(('inspect' #inspect)) to build menus but I find that not that nice On Jun 30, 2013, at 7:34 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Sun, Jun 30, 2013 at 7:06 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Now I'm wondering how I could define menu items in a way that I do not polute the domain object with >> menus. > > > you can use double-dispatch and create both a #menuForLogItem: and a > #menuForSubLogItem: on the UI. This means to add a #menuFromUI: method > in each subclass. You can also use a visitor to have a #accept: method > in each subclass instead. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

June 30, 2013

Re: [Pharo-dev] An ugly question about menu and domain objects

by Damien Cassou

On Sun, Jun 30, 2013 at 7:06 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Now I'm wondering how I could define menu items in a way that I do not polute the domain object with > menus. you can use double-dispatch and create both a #menuForLogItem: and a #menuForSubLogItem: on the UI. This means to add a #menuFromUI: method in each subclass. You can also use a visitor to have a #accept: method in each subclass instead. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

June 30, 2013

An ugly question about menu and domain objects

by StÃ©phane Ducasse

Hi I have domain objects for example logs. And I have a UI. Now I would like to let the programmer to extend the Log items (either by subclassing or extensions) and add new actions. For example I would like that the compiler is able to define errors as log items so that after we can go to the log panel and press 'identify' and that we jump to the place in the code. Now I'm wondering how I could define menu items in a way that I do not polute the domain object with menus. Stef

June 30, 2013

Re: [Pharo-dev] SqueakSource3 with new server name

by Dale K. Henrichs

June 30, 2013

Re: [Pharo-dev] List auto-selection of next item on delete

by StÃ©phane Ducasse

even cooler :) Stef On Jun 30, 2013, at 4:46 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > It's the default behaviour > > > Ben > > On Jun 30, 2013, at 4:31 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > >> Hi >> >> Is there a way to say to a list that when we delete a selected element, the selection should >> be the next one if possible? >> >> Stef >

June 30, 2013

Re: [Pharo-dev] List auto-selection of next item on delete

by Benjamin

It's the default behaviour Ben On Jun 30, 2013, at 4:31 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > Hi > > Is there a way to say to a list that when we delete a selected element, the selection should > be the next one if possible? > > Stef

June 30, 2013

Re: [Pharo-dev] SmalltalkHub upgrade!

by kilon

Thanks Damien :) -- View this message in context: http://forum.world.st/Pharo-dev-SmalltalkHub-upgrade-tp4696167p4696431.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 30, 2013

List auto-selection of next item on delete

by StÃ©phane Ducasse

Hi Is there a way to say to a list that when we delete a selected element, the selection should be the next one if possible? Stef

June 30, 2013

Re: [Pharo-dev] [ANN] SS3 the canary site

by Sven Van Caekenberghe

Hi Tobias, On 28 Jun 2013, at 23:55, Tobias Pape <Das.Linux(a)gmx.de> wrote: > Dear fellow Smalltalkers > > For me to test new features of SqueakSource3 and for you to have a look on > new features and fixed bugs, I have created > > http://canary.netshed.de/ > > which is the most recent, say alpha, deployment of SqueakSource3. > It contains features that are not yet deployed at other ss3 sites, > including the gemstone one. I cannot make any guaranty that code commited > to the canary will survive forever; > it is a play toy, so go play with it :) > > Attached a teaser image. > > Best > -Tobias > > <BrowsingSS3Canary.PNG> Looks quite nice ! And although it is not necessarily efficient to have multiple efforts doing the same thing, some form of competition or alternative implementation is not bad. Cooperation on common goals is of course better still. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

June 30, 2013

Re: [Pharo-dev] SmalltalkHub upgrade!

by Damien Cassou

On Sun, Jun 30, 2013 at 4:01 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > PS: Is a source code browsing feature something that we can expect someday ? It is really something that I miss: I often want to have a quick look at some code, before defining the repository and/or loading it. could we use Helios for that? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

June 30, 2013