- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]
by GitHub Jan. 29, 2016

Jan. 29, 2016

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

1 0

[pharo-project/pharo-core] 0def64: 50557
by GitHub Jan. 29, 2016

Jan. 29, 2016

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 0def643003d9b5298ee0a5c4f06a3e6f4f8daa18 https://github.com/pharo-project/pharo-core/commit/0def643003d9b5298ee0a5c4… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-01-29 (Fri, 29 Jan 2016) Changed paths: M SUnit-UI.package/CommandLineTestRunner.class/instance/helper/printError_of_.st M SUnit-UI.package/CommandLineTestRunner.class/instance/helper/printFailure_of_.st A SUnit-UI.package/CommandLineTestRunner.class/instance/helper/shortStackDescriptionFor_.st M SUnit-UI.package/VTermTestRunner.class/instance/helper/print_short_of_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50556.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50557.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50556.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50557.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50557 17490 Command Line Handler test runner should print a small stack for failures and errors https://pharo.fogbugz.com/f/cases/17490 http://files.pharo.org/image/50/50557.zip

1 0

Nitpick: Launcher Colors
by Sean P. DeNigris Jan. 29, 2016

Jan. 29, 2016

I don't get the addition of alternating row colors to Launcher. As I understand this, it's value is in a table-like situation where one wants to track across the row in the same record. Since both panes have only one cell per row, I don't get the purpose, and it looks really funky to me in the dark theme. My 2c. Sean ----- Cheers, Sean -- View this message in context: http://forum.world.st/Nitpick-Launcher-Colors-tp4874592.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

4 4

[pharo-project/pharo-core] 885c7e: 50556
by GitHub Jan. 29, 2016

Jan. 29, 2016

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 885c7e53d4beeb012d4bdeb6212400b8d5a36e4c https://github.com/pharo-project/pharo-core/commit/885c7e53d4beeb012d4bdeb6… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-01-29 (Fri, 29 Jan 2016) Changed paths: A Collections-Strings.package/Symbol.class/class/access/allSymbols.st A Collections-Strings.package/Symbol.class/class/access/selectorsContaining_.st A Collections-Strings.package/Symbol.class/class/access/thatStartsCaseSensitive_skipping_.st A Collections-Strings.package/Symbol.class/class/access/thatStarts_skipping_.st R Collections-Strings.package/Symbol.class/class/accessing/allSymbols.st A Collections-Strings.package/Symbol.class/class/accessing/selectorThatStartsCaseSensitive_skipping_.st R Collections-Strings.package/Symbol.class/class/accessing/selectorsContaining_.st R Collections-Strings.package/Symbol.class/class/accessing/thatStartsCaseSensitive_skipping_.st R Collections-Strings.package/Symbol.class/class/accessing/thatStarts_skipping_.st A Collections-Strings.package/Symbol.class/class/as yet unclassified/release.st R Collections-Strings.package/Symbol.class/class/cleanup/compactSymbolTable.st A Collections-Strings.package/Symbol.class/class/initialization/allSymbolTablesDo_.st A Collections-Strings.package/Symbol.class/class/initialization/allSymbolTablesDo_after_.st A Collections-Strings.package/Symbol.class/class/initialization/compactSymbolTable.st A Collections-Strings.package/Symbol.class/class/initialization/initialize.st R Collections-Strings.package/Symbol.class/class/initialize-release/initialize.st R Collections-Strings.package/Symbol.class/class/initialize-release/release.st A Collections-Strings.package/Symbol.class/class/instance creation/findInternedSelector_.st A Collections-Strings.package/Symbol.class/class/instance creation/internSelector_.st R Collections-Strings.package/Symbol.class/class/iterating/allSymbolTablesDo_.st R Collections-Strings.package/Symbol.class/class/iterating/allSymbolTablesDo_after_.st A Collections-Strings.package/Symbol.class/class/private/initSelectorTable.st M Collections-Strings.package/Symbol.class/class/private/rehash.st A Collections-Strings.package/Symbol.class/class/private/resetSelectorTable.st A Collections-Strings.package/Symbol.class/class/private/selectorTable.st A Collections-Strings.package/Symbol.class/class/private/shutDown_.st R Collections-Strings.package/Symbol.class/class/system startup/shutDown_.st M Collections-Strings.package/Symbol.class/definition.st A Collections-Strings.package/Symbol.class/instance/testing/isSelectorSymbol.st M Kernel.package/CompiledMethod.class/instance/accessing/selector_.st M NECompletion.package/NECSymbols.class/class/private/interestingSymbolsDo_.st M Rubric.package/RubSHTextStylerST80.class/instance/visiting rb nodes/visitMessageNode_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50555.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50556.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50555.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50556.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50556 17496 add table for all defined method selectors and use it in code completion and syntax highlighting https://pharo.fogbugz.com/f/cases/17496 http://files.pharo.org/image/50/50556.zip

