January 2014 - Pharo-dev - lists.pharo.org

voyage configuration problem

by Norbert Hartl

I have problems loading voyage in a 2.0 image. For testing I downloaded a fresh one and installed voyage via the configuration browser. Somehow the dependencies from magritte down to grease seem to be broken somewhat. I tries to load a package Grease-Pharo20-Core-pmm.1 and a debugger pops up saying This package depends on the following classes: GRDelegatingStream You must resolve these dependencies before you will be able to load these definitions: GRCountingStream count greaseNext:putAll:startingAt: initialize next next: nextPut: nextPutAll: reset greaseNext:putAll:startingAt: Select Proceed to continue, or close this window to cancel the operation. Anybody has a glue what is going on? Is this something introduced by the release of seaside? Hints are appreciated. Norbert

Jan. 7, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30676 Home: https://github.com/pharo-project/pharo-core

Jan. 7, 2014

[pharo-project/pharo-core] ef9c89: 30676

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: ef9c89865470b27f772d543c4ef68370ec58ce5c https://github.com/pharo-project/pharo-core/commit/ef9c89865470b27f772d543c… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-01-07 (Tue, 07 Jan 2014) Changed paths: M Polymorph-Tools-Diff.package/extension/MCWorkingCopyBrowser/instance/viewChanges.st M Polymorph-Widgets.package/IconicListItem.class/class/instance creation/text_icon_.st M SUnit-UI.package/TestRunner.class/instance/actions/addDeclaredPackagesUnderTestTo_.st M SUnit-UI.package/TestRunner.class/instance/actions/addMethodsUnderTestIn_to_.st M SUnit-UI.package/TestRunner.class/instance/actions/promptForPackages.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script329.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30676.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30676 12530 Test Coverage not working https://pharo.fogbugz.com/f/cases/12530 12576 IconicListItem should allow any morph as icon https://pharo.fogbugz.com/f/cases/12576 12578 MCNoChangesException should be used https://pharo.fogbugz.com/f/cases/12578 http://files.pharo.org/image/30/30676.zip

Jan. 7, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30675 Home: https://github.com/pharo-project/pharo-core

Jan. 7, 2014

[pharo-project/pharo-core] 70da0b: 30675

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 70da0b33f74b52b9bb833364fd1e0f588b64207a https://github.com/pharo-project/pharo-core/commit/70da0b33f74b52b9bb833364… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-01-07 (Tue, 07 Jan 2014) Changed paths: M Morphic-Base.package/PluggableButtonMorph.class/instance/initialization/initialize.st M Morphic-Base.package/PluggableListMorph.class/instance/background coloring/backgroundColorFor_.st M Nautilus.package/NautilusUI.class/instance/menus behavior/findMethod.st M Polymorph-Widgets.package/IconicListItem.class/class/instance creation/text_icon_.st M ScriptLoader30.package/ScriptLoader.class/README.md A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script328.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30675.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30675 12568 IconicListItem should lock text morph https://pharo.fogbugz.com/f/cases/12568 12567 PluggableButtonMorph should clip submorphs https://pharo.fogbugz.com/f/cases/12567 12516 Nautilus find methode ... does not select the method https://pharo.fogbugz.com/f/cases/12516 12582 Silly code in PluggableListMorph https://pharo.fogbugz.com/f/cases/12582 http://files.pharo.org/image/30/30675.zip

Jan. 7, 2014

Re: [Pharo-dev] Spotlight Demo

by Guillermo Polito

Maybe widgets should delegate to the theme the rendering? So Morph subclass: Widget. "So this applies only for widget morphs?" Widget subclass: List. List >> drawOn: aCanvas self theme drawList: self onCanvas: aCanvas And then each theme can really render different each widget. On Tue, Jan 7, 2014 at 11:10 AM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > Iâm experimenting with separate the widget from the skinâ¦ problem is > sometimes theming is just change colors, but some others is widget building > it self, so we will need widget factories (for theme), etc. > > all is doable, but all implies time :) > > On 07 Jan 2014, at 11:07, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> > wrote: > > > I think this is too convoluted because, like Estaban says, you want to > keep the theming orthogonal with widget definition. > > > Yes I do not like it either. > > But, you gave me an idea: > > If we implement in Morph the followings: > > Morph>>themer > ^ themer ifNil: [self themerFor: self theme] > > > what would be self theme I do not really like the idea to have all the > morph talking to UITheme > theme > ^ UITheme current > is not sexy to me > > Morph>>themerFor: aTheme > ^ self subclassResponsibility > > And then in a morph we would have something like this: > > SpotlightItemMorph>>themerFor: aTheme > ^ aTheme spotterThemer > > SpotlightItemMorph>>onSelected > self themer configureSelectedItemMorph: self > > > Then we could simply do pretty much what you want: > > SpotlightItemMorph new themer: MySpotterThemer new. > > I like this idea. What do you think? > > > I do not know. Now what is clear is that we need strategy as in your > original design. I was thinking about that too. > > Stef > > >

