June 2014 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] c73c30: 40048
by GitHub June 27, 2014

June 27, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: c73c301cc203f275017ce069c367c775886541b5 https://github.com/pharo-project/pharo-core/commit/c73c301cc203f275017ce069… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-06-27 (Fri, 27 Jun 2014) Changed paths: R AST-Interpreter-Core.package/extension/OCInstanceVariable/instance/accept_assign_inNode_.st R AST-Interpreter-Core.package/extension/OCInstanceVariable/instance/readWith_inNode_.st A FileSystem-Core.package/FileReference.class/class/instance creation/newTempFilePrefix_suffix_.st A FileSystem-Tests-Core.package/FileReferenceTest.class/instance/tests/testTempFilePrefixSuffix.st R OpalCompiler-Core.package/OCInstanceVariable.class/README.md R OpalCompiler-Core.package/OCInstanceVariable.class/definition.st R OpalCompiler-Core.package/OCInstanceVariable.class/instance/accessing/index.st R OpalCompiler-Core.package/OCInstanceVariable.class/instance/accessing/index_.st R OpalCompiler-Core.package/OCInstanceVariable.class/instance/accessing/name.st R OpalCompiler-Core.package/OCInstanceVariable.class/instance/accessing/name_.st R OpalCompiler-Core.package/OCInstanceVariable.class/instance/emitting/emitStore_.st R OpalCompiler-Core.package/OCInstanceVariable.class/instance/emitting/emitValue_.st R OpalCompiler-Core.package/OCInstanceVariable.class/instance/testing/isInstance.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script48.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40048.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Slot.package/Slot.class/instance/emitting/emitStore_.st A Slot.package/Slot.class/instance/emitting/emitValue_.st A Slot.package/TestSlot.class/README.md A Slot.package/TestSlot.class/definition.st A Slot.package/TestSlot.class/instance/meta-object-protocol/read_.st A Slot.package/TestSlot.class/instance/meta-object-protocol/write_to_.st R SmartSuggestions.package/extension/OCInstanceVariable/instance/specialCommands.st Log Message: ----------- 40048 13420 Abstract slot class should emit code to reflectively read the slot https://pharo.fogbugz.com/f/cases/13420 13419 remove OCInstanceVariable https://pharo.fogbugz.com/f/cases/13419 13405 Get support for temporary files https://pharo.fogbugz.com/f/cases/13405 http://files.pharo.org/image/40/40048.zip

1 0

Spec, groups and version-specific packages
by Roberto Minelli June 27, 2014

June 27, 2014

Hi, I have my project with my Configuration and I am using spec groups to load different sets of packages (e.g., development and user groups). With the porting to Pharo 4.0 I discovered that there are some functionalities specific to Pharo 3.0 and others to Pharo 4.0, for example the fact that MethodContext is no longer part of Pharo 4.0. but it has been replaced by Context. I moved such functionalities in a package, say 'MyProject-Extension30â and Pharo 4.0 specific functionalities in 'MyProject-Extension40â. Now the question is, suppose that I have a group like spec group: âUser' with: #(âAâ âBâ âCâ). and another one: spec group: âDev' with: #(âAâ âBâ âCâ âDâ âEâ). Until now, the developer (i.e., me) would do something like (self project version: #bleedingEdge) load: #('Devâ) and a used of my project would do (self project version: #bleedingEdge) load: #(âUserâ) How can I factor inside the dynamic load of the two Pharo-version specific packages? i.e., no matter if âUserâ or âDevâ group is loaded I need to load 'MyProject-Extension40â if I am on Pharo 4.0 and 'MyProject-Extension30â if on Pharo 3.0. Thanks for your help, Roberto

2 3

Centring label
by Yuriy Tymchuk June 27, 2014

June 27, 2014

Hi, is there a way to align text of Specâs LabelModel, so it will appear in the middle? Uko

1 0

super initialize
by Torsten Bergmann June 27, 2014

June 27, 2014

