September 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] [update 2.0] #20293
by Marcus Denker Sept. 18, 2012

Sept. 18, 2012

20293 ----- Issue 6677: replace some methodDict keys includes: with #includesSelector: http://code.google.com/p/pharo/issues/detail?id=66776 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] Zinc Progress
by Camillo Bruni Sept. 17, 2012

Sept. 17, 2012

we just discovered a strange side-effect of enabling progress report on ZnClient when loading mc packages: - with progress notification: ~1s - without notification: ~30ms I didn't dig more into the details bug this is quite a diff :D, and most probably the main cause that pharo loads configurations and mc stuff slowly. The latest pharo2.0 release has the progress report disabled. best cami

4 16

Re: [Pharo-project] Changing permanently the mouse cursor
by Fernando Olivero Sept. 17, 2012

Sept. 17, 2012

HandMorph is the software cursor, which now only gets drawn when the hand is drawn, which only happens when its carrying a morph. Cursor is the hardware cursor, the one handled by the VM and drawn most of the time. IMO, we need to change the VM, to not handle the hardware cursor anymore, so we can rely only on the software cursor. So we can always be sure that HandMorph or (the equivalent using other UI framework) is the cursor being drawn. Fernando On Mon, Sep 17, 2012 at 12:00 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 17 September 2012 11:40, Hilaire Fernandes > <hilaire.fernandes(a)edu.ge.ch> wrote: >> Hello, >> >> One can change temporary the mouse cursor with something like: >> >> World currentHand showTemporaryCursor: ThemeIcons eyedropperIcon >> >> But depending on the widgets the mouse is over, its cursor may change again. >> >> Beside hacking the HandMorph class is there a way to change permanently >> the mouse cursor? >> > Good question. > > AFAIK, last time i seen it in code, the point where cursor is > controlled is in Cursor class. > Hand resets cursor by sending #normal message to it. > > It would be really nice to have changeable default cursor. > The Cursor global used everywhere in system. We should find the way > how to avoid that. > >> Thanks >> >> Hilaire > > -- > Best regards, > Igor Stasenko. >

3 2

Re: [Pharo-project] An idea about visual feedback in Athens
by Fernando Olivero Sept. 17, 2012

Sept. 17, 2012

Igor, the way i've handled the "mouse hit" issue, is by asking the parent shape (morph) to take care of a mouse hit, and let him handle or forward the hit. The topmost shape are sent the mouseDown: aLocalPoint, then each shape can choose to react, if its a composite shape or by a specific behavior. The topmost shape is always "a scene shape", which knows the bounds in global coordinates, then internally it applies local transforms to eventually get to the inner shape which was hit. The separation between scene shapes and shapes, allows this mechanism, similar to the one you propose, to cache the global state. I prefer this approach, instead of the "framework" level as you propose, because is more of a top-down collaboration, always dealing with local coordinates. It greatly simplifies the UI framework, avoiding the messy "god classes" and complex methods you mentioned and many more in Morphic. Fernando On Sun, Sep 2, 2012 at 10:12 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Yes we should really refactor this hierarchy. > We should finish first the event model cleaning at VM/Image border then we work on this one. > > On Aug 31, 2012, at 9:21 PM, Igor Stasenko wrote: > >> and to give an idea, how current Morphic doing that, a starting point is >> MorphicEventDispatcher >> >> personally, i find this code too complex to understand, given heavy >> use of case statements and branches. >> >> But i figured out, that this method: >> >> >> dispatchEvent: anEvent with: aMorph >> "Dispatch the given event for a morph that has chosen the receiver to >> dispatch its events. The method implements a shortcut for repeated >> dispatches of events using the same dispatcher." >> anEvent type == lastType ifTrue:[^self perform: lastDispatch with: >> anEvent with: aMorph]. >> "Otherwise classify" >> lastType := anEvent type. >> anEvent isMouse ifTrue:[ >> anEvent isMouseDown ifTrue:[ >> lastDispatch := #dispatchMouseDown:with:. >> ^self dispatchMouseDown: anEvent with: aMorph]]. >> anEvent type == #dropEvent ifTrue:[ >> lastDispatch := #dispatchDropEvent:with:. >> ^self dispatchDropEvent: anEvent with: aMorph]. >> anEvent isWindowEvent ifTrue:[ >> lastDispatch := #dispatchWindowEvent:with:. >> ^self dispatchWindowEvent: anEvent with: aMorph]. >> lastDispatch := #dispatchDefault:with:. >> ^self dispatchDefault: anEvent with: aMorph >> >> --- >> >> actually can be replaced by one-liner: >> >> dispatchEvent: anEvent with: aMorph >> morph := aMorph. >> ^ anEvent sentTo: self >> >> .. yeah.. my favorite thing: double-dispatch. >> >> -- >> Best regards, >> Igor Stasenko. >> > >

