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

[pharo-project/pharo-core] 3ab076: 30500

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 3ab0764a1658214c915a01509eaaf9aec8e78b17 https://github.com/pharo-project/pharo-core/commit/3ab0764a1658214c915a0150… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-10-18 (Fri, 18 Oct 2013) Changed paths: M Collections-Abstract.package/SequenceableCollection.class/instance/splitjoin/joinUsing_last_.st M CollectionsTests.package/SplitJoinTest.class/instance/running/testJoinUsingLastOnArray.st M MenuRegistration.package/PragmaMenuBuilder.class/instance/menu building/buildTree.st M Morphic-Base.package/ImageMorph.class/instance/geometry/extent_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script155.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30500.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Inspector.package/EyeMorphViewer.class/class/spec/inspectorSpec.st M Spec-Inspector.package/EyeMorphViewer.class/instance/accessing/container.st M Spec-Inspector.package/EyeMorphViewer.class/instance/event-handling/objectChanged.st A Spec-Inspector.package/EyeMorphViewer.class/instance/initialization/initializePresenter.st R Spec-Inspector.package/EyeMorphViewer.class/instance/initialization/initializeWidgets.st A Spec-Inspector.package/EyeMorphViewer.class/instance/initialize/initialize.st A Spec-Inspector.package/extension/ImageMorph/instance/resize_.st Log Message: ----------- 30500 11835 Cannnot revert <Make uncloseable> https://pharo.fogbugz.com/f/cases/11835 11924 Resize the morph while inspecting it https://pharo.fogbugz.com/f/cases/11924 11915 #joinUsing:last: incorrect for single item collection https://pharo.fogbugz.com/f/cases/11915 http://files.pharo.org/image/30/30500.zip

Oct. 18, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation-M-Z/labe… 1 regressions found. Tests.Release.ReleaseTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits

Oct. 18, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation-M-Z/labe… 1 regressions found. Tests.Release.ReleaseTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits

Oct. 18, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation-M-Z/labe… 1 regressions found. Tests.Release.ReleaseTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits

Oct. 18, 2013

Question about Opal

by Goubier Thierry

Hi Markus, I have an Opal-related question: I want to get the ast of an expression analysed in the context of a particular class... I.e. something like: anAst doSemanticAnalysisIn: aClass. This code works if the ast is a methodNode, but not if this is a simple expression (a MessageNode for instance). I know there is a doSemanticAnalysis (which should work, but probably on the UndefinedObject class). So how do I do that? (in 2.0 and the old compiler, the solution is to do anAst annotateInClass: aClass) Thanks, Thierry -- 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

Oct. 18, 2013

[OT] Bare metal Raspberry Pi Squeak

by Torsten Bergmann

http://www.raspberrypi.org/phpBB3/viewtopic.php?f=72&t=57728

Oct. 18, 2013

Re: [Pharo-dev] The Pharo 3 theme

by phil＠highoctane.be

Yeah, that's really what I experienced when trying that out. Now, the good thing about doing such a thing (and I am ready to help if you want) is that we would be able to start doing UIs in the same vein as Adobe Lightroom for example. That's would be really great. It is one reason why I started looking into dark as well. Phil On Fri, Oct 18, 2013 at 10:33 AM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > I started to experiment with a dark theme (after Phil asked it). > The problem is that everything in morphic is so crapy programmed that > remove the hardcoding stuff is incredible hard. > Anyway, I have an initial design that could work (at least for the simple > skins), now it remains the work of decoupling the skin from the morphs... > no idea when I will finish anyway. > > Esteban > > > On Oct 18, 2013, at 10:26 AM, dimitris chloupis <thekilon(a)yahoo.co.uk> > wrote: > > I completely agree, I hate it as much I hate apples new scroll bar, that > disappear as soon as you stop scrolling with magic mouse making them > impossible to use manually. Also what with all the white ? I seriously need > to make a dark theme for pharo, my eyes start hurting ..... aaaaaaaaaaaa ;D > > > On Friday, 18 October 2013, 11:02, Esteban Lorenzano < > estebanlm(a)gmail.com> wrote: > yesterday I also adding settings for IconSet... so you should be able to > play around with themes and icons :) > > On Oct 18, 2013, at 10:06 AM, Goubier Thierry <thierry.goubier(a)cea.fr> > wrote: > > > Is unusable on some brightness settings: the scroll bars become > invisible to my old eyes :) > > > > Thierry > > -- > > 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 > > > > > > >