When you create a new instance with #new automatically #initialize is sent. The default #initialize is provided in ProtoObject at the highest level of the class hierarchy (doing nothing). If you look deeper in the hierarchy you will notice that - some subclasses of Object override the #initialize method and call "super initialize" - some subclasses of Object override the #initialize method without calling "super initialize" No problem at the moment as there is no initialization done in Object or ProtoObject at the current point in time. But the question is should we care if there may be in the future? Thx T.

6 5

spec question
by Pablo R. Digonzelli June 26, 2014

June 26, 2014

Hi all, two questions about Spec. 1) How can i change the font for a ListModel or TextModel? 2) I try , but nothing happend . I does not work but there is no error also l := ListModel new. l backgroundColorBlock: [ Color red ]. l openWithSpec . Can I change de backcolor of ListModel ? Sorry for my english. TIA Ing. Pablo Digonzelli Software Solutions IP-Solutiones SRL Metrotec SRL 25 de Mayo 521 Email: pdigonzelli(a)softsargentina.com pdigonzelli(a)gmail.com Cel: 5493815982714

2 4

Configuration critical warnings and errors in 40047
by Stephan Eggermont June 26, 2014

June 26, 2014

|errors| errors := OrderedCollection new. SystemNavigation default allClassesDo: [ :each | (each name beginsWith: 'ConfigurationOf' ) ifTrue: [ |list| list := MetacelloToolBox validateConfiguration: each. list do: [ :warning | warning isCritical ifTrue:[errors add: each -> warning ]] ]]. errors an OrderedCollection(ConfigurationOf->Error: No usable baseline or versions defined. { noVersionsDefined } [ #validatePragmas ] ConfigurationOfVersionnerTestBitmapCharacterSet->Critical Warning: The name of package 'Collections-BitmapCharacterSet' does not match the file name ' Collections-BitmapCharacterSet-JAA.5' in version '1.0' { packageNameMismatch } [ #validateVersionSpec: ] ConfigurationOfVersionnerTestXMLParserTemplate->Critical Warning: The name of package 'VersionnerTestXML-Parser' does not match the file name 'XML-Parser-NorbertHartl.141' in version '1.0' { packageNameMismatch } [ #validateVersionSpec: ] ConfigurationOfVersionnerTestXMLParserTemplate->Critical Warning: The name of package 'VersionnerTestXML-Tests-Parser' does not match the file name 'XML-Tests-Parser-JAA.14' in version '1.0' { packageNameMismatch } [ #validateVersionSpec: ] ConfigurationOfVersionnerTestXMLWriter->Critical Warning: No version specified for the package 'Collections-Support' in version '2.0.0' { noVersionSpecified } [ #validateVersionSpec: ] ConfigurationOfVersionnerTestXMLWriter->Critical Warning: No version specified for the package 'Collections-Support' in version '2.1.0' { noVersionSpecified } [ #validateVersionSpec: ])

2 1

evicted zombie process from run queue
by HernÃ¡n Morales Durand June 26, 2014

June 26, 2014

Can someone explain what does it mean or why it happens? Is that a common scenario for you? I am measuring execution time for big matrices in CogVM 4.0.0. Image is unresponsive. Cheers, HernÃ¡n

4 10

Re: [Pharo-dev] evicted zombie process from run queue
by Stephan Eggermont June 26, 2014

June 26, 2014

Esteban wrote: >Other frameworks use a datasource design (like cocoa, swtâ¦ and basically all the serious frameworks I know about). >and no, we do not have a default design for this kind of big components (a serious absence, IMO). Serious absence indeed. Stephan

3 3

[Pharo4] Slots: API for Classes
by Marcus Denker June 26, 2014

June 26, 2014

Hi, Already in Pharo3 all instance variables are described using meta-objects (so called slots). To make it easier to access the slots, I added some simple methods to ClassDescription on 4.0 043, Now we can do e.g.: Context slots Context allSlots Point hasSlotNamed: #x Point slotNamed: #x e.g. the slot âxâ of Point knows how to reflectively read itself from a point: (Point slotNamed: #x) read: 5@3 ==> 5 Marcus

10 23

[pharo-project/pharo-core]
by GitHub June 26, 2014

June 26, 2014

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

1 0