April 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Logging API discussion

by Denis Kudriashov

2016-04-27 20:50 GMT+02:00 stepharo <stepharo(a)free.fr>: > > And you say let's replace this "log object context" information with first > class entities "typed signals". It means that for any possible case when I > want to put something in log I should create class for new signal. It's > just not practical. > > why? > MySpecialLog > ... > emit > What I am talking about is that I don't want create MySpecialLog for any MySpecialDomainObject which I want to log.

April 28, 2016

Change Playground title based on the name of the first pane

by Peter UhnÃ¡k

Hi, would it be possible to change the Playground title when the first page changed? I know I can change the title through the top right corner, but just a double click might be more useful. Plus there could be some automatic naming pattern, because it would be nice to still see that it is playgroundâ¦ for example I tend to name them: "PL @ custom name". Thanks, Peter

April 28, 2016

Re: [Pharo-dev] [Pharo 5] Gettext

by Hilaire

Here are the overall process http://pharo.gemtalksystems.com/book/LanguageAndLibraries/Localisation For Dr. Geo I have bit more to decide which font to load at start up depending on the locale (This is where Pharo5's locale refactoring break it) but you should not need it for European languages. Hilaire -- Dr. Geo http://drgeo.eu

April 28, 2016

[pharo-project/pharo-core]

by GitHub

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

April 28, 2016

[pharo-project/pharo-core] 691635: 50726

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 6916359c22b2bb246ac14e94ca25c2275b6e027e https://github.com/pharo-project/pharo-core/commit/6916359c22b2bb246ac14e94… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-04-28 (Thu, 28 Apr 2016) Changed paths: M ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/symbolic versions/stable_.st A ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F6%5F6_.st M QualityAssistant.package/QANautilusPlugin.class/definition.st M QualityAssistant.package/QANautilusPlugin.class/instance/announcement handling/updateMorph.st R QualityAssistant.package/QANautilusPlugin.class/instance/initialization/initialize.st R QualityAssistant.package/QANautilusPluginMorph.class/class/private/startPrivacyPromptTaskIfNecessary.st M QualityAssistant.package/QANautilusPluginMorph.class/definition.st M QualityAssistant.package/QANautilusPluginMorph.class/instance/actions/updateList.st M QualityAssistant.package/QANautilusPluginMorph.class/instance/initialization/initialize.st M QualityAssistant.package/QANautilusPluginMorph.class/instance/initialization/privacyMorph.st M QualityAssistant.package/QANautilusPluginMorph.class/instance/task handling/excecuteTask.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50725.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50726.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50725.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50726.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50726 18115 QA v2.6.6 https://pharo.fogbugz.com/f/cases/18115 http://files.pharo.org/image/50/50726.zip

April 28, 2016

[pharo-project/pharo-core]

by GitHub

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

April 28, 2016

[pharo-project/pharo-core] ac14c7: 50725

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: ac14c752c7e6bc68792f0363fce68a423682bb8d https://github.com/pharo-project/pharo-core/commit/ac14c752c7e6bc68792f0363… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-04-28 (Thu, 28 Apr 2016) Changed paths: M ConfigurationOfGTInspectorCore.package/ConfigurationOfGTInspectorCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGTInspectorCore.package/ConfigurationOfGTInspectorCore.class/instance/versions/version312_.st M ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/symbolic versions/stable_.st A ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/versions/version210_.st M ConfigurationOfGToolkitCore.package/ConfigurationOfGToolkitCore.class/instance/symbolic versions/stable_.st M ConfigurationOfGToolkitCore.package/ConfigurationOfGToolkitCore.class/instance/versions/version321_.st M GT-Spotter.package/GTSpotterExtensionSettings.class/class/private/doesNotUnderstand_.st M GT-Spotter.package/GTSpotterExtensionSettings.class/class/settings/catalogSettingsOn_.st R GT-Tests-Inspector.package/GTInspectorDummyExamplesTest.class/README.md R GT-Tests-Inspector.package/GTInspectorDummyExamplesTest.class/definition.st R GT-Tests-Inspector.package/GTInspectorDummyExamplesTest.class/instance/accessing/allExamplesDummiesProviders.st R GT-Tests-Inspector.package/GTInspectorDummyExamplesTest.class/instance/accessing/invalidExamplesDummiesProviders.st R GT-Tests-Inspector.package/GTInspectorDummyExamplesTest.class/instance/accessing/recursiveExamplesDummiesProviders.st R GT-Tests-Inspector.package/GTInspectorDummyExamplesTest.class/instance/tests/testExists.st R GT-Tests-Inspector.package/GTInspectorDummyExamplesTest.class/instance/tests/testInvalidDefinitions.st R GT-Tests-Inspector.package/GTInspectorDummyExamplesTest.class/instance/tests/testIsEquals.st R GT-Tests-Inspector.package/GTInspectorDummyExamplesTest.class/instance/tests/testIsGTExample.st R GT-Tests-Inspector.package/GTInspectorDummyExamplesTest.class/instance/tests/testMatchesMethod.st R GT-Tests-Inspector.package/GTInspectorDummyExamplesTest.class/instance/tests/testRecursiveDefinitions.st R GT-Tests-Inspector.package/GTInspectorDummyExamplesTest.class/instance/tests/testResult.st R GT-Tests-Inspector.package/GTInspectorDummyExamplesTest.class/instance/tests/testRun.st R GT-Tests-Inspector.package/GTInspectorDummyExamplesTest.class/instance/utils/examplesInClasses_do_.st M GT-Tests-Inspector.package/GTInspectorExamplesManualTest.class/README.md R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50724.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50725.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50724.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50725.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50725 Moose http://files.pharo.org/image/50/50725.zip

