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

Re: [Pharo-dev] Xtreams in Pharo 3

by Sven Van Caekenberghe

Hi Nicolas, On 19 Nov 2013, at 23:50, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > For the OpalCompiler support, I have simply added the compiler method in Xtreams-Parsing because it does not conflict with anything else, I have the feeling that this is bearableâ¦ OK > I have also added a NotFoundError subclass of NotFound in Xtreams-support. > It's not ideal. That also means that bleeding-edge will not load in Squeak 4.4 or older, and maybe not elder version of Pharoâ¦ > Maybe I could have changed NotFoundError reference into NotFound? NotFound is in Pharo 2.0 as well. I wonder if it is really necessary to use the VW name/alias, as it is not referenced, but OK, it could be. I donât think it is as much part of the API as Incomplete is. > In the future, or if we really want a bleeding edge in elder images, we may have to fork the Xtreams-support, but as long as we can, it's better to avoid it. I think that it would be good to keep this a cross platform project (as it spans multiple platforms already). But that requires effort (at least, basic interest, maintenance from multiple people on different platforms). Fuel proves that it can be done. I think it is unavoidable to have some specific code per platform, especially in Support. But indeed, not for the sake of it. I was looking around in the source code and saw some places where I could imagine things being done differently (ZnCharacterEncoders in Pharo are properly Character <> Binary). BTW, does TerminalsFileSystem work on Squeak or is it Pharo specific. Because FileUrl is on its way out (replaced by ZnUrl). The #reading, #writing, #appending messages on FileUrl, in their current implementation, strike me as a bit out of place (as far as I can see, they are not in the VW code either). I mean, I could image #reading or #writing am HTTP Url as well, though that would not necessarily the best design. Doing a #asFileReference in between is acceptable and clearer. Are there any areas in the port of Xtreams that need more work, or do you consider the current situation as complete enough ? In other words, is there a todo list ? Are there version differences with the VW code, and how do you see that evolving ? Sven > 2013/11/19 Sven Van Caekenberghe <sven(a)stfx.eu> > > On 18 Nov 2013, at 22:33, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > Ah, NotFoundError is also undeclared in Squeak, it is the VisualWorks class name. > > It could go into Xtreams-Support... > > OK, are you going to check this in, or should I ? > > How are we going to deal with platform specific stuff (like the Opal compiler switch) ? > > Sven >

Nov. 20, 2013

Re: [Pharo-dev] Spotlight behaviour

by Esteban Lorenzano

