December 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] lowSpaceWatcher fresh Pharo 3.0 image

by Marcus Denker

On 10 Dec 2013, at 10:39, Roberto Minelli <roberto.minelli(a)usi.ch> wrote: > Hi, > > I just downloaded a fresh Pharo 3.0 image and I got a notification when I open the image > >> Not enough memory to launch the lowSpaceWatcher. > > This is triggered by SmalltalkImage>>#lowSpaceWatcher > > Is this normal? > Never saw it. And I open a fresh 3.0 image multiple times a day. Marcus

Dec. 10, 2013

lowSpaceWatcher fresh Pharo 3.0 image

by Roberto Minelli

Hi, I just downloaded a fresh Pharo 3.0 image and I got a notification when I open the image > Not enough memory to launch the lowSpaceWatcher. This is triggered by SmalltalkImage>>#lowSpaceWatcher Is this normal? Cheers, R

Dec. 10, 2013

Re: [Pharo-dev] Smalltalk in a C World

by askoh

Has anyone tried Pragmatic Smalltalk? Is what he says about the VM being a relic of the past true? Can someone get David Chisnall to join the discussions? All the best, Aik-Siong Koh -- View this message in context: http://forum.world.st/Smalltalk-in-a-C-World-tp4728217p4728931.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Dec. 10, 2013

Re: [Pharo-dev] Smalltalk in a C World

by Sven Van Caekenberghe

On 10 Dec 2013, at 09:26, phil(a)highoctane.be wrote: > As I am currently reading Andres Valloud books, and trying out the exercises, man, what do I know about how to make decent enough code. Close to nothing it seems. Yes, it is a mind blowing book, one of the best books, if not the best, about programming I ever read. Sven

Dec. 10, 2013

Re: [Pharo-dev] Smalltalk in a C World

by phil＠highoctane.be

I was more about primitives doing things with I/O. On Tue, Dec 10, 2013 at 9:50 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > On Dec 9, 2013, at 10:45 PM, phil(a)highoctane.be wrote: > > > Now, moving forward, what would be required to have an interpreter > embedded in C, even if this means having another image with a special API > and the whole enchilada? > > > > At least a working prototype. > > > > I have looked at the "Porting the VM" document and the part about > headless (which is now done differently). > > > > What comes to my mind is to define a specific neutral C platform that > would be able to execute basic bytecode. > > > > From videos of Ben, I saw SystemTracer (or SystemTracer2) recreating a > very tiny image making some noise to prove it was working. > > > > Could it be possible to target this kind of tiny image running inside a > C program through a base interpreter? This would avoid having to deal with > the whole primitives and plugins at the beginning. > > Guille continued and we are working to use his bootstrap as a basis for > 4.0. > Now you will need the key primitives such as become: at: at:put: and other. > > Stef >

Dec. 10, 2013

Re: [Pharo-dev] Smalltalk in a C World

by StÃ©phane Ducasse

On Dec 9, 2013, at 10:45 PM, phil(a)highoctane.be wrote: > Now, moving forward, what would be required to have an interpreter embedded in C, even if this means having another image with a special API and the whole enchilada? > > At least a working prototype. > > I have looked at the "Porting the VM" document and the part about headless (which is now done differently). > > What comes to my mind is to define a specific neutral C platform that would be able to execute basic bytecode. > > From videos of Ben, I saw SystemTracer (or SystemTracer2) recreating a very tiny image making some noise to prove it was working. > > Could it be possible to target this kind of tiny image running inside a C program through a base interpreter? This would avoid having to deal with the whole primitives and plugins at the beginning. Guille continued and we are working to use his bootstrap as a basis for 4.0. Now you will need the key primitives such as become: at: at:put: and other. Stef

Dec. 10, 2013

[pharo-project/pharo-core]

by GitHub

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

Dec. 10, 2013

