- Pharo-dev - lists.pharo.org

IMPORTANT: iceberg home changed
by Esteban Lorenzano April 29, 2017

April 29, 2017

As part of our work for release, I changed the home of Iceberg into his own place: https://github.com/pharo-vcs/iceberg So, now to install you will need: Metacello new baseline: 'Iceberg'; repository: 'github://pharo-vcs/iceberg:dev-0.4'; load. I also uploaded a Configuration to the *catalog>http://catalog.pharo.org*, so you can load while doing the transition.

7 9

saving an image on windows and opening it on mac problems
by Andrei Chis April 27, 2017

April 27, 2017

Hi all, I saw that there are a few issues about images saved on an operating system not working when opened on other operating systems: - https://pharo.fogbugz.com/f/cases/19852/Unable-to-open-image-in-OSX-after-i… - https://pharo.fogbugz.com/f/cases/19869/Infinite-loop-on-mac-when-opening-a… - https://pharo.fogbugz.com/f/cases/19272/Image-freezes-on-Linux-if-it-was-pr… - http://forum.world.st/Image-freezes-on-Linux-if-it-was-previously-saved-on-… I gave the fix in case 19869 a try and with it I can save an image on windows and open it on mac, however, there are some side effects. First several folders having the following name are created in the image folder: '\Users\andrei\test-image' '\Users\andrei\test-image\pharo-local\' '\Users\andrei\test-image\pharo-local\ombu-sessions' Second, I can only open the image on man once. The second time I get the following stack: [31mPrimitiveFailed: primitive #createDirectory: in WindowsStore failed [0mWindowsStore(Object)>>primitiveFailed: WindowsStore(Object)>>primitiveFailed WindowsStore(DiskStore)>>createDirectory: WindowsStore(FileSystemStore)>>ensureCreateDirectory: WindowsStore(FileSystemStore)>>ensureCreateDirectory: WindowsStore(FileSystemStore)>>ensureCreateDirectory: WindowsStore(FileSystemStore)>>ensureCreateDirectory: WindowsStore(FileSystemStore)>>ensureCreateDirectory: WindowsStore(FileSystemStore)>>ensureCreateDirectory: FileSystem>>ensureCreateDirectory: FileReference>>ensureCreateDirectory OmSessionStore>>resetWithStoreNamed: OmSessionStore>>resetWithNextStoreName OmSessionStore>>store WeakMessageSend>>value WeakMessageSend>>cull: WeakMessageSend>>cull:cull: [ action cull: arg1 cull: announcer ] in LegacyWeakSubscription(WeakAnnouncementSubscription)>>deliver: in Block: [ action cull: arg1 cull: announcer ] BlockClosure>>on:do: BlockClosure>>on:fork: LegacyWeakSubscription(WeakAnnouncementSubscription)>>deliver: [ tmp4 deliver: arg1 ] in SubscriptionRegistry>>deliver:to:startingAt: in Block: [ tmp4 deliver: arg1 ] BlockClosure>>ifCurtailed: SubscriptionRegistry>>deliver:to:startingAt: SubscriptionRegistry>>deliver:to: SubscriptionRegistry>>deliver: SystemAnnouncer(Announcer)>>announce: SystemAnnouncer>>announce: SystemAnnouncer>>snapshotDone: SessionManager>>snapshot:andQuit: [0m So it seems that OmSessionStore is not reset and holds a reference to a the windows path which it tries to create. Cheers, Andrei

6 10

OmSessionStore and SnapshotDone event (was: saving an image on windows and opening it on mac problems)
by Andrei Chis April 27, 2017

April 27, 2017