so... here you have it: http://smalltalkhub.com/#!/~estebanlm/Pharo3DarkTheme Esteban On Nov 20, 2013, at 4:29 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > On 20 Nov 2013, at 15:45, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > >> The problem with dark themes is that they require icons prepared for >> dark backgrounds. And not only in terms of alpha channels, but also in >> terms of contrast. >> >> I like the dark theming of Adobe products, or the "gray" theming of >> video editing software. >> But I once read that it was made dark to give prominence to the >> subject of the editor, in this case pictures and videos. >> >> Sublime Text and even Vim can afford this, because they're code pane >> centric editors. >> In our case, what should have the prominence? The code pane? the >> selectors in the browser? > > I have no idea, but huge white pane kills my eyes :) > >> >> Anyhow, I like the fact Pharo looks better and better. >> I'd only want that no operation other than painting/event dispatching >> take place in the main (UI?) thread. :) >> >> Regards, >> Esteban A. Maringolo >> >> >> 2013/11/20 Esteban Lorenzano <estebanlm(a)gmail.com>: >>> btw... my goal is to achieve this: >>> >>> http://blog.jetbrains.com/blog/2013/06/11/inside-darcula-look-and-feel-an-i… >>> >>> (as Phil suggested some time ago, in a thread which was the reason I started to try a dark theme). >>> >>> Also... my intention is to contribute to clean a bit morphic by removing silly hardcode stuff and creating a separation betweek "skin" and "morph"... and more important, to easy the creation of new skins. >>> >>> but I still do not find a design that satisfy me... we'll see. >>> >>> Esteban >>> >>> On Nov 20, 2013, at 3:18 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>>> ok... I will package it and made it available in the course of the day then. >>>> more hands means faster results :) >>>> >>>> Esteban >>>> >>>> On Nov 20, 2013, at 2:53 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>>> >>>>> On 20 Nov 2013, at 14:42, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>>> >>>>>> :) >>>>>> >>>>>> <Screen Shot 2013-11-20 at 2.40.12 PM.png> >>>>>> >>>>>> I'm slowly working in a darktheme... problem is the INCREDIBLE amount of hardcode colors and silly code. >>>>>> So it will take some time until is ready (also because I work on it when I'm bored and not wanting to do what I should do... like today :P) >>>>> >>>>> Hey, Esteban, that looks already quite impressive. >>>>> I am sure there are some people really anxious to try this and help. >>>>> Is this theme already available somewhere ? >>>>> >>>>>> Esteban >>>>>> >>>>>> >>>>>> On Nov 20, 2013, at 2:34 PM, kilon alios <kilon.alios(a)gmail.com> wrote: >>>>>> >>>>>>> yes I can confirm that this work also on windoom 7. Indeed Sven your Pharo looks a bit more sexy than mine. >>>>>>> >>>>>>> the code you posted works also like a charm for me , thank you. Now If I could get also a dark theme working with pharo that would be awesome. All this white hurts my eyes. But I guess I will have to compromise for the time being :) >>>>>>> >>>>>>> thank you >>>>>>> >>>>>>> >>>>>>> On Wed, Nov 20, 2013 at 2:58 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>>>>> >>>>>>> On 20 Nov 2013, at 13:46, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>>>>>> >>>>>>>> Sven. >>>>>>>> >>>>>>>> What version are YOU using? Fonts and windows look so clean an sharp! :) >>>>>>> >>>>>>> ;-) >>>>>>> >>>>>>> Yes they are. >>>>>>> >>>>>>> Like I said, Pharo version #30582 >>>>>>> >>>>>>> defaultFont Source Sans Pro Normal points: 12 height: 21 >>>>>>> listFont Source Sans Pro Normal points: 12 height: 21 >>>>>>> menuFont Source Sans Pro Normal points: 12 height: 21 >>>>>>> windowTitleFont Source Sans Pro Bold points: 12 height: 21 >>>>>>> balloonFont Source Sans Pro Normal points: 9 height: 16 >>>>>>> codeFont Source Code Pro Normal points: 11 height: 19 >>>>>>> buttonFont Source Sans Pro Normal points: 12 height: 21 >>>>>>> haloFont Source Sans Pro Normal points: 9 height: 16 >>>>>>> >>>>>>> Installed with a script from our local look and feel guru, Doru: >>>>>>> >>>>>>> #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' 'SourceSansProBoldâ) >>>>>>> do: [ :each | >>>>>>> Smalltalk globals >>>>>>> at: each asSymbol >>>>>>> ifAbsent: [ >>>>>>> Gofer new >>>>>>> smalltalkhubUser: 'girba' project: 'FreeFonts'; >>>>>>> package: each; >>>>>>> load ]. >>>>>>> (Smalltalk at: each asSymbol) new install ]. >>>>>>> FreeTypeSystemSettings loadFt2Library: true. >>>>>>> FreeTypeFontProvider current updateFromSystem. >>>>>>> >>>>>>> StandardFonts >>>>>>> setAllStandardFontsTo: (LogicalFont familyName: 'Source Sans Pro' pointSize: 12); >>>>>>> haloFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 9); >>>>>>> windowTitleFont: (LogicalFont familyName: 'Source Sans Pro Bold' pointSize: 12); >>>>>>> balloonFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 9); >>>>>>> codeFont: (LogicalFont familyName: 'Source Code Pro' pointSize: 11). >>>>>>> >>>>>>> And then I finally make the window font bold, manually. >>>>>>> >>>>>>> The screenshot was done on Mac OS X 10.9 >>>>>>> >>>>>>> HTH, >>>>>>> >>>>>>> Sven >>>>>>> >>>>>>>> Esteban A. Maringolo >>>>>>>> >>>>>>>> >>>>>>>> 2013/11/20 Sven Van Caekenberghe <sven(a)stfx.eu> >>>>>>>> What version are you using ? >>>>>>>> >>>>>>>> In #30582 it does work: >>>>>>>> <Screen Shot 2013-11-20 at 13.34.46.png> >>>>>>>> >>>>>>>> You can always try typing a space after Objectâ¦ >>>>>>>> >>>>>>>> Sven >>>>>>>> >>>>>>>> On 20 Nov 2013, at 13:23, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>>>>>>> >>>>>>>>> HI, >>>>>>>>> >>>>>>>>> do you know why search behaves like this? I was expecting Object to show up >>>>>>>>> >>>>>>>>> <Screenshot 2013-11-20 13.20.40.png> >>>>>>>>> >>>>>>>>> >>>>>>>>> Cheers >>>>>>>>> Uko >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>> >>> >>> >> > >

