January 2015 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

Jan. 22, 2015

[pharo-project/pharo-core] 5af3c5: 40454

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 5af3c5060fca692bcc86cdf90c43eae7d1389a44 https://github.com/pharo-project/pharo-core/commit/5af3c5060fca692bcc86cdf9… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-01-22 (Thu, 22 Jan 2015) Changed paths: R Graphics-Display Objects.package/DisplayScreen.class/instance/initialization/release.st M Nautilus.package/AbstractNautilusUI.class/instance/icons behavior/runScriptMethod_.st M Nautilus.package/MethodIsScriptAction.class/README.md M Nautilus.package/MethodIsScriptAction.class/instance/order/isActionHandled.st M Nautilus.package/MethodIsScriptAction.class/instance/order/privateActionIcon.st M NautilusCommon.package/extension/CompiledMethod/instance/isScriptMethod.st A NautilusCommon.package/extension/CompiledMethod/instance/isScriptMethodWithScript.st M Refactoring-Changes.package/RBRefactoryChangeManager.class/instance/initialize-release/release.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script454.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40454.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M StartupPreferences.package/StartupPreferencesLoader.class/README.md Log Message: ----------- 40454 14764 Review DisplayScreen>>release https://pharo.fogbugz.com/f/cases/14764 14763 RBRefactoryChangeManager>>#release method call order https://pharo.fogbugz.com/f/cases/14763 14714 StartupPreferencesLoader class comment references class StartupLoader https://pharo.fogbugz.com/f/cases/14714 14747 Beside <script> pragma also allow <script: someActionCode> pragma in a method https://pharo.fogbugz.com/f/cases/14747 http://files.pharo.org/image/40/40454.zip

Jan. 22, 2015

[pharo-project/pharo-core]

by GitHub

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

Jan. 22, 2015

[pharo-project/pharo-core] e94dce: 40453

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: e94dcee0885d0e6ae3ef6958db8439ca3e655eb0 https://github.com/pharo-project/pharo-core/commit/e94dcee0885d0e6ae3ef6958… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-01-22 (Thu, 22 Jan 2015) Changed paths: R Collections-Strings.package/String.class/instance/accessing/do_toFieldNumber_.st R Collections-Strings.package/String.class/instance/accessing/tabDelimitedFieldsDo_.st R Collections-Strings.package/String.class/instance/converting/splitInteger.st A Deprecated40.package/extension/Stream/instance/isMessageStream.st A Deprecated40.package/extension/String/instance/do_toFieldNumber_.st A Deprecated40.package/extension/String/instance/splitInteger.st A Deprecated40.package/extension/String/instance/tabDelimitedFieldsDo_.st M Monticello.package/MCClassDefinition.class/instance/installing/createClass.st R Monticello.package/extension/Stream/instance/isMessageStream.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script453.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40453.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40453 14762 Deprecate Stream>>isMessageStream https://pharo.fogbugz.com/f/cases/14762 14761 Move Collections-Strings deprecated methods to Deprecated40 package https://pharo.fogbugz.com/f/cases/14761 14758 Simplify MCClassDefinition>>#createClass https://pharo.fogbugz.com/f/cases/14758 http://files.pharo.org/image/40/40453.zip

Jan. 22, 2015

Re: [Pharo-dev] WhatsUp from: 2015-01-19 until: 2015-01-31

by phil＠highoctane.be

On Mon, Jan 19, 2015 at 7:00 AM, <seaside(a)rmod.lille.inria.fr> wrote: > Hi! We're sending this automatic email twice a month, to give the > community an opportunity to easily know what's happening and to coordinate > efforts. Just answer informally, and feel free to spawn discussions > thereafter! > > ### Here's what I've been up to since the last WhatsUp: > > Solution successfully deployed in production. Documentation for operators produced using Pillar. > > ### What's next, until 2015-01-31 (*): > > Preparing Amber presentation for FOSDEM. Attending Pharo Days and FOSDEM. Closing new funding for project follow up (done !) (*) we'll be expecting results by then ;) Phil

Jan. 22, 2015

Re: [Pharo-dev] [ANN] Pharo Consortium New Academic Partner: DCyT - Universdad Nacional de Quilmes

by phil＠highoctane.be

