- Pharo-dev - lists.pharo.org

[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

Re: [Pharo-dev] recovering from a deep disc crashâ¦.

by Nicolas Cellier

Igor, your hardware never failed? It must be some special brand crafted in former soviet union ;) 2013/10/18 Igor Stasenko <siguctua(a)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 :( > > > > On 18 October 2013 11:18, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > >> I remember trying to recover mail folders by reading the blocks on disk >> one by one with a binary editor... >> >> Ended learning far too much about the internal layout of an ext2 >> filesystem. >> >> But dead harddrive is nice in one way: you don't loose time trying to >> recover stuff, you know it's dead :( >> >> Thierry >> >> Le 17/10/2013 23:10, StÃ©phane Ducasse a Ã©crit : >> >> so backup your machineâ¦ because mine was still working at 8h this >>> morning and 8h40 dropped dead >>> >>> >>> >>> >> -- >> 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 >> >> > > > -- > Best regards, > Igor Stasenko. >

Oct. 18, 2013

Re: [Pharo-dev] recovering from a deep disc crashâ¦.

by Igor Stasenko

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 :( On 18 October 2013 11:18, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > I remember trying to recover mail folders by reading the blocks on disk > one by one with a binary editor... > > Ended learning far too much about the internal layout of an ext2 > filesystem. > > But dead harddrive is nice in one way: you don't loose time trying to > recover stuff, you know it's dead :( > > Thierry > > Le 17/10/2013 23:10, StÃ©phane Ducasse a Ã©crit : > > so backup your machineâ¦ because mine was still working at 8h this morning >> and 8h40 dropped dead >> >> >> >> > -- > 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 > > -- Best regards, Igor Stasenko.

Oct. 18, 2013

Re: [Pharo-dev] The Pharo 3 theme

by Goubier Thierry

Le 18/10/2013 11:18, Esteban Lorenzano a Ã©crit : > > On Oct 18, 2013, at 11:15 AM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > >> >> >> Le 18/10/2013 10:33, Esteban Lorenzano a Ã©crit : >>> I started to experiment with a dark theme (after Phil asked it). >> >> You've beaten me to it! But I know that I'm having too much on my plate at the moment. > > yeah, me too... but I also have insomnia, and those nights I usually hack something (only condition is: no regular work, just things I'm curious or exited) :) I now have so little time to myself that I can only focus on things I like :) And destroying dry walls is on my leisure schedule, not Pharo coding... >> >>> The problem is that everything in morphic is so crapy programmed that >>> remove the hardcoding stuff is incredible hard. >> >> One of the reason why I wasn't rushing to it :):) >> >>> 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. >> >> Could you reuse the Pharo theme and change the color scheme here? I expected that dark theme issue and related work to be a good test bed to redesign / modularize the theme software architecture, but if people need it, then rushing a bit and refactoring later could be the way to go. > > yes, but even the basics is hard to achieve. > So far my design is simple: let the morphs skins themselves, using a theme (or the default), and double dispatch to ensure decoupling... > > The design works, the problem is the cleanup needed to make it work (tons of places where colors and others are hardcoded). Take this as an example: > > Text class>>fromString: aString > "Answer an instance of me whose characters are those of the argument, aString." > > | defaultFontStyle fontNumber | > > defaultFontStyle := TextStyle default. > fontNumber := defaultFontStyle ifNil: 1 ifNotNil: [defaultFontStyle defaultFontIndex]. > > ^ self > string: aString > attributes:{ > (TextFontChange fontNumber: fontNumber). > ( TextColor color: Color black ) > } > > The problem is that this is constructing a Text object with hardcoded default attributes (which btw, are non necessary). > That means if you have a black (or darkGray) bg for your text areas, as soon as you accept (it creates a "clean text object") you will not be able to see your text :) > Other thing is that many of this stuff are not just bad, but also useless, I rewrote that method as: > > ^ self string: aString attributes: {} > > and everything continues working exactly as before (with the difference that now a black bg works :) Impressive, really! 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

[pharo-project/pharo-core]

by GitHub

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

Oct. 18, 2013

[pharo-project/pharo-core] dcc38d: 30499

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: dcc38d2a11f48ae493c5b77f701b535b6721aaa4 https://github.com/pharo-project/pharo-core/commit/dcc38d2a11f48ae493c5b77f… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-10-18 (Fri, 18 Oct 2013) Changed paths: R Morphic-Base.package/extension/Form/instance/defaultCanvasClass.st R Morphic-Base.package/extension/Form/instance/getCanvas.st R Morphic-Base.package/extension/Object/instance/currentWorld.st A Morphic-Core.package/extension/Color/instance/fillRectangle_on_.st A Morphic-Core.package/extension/Form/instance/defaultCanvasClass.st A Morphic-Core.package/extension/Form/instance/getCanvas.st A Morphic-Core.package/extension/Object/instance/currentWorld.st R Polymorph-Widgets.package/extension/Color/instance/fillRectangle_on_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script154.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30499.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Tests.package/PackageInfoTest.class/instance/util/packageClass.st R Tests.package/PackageInfoTest.class/instance/util/testGatherExtensionsFromSamePackage.st Log Message: ----------- 30499 11928 failing testPackageInfoTest>>testGatherExtensionsFromSamePacka https://pharo.fogbugz.com/f/cases/11928 11939 Move some extending messages to the Morphic-Core package https://pharo.fogbugz.com/f/cases/11939 http://files.pharo.org/image/30/30499.zip

Oct. 18, 2013