Hi, OmSessionStore registers an action (OmSessionStore>>#store) when the event SnapshotDone is triggered. However this event is triggered immediately when an image is opened after being saved, before the file system was reset. This means that OmSessionStore>>#store is called before the file system is reset. Hence, if you save an image on windows and open it on mac you run into issues as OmSessionStore>>#store performs file operations that will work with a WindowsStore instead of a MacStore. Does OmSessionStore need to register to SnapshotDone events? When the image is opened OmSessionStore>>#store will be called anyway as OmSessionStore registers a start-up action. Cheers, Andrei

3 4

Monticello: Script to suck up versions from a filetree repository and copy them to an HTTP repository?
by Eliot Miranda April 27, 2017

April 27, 2017

Hi All, anyone have a script for copying versions of packages in filetree repositories into MC HTTP repositories? I'm looking at a filetree: repository for a package right now and... - in the repository browser only Foo.package appears, not a list of versions - when I view the history of the package I get a list of versions but there is no menu on selections from the list, so no obvious way of accessing a version (browsing it, copying it, viewing differences between versions, etc) _,,,^..^,,,_ best, Eliot

4 3

[pharo-project/pharo-core]
by GitHub April 27, 2017

April 27, 2017

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

1 0

[pharo-project/pharo-core] 7d63a4: 60473
by GitHub April 27, 2017

April 27, 2017

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 7d63a4ad238ecb55853f9a495424b126aa0dd0ef https://github.com/pharo-project/pharo-core/commit/7d63a4ad238ecb55853f9a49… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-04-27 (Thu, 27 Apr 2017) Changed paths: M FFI-Pools.package/FFIConstants.class/README.md M FFI-Pools.package/FFIConstants.class/class/pool initialization/initialize.st R FFI-Pools.package/FFIConstants.class/class/pool initialization/initializeCallingConventions.st R FFI-Pools.package/FFIConstants.class/class/pool initialization/initializeErrorConstants.st R FFI-Pools.package/FFIConstants.class/class/pool initialization/initializeTypeConstants.st A FFI-Pools.package/FFIConstants.class/class/private - initialization/initializeCallingConventions.st A FFI-Pools.package/FFIConstants.class/class/private - initialization/initializeErrorConstants.st A FFI-Pools.package/FFIConstants.class/class/private - initialization/initializeTypeConstants.st M Monticello.package/MCPackageManager.class/class/event registration/registerInterestOnSystemChangesOnAnnouncer_.st A Monticello.package/MCPackageManager.class/class/system changes/classRenamed_.st M Rubric.package/RubOpeningClosingDelimiterDecorator.class/instance/drawing/drawOn_.st M Rubric.package/RubTextSelectionColor.class/class/default accessing/oppositeDelimiterSelection.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60472.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60473.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60472.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60473.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Zodiac-Tests.package/ZdcSecureSocketStreamTests.class/instance/tests/testIsNativeSSLPluginPresent.st Log Message: ----------- 60473 19968 Class rename do not mark extending packages dirty https://pharo.fogbugz.com/f/cases/19968 19987 Bad highlight for matching parentheses with dark theme https://pharo.fogbugz.com/f/cases/19987 19995 Fix typo in testIsNativeSSLPluginPresent https://pharo.fogbugz.com/f/cases/19995 19996 Cleanup FFIConstants https://pharo.fogbugz.com/f/cases/19996 http://files.pharo.org/image/60/60473.zip

1 0

Code colors with dark theme (out of box)
by Torsten Bergmann April 27, 2017

April 27, 2017

The damn deal might be done to switch Pharo 6 now to the dark theme - but my impression is that the way we provide it now lets say is "not very comfortable". When - opening Pharo 6.0 Latest update: #60471 (as of today) - opening a new Nautilus browser the code color settings are unreadable (see screenshot). I suggest to use black text on black background in the future to improve the situation even further ;) Are there already any bugs to have a better color code scheme for the dark theme? Have fun T.

3 4

[pharo-project/pharo-core]
by GitHub April 27, 2017

April 27, 2017

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

1 0

[pharo-project/pharo-core] f71be9: 60472
by GitHub April 27, 2017

April 27, 2017

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: f71be96bc15de12d74e339971558b0e77b3e9bda https://github.com/pharo-project/pharo-core/commit/f71be96bc15de12d74e33997… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-04-27 (Thu, 27 Apr 2017) Changed paths: M BaselineOfMorphic.package/BaselineOfMorphic.class/instance/actions/postload_package_.st M SUnit-UITesting.package/SimulateKeystrokesSpecification.class/instance/tests/testSimulateKeystroke.st M SUnit-UITesting.package/SimulateKeystrokesSpecification.class/instance/tests/testSimulateKeystrokes.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60471.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60472.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60471.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60472.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-SessionManager.package/SessionManager.class/README.md M Text-Edition.package/TextEditor.class/instance/menu messages/changeStyle.st Log Message: ----------- 60472 19992 Use assert:equals: in simulateKeyStroke tests https://pharo.fogbugz.com/f/cases/19992 19463 Improve SessionManager class comment https://pharo.fogbugz.com/f/cases/19463 19983 activate the Dark theme by default in the bootstrapped image https://pharo.fogbugz.com/f/cases/19983 19991 Use of deprecated name method in TextEditor>>changeStyle https://pharo.fogbugz.com/f/cases/19991 http://files.pharo.org/image/60/60472.zip

1 0

Commenting the Session Manager
by Guillermo Polito April 27, 2017

April 27, 2017

Hi all, I took some minutes to write down a class comment for the SessionManager class. There was an issue asking for it: https://pharo.fogbugz.com/f/cases/19463/Improve-SessionManager-class-comment Since it is an important topic, and sometimes too low level for some people, I'd like to have some feedback. Is it well explained? Is there something that is key for you and is missing? I know that the comment is not exhaustive, it can be iterated and enhanced, but we can have a nice first version of it for the release. Thanks, Guille =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= I am the object responsible of managing how sessions work in Pharo. A session defines the boundaries of work in the image. A new session starts when the image starts or when the image is saved. A session ends when the image quits or it is saved. There is only one active session at a single point of time. Saving the image causes the active to stop, and starts a new session. The current active session is hold by myself, the singleton session manager. It can be accessed by doing: SessionManager default currentSession. The most important responsibility of the session manager is to manage how resources and services in the image are started up and shut down at the beginning and end of a session respectively. For example, when the image starts, several initialization routines should be executed to make sure that the image has access to the graphic drivers, the standard input/output file descriptors and so on. Such initialization happens in the #snapshot:andQuit: method. #snapshot:andQuit: will: - stop current session - save current image if requested - quit if requested - start a new session When a session is started, all elements registered in the startup list are started up. When a session is stopped, all elements registered in the shutdown list are shut down. # Managing Startup and Shutdown lists The startup and shutdown lists can be accessed through the messages: SessionManager default startupList. SessionManager default shutdownList. In general terms, the shutdown list is the startup list reversed. Upon a startup [shutdown], all elements in the startup list are sent the message #startup: [#shutdown:] with a boolean as argument that indicates wether the image is being saved [closed]. Internally, startup and shutdown lists are prioritised. Priorities are managed by startup categories. By default the session manager includes the following categories in decreasing priority order: - System - Network - Graphical User Interface - Tools - User Categories can be accessed as follows: SessionManager default categoryNamed: aName. New categories can be registered in the system using the messages: SessionManager default createCategory: aCategoryName. SessionManager default createCategory: aCategoryName after: anotherCategoryName. Finally, to subscribe some resource handler to the startup shutdown lists, we need to subscribe a handler, subclass of AbstractSessionHandler. The most common handler implementation so far is the ClassSessionHandler, that allows to subscribe a class for startup and shutdown, keeping backwards compatibility to the old startup mechanism. ClassSessionHandler forClassNamed: aClassName We can register a session handler as follows SessionManager default register: (ClassSessionHandler forClassNamed: self name) inCategory: SessionManager default systemCategory. Or alternatively, by talking to the corresponding category: SessionManager default systemCategory register: (ClassSessionHandler forClassNamed: self name) # System Category Priorities A system category internally prioritizes its elements to provide a fine grained control on the startup and shutdown order. All methods above have variants that allow developers to specify the priority inside the category: SessionManager default register: (ClassSessionHandler forClassNamed: self name) inCategory: SessionManager default systemCategory atPriority: 100. SessionManager default systemCategory register: (ClassSessionHandler forClassNamed: self name) atPriority: 100 By default, if no priority is specified, a default priority is used. Every category answers to the message #defaultPriority. # How does an image restart from the point it was before An important point in the image startup is how does it manage to restart from the point where it was executing when it was saved. When the image is saved, using the snapshot primitive, the entire image is freezed at the point of the snapshot. More particularly, the process that invoked the snapshot primitive is freezed at the point of the primitive call. This works as a process fork: the running image will return from the snapshot primitive and the saved file will also start from the freezed point. To differentiate whether we are executing in the running image or in the freshly-saved image, the snapshot primitive returns a boolean indicating it. Read the comment of #snapshotPrimitive for more details.

4 7