January 2015 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]
by GitHub Jan. 22, 2015

Jan. 22, 2015

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

1 0

[pharo-project/pharo-core] 5af3c5: 40454
by GitHub Jan. 22, 2015

Jan. 22, 2015

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 5af3c5060fca692bcc86cdf90c43eae7d1389a44 https://github.com/pharo-project/pharo-core/commit/5af3c5060fca692bcc86cdf9… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-01-22 (Thu, 22 Jan 2015) Changed paths: R Graphics-Display Objects.package/DisplayScreen.class/instance/initialization/release.st M Nautilus.package/AbstractNautilusUI.class/instance/icons behavior/runScriptMethod_.st M Nautilus.package/MethodIsScriptAction.class/README.md M Nautilus.package/MethodIsScriptAction.class/instance/order/isActionHandled.st M Nautilus.package/MethodIsScriptAction.class/instance/order/privateActionIcon.st M NautilusCommon.package/extension/CompiledMethod/instance/isScriptMethod.st A NautilusCommon.package/extension/CompiledMethod/instance/isScriptMethodWithScript.st M Refactoring-Changes.package/RBRefactoryChangeManager.class/instance/initialize-release/release.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script454.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40454.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M StartupPreferences.package/StartupPreferencesLoader.class/README.md Log Message: ----------- 40454 14764 Review DisplayScreen>>release https://pharo.fogbugz.com/f/cases/14764 14763 RBRefactoryChangeManager>>#release method call order https://pharo.fogbugz.com/f/cases/14763 14714 StartupPreferencesLoader class comment references class StartupLoader https://pharo.fogbugz.com/f/cases/14714 14747 Beside <script> pragma also allow <script: someActionCode> pragma in a method https://pharo.fogbugz.com/f/cases/14747 http://files.pharo.org/image/40/40454.zip

1 0

[pharo-project/pharo-core]
by GitHub Jan. 22, 2015

Jan. 22, 2015

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

1 0

[pharo-project/pharo-core] e94dce: 40453
by GitHub Jan. 22, 2015

Jan. 22, 2015

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: e94dcee0885d0e6ae3ef6958db8439ca3e655eb0 https://github.com/pharo-project/pharo-core/commit/e94dcee0885d0e6ae3ef6958… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-01-22 (Thu, 22 Jan 2015) Changed paths: R Collections-Strings.package/String.class/instance/accessing/do_toFieldNumber_.st R Collections-Strings.package/String.class/instance/accessing/tabDelimitedFieldsDo_.st R Collections-Strings.package/String.class/instance/converting/splitInteger.st A Deprecated40.package/extension/Stream/instance/isMessageStream.st A Deprecated40.package/extension/String/instance/do_toFieldNumber_.st A Deprecated40.package/extension/String/instance/splitInteger.st A Deprecated40.package/extension/String/instance/tabDelimitedFieldsDo_.st M Monticello.package/MCClassDefinition.class/instance/installing/createClass.st R Monticello.package/extension/Stream/instance/isMessageStream.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script453.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40453.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40453 14762 Deprecate Stream>>isMessageStream https://pharo.fogbugz.com/f/cases/14762 14761 Move Collections-Strings deprecated methods to Deprecated40 package https://pharo.fogbugz.com/f/cases/14761 14758 Simplify MCClassDefinition>>#createClass https://pharo.fogbugz.com/f/cases/14758 http://files.pharo.org/image/40/40453.zip

1 0

Re: [Pharo-dev] [Pharo-users] CommandLine handler and UTF8 path
by Sven Van Caekenberghe Jan. 22, 2015

Jan. 22, 2015

Command line arguments enter the image level via VirtualMachine>>#getSystemAttribute: At that point they are already Strings. In your case, they must already be wrong at that point. > On 20 Jan 2015, at 16:51, Hilaire <hilaire(a)drgeo.eu> wrote: > > Le 20/01/2015 16:34, Sven Van Caekenberghe a Ã©crit : >> No they are not - Strings and Characters in Pharo are using plain Unicode encoding internally. > > Thanks for the update, and the reference link. > > Hilaire > > -- > Dr. Geo - http://drgeo.eu > iStoa - http://istoa.drgeo.eu > >

