- Pharo-dev - lists.pharo.org

[update 3.0] #30429
by Marcus Denker Sept. 29, 2013

Sept. 29, 2013

30429 ----- 11701 Explore should use new inspector in Tree mode https://pharo.fogbugz.com/f/cases/11701 -> fixes "Smalltalk tools inspector" to return the class of the inspector -> call methods on "Smalltalk tools inspector", not "Smalltalk tools" -> remove concept of #basicInspector tool -> remove "Inspect Basic" from menu of new inspector -> "Explore" now opens the EyeInspector in TreeMode everywhere -> make inspect:label: work TODO: - self is not bound in the tree inspector textpane - menus are missing om tree elements (I will put an issue for those two) - tree widget seems a bit slow Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1275.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Tools-MarcusDenker.108… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Inspector-MarcusDenker.9… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-Base-MarcusDenker.123…

1 0

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Sept. 29, 2013

Sept. 29, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=wi… 1 regressions found. Zinc.Zodiac.ZnHTTPSTests.testGetPharoVersion

1 0

[update 3.0] #30428
by Marcus Denker Sept. 29, 2013

Sept. 29, 2013

1 0

Notes of our monthly iteration analysis
by StÃ©phane Ducasse Sept. 28, 2013

Sept. 28, 2013

27 September 2013 TODO ---- - New debugger glitches / enhancements => need to merge with GSOC - OPAL methods withoutsource stalled - Metacello 2 not integrated integrated as soon as a BuilderCI is working Still issues in 30. should be Integrated in this release => change required to remove dependency to OSProcess - TxModel - refactoring immutable position selection - need to discuss camille model - visual is working - scrolling should be added - page up down should be added - morph widget - finish - Rubric - CI on linux is broken - Memory consumption backport 2.0 - Spec review - VM acceptance tests - fixed version of Moose - NewList Widget little glitches - NewSpec interpreter two days of work should be integrated in this iteration - Kill Package Info - Rpackage iteration under way - SmalltalkHub (in the next version) - Diff to the mailing-list (nicolas) - Inbox for projects - ControlKey on linux - nick will discuss with guille - Monkey - NativeBoost with new ASMJit version - NativeBoost on PharoS - Web site Progress is down - New look in feel - November - SystemEvents (may be) - Display VM Guile and Esteban are killing globals DONE ---- - FileTree integrated - New Inspector Glitch - Unloading the Old compiler - Memory consumption, weak announcements - insetBy: margin Pharo Workshop -------------- observer patterns trigger and announcement supports on:send:to: vs. dependent => and announcement are costly when no state. => probably the solution would be to use trigger: remove object>>changed: and dependentFields keep announcement for larger case. literal object syntax Morph>>on:send:to: Morph>>on:do: inconsistency on:do: for announcement is not nice for announcement may be we should have onAnnoucement: do:

1 0

XML...
by phil＠highoctane.be Sept. 28, 2013

Sept. 28, 2013