Nov. 20, 2013

Re: [Pharo-dev] Convert to Athens

by J.F. Rick

Thanks. It works. I already have found a few bugs and one thing I don't understand. (1) A few Paint things seem to implement athensFillRectangle:on: and athensFillPath:on: rather than fillRectangle:on: and fillPath:on:. It seems like it should be the latter rather than the former. I changed the names and the evil rectangle of doom disappeared. (2) Using the AthenWrapMorph, it seems that the bottom row of pixels is not rendered or clipped. I can stop this phenomenon by changing the createSurface method to have the extent be 0@1 bigger. While that works, it seems like there's a bug somewhere in AthensCairoSurface. (3) I ended up changing a morph so that it should render differently. In standard Pharo, I just use "self changed" and it updates. Is there an equivalent in Athens? Do I have to explicitly tell Athens to rerender it? If so, how? I tried "self render" but that did not seem to help. Cheers, Jeff On Wed, Nov 20, 2013 at 11:08 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > http://www.smalltalkhub.com/#!/~Pharo/Athens > > > On 20 November 2013 09:04, J.F. Rick <self(a)je77.com> wrote: > >> Right. Where is this Athens repository? I have the latest in Pharo30/main >> (Athens-Morphic-MarcusDenker.23.mcz) and that does not seem to include >> AthensWrapperMorph. >> >> Cheers, >> >> Jeff >> >> >> On Wed, Nov 20, 2013 at 8:35 AM, Igor Stasenko <siguctua(a)gmail.com>wrote: >> >>> >>> >>> >>> On 19 November 2013 17:42, J.F. Rick <self(a)je77.com> wrote: >>> >>>> Indeed. I would like to know that. It doesn't seem to be included in >>>> the latest Pharo 3.0. >>>> >>>> >>> it could be not yet included. >>> in that case, load most recent Athens-Morphic package from athens >>> repository. >>> >>> >>> >>>> Cheers, >>>> >>>> Jeff >>>> >>>> >>>> On Fri, Nov 15, 2013 at 7:34 PM, Hilaire Fernandes < >>>> hilaire.fernandes(a)gmail.com> wrote: >>>> >>>>> Le 15/11/2013 14:17, Igor Stasenko a Ã©crit : >>>>> > >>>>> > for transition , i implemented a special morph, AthensWrapMorph >>>>> > which wraps (as its name says) its children morphs and forces them >>>>> to be >>>>> > rendered by athens >>>>> > (the child morphs will never receive #drawOn: but >>>>> #drawOnAthensCanvas: >>>>> > instead ). >>>>> >>>>> >>>>> I guess Jeff, may want to know where to find this wrapper. >>>>> >>>>> Hilaire >>>>> >>>>> >>>>> -- >>>>> Dr. Geo http://drgeo.eu >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Jochen "Jeff" Rick, Ph.D. >>>> http://www.je77.com/ >>>> Skype ID: jochenrick >>>> >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >> >> >> >> -- >> Jochen "Jeff" Rick, Ph.D. >> http://www.je77.com/ >> Skype ID: jochenrick >> > > > > -- > Best regards, > Igor Stasenko. > -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

Nov. 20, 2013

Re: [Pharo-dev] http://smalltalkhub.com/ down?

by Camillo Bruni

sorry, seems like the local network was down for 30secs :) On 2013-11-20, at 17:01, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > no > On 20 Nov 2013, at 16:58, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> subj > >

Nov. 20, 2013

Re: [Pharo-dev] http://smalltalkhub.com/ down?

by Yuriy Tymchuk

no On 20 Nov 2013, at 16:58, Camillo Bruni <camillobruni(a)gmail.com> wrote: > subj

Nov. 20, 2013