[pharo-project/pharo-core] 6a1e6f: 30634

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 6a1e6f5c48d0cb93a2a1edb7b4c4aac40f589e0e https://github.com/pharo-project/pharo-core/commit/6a1e6f5c48d0cb93a2a1edb7… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-12-10 (Tue, 10 Dec 2013) Changed paths: A Komitter.package/DataRetriever.class/README.md A Komitter.package/DataRetriever.class/class/instance creation/for_.st A Komitter.package/DataRetriever.class/definition.st A Komitter.package/DataRetriever.class/instance/accessing/block_.st A Komitter.package/DataRetriever.class/instance/accessing/data.st A Komitter.package/DataRetriever.class/instance/accessing/nullObject_.st A Komitter.package/DataRetriever.class/instance/initialize/initialize.st A Komitter.package/DataRetriever.class/instance/private/retrieveData.st A Komitter.package/DataRetriever.class/instance/private/signalDataIsReady.st A Komitter.package/DataRetriever.class/instance/protocol/release.st M Komitter.package/KomitPackage.class/definition.st M Komitter.package/KomitPackage.class/instance/accessing/patch.st M Komitter.package/KomitPackage.class/instance/initialize/initialize.st R Komitter.package/KomitPackage.class/instance/private/resetFork.st M Komitter.package/KomitPackage.class/instance/private/retrievePatch.st R Komitter.package/KomitPackage.class/instance/private/signalPatchIsReady.st M Komitter.package/KomitPackage.class/instance/protocol/flush.st M Komitter.package/KomitSliceUI.class/instance/initialization/initializeDialogWindow_.st M Komitter.package/KomitterUI.class/instance/initialization/initializeDialogWindow_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script289.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30634.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-MorphicAdapters.package/MorphicButtonAdapter.class/class/specs/defaultSpec.st M Tools.package/FinderUI.class/instance/t - accessing/menu_shifted_.st Log Message: ----------- 30634 12376 Finder raises an error when right clicking on the main panel https://pharo.fogbugz.com/f/cases/12376 12380 The logic to retrieve the patch of KomitPackage should be extracted https://pharo.fogbugz.com/f/cases/12380 12378 On Unix, the shortcut to validate the Komitter window is not working https://pharo.fogbugz.com/f/cases/12378 12375 PluggableButtonMorph error on getMenuSelector https://pharo.fogbugz.com/f/cases/12375 http://files.pharo.org/image/30/30634.zip

Dec. 10, 2013

Re: [Pharo-dev] Smalltalk in a C World

by phil＠highoctane.be

I did a ton of Java (coding, training people, large scale deployments) and Java has enterprise grade features. For large apps/clients, not much can beat it these days. If you need to staff a team for a sizeable project, not much choice either. Things like this: http://ec.europa.eu/dgs/informatics/procurement/calls_running/index_en.htm where you see things like in this page ( http://ted.europa.eu/udl?uri=TED:NOTICE:380314-2013:TEXT:EN:HTML) : II.2.1) Total quantity or scope: 9 600 person-years (indicative, non-binding) for all lots for the maximum possible duration of the framework contracts. I guess there are not enough Pharo-aware people on the planet to fit this :-) There, the choice is going to be Java. Now, except when working with decent tools like Jetbrains' IntelliJ (don't get me started with Eclipse), it is really annoying to type. I am even a reseller of these products FWIW. Other than that it is a fine language. And cool people do cool things with it, like AOT (Ahead of Time) compilers. http://www.excelsior-usa.com/jet.html or the JRockitVM (from the ashes of BEA) http://www.oracle.com/technetwork/middleware/jrockit/overview/index.html If we could get an instrumented VM like that, well... For manifesting ideas out of my head, I do prefer Pharo. As a self-employed individual, more power to me. As a startup junkie, more power to me. If I need a Java or .NET guy, I've plenty of contacts in cheap countries who do work very very well. And f*ck Ruby on Rails. Now, I said it. As I am currently reading Andres Valloud books, and trying out the exercises, man, what do I know about how to make decent enough code. Close to nothing it seems. That is what is great in Pharo, a community of great minds. That you do not find often in a huge crowd as the chatter is too loud. </rant> Phil

Dec. 10, 2013

Re: [Pharo-dev] [Spec] Non resizable window

by Roberto Minelli

On Dec 10, 2013, at 8:11 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Dec 10, 2013, at 7:49 AM, Roberto Minelli <roberto.minelli(a)usi.ch> wrote: > >> Hi, >> >> Is there any simple way to make a SpecWindow not resizable? > > No idea but we should be able to specify that in the spec +1 ;-) > >> >> Cheers, >> R >> > >

Dec. 10, 2013