After having an extra look, there is a ConfigurationOfXMLSupport in my image (coming from Seaside 3) which reads: baseline120: spec <version: '1.2.0-baseline'> spec for: #common do: [ spec blessing: #baseline; repository: 'http://www.squeaksource.com/XMLSupport'. spec project: 'XML-Writer' with: [ spec className: 'ConfigurationOfXMLWriter'; repository: 'http://www.squeaksource.com/XMLWriter' ]; package: 'Collections-OrderPreservingDictionary' with: [ spec repository: 'http://www.squeaksource.com/OrderPreservingDict' ]; package: 'Collections-BitmapCharacterSet' with: [ spec repository: 'http://www.squeaksource.com/BitmapCharacterSet' ]; package: 'XML-Parser' with: [ spec requires: #('XML-Writer' 'Collections-OrderPreservingDictionary' 'Collections-BitmapCharacterSet') ]; package: 'XML-Tests-Parser' with: [ spec requires: 'XML-Parser' ]. spec package: 'Opax' with: [ spec repository: 'http://www.squeaksource.com/OPAX'; requires: 'XML-Parser' ]. spec group: 'default' with: #('Core'); group: 'Core' with: #('XML-Parser'); group: 'Tests' with: #('XML-Tests-Parser') ]. spec for: #squeakcommon do: [ spec package: 'Pastell' with: [ spec requires: #('XML-Parser'); repository: 'http://www.squeaksource.com/Pastell' ] ]. spec for: #gemstone do: [ spec repository: 'http://seaside.gemstone.com/ss/XMLSupport'. spec project: 'Grease Core' with: [ spec className: 'ConfigurationOfGrease'; versionString: '1.0.3-baseline'; loads: #('Core'); repository: 'http://www.squeaksource.com/MetacelloRepository' ]. spec package: 'Collections-OrderPreservingDictionary' with: [ spec file: 'Collections-OrderPreservingDictionary.g'; repository: 'http://seaside.gemstone.com/ss/PharoCompat']. spec package: 'SIXX' with: [ spec requires: #('XML-Parser' 'Grease Core'); repository: 'http://seaside.gemstone.com/ss/SIXX']. spec package: 'XML-Observable'. spec package: 'XML-Parser' with: [ spec file: 'XML-Parser.g']. spec group: 'Core' with: #('XML-Observable'); group: 'default' with: #('Core') ] And obviously picks things up from squeaksource... Damnit. Phil

2 1

Pharo3Inbox contributor request
by Ben Coman Sept. 28, 2013

Sept. 28, 2013

I've recently been getting used to FogBugz and am now familiarizing myself with the Pharo 3 bug fix process. This is nicely described in a video by Camillo [1]. For practice I've logged a simple issue for a spelling correction [2]. To complete this, could SmalltalkHub user 'BenComan' be added to Pharo3Inbox. cheers -ben [1] http://vimeo.com/75183993 [2] https://pharo.fogbugz.com/f/cases/edit/11702/spelling-error-transferred

3 2

LDAP - licensing....
by phil＠highoctane.be Sept. 28, 2013

Sept. 28, 2013

Hello, I am looking for an LDAP integration for Pharo 2.0 After googling, I found LDAPlayer On Squeaksource: http://www.squeaksource.com/@O_tBkvZNK0GC3Hlz/Ghl6udGE I saw from the mailing lists that Olivier Auverlot did some work on that. It would be good to have such a thing on Smalltalkhub. Maybe I missed it but the query returned no results there. Thx Phil

5 9

[update 3.0] #30427
by Marcus Denker Sept. 28, 2013

Sept. 28, 2013

30427 ----- 11700 Small code critics cleanup in Tools https://pharo.fogbugz.com/f/cases/11700 11697 Small code critics cleanup Nautilus+Nautilus common https://pharo.fogbugz.com/f/cases/11697 11696 Small kernel clean up https://pharo.fogbugz.com/f/cases/11696 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1271.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/NautilusCommon-MarcusDenker.1… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Nautilus-MarcusDenker.544.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-MarcusDenker.1624.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Compiler-MarcusDenker.534.diff

1 0

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Sept. 28, 2013

Sept. 28, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=wi… 1 regressions found. Zinc.Tests.ZnServerTests.testEntityTooLarge

1 0

[Issue Tracker] input of submitters/bug fixers needed
by Marcus Denker Sept. 28, 2013

Sept. 28, 2013

Hello, The issue tracker is again at over 500 entries: https://pharo.fogbugz.com/f/filters/33/All-by-project Please, if you submitted a bug in the past, check it's status! -> Maybe someone asked you a trivial question that *you* can answer in 10 seconds, but if you don't, the issue can not be moved forward? -> Maybe you fixed an issue but there was some problem ("You said you uploaded a Slice but I can't find it!". *you* can fix this in 20 seconds, whereas for everyone else this means re-creating your work from scratch. -> Maybe your bug that you reported ages ago is already fixed? You can check this very very quickly, whereas for everyone else this means quite some effort of understanding, re-creating and even then not being sure if it's really fixed. -> Maybe you added an Issue which is more your private project that nobody else will work on, anyway. Maybe you can think about not having an issue for that? -> Maybe you reported some real triviality. Why not fix it yourself? Does it really need someone else to submit a Slice? Marcus

5 8