http://smalltalkhub.com/ down?

by Camillo Bruni

subj

Nov. 20, 2013

Multithreading

by Yuriy Tymchuk

Hi everyone, is there any chapter on multithreading in Pharo books? If not maybe Iâll write something about that, but any material will be useful for me right now.

Nov. 20, 2013

[pharo-project/pharo-core]

by GitHub

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

Nov. 20, 2013

[pharo-project/pharo-core] 361d2e: 30586

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 361d2ea339d2fd9ad1aadd95649c36b5d023973e https://github.com/pharo-project/pharo-core/commit/361d2ea339d2fd9ad1aadd95… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-11-20 (Wed, 20 Nov 2013) Changed paths: A Collections-Abstract.package/Collection.class/instance/math functions/sumNumbers_.st A CollectionsTests.package/TIterateTest.class/instance/tests - iterating/testSumNumbers.st M Nautilus.package/PackageTreeNautilusUI.class/instance/private dispatch/renameClassCategory_.st M Nautilus.package/PackageTreeNautilusUI.class/instance/private dispatch/renamePackageCategory_.st A Nautilus.package/PackageTreeNautilusUI.class/instance/private/basicRenamePackage_.st M RPackage-Core.package/RPackage.class/instance/accessing/name_.st R RPackage-Core.package/RPackage.class/instance/as yet unclassified/removeClassTagsForClassNamed_.st A RPackage-Core.package/RPackage.class/instance/class tags/removeClassTagsForClassNamed_.st A RPackage-Core.package/RPackage.class/instance/private/renameTagsPrefixedWith_to_.st A RPackage-Core.package/RPackageTag.class/instance/accessing/nameWithoutPackagePrefix.st R RPackage-Core.package/RPackageTag.class/instance/accessing/nameWthoutPackagePrefix.st M RPackage-Core.package/RPackageTag.class/instance/accessing/renameTo_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script241.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30586.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30586 12204 Pharo3Theme beCurrent https://pharo.fogbugz.com/f/cases/12204 12200 Rename RPackage does not rename class tags https://pharo.fogbugz.com/f/cases/12200 12182 Collection>>sumNumbers: should provide an alternative to failing sum: https://pharo.fogbugz.com/f/cases/12182 http://files.pharo.org/image/30/30586.zip

Nov. 20, 2013

Re: [Pharo-dev] Spotlight behaviour

by Yuriy Tymchuk

