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

Re: [Pharo-dev] funny TIOBE
by Stephan Eggermont March 29, 2014

March 29, 2014

Sean wrote: >Maybe we died and don't know it... must be heaven, not hot enough for the other place ;) Well, I donât know. We keep on fixing bugs and donât get any closer to release :) Stephan

3 2

funny TIOBE
by Pavel Krivanek March 28, 2014

March 28, 2014

Hi, after a very long time I checked the TIOBE index and Smalltalk is not listed there at all... :-) Cheers, -- Pavel

4 3

Every class should redefine printOn:
by Pharo4Stef March 28, 2014

March 28, 2014

Hi guys Iâm trying to understand freeType and when I debug I get aBlah aFoo and this is frankly annoying because Iâm trying to learn the implementation and it does not help me at all. I hate the classes that only their implementors understand. In Pharo 4.0 I will put a strict rule: - no class will be integrated if they do not redefine printOn: - I will set a general rules to check printOn: methods. printOn: methods are the first debugging information. Stef

2 2

Re: [Pharo-dev] New Nautilus side bar buttons
by Stephan Eggermont March 28, 2014

March 28, 2014

Benjamin wrote >since I do not really like the new buttons introduced in Nautilus, >and since the previous one were broken, I propose this new set >of buttons based on the eclipse theme. Would you be so kind to explain what you do not like about them, and compare to both the earlier ones and this proposal? - I donât like that they donât adapt good enough to the chosen theme, they only fit with the Pharo3Theme; - I donât like that they do not show well that S and B provide two mutually exclusive views while I and C provide direct actions; - I donât like that they donât show well when they can be used; - I donât iike that S and B donât show the current state well - I donât like that you need the help text on hover to understand what they are for. - I donât like the alignment. This browser I look at so much, it deserves to have the letters aligned vertically correctly (visually, so C a few pixels to the left, I to the right); The main advantages they have in my opinion are: - They fit the theme; - They take much less attention away from the contents. Stephan

1 0

Re: [Pharo-dev] Release Mode
by Stephan Eggermont March 28, 2014

March 28, 2014

Philippe wrote >The look of nautilus button isn't "ok to integrate" since there is much more work needed to get this working properly. Thatâs two different issues. One is integrated, the other not. 13137 The SBIC buttons change is ok, afaik. 13135 exposes lotâs of issues in the tools. All kinds of off-by-ones in sizes. I also prefer the scrollbar fixes (13136) Stephan

4 3

Re: [Pharo-dev] New Nautilus side bar buttons
by Stephan Eggermont March 28, 2014

March 28, 2014

Nice. To make them perfect - The I and C are too dominant. Perhaps have the c use the green from âtricky assertingâ and the I a bit more pastel? Something that looks a bit more washed out like the theme? Stephan

1 0

Contribution process: broken links / missing page
by phil＠highoctane.be March 28, 2014

March 28, 2014

https://code.google.com/p/pharo/wiki/HowToContribute but then https://pharo.fogbugz.com/default.asp?W39 --> doesn't exist Then http://www.pharo-project.org/community/how-to-contribute which leads to "this page explains... --- Philippe Back Visible Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail:phil@highoctane.be | Web: http://philippeback.eu Blog: http://philippeback.be | Twitter: @philippeback Youtube: http://www.youtube.com/user/philippeback/videos High Octane SPRL rue cour Boisacq 101 | 1301 Bierges | Belgium Pharo Consortium Member - http://consortium.pharo.org/ Featured on the Software Process and Measurement Cast - http://spamcast.libsyn.com Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller

1 0

Re: [Pharo-dev] Release Mode
by Stephan Eggermont March 28, 2014

March 28, 2014

Sean wrote: >As cool as they are, are: >- changing the look of Nautilus buttons >showstopping bugs?! Yes. Or at least they should be. Releases are for new users. There the first impression is crucial. We are all used to these ugly buttons and know that the functionality is the same. New users donât know that and expect things that look different to behave differently. They are also important for people following new technologies trying to decide which ones to adopt. Not fixing these things essentially says our community is so resource-starved we cannot afford to spend time fixing such obvious mistakes. That is not the message I want to send with a new release. Stephan

1 0

New website about Spec - http://spec.st
by Benjamin March 28, 2014

March 28, 2014

Hi guys :) I am glad to announce (even if Philippe already let the cat out :P) a website dedicated to Spec: http://spec.st. You can find a quick introduction, documentation (mainly what is now in the Pharo For The Enterprise book), and a news feed where I will explain the API changes, the news widgets introduce etc. The website contents can be found here (https://github.com/spec-framework/website) so if you want to contribute you are welcome :) Ben PS: I would like to thank Johan Fabry who helped me a lot writing the documentation, Sean P. DeNigris who fixed my english a couple of times and Nicolas Petton who helped me on the website look and feel

4 5

someone using Magritte-Morph?
by Esteban Lorenzano March 28, 2014

March 28, 2014

Hi, It looks to me that this: MAListMorph>>#strings ^ self options collect: [ :each | self magritteDescription reference toString: each ] should instead be: MAListMorph>>#strings ^ self options collect: [ :each | self magritteDescription displayStringFor: each ] what do you think? Esteban

3 2