Jan. 7, 2014

Re: [Pharo-dev] fixing the search in the MC browser would be sooooo cool

by Goubier Thierry

Le 07/01/2014 11:09, StÃ©phane Ducasse a Ã©crit : > > Sometimes I type Morphic > > to see all the packages of morphic and I do not get them at all just Polymorph > > after if I type Polymorph I do not see Polymorph > > same with ScriptLoader Strange, I have a hard time reproducing it. I find it a bit confusing that it search on substrings and not by the start of the package name, but that's all (at least the Morphic / Polymorph thing worked for me). > Sometimes I have to look by hand in the right pane + plus click on it then filter on the left pane > So this is totally bogus to me. Focus issues? I just noticed the package / all toggle on the right as well. Thierry > Stef > >> Hi Stef, >> >> what is the problem exactly? It seems to work as expected. >> >> Thierry >> >> Le 07/01/2014 09:53, StÃ©phane Ducasse a Ã©crit : >>> Hi guys >>> >>> if you want to help, the search (left) in the mCBrowser (once we do Open) is totally broken. >>> It is a pain to look for packages when we have to check things. >>> There is a bug entry (I od not remember its number). >>> Stef >>> >>> >> >> -- >> Thierry Goubier >> CEA list >> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >> 91191 Gif sur Yvette Cedex >> France >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >> > > > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Jan. 7, 2014

Re: [Pharo-dev] Two videos to explain what we do when integrating a fix.

by Esteban Lorenzano

sourcetree +100:) On 07 Jan 2014, at 12:04, kilon alios <kilon.alios(a)gmail.com> wrote: > Plus there is like tons of gui tools for git out there (I have used smartgit) making command line a last option. Also I dont understand , git works the same on all 3 big OSes (windows , macos , linux). > > Î£ÏÎ¹Ï 7 ÎÎ±Î½ 2014 12:57 Î¼.Î¼., Î¿ ÏÏÎ®ÏÏÎ·Ï "Benjamin" <Benjamin.VanRyseghem.Pharo(a)gmail.com> ÎÎ³ÏÎ±ÏÎµ: > I do not want that end users to get expose to > >> git on the command-line with different platforms. We should keep the simplicity of Pharo. > >> > > Having an integration process based on git will expose only core-developpers ton git :) > > Not the end-users ;) > Ben > >

Jan. 7, 2014

Re: [Pharo-dev] Two videos to explain what we do when integrating a fix.

by kilon alios

Plus there is like tons of gui tools for git out there (I have used smartgit) making command line a last option. Also I dont understand , git works the same on all 3 big OSes (windows , macos , linux). Î£ÏÎ¹Ï 7 ÎÎ±Î½ 2014 12:57 Î¼.Î¼., Î¿ ÏÏÎ®ÏÏÎ·Ï "Benjamin" < Benjamin.VanRyseghem.Pharo(a)gmail.com> ÎÎ³ÏÎ±ÏÎµ: > I do not want that end users to get expose to > >> git on the command-line with different platforms. We should keep the > simplicity of Pharo. > >> > > Having an integration process based on git will expose only > core-developpers ton git :) > > Not the end-users ;) > Ben > > >

Jan. 7, 2014

Re: [Pharo-dev] Two videos to explain what we do when integrating a fix.

by Luc Fabresse

2014/1/7 Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> > I do not want that end users to get expose to > >> git on the command-line with different platforms. We should keep the > simplicity of Pharo. > >> > > Having an integration process based on git will expose only > core-developpers ton git :) > yes. For example, I really like what people (camillo? esteban? igor?) did for the VM code on github. now it is easy to get a synchronized VMMaker image and also commit to git the new mcz versions. Luc > Not the end-users ;) > Ben > > >

Jan. 7, 2014