On 20 Nov 2013, at 15:45, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > The problem with dark themes is that they require icons prepared for > dark backgrounds. And not only in terms of alpha channels, but also in > terms of contrast. > > I like the dark theming of Adobe products, or the "gray" theming of > video editing software. > But I once read that it was made dark to give prominence to the > subject of the editor, in this case pictures and videos. > > Sublime Text and even Vim can afford this, because they're code pane > centric editors. > In our case, what should have the prominence? The code pane? the > selectors in the browser? I have no idea, but huge white pane kills my eyes :) > > Anyhow, I like the fact Pharo looks better and better. > I'd only want that no operation other than painting/event dispatching > take place in the main (UI?) thread. :) > > Regards, > Esteban A. Maringolo > > > 2013/11/20 Esteban Lorenzano <estebanlm(a)gmail.com>: >> btw... my goal is to achieve this: >> >> http://blog.jetbrains.com/blog/2013/06/11/inside-darcula-look-and-feel-an-i… >> >> (as Phil suggested some time ago, in a thread which was the reason I started to try a dark theme). >> >> Also... my intention is to contribute to clean a bit morphic by removing silly hardcode stuff and creating a separation betweek "skin" and "morph"... and more important, to easy the creation of new skins. >> >> but I still do not find a design that satisfy me... we'll see. >> >> Esteban >> >> On Nov 20, 2013, at 3:18 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >>> ok... I will package it and made it available in the course of the day then. >>> more hands means faster results :) >>> >>> Esteban >>> >>> On Nov 20, 2013, at 2:53 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>>> >>>> On 20 Nov 2013, at 14:42, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> >>>>> :) >>>>> >>>>> <Screen Shot 2013-11-20 at 2.40.12 PM.png> >>>>> >>>>> I'm slowly working in a darktheme... problem is the INCREDIBLE amount of hardcode colors and silly code. >>>>> So it will take some time until is ready (also because I work on it when I'm bored and not wanting to do what I should do... like today :P) >>>> >>>> Hey, Esteban, that looks already quite impressive. >>>> I am sure there are some people really anxious to try this and help. >>>> Is this theme already available somewhere ? >>>> >>>>> Esteban >>>>> >>>>> >>>>> On Nov 20, 2013, at 2:34 PM, kilon alios <kilon.alios(a)gmail.com> wrote: >>>>> >>>>>> yes I can confirm that this work also on windoom 7. Indeed Sven your Pharo looks a bit more sexy than mine. >>>>>> >>>>>> the code you posted works also like a charm for me , thank you. Now If I could get also a dark theme working with pharo that would be awesome. All this white hurts my eyes. But I guess I will have to compromise for the time being :) >>>>>> >>>>>> thank you >>>>>> >>>>>> >>>>>> On Wed, Nov 20, 2013 at 2:58 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>>>> >>>>>> On 20 Nov 2013, at 13:46, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>>>>> >>>>>>> Sven. >>>>>>> >>>>>>> What version are YOU using? Fonts and windows look so clean an sharp! :) >>>>>> >>>>>> ;-) >>>>>> >>>>>> Yes they are. >>>>>> >>>>>> Like I said, Pharo version #30582 >>>>>> >>>>>> defaultFont Source Sans Pro Normal points: 12 height: 21 >>>>>> listFont Source Sans Pro Normal points: 12 height: 21 >>>>>> menuFont Source Sans Pro Normal points: 12 height: 21 >>>>>> windowTitleFont Source Sans Pro Bold points: 12 height: 21 >>>>>> balloonFont Source Sans Pro Normal points: 9 height: 16 >>>>>> codeFont Source Code Pro Normal points: 11 height: 19 >>>>>> buttonFont Source Sans Pro Normal points: 12 height: 21 >>>>>> haloFont Source Sans Pro Normal points: 9 height: 16 >>>>>> >>>>>> Installed with a script from our local look and feel guru, Doru: >>>>>> >>>>>> #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' 'SourceSansProBoldâ) >>>>>> do: [ :each | >>>>>> Smalltalk globals >>>>>> at: each asSymbol >>>>>> ifAbsent: [ >>>>>> Gofer new >>>>>> smalltalkhubUser: 'girba' project: 'FreeFonts'; >>>>>> package: each; >>>>>> load ]. >>>>>> (Smalltalk at: each asSymbol) new install ]. >>>>>> FreeTypeSystemSettings loadFt2Library: true. >>>>>> FreeTypeFontProvider current updateFromSystem. >>>>>> >>>>>> StandardFonts >>>>>> setAllStandardFontsTo: (LogicalFont familyName: 'Source Sans Pro' pointSize: 12); >>>>>> haloFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 9); >>>>>> windowTitleFont: (LogicalFont familyName: 'Source Sans Pro Bold' pointSize: 12); >>>>>> balloonFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 9); >>>>>> codeFont: (LogicalFont familyName: 'Source Code Pro' pointSize: 11). >>>>>> >>>>>> And then I finally make the window font bold, manually. >>>>>> >>>>>> The screenshot was done on Mac OS X 10.9 >>>>>> >>>>>> HTH, >>>>>> >>>>>> Sven >>>>>> >>>>>>> Esteban A. Maringolo >>>>>>> >>>>>>> >>>>>>> 2013/11/20 Sven Van Caekenberghe <sven(a)stfx.eu> >>>>>>> What version are you using ? >>>>>>> >>>>>>> In #30582 it does work: >>>>>>> <Screen Shot 2013-11-20 at 13.34.46.png> >>>>>>> >>>>>>> You can always try typing a space after Objectâ¦ >>>>>>> >>>>>>> Sven >>>>>>> >>>>>>> On 20 Nov 2013, at 13:23, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>>>>>> >>>>>>>> HI, >>>>>>>> >>>>>>>> do you know why search behaves like this? I was expecting Object to show up >>>>>>>> >>>>>>>> <Screenshot 2013-11-20 13.20.40.png> >>>>>>>> >>>>>>>> >>>>>>>> Cheers >>>>>>>> Uko >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>> >> >> >

Nov. 20, 2013