April 28, 2016

STON - a little suggestion

by Carlos Lombardi

Hi, I want to use STON to enable the backup a graph of objects pertaining to an application. Some of the objects in this graph include, in their state, a Map that is not supported by STON. To write these objects, I would like to write via the standard procedure all the instance variables unless that pointing to such a map, and then add a modified version of that map by hand. To exclude the conflicting variable is easy, I just redefine #stonAllInstVarNames at the class side as follows: ^self instVarNames reject: [ :theName | (theName = #references) ] in this way, I do not need to modify the method if the state of these objects changes. On the other hand, I found not easy to use the standard mechanism for the included instance variables. This mechanism is embedded in STONWriter>>writeObject: . I found no option but repeat the logic codified there, in the method #stonOn: of my class. The easiest way to let STON integrate the standard mechanism to store the state of an object, with by-hand additions, is to slightly modify STONWriter>>writeObject:, adding just one line. Objects including instance variables would be written as follows: self writeObject: anObject streamMap: [ :dictionary | instanceVariableNames do: [ :each | (anObject instVarNamed: each) ifNotNil: [ :value | dictionary at: each asSymbol put: value ] ifNil: [ anObject stonShouldWriteNilInstVars ifTrue: [ dictionary at: each asSymbol put: nil ] ] ] . anObject stonAdditionalInfoOn: dictionary . ] the added line is the last one, the invocation to #stonAdditionalInfoOn:. Of course, the method #stonAdditionalInfoOn: should be added to the Object class. By redefining this method in my class, I was able to easily add the modified, STON-compatlble value, to the values handled by the STON code. I did not need to modify the STON code to read the STON String to generate a new object. Do you think that doing this modification to STON could be a good idea? Cordially - Carlos PS: I envisaged as an alternative, to allow the following method in my class stonOn:stonWriter stonWriter writeObjectAsMap: self do: [:mapWriter | // added code goes here stonWriter writeInstVarsOf: self on: mapWriter // added code goes here ] To this end, the methods #writeObjectAsMap:do: and #writeInstVarsOf:on should be added to STONWriter. The method writeInstVar: aSymbol of: anObject on: mapWriter could be offered as well, to allow more fine-grained redefinitions of stonOn: , while keeping the ability to use the standard mechanism to store an instance variable. I think that the option I described earlier is simpler, I include this one because maybe other people would prefere it.

April 28, 2016

Re: [Pharo-dev] Command Line Arguments

by Cyril Ferlicot D.

Le 27/04/2016 22:51, blake watson a Ã©crit : > Phil, Estevan-- > > I think part of what confused me is that there's no printout at all > under Windows, so Pharo opens and says "Yep, that worked." But there's > no actual output anywhere. Hi, This is because stdin/stdout/stderr stream does not work on windows :( There might be a "stderr" file close to your image with the output. > >>>ps: this questions are more for the pharo-users list than pharo-dev :) > > Duly noted. For some reason, I thought that was defunct. (But I had just > unsubscribed somehow.) > > -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

April 27, 2016

Re: [Pharo-dev] Mocketry names again

by Carlos Lombardi

Hi again, ok, just to have coherence between the names for the two possible outcomes of a method, you could use #beReturnedBy instead of #beReturnedFrom: . You would have #beReturnedBy: and #beRaisedBy: On Wed, Apr 27, 2016 at 10:00 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > 2016-04-27 0:33 GMT+02:00 Carlos Lombardi <carlombardi(a)gmail.com>: > >> ... maybe >> >> #result should beTheResultOf: [mock someMessage]. >> #result should not beTheResultOf: [mock anotherMessage]. >> > > It's nice.I think "The" can be omitted: > > #result should beResultOf: [mock someMessage]. > > > But anyway I use word #return because there are different types of result: > value return and error signal. There is no expression for last case but it > would be like: > > anError should beRaisedBy: [mock someMessage] > >

April 27, 2016