2 1

[Pharo-project] Sending email with Pharo
by Hilaire Fernandes Sept. 17, 2012

Sept. 17, 2012

Dear all, A DrGeo user asked me if it will be possible to share DrGeo sketch by Email. I guess he means, sending an email with an attached DrGeo file. My question is: - can we send email with Pharo? - if yes, can we attach file to such email? Any pointer, if any, appreciated Thanks Hilaire PS: if any of you have any idea how to share a file between different DrGeo instances running in different host, I will greatly appreciate your ideas/advices.

3 6

[Pharo-project] [update 2.0] #20292
by Marcus Denker Sept. 17, 2012

Sept. 17, 2012

20292 ----- Issue 6630: [Enh] Pointers only via STRONG references http://code.google.com/p/pharo/issues/detail?id=6630 Issue 6674: Make HTTPProgress a proper object http://code.google.com/p/pharo/issues/detail?id=6674 Issue 6676: PseudoClassOrganizer DNU #categoriesSorted http://code.google.com/p/pharo/issues/detail?id=6676 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [update 2.0] #20291
by Marcus Denker Sept. 17, 2012

Sept. 17, 2012

20291 ----- Issue 6637: Unused global variable? http://code.google.com/p/pharo/issues/detail?id=6637 Issue 6616: ReleaseTest for RPackageOrganizer http://code.google.com/p/pharo/issues/detail?id=6616 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [update 2.0] #20290
by Marcus Denker Sept. 17, 2012

Sept. 17, 2012

20290 ----- Issue 6620: Fix testRemoveTaggedClasses bad reference http://code.google.com/p/pharo/issues/detail?id=6620 ScriptLoader new unregisterPackage: 'Graphics'. ScriptLoader new unregisterPackage: 'RPackage'. ScriptLoader new addHomeRepositoryToAllPackages. -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [NB] Speaking about callbacks
by Igor Stasenko Sept. 17, 2012

Sept. 17, 2012

Hello, there i am happy to say that during last week, i found a cure for my callback code, and so finally callbacks are now working without crashing the VM. :) But before releasing it to public, first, i need to update VMs for that, because of additional callback support code in VM. Right now, i'd like to discuss about different ways of defining/creating callbacks. And i need more input from people, because i think the way how i implemented it is good for get started, but it looks like there could be more convenient forms :) So, the existing implementation, for creating a callback, you must make a subclass of NBFFICallback, overide #fnSpec method and then instantiate it by using: callback := MyCallBack on: [:... some block ] and then you must pass it somewhere (to some external function), and so, when callback get called, your block will handle it. In objective-C, however it would be much nicer to have a smalltalk objects act as a Obj-C objects (so implementing a methods for it will naturally map them as a callbacks ). For instance imagine that i wanna make own subclass of NSFoo obj-C class and wanna override the #bar method. And then i passing it as an obj-c instance around and each time ,Obj-C #bar message is sent to it , i got a #bar message sent to my smalltalk instance. That would be really cool, isnt? Despite it is only applicable to obj-c because of similar object model :) I imagine it could be done as following: in #bar method you putting a special pragma: MyClass>>bar <objCMethod: 'int ()'> ^ 5 that's it, you telling the compiler that given method can be called from Objective-C.. and you don't have to manually instantiate callbacks etc.. In fact, same form can be used for non-objC callbacks , you must just tell something like: callback := (MyClass>>#bar) asCallbackFor: myObject. here, you instantiating a callback, which when called, the object 'myObject' will receive #bar message. But unlike from Obj-C this callback won't work for all instances of MyClass, but just for specific one. And third form is a variation of original one, instead of subclassing the NBFFICallback, actually i can change implementation to use special factory class(es) for it, so to create a callback you will do something like: callbackFactory := NBFFICallback withSignature: #( int (int x, void * bar)). callback := callbackFactory on: [:x :bar | .... ]. So, i'd like to hear your input, which one you like, and which ones you prefer to have 1. requires creating a subclass of NBFFICallback, overriding it's fnSpec method. Takes a block closure as a callback. 2. first you must create a factory object by specifying a callback signature, then you can instantiate new callbacks by passing a block closure to that factory 3. to create a callback you must specify it's signature in one of the compiled methods, and specify an object which will receive a message when callback will be called. -- Best regards, Igor Stasenko.

4 8

Re: [Pharo-project] Sending email with Pharo
by Stephan Eggermont Sept. 17, 2012

Sept. 17, 2012

Hi Hilaire, There was a post from Scott Sproule on using Amazon SES with zinc and stunnel. Sven, you remember? From the response it was not clear to me if he managed to get everything working, and the need for stunnel might not be there with the current SSL support. SES is about 10% of the cost of postmaster. Attaching to mail is a well-known process. There are no problems there. Stephan

2 1