November 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] VM Exit Value

by Sven Van Caekenberghe

On 25 Nov 2011, at 09:27, Sven Van Caekenberghe wrote: > For scripting purposes, I would like to use/control the VM exit status/value (on Linux). > > There is SmalltalkImage>>#snapshot:andQuit: but there is nothing there that indicates that one can set the process exit status. Is there a way to do that ? > > Has anyone a good idea on how the CogVM could communicate back to its invoking script whether is ran OK or not ? I think I found something else that might be helpful, but I have not yet worked it out fully. Basically using the #stdout stream in 1.3 it is very easy to generate ouput (this is really a very cool feature!). This script will produce either 'OK' or 'FAILED' depending on the #signalling (and produce a PharoDebug.log file as well): FileStream stdout wantsLineEndConversion: true. [ Error signal: 'Something went terribly wrong'. FileStream stdout nextPutAll: 'OK'; cr. ] on: Error do: [ :exception | Smalltalk logError: exception description inContext: exception signalerContext. FileStream stdout nextPutAll: 'FAILED'; cr. ]. Smalltalk snapshot: false andQuit: true. The problem with this technique is that you cannot use stdout for anything else. Sven

Nov. 25, 2011

Re: [Pharo-project] VM Exit Value

by Igor Stasenko

There is already support for that in platform-specific code. The function is sqInt ioExitWithErrorCode(int); so, the only thing which we need is to change the #primitiveQuit to see if there an extra argument to it, and then call that function instead of ioExit looks like easy to do. Btw, actually Cog VMs already doing that: primitiveQuit self ioExitWithErrorCode: (argumentCount = 1 ifTrue: [objectMemory integerValueOf: self stackTop] ifFalse: [0]) so.. you need only 1 thing: add one more method to Smalltalk: quitPrimitive: exitCode "Primitive. Exit to another operating system on the host machine, if one exists. All state changes in the object space since the last snapshot are lost. Essential. See Object documentation whatIsAPrimitive." <primitive: 113> self primitiveFailed so you can use it right now. -- Best regards, Igor Stasenko.

Nov. 25, 2011

Re: [Pharo-project] VM Exit Value

by Sven Van Caekenberghe

On 25 Nov 2011, at 16:09, StÃ©phane Ducasse wrote: > sven could you add an entry on the cog bug tracker? http://code.google.com/p/cog/issues/detail?id=64

Nov. 25, 2011

Re: [Pharo-project] Pharo 1.3 vs 1.2.1 some results for ConfigurationOfODBC

by Ben Coman

Nov. 25, 2011

Re: [Pharo-project] deprecated: in Deprecated14

by Marcus Denker

On Nov 25, 2011, at 11:53 AM, Pavel Krivanek wrote: > Hi, > > I would like to ask if the current solution where the method > Object>>#deprecated: is placed in the package Deprecated14, is good. I think the idea was to deprecate deprecated: so people use the one with more infos... (deprecated:on:in:) But for small external projects, deprecated: is just fine and there are users. So I suggest we just move it out of the deprecated package and have it as a simple to use version of deprecation tagging. > For images where this package is not present (e.g. Pharo-Kernel) we > got unimplemented call and possible DNU. The method > #deprecated:on:in: is in the kernel. > > Of course if you do not have deprecated code in the image then call of > it should raise error. However some external packages (and some > internal packages like Zinc) do not have deprecated code in separate > package and do use #deprecated: for deprecation warnings. > > Because #deprecated: is bound to Pharo version, I think it would be > better solution to have a message named pharoDeprecated: that will be > called from Pharo packages that will be placed in Deprecated14 package > and then have #deprecated: message placed in the kernel that will be > used by external packages. > > Cheers, > -- Pavel > -- Marcus Denker -- http://marcusdenker.de

Nov. 25, 2011

Re: [Pharo-project] VM Exit Value

by StÃ©phane Ducasse

sven could you add an entry on the cog bug tracker? Stef On Nov 25, 2011, at 9:48 AM, Sven Van Caekenberghe wrote: > > On 25 Nov 2011, at 09:37, Lukas Renggli wrote: > >> Not nice, but works reasonably well. The invoking script "listens" to Pharo generating some output file. >> Have a look at builder.sh, it does that. > > Thx, I knew about that one. > And indeed, it does seems to work, but it is not very nice compared to how everything else in *nix is supposed to work. > > Sven > >