1 0

[pharo-project/pharo-core]
by GitHub Jan. 29, 2016

Jan. 29, 2016

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

1 0

[pharo-project/pharo-core] 6456a3: 50555
by GitHub Jan. 29, 2016

Jan. 29, 2016

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 6456a3f5d3400e8efce6941a99ea425f7c3da45a https://github.com/pharo-project/pharo-core/commit/6456a3f5d3400e8efce6941a… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-01-29 (Fri, 29 Jan 2016) Changed paths: R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50554.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50555.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50554.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50555.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50555 16735 Replace Startup/Shutdown list with SessionManager https://pharo.fogbugz.com/f/cases/16735 http://files.pharo.org/image/50/50555.zip

2 1

[pharo-project/pharo-core]
by GitHub Jan. 29, 2016

Jan. 29, 2016

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

1 0

Smalltalkhub scheduled maintenance next monday (February, 1st)
by Christophe Demarey Jan. 29, 2016

Jan. 29, 2016

Hello, Smalltalk will be down next monday (february, 1st) from 12:30 to 13:30 (french local time). IT will add storage to the root partition. Regards, Christophe

1 0

Experiences with git, tODE and GsDevKit_home: Part 1 - basic structure considerations
by Dale Henrichs Jan. 28, 2016

Jan. 28, 2016

This is the first post in what I expect to be a series of posts describing how I work with git and Smalltalk. The content of this post is based on work that I have done over the last 4 years working with FileTree[4], Metacello[3], tODE[1], GsDevKit_home[2], and git. It's important to note that while I will talk exclusively about git in this series of posts, 99% of what I talk about can be directly mapped to other disk-based SCM like svn, mercurial, etc. I will describe the structure used by GsDevKit_home with the intent to provide a reference point for discussion. The structure I am describing is basically my third attempt at disk structure, so it benefits from "mistakes" that I have made in previous attempts. I've been using the current structure on a daily basis for the last 9 months, so what I'm describing is based on real-life structures and code. ---- Currently,the fundamental pharo structure can be described as consisting of: a vm, a sources file, an image file, a changes file, and a package-cache. The vm and sources file are shared resources and can be used with a collection of images. The image and changes files are tied together as the changes files has the source for methods that are in the image. The image and changes files are also tied to specific versions of the sources file and vm... The package-cache can be shared amongst a wide variety of images including images created by different vms ... When you plug git into the mix, you'll have a a local git repository for each project that you have loaded in your image or intend to load into your image. The git repository should be considered as a resource that lies in between the package-cache and a changes file. The git repository is not tightly coupled to the image like the changes file (you can delete a git repository without impacting the functionality of an image), but if you are making changes in the image, then you _are_ coupled to a particular git commit identified by its SHA. Metacello will record the SHA of the git repository at the time that packages are loaded from a git repository (to enable this feature in Pharo, some methods need to be implemented in the MetacelloPlatform for Pharo) and this information is stored along with the Metacello registration for the project. Since the git repository can be independently manipulated from the shell or an image can be saved that references a SHA that is no longer "current" .... it is very important that the SHA be recorded and made visible to users via the tools. In the early days of my work with git, I didn't have this feature and it was very difficult to recover work from old images - I also made mistakes by committing an older version of a package over a newer commit ... nasty stuff ... Currently in tODE, i provide two menu items to work with "version skew": `skew diff` and `skew save`. The `skew diff` menu item just show the differences between to two commits (the commit when the code was loaded and the current commit) - if your project isn't dirty and the diff doesn't contain unexpected changeds, then you may simple load the new commit into your image and move forward. The `skew save` menu item, basically does a merge between the code in the image and the current commit - there a number of git operations that go into this process: checkout original SHA; save packages and commit; checkout custom branch from the "current commit", merge new commit into the branch. I plan on adding a `skew clone` menu item that does a git clone into a repository directory that is reserved for use by the stone (image) and then checks out the original SHA... this option would be more useful for folks who "know what they are doing" and allow for different work flows to be followed... Soooo --- managing skew is an important function for the "project browser"... Here's what the tODE "Project Browser" looks like when version skew is detected: project list with version skew Well I think that's enough for now...Here are some topics that I plan to cover in future posts: - what has to be done to get the initial clone and hook it into an image? - sharing git repos between separate "active images" - cloning a github:// repos? - ssh vs https clones - working with remotes Dale [1] https://github.com/dalehenrich/tode [2] https://github.com/GsDevKit/GsDevKit_home [3] https://github.com/dalehenrich/metacello-work [4] https://github.com/dalehenrich/filetree

3 6

why do I get error...when I try to find senders?
by stepharo Jan. 28, 2016

Jan. 28, 2016

Hi I open playground or nautilus. I type compile:classified: and select the text and I press senders and I get a syntax error expected.... Just typing this mail now I cannot reproduce it. There is something wrong with the system. Stef

4 5