- Pharo-dev - lists.pharo.org

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

by Marcus Denker

On Oct 15, 2013, at 12:56 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On Oct 15, 2013, at 9:43 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. > > the problem with this is that we do not have a clear roadmap for Pharo4 (yet). > How it works now is: at the beginning of a year iteration we make a list of what we want, taking into account what emerged latest year (both new possibilities opened and new/old problems that emerged). > > That gives us what we can more or less call a "next release road map". And is "more or less" because situation can change. For example we wanted a complete revamp of Pharo3 L&F, and we wanted also a complete migration of Morph to be rendered with Athens, and reality showed that is not achievable this year... so it will wait until next one (and that does not means at all that we stopped work on that area, just that the completion of the task will take more time than expected). > So... what's the roadmap for Pharo4? No Idea :) > What we already know is that we made a huge move forward in infrastructure for Pharo3 (starting by Opal, but not restrained to that), and now we want to focus in the tools (but without doing *just* that, because there are lots of tasks to do in kernel, modularization, cleanups, etc.) > > in general, for pharo there is a vision document that shows the long (really long) term goals. Now I do not remember where is it, but should be somewhere in the pharo site (probably not visible enough). > The problem is that I think we already did a lot of that vision. We need a new one.

Oct. 15, 2013

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

by Esteban Lorenzano

On Oct 15, 2013, at 9:43 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. the problem with this is that we do not have a clear roadmap for Pharo4 (yet). How it works now is: at the beginning of a year iteration we make a list of what we want, taking into account what emerged latest year (both new possibilities opened and new/old problems that emerged). That gives us what we can more or less call a "next release road map". And is "more or less" because situation can change. For example we wanted a complete revamp of Pharo3 L&F, and we wanted also a complete migration of Morph to be rendered with Athens, and reality showed that is not achievable this year... so it will wait until next one (and that does not means at all that we stopped work on that area, just that the completion of the task will take more time than expected). So... what's the roadmap for Pharo4? No Idea :) What we already know is that we made a huge move forward in infrastructure for Pharo3 (starting by Opal, but not restrained to that), and now we want to focus in the tools (but without doing *just* that, because there are lots of tasks to do in kernel, modularization, cleanups, etc.) in general, for pharo there is a vision document that shows the long (really long) term goals. Now I do not remember where is it, but should be somewhere in the pharo site (probably not visible enough). > > 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 ? yep, that's a good point :) > > > > -- > View this message in context: http://forum.world.st/Is-there-a-Roadmap-for-Pharo-3-0-and-Pharo-4-0-tp4714… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Oct. 15, 2013

[pharo-project/pharo-core]

by GitHub

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

Oct. 15, 2013

[pharo-project/pharo-core] 824bfe: 20624

by GitHub

Branch: refs/heads/2.0 Home: https://github.com/pharo-project/pharo-core Commit: 824bfeb8614fea972c345306599b6e8822528d43 https://github.com/pharo-project/pharo-core/commit/824bfeb8614fea972c345306… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-10-15 (Tue, 15 Oct 2013) Changed paths: M FileSystem-Core.package/UnixResolver.class/instance/preferences.st M FileSystem-Core.package/UnixResolver.class/methodProperties.json M NautilusRefactoring.package/NautilusRefactoring.class/instance/privatePullUpInstVarFrom..st M NautilusRefactoring.package/NautilusRefactoring.class/methodProperties.json A Polymorph-Widgets.package/EntryCompletion.class/instance/closeIfNotNeeded..st R Polymorph-Widgets.package/EntryCompletion.class/instance/closeIfNotOver..st M Polymorph-Widgets.package/EntryCompletion.class/methodProperties.json M Polymorph-Widgets.package/IdentifierChooserMorph.class/instance/selectFirstItem.st M Polymorph-Widgets.package/IdentifierChooserMorph.class/methodProperties.json M Polymorph-Widgets.package/PluggableTextFieldMorph.class/instance/chooserHasFocus.st M Polymorph-Widgets.package/PluggableTextFieldMorph.class/instance/drawOn..st M Polymorph-Widgets.package/PluggableTextFieldMorph.class/methodProperties.json M ScriptLoader20.package/ScriptLoader.class/instance/commentForCurrentUpdate.st A ScriptLoader20.package/ScriptLoader.class/instance/script597.st A ScriptLoader20.package/ScriptLoader.class/instance/update20624.st M ScriptLoader20.package/ScriptLoader.class/methodProperties.json Log Message: ----------- 20624 11872 PreferenceStartup raises an exception on StackVM 2.0 Version On Raspberry https://pharo.fogbugz.com/f/cases/11872 11853 Inst Var Pull Up does not work https://pharo.fogbugz.com/f/cases/11853 11859 Backport 2.0: Issue 11549 PluggableTextMorph closes completion menu on keydown https://pharo.fogbugz.com/f/cases/11859

Oct. 15, 2013

[update 2.0] #20624

by Marcus Denker

20624 ----- 11872 PreferenceStartup raises an exception on StackVM 2.0 Version On Raspberry https://pharo.fogbugz.com/f/cases/11872 11853 Inst Var Pull Up does not work https://pharo.fogbugz.com/f/cases/11853 11859 Backport 2.0: Issue 11549 PluggableTextMorph closes completion menu on keydown https://pharo.fogbugz.com/f/cases/11859 Diff information: http://ss3.gemstone.com/ss/Pharo20/Polymorph-Widgets-MarcusDenker.780.diff http://ss3.gemstone.com/ss/Pharo20/NautilusRefactoring-MarcusDenker.80.diff http://ss3.gemstone.com/ss/Pharo20/FileSystem-Core-MarcusDenker.71.diff

Oct. 15, 2013

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