Nov. 25, 2011

[Pharo-project] deprecated: in Deprecated14

by Pavel Krivanek

Hi, I would like to ask if the current solution where the method Object>>#deprecated: is placed in the package Deprecated14, is good. For images where this package is not present (e.g. Pharo-Kernel) we got unimplemented call and possible DNU. The method #deprecated:on:in: is in the kernel. Of course if you do not have deprecated code in the image then call of it should raise error. However some external packages (and some internal packages like Zinc) do not have deprecated code in separate package and do use #deprecated: for deprecation warnings. Because #deprecated: is bound to Pharo version, I think it would be better solution to have a message named pharoDeprecated: that will be called from Pharo packages that will be placed in Deprecated14 package and then have #deprecated: message placed in the kernel that will be used by external packages. Cheers, -- Pavel

Nov. 25, 2011

[Pharo-project] Issue 5028: failing MCPackageManager initialization

by Pavel Krivanek

http://code.google.com/p/pharo/issues/detail?id=5028 MCPackageManager class >> #initialize contains unimplemented call of #unregisterForNotifications so Monticello cannot be loaded to a fresh image. This method is no more present in the image. Does anyone know why it was removed? It seems to be related to same changes done by Stef. -- Pavel

Nov. 25, 2011

Re: [Pharo-project] Morphic replacement

by Igor Stasenko

On 25 November 2011 11:00, Fernando Olivero <fernando.olivero(a)usi.ch> wrote: > Dear all, > > I've been working on a hole replacement of Morphic myself, because if > was tired of fixing Morphic (or porting CUIS Morphic into Pharo), and > found much more productive the approach of rewriting it from scratch. > > In my expierience, i was 100% more productive by not trying to be > backward compatible with Morphic, Polymorph , etc. > > I found it easier to Â come up with a new set of widgets (EntryField, > AutoCompletionEntryField, Button, Label, Column, Row, > ScrollableColumns) from scratch. They are all fairly tested also. > > Maybe it's time to move on, and develop from the ground up a > Morphic-like successor, instead of fixing the current Morphic. There's > no problem with preserving the current UI for all the apps that are > out there, and provide a cleaner, simpler UI framework for the new > apps. > > Regarding the new "morphic", I only assume that i have a scalable > canvas, and the vm's notifying me of the user events. On top of that i > recreated a World, that can have multiple views. There's only one > World at a given time. Views are presented within the world in a given > viewport, and present a scene. Scene are were the shapes live in. > No World as a subclass of PasteUpMorph, no globals such as World, > ActiveWorld, Hand. ActiveHand, etcs.. > > The world has a mouse and a keyboard, which take care of events > announced by the world. For example GMouse>>down: aDisplayPosition, > would take care of transforming the display position into a world > position, into a view position, into a scene position, and finally > notifying the proper shape under the mouse that it has been clicked at > a certain local position. GShape>>clickedAt: , > GShape>>secondaryClickedAt:, etc.. > No Events hierarchy, or the awful switch currently in HandMorph ( > generateMouseEvent: or generateKeyboardEvent:). > > I have a "Gaucho" system working now, Â with GShape (instead of > Morphs), using the simple new layouts developed by Juan in CUIS, > uniform usage of keybindings across the whole GShape hierarchy, > amongst other goodies. It's still tailored to be a Morphic replacement > for Gaucho, so first i need to polish a few things prior to releasing > it. > > For example, i'm going to ditch my current scalable canvas > implementation, in favor of Athens. > Glad to hear that. > Hope that very soon i can provide more details, but my plans are to > release it as part of the next Gaucho version, to provide a working > example. > > Fernando > > -- Best regards, Igor Stasenko.

Nov. 25, 2011

[Pharo-project] [update 1.4] #14236

by Marcus Denker

14236 ----- Issue 5024: incomplete SUnit http://code.google.com/p/pharo/issues/detail?id=5024 Issue 5022: UITheme uncategorized method http://code.google.com/p/pharo/issues/detail?id=5022 -- Marcus Denker -- http://marcusdenker.de

Nov. 25, 2011