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

Re: [Pharo-project] ProtoObject basicNew :)

by StÃ©phane Ducasse

Apparently I can do a doit I was naively doing an inspect ;) > Don't you just need the basicNew primitive, and make sure that the "magic number" is set in the object that has the basicNew installed to something that makes sense? I do not know what is the magic number. I guess that my problem was that I have first to define what is the minimal behavior. > If you want to send messages to the object, probably also best install some dictionary as the method dict instvar. But I guess that ProtoObject has some behavior since I can browse the class with a browser. > > Toon > > On 11/25/2011 09:26 PM, StÃ©phane Ducasse wrote: >> Hi >> I would like to know the methods that I should define in a subclass of ProtoObject so that I can use basicNew. >> Does any of you have an idea? >> >> Stef > >

Nov. 25, 2011

Re: [Pharo-project] ProtoObject basicNew :)

by Toon Verwaest

Don't you just need the basicNew primitive, and make sure that the "magic number" is set in the object that has the basicNew installed to something that makes sense? If you want to send messages to the object, probably also best install some dictionary as the method dict instvar. Toon On 11/25/2011 09:26 PM, StÃ©phane Ducasse wrote: > Hi > I would like to know the methods that I should define in a subclass of ProtoObject so that I can use basicNew. > Does any of you have an idea? > > Stef

Nov. 25, 2011

[Pharo-project] ProtoObject basicNew :)

by StÃ©phane Ducasse

Hi I would like to know the methods that I should define in a subclass of ProtoObject so that I can use basicNew. Does any of you have an idea? Stef

Nov. 25, 2011

Re: [Pharo-project] deprecated: in Deprecated14

by Pavel Krivanek

Ok for me -- Pavel 25.11.2011 v 16:15, Marcus Denker <marcus.denker(a)inria.fr>: > > 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

[Pharo-project] [update 1.4] #14238

by Marcus Denker

14238 ----- Issue 4998: ContextPart>>#runUntilErrorOrReturnFrom: (for testing) http://code.google.com/p/pharo/issues/detail?id=4998 Issue 4994: Two failing test in ProcessTest http://code.google.com/p/pharo/issues/detail?id=4994 Issue 5014: zn updates http://code.google.com/p/pharo/issues/detail?id=5014 -- Marcus Denker -- http://marcusdenker.de

Nov. 25, 2011

Re: [Pharo-project] VM Exit Value

by Sven Van Caekenberghe

Thank you! On 25 Nov 2011, at 17:06, Igor Stasenko wrote: > Yes, it works! > > if i open image like that: > ./results/NBCog.app/Contents/MacOS/NBCog ./image/generator.image ; echo $? > > and then do: > Smalltalk quitPrimitive: 10 > > it prints: > 10 > > > On 25 November 2011 17:01, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> in the bug tracker please :) >> >> >> On Nov 25, 2011, at 4:59 PM, Igor Stasenko wrote: >> >>> 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

[Pharo-project] [update 1.4] #14237

by Marcus Denker

14237 ----- Issue 5010: Testing GUI widgets http://code.google.com/p/pharo/issues/detail?id=5010 Issue 5027: rename _log.txt to PharoDebug.log http://code.google.com/p/pharo/issues/detail?id=5027 Issue 5026: update Pharo-Kernel and Pharo-Core package sets http://code.google.com/p/pharo/issues/detail?id=5026 -- Marcus Denker -- http://marcusdenker.de

Nov. 25, 2011

Re: [Pharo-project] Building 32-bit Cairo library on Macs

by StÃ©phane Ducasse

cool We want more :) Stef On Nov 25, 2011, at 5:17 PM, Igor Stasenko wrote: > Just to let you know: > > it works on Mac! > I just loaded the code which Javier did for linux, changed path to > library and it worked out of the box. > all examples in [1] are working out of the box! > > So, now i can start wiring Cairo backend for Athens :) > > [1] http://squeaksource.com/NBCairo/ > > -- > Best regards, > Igor Stasenko. >

Nov. 25, 2011

[Pharo-project] [update 1.4] #14237

by Marcus Denker

14237 ----- Issue 5010: Testing GUI widgets http://code.google.com/p/pharo/issues/detail?id=5010 Issue 5027: rename _log.txt to PharoDebug.log http://code.google.com/p/pharo/issues/detail?id=5027 Issue 5026: update Pharo-Kernel and Pharo-Core package sets http://code.google.com/p/pharo/issues/detail?id=5026 -- Marcus Denker -- http://marcusdenker.de

Nov. 25, 2011

Re: [Pharo-project] Morphic replacement

by Schwab,Wilhelm K

Benefit of doubt: I assume they used absolute coordinates in the belief that it would reduce the amount of translation of coordinates that would be needed??? Less benefit of doubt: they might have done it to make things easier on "end users." If that were their answer, I would respond with a long-standing life lesson: NEVER coddle the user; it always backfires. The user won't do anything with the code you mangled thinking you were going to help them, and you've just made life hard on the people they will have to hire to do things for them. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Igor Stasenko [siguctua(a)gmail.com] Sent: Friday, November 25, 2011 11:26 AM To: Pharo-project(a)lists.gforge.inria.fr; fernando.olivero(a)usi.ch Subject: Re: [Pharo-project] Morphic replacement On 25 November 2011 17:22, Fernando Olivero <fernando.olivero(a)usi.ch> wrote: > Glad to be able to say: yes! > > Each object speaks in its own coordinate system, its parent already > internalized the point. > > Suppose we have a click, announced by the mouse at a given point, > given in Display coordinates. > > From now on we go, from the display, to the view , to the scene, to > the shape, and on each step the parent deals with a point in its own > coordinate system, and passes on the internalized click to its > children. > > Views present a scene, consisting of shapes, at a given viewport of the display. > > Makes it a lot easier when you are programming the interaction of > custom widgets, to always deal with local coordinates, and greatly > simplifies the event handling code as well. > ideed. i don't understand, why original Morphic authors decided to use absolute coordinates for morphs > > On Fri, Nov 25, 2011 at 5:00 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> did you kill the absolute coordinates? >> >> say yes please :) >> >> Stef >> >> On Nov 25, 2011, at 11:00 AM, Fernando Olivero 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. >> >> excellent! >> >>> >>> 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. >>> >>> 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