Oct. 18, 2013

recovering from a deep disc crashâ¦.

by Torsten Bergmann

Hardware that runs without problems must be from the "good old days". If Nico is right then I guess Pharo is already running on an "Ural-1"? Where can I download the VM? http://en.wikipedia.org/wiki/Ural_(computer) I try to imagine the size of the apartment and the way it was stolen... ;) Thats why Native Boost is so fast on newer machines, it was handcraftet on an old machine to speed it up... :) Bye T. Nico wrote: >Igor, >your hardware never failed? >It must be some special brand crafted in former soviet union ;) >2013/10/18 Igor Stasenko <siguctua at gmail.com> > >> thankfully, i never had problems with hardware: it serves me well. >> But still didn't prevented from losing precious data: the humans who break >> into my apartment and stole the machine, >> with all data it has :(

Oct. 18, 2013

Re: [Pharo-dev] default monospaced code font

by Frank Shearar

That's why we call it a bikeshed: if you ask for opinions on something deeply arcane (nuclear reactor plans, compilers, ...) you get no reaction because the investment needed to actually comment properly is just too high. But everyone knows how to build a bikeshed, so everyone fights over the colour! frank On 18 October 2013 11:57, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > Yeah, there are subjects for which every one can have a cheap and strong > opinion. > It's not like discussing the arcane of OldCompiler, gory Morphic layout > details, or whatever.. > Every one wanting to improve this area is now aware of skinny reactions :) > > > 2013/10/18 Norbert Hartl <norbert(a)hartl.name> >> >> 97 (..wellâ¦98) mails in one thread is quite a number. So fonts seems to be >> the biggest concern these days. That could say something about pharo ;) >> >> Norbert >> Am 17.10.2013 um 19:58 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >> >> > yes, that's because I failed to configure the new fonts and system >> > fallbacks to the default font... to everything. >> > anyway I switched back, while I see why font changes are not taken into >> > account. >> > >> > no log needed :) >> > >> > On Oct 17, 2013, at 7:53 PM, btc(a)openInWorld.com wrote: >> > >> >> Not sure if anyone noticed this previously, but I had a problem with >> >> Monticello repositories not showing the usual convention to bold and >> >> underline items to indicate which were in the image - and tracked this down >> >> to being introduced between builds #30469 and #30470. Coincidently this is >> >> where the default font seemed to change from DejaVu to Source Code Pro. >> >> Looks like the default is back to DejaVi in build #30497, so I'm not sure >> >> what you'd like to do about logging this as an issue. >> >> >> >> cheers -ben >> >> >> > >> > >> >> >

Oct. 18, 2013

Re: [Pharo-dev] default monospaced code font

by Nicolas Cellier

Yeah, there are subjects for which every one can have a cheap and strong opinion. It's not like discussing the arcane of OldCompiler, gory Morphic layout details, or whatever.. Every one wanting to improve this area is now aware of skinny reactions :) 2013/10/18 Norbert Hartl <norbert(a)hartl.name> > 97 (..wellâ¦98) mails in one thread is quite a number. So fonts seems to be > the biggest concern these days. That could say something about pharo ;) > > Norbert > Am 17.10.2013 um 19:58 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > > yes, that's because I failed to configure the new fonts and system > fallbacks to the default font... to everything. > > anyway I switched back, while I see why font changes are not taken into > account. > > > > no log needed :) > > > > On Oct 17, 2013, at 7:53 PM, btc(a)openInWorld.com wrote: > > > >> Not sure if anyone noticed this previously, but I had a problem with > Monticello repositories not showing the usual convention to bold and > underline items to indicate which were in the image - and tracked this down > to being introduced between builds #30469 and #30470. Coincidently this is > where the default font seemed to change from DejaVu to Source Code Pro. > Looks like the default is back to DejaVi in build #30497, so I'm not sure > what you'd like to do about logging this as an issue. > >> > >> cheers -ben > >> > > > > > > >

Oct. 18, 2013