- Pharo-dev - lists.pharo.org

The Pharo 3 theme
by Goubier Thierry Oct. 18, 2013

Oct. 18, 2013

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

6 10

default monospaced code font
by Pavel Krivanek Oct. 18, 2013

Oct. 18, 2013

Hi, the issue that sets the new Pharo 3.0 look&feel uses a monospaced font for the code. It is only a coincidence that it is not set this way in the prebuild Pharo image. I have big doubts if this is the way to go. I think that proportional fonts are more natural for Smalltalk and without them the code is harder to read and not so beauty. I think that something like elastic tabstops would be much better solution. http://tibleiz.net/code-browser/elastic-tabstops.html On the other way, it is only my personal opinion and if you think that the Eclipse-like look will attract more new users... -- Pavel

25 94

[pharo-project/pharo-core]
by GitHub Oct. 18, 2013

Oct. 18, 2013

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

1 0

[pharo-project/pharo-core] dcc38d: 30499
by GitHub Oct. 18, 2013

Oct. 18, 2013

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

1 0

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Oct. 18, 2013

Oct. 18, 2013

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

1 0

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Oct. 18, 2013

Oct. 18, 2013

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

1 0

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Oct. 18, 2013

Oct. 18, 2013

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

1 0

realtime
by Paul Davidowitz Oct. 18, 2013

Oct. 18, 2013

Can Pharo be used for 'realtime' applications such as music midi or metronome? Isn't garbage collection a concern? (But I once read that Tektronix used Smalltalk in their oscilloscopes.) Thanks, -Paul

3 2

IMPORTANT: RPackage behavior changed and Nautilus updated
by Esteban Lorenzano Oct. 18, 2013

Oct. 18, 2013

Hi, I just important an important change in Pharo. I made a new step over the integration of RPackage into the system, and as a result there is a different behavior. Although 99% of users shouldn't notice it, that can drive to headaches to tool developers, like Thierry and his AltBrowser (but I'm not sure about that) :) I'm sorry, but this is inevitable... and part of a long path discussed and adopted since almost 1 1/2 years. So, what's the change? Now 1 RPackage 0 1 MCPackage. As a result, package granularity is coarse, and then categories for class are stored as package tags. Other consequence is that RPackageSet is now more or less useless, but I'm keeping it because it provides caching services for monticello, and the speed up resulting is good :) This change opens the path to remove old PackageInfo, finally :) To take the new structure into account (and to add a long time awaited feature), I modified nautilus to use a tree instead a simple list (finally!) And since I was in the mood, I moved groups to same list, taking the idea of the screenshot Stef sent the other day (lots of good ideas that we should adopt there), and then I removed the "groups" button... in functionality is good, but visually not so much... I accept ideas about :) THERE WILL BE BUGS! This is a really deep and important change, I'm pushing it because we need to test and fix. So, do not hesitate to send your reports! Also, there are features in modified-nautilus that are missing. It would be good to have a list of them so I can implement it :) Please, report any issue around. Enjoy, Esteban

7 17

recovering from a deep disc crashâ¦.
by Torsten Bergmann Oct. 17, 2013

Oct. 17, 2013

Hope you dont burn the disk packs and start something new when things starts to get interesting ...

1 0