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

Re: [Pharo-dev] [Pharo-users] Please contributors fill up this form...

by Norbert Hartl

PharoContributor new name: 'Norbert Hartl'; email: 'norbert(a)hartl.name'; website: 'http://norbert.hartl.name'; description: 'Software engineer at 2denker GmbH, cologne, germany.'; yourself. Am 09.10.2013 um 13:34 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Hi guys > > I would like to get > contributors.pharo.org a bit more representative of Pharo. > > We should have Previous contributors and enhance the current list. > Can you please reply to this mail > > PharoContributor new > name: 'Esteban Lorenzano'; > id: 'estebanlm'; > email: 'estebanlm(a)gmail.com'; > website: 'http://smallworks.eu'; > description: 'Pharo core team. Contributor of several projects, including Kernel, DBXTalk, Voyage, Mars, etc. Also I work on the VM.'; > image: 'http://www.gravatar.com/avatar/193af464509ae8fbcc04abad70b72fc0?s=120'; > yourself > > > Stef

Oct. 15, 2013

Re: [Pharo-dev] default monospaced code font

by Sven Van Caekenberghe

On 15 Oct 2013, at 08:30, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > 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 Yeah, I can't imagine many Smalltalkers liking a mono-spaced font, I personally hate it. > On the other way, it is only my personal opinion and if you think that > the Eclipse-like look will attract more new users... I don't like Eclipse ;-) But like Marcus says, it is just a different icon set. We want win any points on originality or personality though, which is a missed opportunity.

Oct. 15, 2013

Re: [Pharo-dev] https://pharo.fogbugz.com ??

by nicolas petton

Hi! I could give you access to the image and seaside panel. Would that be enough? Else we could move the website somewhere else. Nico On Oct 15, 2013 8:30 AM, "Marcus Denker" <marcus.denker(a)inria.fr> wrote: > > On Oct 15, 2013, at 12:13 AM, Camillo Bruni <camillobruni(a)gmail.com> > wrote: > > > The full description should be up here: > https://pharo.fogbugz.com/default.asp?pre=preLogOff > > > > I wish I could update the bugs.pharo.org website :/ > > > > Yes, we need to make this website deployed in a way that it is fixable by > anyoneâ¦ there are some > things that need to be done that have not been done in Months. > > Marcus > >

Oct. 15, 2013

Re: [Pharo-dev] default monospaced code font

by Henrik Johansen

On Oct 15, 2013, at 8:30 , Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > 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. +1 from me, I much prefer a proportional font, and letting the auto-format take care of alignment with tabs for the elements that need it. It may not be 100%, but it's good enough that I don't feel I'm using a large quantity of coding time actually formatting my code. If switching to monospaced, at least do so for ALL elements in the browser, mixing font like in that bottom picture (other than emphasis/size) is *really* jarring to the eye. Cheers, Henry

Oct. 15, 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/label=wi… 1 regressions found. Zinc.Tests.ZnServerTests.testRequestLineTooLong

Oct. 15, 2013

Re: [Pharo-dev] Is there a Roadmap for Pharo 3.0 and Pharo 4.0

by Marcus Denker

On Oct 15, 2013, at 9:44 AM, kilon <thekilon(a)yahoo.co.uk> wrote: > I really like the idea of roadmap. In an open source project people are free > to work in anything they like , even bring new nice features of their design > as long as they don't disturb the existing code. > > But the same people, including me, or even mere users , wonder where the > software is heading. Even an exploration ship , that sets to explore new > areas has goals. I would like to see in the pharo website a roadmap not just > for 3 but even for pharo 4. I know that Stephane has given a presentation > about pharo 3 roadmap , maybe you could link those slides. > > So what is the future of pharo ? > > Another request for the website would be a small collection of bullet points > about what makes Pharo special, in the about section there is a very general > description of what pharo is. I would like something more concrete. I want > specific features, specific libraries. Assume that people reading this have > no idea what smalltalk is and no idea what Squeak is. 10-30 bullet points > should be a good start. No lengthy descriptions, straight to the point. > > What you feel about this ? > Yes, we should do that. I will put an item on my TODO. Marcus

