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

[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.testHeaderLineTooLong

Oct. 15, 2013

Is there a Roadmap for Pharo 3.0 and Pharo 4.0

by kilon

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 ? -- 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

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

by StÃ©phane Ducasse

+1 On Oct 15, 2013, at 8:29 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] serializing and materializing MSE files with the Fame meta-engine

by StÃ©phane Ducasse

doru may be we should clean the code of metabrowser because I thought (during a lecture that it contains dead code). On Oct 13, 2013, at 11:40 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I put together a short description/tutorial on using Fame for serialization and materialization of models and meta-models. Perhaps it can be useful for others, too: > http://www.humane-assessment.com/blog/serializing-and-materializing-mse-fil… > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Oct. 15, 2013

Re: [Pharo-dev] default monospaced code font

by Marcus Denker

On Oct 15, 2013, at 8:31 AM, 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. > 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

Oct. 15, 2013

default monospaced code font

by Pavel Krivanek

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

Oct. 15, 2013

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

by Marcus Denker

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

[pharo-project/pharo-core]

by GitHub

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

Oct. 15, 2013

[pharo-project/pharo-core] 040518: 30483

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 040518aeb4ae0e8bf80891d7e18fe4253112c530 https://github.com/pharo-project/pharo-core/commit/040518aeb4ae0e8bf80891d7… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-10-14 (Mon, 14 Oct 2013) Changed paths: M ConfigurationCommandLineHandler-Tests.package/ConfigurationCommandLineHandlerTest.class/instance/tests/testGroups.st A Deprecated30.package/extension/KMBuilder/instance/attachShortcutCategory_to_.st M KernelTests-Classes.package/ClassDescriptionTest.class/instance/tests/testClassDescriptionRespectsPolymorphismWithTraitDescription.st M KernelTests-Classes.package/ClassTest.class/instance/testing/testClassRespectsPolymorphismWithTrait.st M KernelTests-Methods.package/CompiledMethodTest.class/instance/tests - accessing/testBytecode.st R Keymapping-Pragmas.package/KMBuilder.class/instance/keymap-building/attachShortcutCategory_to_.st A SUnit-Core-Kernel.package/TAssertable.class/instance/asserting/assertCollection_equals_.st A SUnit-Core-Kernel.package/TAssertable.class/instance/private/comparingCollectionBetween_and_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script138.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30483.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R System-CommandLine.package/ShrinkingCommandLineHandler.class/README.md R System-CommandLine.package/ShrinkingCommandLineHandler.class/class/accessing/commandName.st R System-CommandLine.package/ShrinkingCommandLineHandler.class/class/accessing/description.st R System-CommandLine.package/ShrinkingCommandLineHandler.class/definition.st R System-CommandLine.package/ShrinkingCommandLineHandler.class/instance/activation/activate.st R System-Support.package/SmalltalkImage.class/instance/PharoKernel-private/privCleanChangeSets.st R System-Support.package/SmalltalkImage.class/instance/PharoKernel-private/privCleanGlobals.st R System-Support.package/SmalltalkImage.class/instance/PharoKernel-private/privCleanMonticello.st R System-Support.package/SmalltalkImage.class/instance/PharoKernel-private/privCleanProcesses.st R System-Support.package/SmalltalkImage.class/instance/PharoKernel-private/privCleanShutDownList.st R System-Support.package/SmalltalkImage.class/instance/PharoKernel-private/privCleanStartUpList.st R System-Support.package/SmalltalkImage.class/instance/PharoKernel-private/privCleanTextConstants.st R System-Support.package/SmalltalkImage.class/instance/PharoKernel-private/privCleanUnloadMethods.st R System-Support.package/SmalltalkImage.class/instance/PharoKernel-private/privRecompileAll.st R System-Support.package/SmalltalkImage.class/instance/PharoKernel-private/privShrinkUnicodeTables.st R System-Support.package/SmalltalkImage.class/instance/PharoKernel-private/privShrinkingProcess.st R System-Support.package/SmalltalkImage.class/instance/PharoKernel-private/privShrinkingProcessWith_.st R System-Support.package/SmalltalkImage.class/instance/PharoKernel/kernelPackageNames.st R System-Support.package/SmalltalkImage.class/instance/PharoKernel/shrinkToKernel.st R System-Support.package/SmalltalkImage.class/instance/PharoKernel/shrinkToKernelWith_.st M Tests-CodeImport.package/ChunkImportTestCase.class/instance/importing-code/testImportAClassCategory.st M Tests-System-CommandLine.package/CommandLineArgumentsTest.class/instance/tests/testAllParameters.st Log Message: ----------- 30483 11877 Improve testClassRespectsPolymorphismWithTrait error message https://pharo.fogbugz.com/f/cases/11877 11870 move shrinking methods to own class https://pharo.fogbugz.com/f/cases/11870 11878 Move KMBuilder deprecated methods to Deprecated30 package https://pharo.fogbugz.com/f/cases/11878 http://files.pharo.org/image/30/30483.zip

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=ma… 1 regressions found. Tests.Release.ReleaseTest.testKernelExtensions

Oct. 15, 2013