I love that chart. Making business with Pharo is becoming very real for me. I made most of my money out of Pharo last year. And there will be some more in 2015. At least one development to be done in Q1. The more we can use it in production, the better we can contribute back, and learn/document how things are going. I am very happy to see that Glorp is having renewed activity. We must be supporting RDBMs in the enterprise space, there is no way out. Postgres should be our main target. Tons of clients are using it and it can scale like mad. Hopefully more Pharo business coming. I'd love to be able to pay all of my mortage and more with Pharo related business :-) Phil On Thu, Jan 22, 2015 at 10:33 AM, Ben Coman <btc(a)openinworld.com> wrote: > Based on the info from the web site, looks like good steady progress > building the consortium for a sustainable future for Pharo. > Great work! > cheers -ben > > On Thu, Jan 22, 2015 at 1:52 AM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > >> The Pharo Consortium is very happy to announce that the DCyT - Universdad >> Nacional de Quilmes has joined the Consortium as an Academic Partner. >> >> About >> >> - DCyT - Universdad Nacional de Quilmes: http://www.unq.edu.ar >> - Pharo Consortium: http://consortium.pharo.org >> >> The goal of the Pharo Consortium is to allow companies and institutions >> to support the ongoing development and future of Pharo. >> Individuals can support Pharo via the Pharo Association: >> http://association.pharo.org >> > >

Jan. 22, 2015

Re: [Pharo-dev] [Pharo-users] CommandLine handler and UTF8 path

by phil＠highoctane.be

Unix environAt: index | address | address := NBExternalAddress value: (self environ nbUInt32AtOffset: index-1 * 4). address isNull ifTrue: [ ^ nil ]. ^ address readString Windows getEnv: aVariableName | valueSize buffer | valueSize := self getEnvSize: aVariableName. valueSize = 0 ifTrue: [ ^ nil ]. buffer := String new: valueSize. (self getEnv: aVariableName buffer: buffer size: valueSize) = (valueSize - 1) ifFalse: [ ^ nil ]. ^ buffer allButLast getEnvSize: nameString <primitive: #primitiveNativeCall module: #NativeBoostPlugin error: errorCode > ^ self nbCall: #( int GetEnvironmentVariableA ( String nameString, nil, 0 ) ) module: #Kernel32 In Windows: OSPlatform current environment at: #PATH works. So, they both depend on NB indeed. Phil On Wed, Jan 21, 2015 at 11:50 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 21 Jan 2015, at 23:25, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > > > > > On Tue, Jan 20, 2015 at 12:35 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > > Hi Eliot, > > > > > On 20 Jan 2015, at 20:38, Eliot Miranda <eliot.miranda(a)gmail.com> > wrote: > > > > > > > > > > > > On Tue, Jan 20, 2015 at 8:00 AM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > > > Command line arguments enter the image level via > VirtualMachine>>#getSystemAttribute: > > > > > > At that point they are already Strings. > > > > > > ByteString, according to the primitive. So if the shell supplies e.g. > UTF-8 strings for command-line parameters, which the VM sees as bytes, then > the ByteString instances answered by getSystemAttribute: would need > decoding, right? > > > > > > In your case, they must already be wrong at that point. > > > > > > Not necessarily. The getSystemAttribute: primitive doesn't do > decoding. Perhaps it should. > > > > Yes, probably. I just tried on Mac OS X, Pharo 4: > > > > $ export FOO=Ã©lÃ¨ve-FranÃ§ais > > > > $ echo $FOO > > Ã©lÃ¨ve-FranÃ§ais > > > > $ ./pharo Pharo.image eval 'OSPlatform current environment at: #FOO' > > 'ÃÂ©lÃÂ¨ve-FranÃÂ§ais' > > > > $ ./pharo Pharo.image eval '(OSPlatform current environment at: #FOO) > asByteArray utf8Decoded' > > 'Ã©lÃ¨ve-FranÃ§ais' > > > > The question is, is this true for all platforms ? Windows ? > > > > I'm trying to test this in Pharo 3. I get > > > > KeyNotFound: key #FOO not found in PlatformIndependentEnvironment > > PlatformIndependentEnvironment(OSEnvironment)>>at: in Block: [ > KeyNotFound signalFor: aKey ] > > UndefinedObject>>ifNil: > > PlatformIndependentEnvironment(OSEnvironment)>>at:ifAbsent: > > PlatformIndependentEnvironment(OSEnvironment)>>at: > > UndefinedObject>>DoIt > > OpalCompiler>>evaluate > > OpalCompiler(AbstractCompiler)>>evaluate: > > SmalltalkImage>>evaluate: > > EvaluateCommandLineHandler>>evaluate: in Block: [ ... > > BlockClosure>>on:do: > > > > > > Does the environment access depend on NativeBoost? > > Yes, I believe so. > > > > > On 20 Jan 2015, at 16:51, Hilaire <hilaire(a)drgeo.eu> wrote: > > > > > > > > Le 20/01/2015 16:34, Sven Van Caekenberghe a Ã©crit : > > > >> No they are not - Strings and Characters in Pharo are using plain > Unicode encoding internally. > > > > > > > > Thanks for the update, and the reference link. > > > > > > > > Hilaire > > > > > > > > -- > > > > Dr. Geo - http://drgeo.eu > > > > iStoa - http://istoa.drgeo.eu > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > best, > > > Eliot > > > > > > > > > > > > -- > > best, > > Eliot > > > -- --- 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