Oct. 15, 2013

Re: [Pharo-dev] default monospaced code font

by kilon

I don't like Eclipse myself, I do like the new icons. We can definitely "steal" some ideas from Eclipse. One I liked was perspectives, which are windows layout setups. I also don't like that pharo has poped up windows and I prefer Eclipse approach of more like docked windows. So we can definitely takes some good ideas from Eclipse and unite them with the good ideas of Pharo , while leave Eclipse bad ideas out. about elastic fonts, I am not against it, as long as it does not complicate things up. I can't say I have an issue reading pharo code. For me managing multiple windows is far more bothersome problem. The question as always whos the one that will implement it ? Because its one thing to like it, another to implement it :D Marcus Denker-4 wrote > On Oct 15, 2013, at 8:31 AM, Pavel Krivanek < > pavel.krivanek@ > > wrote: > >> 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. >> > > technical problem, fonts are somehow resetted on the build server, no idea > why. > >> tI 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 >> > It's a matter of taste I fearâ¦ we will see if everyone is against it or > not. > First we should set those fonts that where meant to be set and try. > >> On the other way, it is only my personal opinion and if you think that >> the Eclipse-like look will attract more new usersâ¦ > > For me who never uses eclipse they just are cleaner iconsâ¦ > > Marcus > > > signature.asc (210 bytes) > <http://forum.world.st/attachment/4714435/0/signature.asc> -- View this message in context: http://forum.world.st/default-monospaced-code-font-tp4714433p4714460.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 15, 2013

[pharo-project/pharo-core]

by GitHub

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

Oct. 15, 2013