4 6

More people needed to review issues
by Marcus Denker Jan. 22, 2015

Jan. 22, 2015

Hello, Now that so many people talk so much: We need more people to *regularly* look at the issue tracker: https://pharo.fogbugz.com/ <https://pharo.fogbugz.com/> -> check if reported issues are reproducable -> check proposed solutions -> comment on new features (âI donât like that becauseâ¦.â) -> fix issues that are not yet fixed -> summarise issues with long discussions and distill âThe next action that needs to be done is:â â¦. Marcus

5 4

pharo-contribution CI out of space?
by Yuriy Tymchuk Jan. 22, 2015

Jan. 22, 2015

Hi, Iâm getting this things in logs: Downloading PharoV20.sources: http://files.pharo.org/sources//PharoV20.sources.zip <http://files.pharo.org/sources//PharoV20.sources.zip> pharo-vm/PharoV20.sources: write error (disk full?). Continue? (y/n/^C) warning: pharo-vm/PharoV20.sources is probably truncated did we run out of space on pharo-contribution? Uko

5 7

Re: [Pharo-dev] [squeak-dev] re: Context status 2015-01-16
by Nicolas Cellier Jan. 21, 2015

Jan. 21, 2015

2015-01-19 15:41 GMT+01:00 Craig Latta <craig(a)netjam.org>: > > Okay, I'll add both of the execution-driven imprinters to the > repository. They're called "active" and "passive" imprinting. > > Active imprinting is directed by the system that initially has the > desired code. An ActiveImprintingServer has clients in the systems which > will receive the code. Every time the server system runs a method in a > certain process, it imprints that method onto each of the clients. One > use case for this is giving the code of a demo to an audience as you run > it. > > Passive imprinting is directed by the system that wants the code. > The target system makes a remote-messaging connection to a system which > has the code, and runs an expression which will use the code. Every time > a method is missing from the target system (in any process), the target > system requests the missing method from the provider system, installs > it, and retries running that method. > > I have imprinted the exception-handling system, the compiler, and > the class builder with both approaches. > > > In this scheme, something is striking me. Some images share some code (classes, compiledMethods) But what about code mutations/updates? Without such mutations, is it still Smalltalk? Without active imprinting, such mutations might not be obvious to propagate (for example a subclass now overrides a message of super) And since you import class builder and compiler in the target, on what purpose? Is the target going to change a class locally? What if it then imports incompatible methods from provider? Or is the goal to just replicate some mutations from the provider? Maybe the scheme is more interesting for deployment of static code, but I'm curious to know if ever live updates would still be possible... > thanks, > > -C > > -- > Craig Latta > netjam.org > +31 6 2757 7177 (SMS ok) > + 1 415 287 3547 (no SMS) > > >

2 1

Re: [Pharo-dev] pharo-contribution CI out of space?
by Stephan Eggermont Jan. 20, 2015

Jan. 20, 2015

I've removed all jobs from the queue. Stephan

1 0

[ANN] Updated SQLite3 wrapper project based on NB
by Torsten Bergmann Jan. 20, 2015

Jan. 20, 2015

Some of you may already have noticed that it is already available but there was not yet a formal announcement, so here it is: There is a new way/project to work with the SQLite3 embeddable database. While in the past there was already a SQLite wrapper project for Pharo based on FFI this one is based on NativeBoost and also has some support for Glorp. The "NBSQLite3 for Pharo" is a project to provide an API and access to the SQLite3 database from within the Pharo image. With this tool you can use the small relational SQL engine into own Pharo projects. The project page is located on http://smalltalkhub.com/#!/~PharoExtras/NBSQLite3 More details can be found on the project page or on blog posts of PierceNg (the orginal author): http://www.samadhiweb.com/blog The project is now additionally refactored, supported with green tests, documented, split in seperate loadable packages and moved to the PharoExtras team at STHub. A Metacello configuration for Pharo 4 is ready in the Pharo 4 configuration browser. If you like you can help to test on/adopt to different platforms (at a minimum known to work on Windows) or improve it further. Have fun Pierce and T.

2 5