Jan. 22, 2015

Re: [Pharo-dev] More people needed to review issues

by Esteban Lorenzano

+1 > On 22 Jan 2015, at 11:02, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Yes, we do see it useful :) > > Doru > > On Thu, Jan 22, 2015 at 10:56 AM, Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>> wrote: > If other see that as useful, I'll volunteer to have a try at it. I've started poking around the CI & Fogbugz interface code. > Any further thoughts on design? > > Maybe it could run as a Pharo CI job, or alternatively, it would provide me a nice goal-directed opportunity to get it run for minutes a day on a cloud service. > > cheers -ben > > On Thu, Jan 22, 2015 at 5:33 PM, Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> wrote: > Marcus, can the issue tracker send an email to the mailing list every morning with some report? > > - # of issues opened > - # of issues in state X > - # of issues in state Y > - # of issues older than a month... > > We can try to do something like that this friday afternoon together if you want. > > Maybe if we automatize a mail like that every morning 1) you don't have to do it manually so it's less pain for you and 2) with numbers people will have another feeling. > > El Thu Jan 22 2015 at 10:25:38 AM, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> escribiÃ³: > > Hello, > > Now that so many people talk so much: > > We need more people to *regularly* look at the issue tracker: > > https://pharo.fogbugz.com/ <https://pharo.fogbugz.com/> > > -> check if reported issues are reproducable > -> check proposed solutions > -> comment on new features (âI donât like that becauseâ¦.â) > -> fix issues that are not yet fixed > -> summarise issues with long discussions and distill âThe next action that needs to be done is:â > > â¦. > > Marcus > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com/> > > "Every thing has its own flow"

Jan. 22, 2015

Re: [Pharo-dev] More people needed to review issues

by Tudor Girba

Yes, we do see it useful :) Doru On Thu, Jan 22, 2015 at 10:56 AM, Ben Coman <btc(a)openinworld.com> wrote: > If other see that as useful, I'll volunteer to have a try at it. I've > started poking around the CI & Fogbugz interface code. > Any further thoughts on design? > > Maybe it could run as a Pharo CI job, or alternatively, it would provide > me a nice goal-directed opportunity to get it run for minutes a day on a > cloud service. > > cheers -ben > > On Thu, Jan 22, 2015 at 5:33 PM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> Marcus, can the issue tracker send an email to the mailing list every >> morning with some report? >> >> - # of issues opened >> - # of issues in state X >> - # of issues in state Y >> - # of issues older than a month... >> >> We can try to do something like that this friday afternoon together if >> you want. >> >> Maybe if we automatize a mail like that every morning 1) you don't have >> to do it manually so it's less pain for you and 2) with numbers people will >> have another feeling. >> >> El Thu Jan 22 2015 at 10:25:38 AM, Marcus Denker <marcus.denker(a)inria.fr> >> escribiÃ³: >> >> Hello, >>> >>> Now that so many people talk so much: >>> >>> We need more people to *regularly* look at the issue tracker: >>> >>> https://pharo.fogbugz.com/ >>> >>> -> check if reported issues are reproducable >>> -> check proposed solutions >>> -> comment on new features (âI donât like that becauseâ¦.â) >>> -> fix issues that are not yet fixed >>> -> summarise issues with long discussions and distill âThe next action >>> that needs to be done is:â >>> >>> â¦. >>> >>> Marcus >>> >> > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 22, 2015

Re: [Pharo-dev] More people needed to review issues

by Ben Coman

If other see that as useful, I'll volunteer to have a try at it. I've started poking around the CI & Fogbugz interface code. Any further thoughts on design? Maybe it could run as a Pharo CI job, or alternatively, it would provide me a nice goal-directed opportunity to get it run for minutes a day on a cloud service. cheers -ben On Thu, Jan 22, 2015 at 5:33 PM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > Marcus, can the issue tracker send an email to the mailing list every > morning with some report? > > - # of issues opened > - # of issues in state X > - # of issues in state Y > - # of issues older than a month... > > We can try to do something like that this friday afternoon together if you > want. > > Maybe if we automatize a mail like that every morning 1) you don't have to > do it manually so it's less pain for you and 2) with numbers people will > have another feeling. > > El Thu Jan 22 2015 at 10:25:38 AM, Marcus Denker <marcus.denker(a)inria.fr> > escribiÃ³: > > Hello, >> >> Now that so many people talk so much: >> >> We need more people to *regularly* look at the issue tracker: >> >> https://pharo.fogbugz.com/ >> >> -> check if reported issues are reproducable >> -> check proposed solutions >> -> comment on new features (âI donât like that becauseâ¦.â) >> -> fix issues that are not yet fixed >> -> summarise issues with long discussions and distill âThe next action >> that needs to be done is:â >> >> â¦. >> >> Marcus >> >

Jan. 22, 2015