[pharo-project/pharo-core] 503455: 30484

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 5034553d07f342a5a0e512757a04e6afec677d96 https://github.com/pharo-project/pharo-core/commit/5034553d07f342a5a0e51275… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-10-15 (Tue, 15 Oct 2013) Changed paths: A Graphics-Primitives.package/Color.class/instance/queries/isTranslucentButNotTransparent.st M Graphics-Primitives.package/Color.class/instance/transformations/orColorUnlike_.st A Graphics-Tests-Primitives.package/RectangleTest.class/instance/tests/testWithBottomDoesNotProduceInvalidRectangle.st A Graphics-Tests-Primitives.package/RectangleTest.class/instance/tests/testWithLeftDoesNotProduceInvalidRectangle.st A Graphics-Tests-Primitives.package/RectangleTest.class/instance/tests/testWithRightDoesNotProduceInvalidRectangle.st A Graphics-Tests-Primitives.package/RectangleTest.class/instance/tests/testWithTopDoesNotProduceInvalidRectangle.st A Growl.package/GrowlMorph.class/class/instance creation/openWithLabel_contents_backgroundColor_labelColor_.st M Growl.package/GrowlMorph.class/definition.st M Growl.package/GrowlMorph.class/instance/accessing/alpha_.st M Growl.package/GrowlMorph.class/instance/accessing/contentsColor.st A Growl.package/GrowlMorph.class/instance/accessing/contentsColor_.st M Growl.package/GrowlMorph.class/instance/accessing/labelColor.st A Growl.package/GrowlMorph.class/instance/accessing/labelColor_.st M Growl.package/GrowlMorph.class/instance/building/label_contents_.st A Growl.package/GrowlMorph.class/instance/initialization/contentsAttributes.st A Growl.package/GrowlMorph.class/instance/initialization/createDismissHandle.st A Growl.package/GrowlMorph.class/instance/initialization/initializeContentsAttributes.st A Growl.package/GrowlMorph.class/instance/initialization/initializeLabelAttributes.st A Growl.package/GrowlMorph.class/instance/initialization/labelAttributes.st A Growl.package/GrowlMorph.class/instance/initialization/nextColorStep_.st R Growl.package/GrowlMorph.class/instance/initialize/contentsAttributes.st R Growl.package/GrowlMorph.class/instance/initialize/createDismissHandle.st R Growl.package/GrowlMorph.class/instance/initialize/initializeContentsAttributes.st R Growl.package/GrowlMorph.class/instance/initialize/initializeLabelAttributes.st R Growl.package/GrowlMorph.class/instance/initialize/labelAttributes.st R Growl.package/GrowlMorph.class/instance/initialize/nextColorStep_.st M Kernel-BasicObjects.package/Rectangle.class/instance/rectangle functions/withBottom_.st M Kernel-BasicObjects.package/Rectangle.class/instance/rectangle functions/withLeft_.st M Kernel-BasicObjects.package/Rectangle.class/instance/rectangle functions/withRight_.st M Kernel-BasicObjects.package/Rectangle.class/instance/rectangle functions/withTop_.st A Morphic-Base-Basic.package/PolygonMorph.class/instance/access/borderColor_.st R Morphic-Base-Basic.package/PolygonMorph.class/instance/accessing/borderColor_.st M Morphic-Base-Basic.package/PolygonMorph.class/instance/drawing/drawOnFormCanvas_.st M Morphic-Base-Basic.package/PolygonMorph.class/instance/private/filledForm.st R Morphic-Base-Basic.package/StringMorph.class/instance/accessing/hasTranslucentColor.st A Morphic-Base-Basic.package/StringMorph.class/instance/accessing/isTranslucentButNotTransparent.st R Morphic-Base-Basic.package/TextMorph.class/instance/accessing/hasTranslucentColor.st A Morphic-Base-Basic.package/TextMorph.class/instance/accessing/isTranslucentButNotTransparent.st R Morphic-Base-Kernel.package/BorderedMorph.class/instance/accessing/hasTranslucentColor.st A Morphic-Base-Kernel.package/BorderedMorph.class/instance/testing/isTranslucentButNotTransparent.st M Morphic-Base-Kernel.package/Morph.class/instance/accessing/hasTranslucentColor.st M Morphic-Base-Kernel.package/Morph.class/instance/accessing/wantsToBeCachedByHand.st A Morphic-Base-Kernel.package/Morph.class/instance/testing/isTranslucentButNotTransparent.st M Morphic-Base-MorphTreeWidget.package/MorphTreeMorph.class/instance/column handling/headerBounds.st M Morphic-Base-MorphTreeWidget.package/MorphTreeNodeMorph.class/instance/accessing/spacerWidth.st M Morphic-Base-Text Support.package/Paragraph.class/class/settings/insertionPointColor.st M Morphic-Base-Text Support.package/Paragraph.class/instance/selection/selectionRectsFrom_to_.st M Morphic-Base-Windows.package/SystemWindow.class/instance/testing/wantsToBeCachedByHand.st M Nautilus.package/AbstractNautilusUI.class/instance/private/runPackagesTestsNotifying_.st M Nautilus.package/NautilusUI.class/instance/widget - method/notifyTitle_contents_.st M Nautilus.package/NautilusUI.class/instance/widget - method/notifyTitle_contents_color_.st M Polymorph-Widgets-Themes.package/ThemeSettings.class/instance/accessing/menuShadowColor.st M Polymorph-Widgets-Themes.package/ThemeSettings.class/instance/accessing/secondarySelectionColor.st M Polymorph-Widgets-Themes.package/ThemeSettings.class/instance/accessing/selectionColor.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script139.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30484.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Tools-Editor.package/ColorEditor.class/instance/initialization/updateColor.st Log Message: ----------- 30484 issue 11867: GrowlEnhancements so that we can see the text when Sunit is running https://pharo.fogbugz.com/f/cases/11867 issue 11866 More Degenerated Rectangle fixed https://pharo.fogbugz.com/f/cases/11866 issue 11519 Merge Color and Translucent Color (part 1) Just the little improvements first https://pharo.fogbugz.com/f/cases/11519 http://files.pharo.org/image/30/30484.zip

Oct. 15, 2013

[update 3.0] #30484

by StÃ©phane Ducasse

Oct. 15, 2013