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

[Pharo 5] Some feedbacks
by Hilaire May 2, 2016

May 2, 2016

Hi, While giving a try to Pharo5, I wrote some notes about how it fells. It may be useful to share it. Of course it is also very opinionated and may be rude. But no offense to consider, really. More time is need for a real developer experience, may be later. Hilaire -- Dr. Geo http://drgeo.eu

6 12

STON - a little suggestion
by Carlos Lombardi May 2, 2016

May 2, 2016

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.

2 1

[pharo-project/pharo-core] a0845b: 50741
by GitHub May 2, 2016

May 2, 2016

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: a0845baf8b1f465380959b56d1898655e8a68687 https://github.com/pharo-project/pharo-core/commit/a0845baf8b1f465380959b56… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-02 (Mon, 02 May 2016) Changed paths: A FreeType.package/FT2Handle.class/class/private/destroyMutex.st M FreeType.package/FT2Handle.class/definition.st M FreeType.package/FT2Handle.class/instance/private/pvtDestroyHandle.st A Kernel.package/CompiledMethod.class/instance/converting/asOrderedCollection.st A Kernel.package/CompiledMethod.class/instance/testing/isCollection.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50740.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50741.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50740.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50741.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50741 18133 GTInspector subscript out of bounds in raw tab https://pharo.fogbugz.com/f/cases/18133 18147 pvtDestroyHandle still presenting problems https://pharo.fogbugz.com/f/cases/18147 http://files.pharo.org/image/50/50741.zip

1 0

[pharo-project/pharo-core]
by GitHub May 2, 2016

May 2, 2016

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

1 0

Logging API discussion
by Denis Kudriashov May 2, 2016

May 2, 2016

Hello. I resumed discussion about SystemLogger and Beacon here http://forum.world.st/What-the-state-of-unifying-Beacon-with-SystemLogger-t… . I plan to unify both approaches by saving traditional terminology from SystemLogger and cool features from Beacon. Let's think about logging API to log any object in the system. Most natural way is just send message #log to object itself: anObject log It would be nice replacement for Object>>logCr. But when we log some information we usually want to log it with little remark, importance level and (most important) timestamp. This information is kind of standard for logging domain. But it requires much more methods for logging API. So we need extra information to put together with objects: 1. timestamp 2. user message 3. importance level (debug, info, error, etc.) 4. whatever (process hash, process name for example) 5. sometimes it can be needed to put in log something different than object itself. (for example it can be just copy of object to not change state of log entry during app lifetime) Here is possible API based on Object extensions. It has drawbacks but it is good to think about it too: "it will put anObject in logs with default #info level" anObject log "it will put anObject in logs with default #info level and given user message" anObject logWith: 'something interesting was happened with anObject' "inside block we can put any logging domain information from application and also override content by specific representation" anObject logBy: [:logEntry | logEntry message: 'something interesting to be saved with our object' logEntry content: anotherObject] "here logs with interest about anObject will receive logEntry with anotherObject instead of anObject" And similar for different kind of levels: anObject logForDebug. anObject logForDebugWith: 'some debug message' anObject logForDebugBy: [:logEntry | ] anObject logAsError. anObject logAsError: 'object computation was wrong' anObject logAsErrorBy: [:logEntry | ] And most general: anObject logAs: LogLevel warn anObject logAs: LogLevel warn with: 'something interesting' anObject logAs: LogLevel warn by: [:logEntry | ] And in case of classic logging with strings only first expressions would be used: 'some info message' log. 'some debug message' logForDebug 'some error message' logAsError 'some warn message' logAs: LogLevel warn Problem with this approach: it pollutes Object with 12 extra methods and it can be more. So maybe it is better to use current SystemLogger API based on class Log: Log info: anObject Log info: anObject as: 'computation result' "as example" Log info: anObject as: [:logEntry | logEntry message: 'something interesting to be saved with our object logEntry content: anotherObject] Log error: anObject Log error: anObject as: 'computation was wrong'' Log error: anObject as: [:logEntry | ] Comparing to original SystemLogger versions I separate user message from object content. It makes possible to log any object with extra user message. But anyway it not feels very well IMHO. And it requires three methods for each log level. Maybe we can put this methods into LogLevel itself: Log info add: anObject Log info add: anObject as: 'computation result' Log info add: anObject as: [:logEntry | logEntry message: 'something interesting to be saved with our object logEntry content: anotherObject] Log error add: anObject Log error add: anObject as: 'computation was wrong'' Log error add: anObject as: [:logEntry | ] And we can make short version for default logging level (which can be object specific): Log add: anObject Log add: anObject as: 'computation result' Log add: anObject as: [:logEntry | ] That's all. I hope we can produce best suitable API for object logging. Then we can think how to adopt SystemLogger or Beacon for it. Also think about this API in context that we can register specific loggers for specific objects and specific importance level. Best regards, Denis

7 39

looking for pictures of new contributors
by Esteban Lorenzano May 1, 2016

May 1, 2016

Hi, For the pharo.org site, I need photos of this persons (Pharo 5 new contributors): Abdelghani Alidra David Allouche Thibault Arloing Vincent Blondeau Miguel Campusano Christopher Coat Paul DeBruicker Sergio Fedi HolgerHansPeter Freyther Thomas Heniart Skip Lentz Henrik Nergaard Marion Noirbent Merwan Ouddane Alain Rastoul Stefn Reichhart Valentin Ryckewaert Boris Spasojevic Roger Stebler Pablo Tesone Franck Warlouzet Photo has to be a 70x70 PNG fileâ¦ if you do not send me a photo you will appear as a nice gray pharo, like this: http://pharo.org/files/faces/noface.png :) cheers, Esteban

3 5

Menus is spelt incorrectly in the setting browser
by kmo May 1, 2016

May 1, 2016

In Pharo 5 if you go to Settings->Appearance->Morphic, the settings header for menu settings reads "Menues". This should be "Menus". Looks bad as most new users will want to look at settings - even if only to see what's there. -- View this message in context: http://forum.world.st/Menus-is-spelt-incorrectly-in-the-setting-browser-tp4… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

2 2

[pharo-project/pharo-core]
by GitHub May 1, 2016

May 1, 2016

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

1 0

[pharo-project/pharo-core] ae89f5: 50740
by GitHub May 1, 2016

May 1, 2016

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: ae89f566230fa31d3f5743eca3471a7a617e840f https://github.com/pharo-project/pharo-core/commit/ae89f566230fa31d3f5743ec… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-01 (Sun, 01 May 2016) Changed paths: R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50739.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50740.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50739.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50740.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M StartupPreferences.package/StartupPreferencesLoader.class/class/private/preferencesGeneralFolder.st M StartupPreferences.package/StartupPreferencesLoader.class/instance/startup loading/loadFromDefaultLocations.st A StartupPreferences.package/StartupPreferencesLoadingError.class/README.md A StartupPreferences.package/StartupPreferencesLoadingError.class/definition.st Log Message: ----------- 50740 18140 StartupPreferencesLoader does not guard enough against errors https://pharo.fogbugz.com/f/cases/18140 http://files.pharo.org/image/50/50740.zip

1 0

[pharo-project/pharo-core]
by GitHub May 1, 2016

May 1, 2016

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

1 0