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

Re: [Pharo-project] Netstyle experience (was Do not feed the trolls)

by Christoph Wysseier

Dear Stef Am 22.02.12 08:32, schrieb StÃ©phane Ducasse: > I'm convinced that having support for multitouch event/ genie and others works (for iPad = $$$$) is important. Without pretending to know the future, IMHO standalone apps for tablets and mobile will disappear over time. Out of my perspective it would be far more important to move in the direction of web-based technologies also in this area. Looking at the success stories of Pharo and our own strategy I do not see the advantages of having multi-touch support for the development of such applications. Or did I misinterpret your intention? Cheers, Chris

Feb. 22, 2012

Re: [Pharo-project] Proposal: coverage tests

by Marcus Denker

On Feb 21, 2012, at 10:40 PM, Mariano Martinez Peck wrote: > That is just AMAZINGLY COOL. I cannot believe we can do that in 5 lines of code. WOW. But -> it is interpreted -> it is very low level Now imagine we would have instead of bytecode the a high level AST *and* a way to extend a runtime compiler infrastructure at runtime... With that you can do it in less lines, and even very trivally :-) Marcus -- Marcus Denker -- http://marcusdenker.de

Feb. 22, 2012

Re: [Pharo-project] gl/cl interop

by StÃ©phane Ducasse

On Feb 22, 2012, at 3:58 AM, chadwick wrote: > Hi, I'm new to Pharo & interested in doing some OpenCL + OpenGL for visualization. Looking around I'm confused by the differences between the various OpenGL libs and Alien vs FFI vs NativeBoost. Years ago I did some OpenGL-based GPGPU work in Squeak (OpenCobalt), but that's all out of date I think. For interop I need to get hold of the current gl context (e.g. glxGetCurrentContext), but according to other threads here that's not so easy in Squeak or Pharo. I tried NativeBoost but it didn't have a Linux implementation. What's the best way to proceed ? Igor will release soon a new canvas that directly access openGL. The new canvas is called Athens Athens supports Cairo OpenGL bitmap Athens OpenGL calling is based on NativeBoost. Now on the way to go there Javier used NativeBoost to check how we can get access to openGl Context on linux. I should sit with igor this morning to get a cube in OpenGL debugging on the fly presentation and we will do a video for YOU. Happy :). Stef

Feb. 22, 2012

Re: [Pharo-project] Netstyle experience (was Do not feed the trolls)

by Guido Stepken

"mouseOverHandler" is *absolutely* depreciated everywhere, iOS, Android AND Windows 8 ... tablet useforms dominate Desktop useforms more and more. just my 2ct. Am 22.02.2012 08:32 schrieb "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr>: > > > > People might mistakenly think that we wanna change things solely for > > the sake of change. But it is not like that. > > We need these changes , need to fix our infrastructure, because > > without solid basement you cannot build anything good. > > > Thanks Igor. Let us take a concrete example. > I'm convinced that having support for multitouch event/ genie and others > works (for iPad = $$$$) is important. > If you happen to know how we can get this code plug and play let me know > :) but I guess that you will not easily. > > But really read it! Really read it it is worth the 2 min you can people vs > the days giro and me are spending there (and this is not about just coding > but understanding the situation and building a better one). > Because we are far from doing stuff for research. We are not doing > research in interaction design! > > I could show you some of the compiler code too. > > > Stef > > > > HandMorph>>handleEvent: anEvent > | evt ofs | > owner ifNil:[^self]. > evt := anEvent. > self logEventStats: evt. > > evt isMouse ifTrue:[ > "just for record, to be used by capture block" > lastMouseEvent := evt]. > > captureBlock ifNotNil: [ ^ captureBlock value: anEvent ]. > evt isMouseOver ifTrue:[^self sendMouseEvent: evt]. > > self showDebugEvent: evt. > > "Notify listeners" > self sendListenEvent: evt to: self eventListeners. > > evt isWindowEvent ifTrue: [ > self sendEvent: evt focus: nil. > ^self mouseOverHandler processMouseOver: lastMouseEvent]. > > > evt isKeyboard ifTrue:[ > self sendListenEvent: evt to: self keyboardListeners. > self sendKeyboardEvent: evt. > ^self mouseOverHandler processMouseOver: lastMouseEvent]. > > evt isDropEvent ifTrue:[ > self sendEvent: evt focus: nil. > ^self mouseOverHandler processMouseOver: lastMouseEvent]. > > evt isMouse ifTrue:[ > self sendListenEvent: evt to: self mouseListeners. > lastMouseEvent := evt]. > > "Check for pending drag or double click operations." > mouseClickState ifNotNil:[ > (mouseClickState handleEvent: evt from: self) ifFalse:[ > "Possibly dispatched #click: or something and will > not re-establish otherwise" > ^self mouseOverHandler processMouseOver: > lastMouseEvent]]. > > evt isMove ifTrue:[ > self position: evt position. > self sendMouseEvent: evt. > ] ifFalse:[ > "Issue a synthetic move event if we're not at the position > of the event" > (evt position = self position) ifFalse:[self moveToEvent: > evt]. > "Drop submorphs on button events" > (self hasSubmorphs) > ifTrue:[self dropMorphs: evt] > ifFalse:[self sendMouseEvent: evt]. > ]. > self showMouseFocusEvent: evt. > self mouseOverHandler processMouseOver: lastMouseEvent. > > > HandMorph>>processEvents > "Process user input events from the local input devices." > > | evt evtBuf type hadAny | > ActiveEvent ifNotNil: > ["Meaning that we were invoked from within an event > response. > Make sure z-order is up to date" > > self mouseOverHandler processMouseOver: > lastMouseEvent]. > hadAny := false. > [(evtBuf := Sensor nextEvent) isNil] whileFalse: > [evt := nil. "for unknown event types" > type := evtBuf first. > type = EventTypeMouse ifTrue: [recentModifiers := > evtBuf sixth. evt := self generateMouseEvent: evtBuf]. > type = EventTypeKeyboard > ifTrue: [recentModifiers := evtBuf fifth. > evt := self generateKeyboardEvent: evtBuf]. > type = EventTypeDragDropFiles > ifTrue: [evt := self > generateDropFilesEvent: evtBuf]. > type = EventTypeWindow > ifTrue:[evt := self generateWindowEvent: > evtBuf]. > "All other events are ignored" > (type ~= EventTypeDragDropFiles and: [evt isNil]) > ifTrue: [^self]. > evt isNil > ifFalse: > ["Finally, handle it" > > self handleEvent: evt. > hadAny := true. > > "For better user feedback, return > immediately after a mouse event has been processed." > (evt isMouse and: [evt isMouseWheel > not]) ifTrue: [^self]]]. > "note: if we come here we didn't have any mouse events" > mouseClickState notNil > ifTrue: > ["No mouse events during this cycle. Make sure > click states time out accordingly" > > mouseClickState handleEvent: lastMouseEvent > asMouseMove from: self]. > hadAny > ifFalse: > ["No pending events. Make sure z-order is up to > date" > > self mouseOverHandler processMouseOver: > lastMouseEvent] > > > HandMorph>>generateMouseEvent: evtBuf > "Generate the appropriate mouse event for the given raw event > buffer" > > | position buttons modifiers type trail stamp oldButtons evtChanged > | > evtBuf first = lastEventBuffer first > ifTrue: > ["Workaround for Mac VM bug, *always* generating 3 > events on clicks" > > evtChanged := false. > 3 to: evtBuf size > do: [:i | (lastEventBuffer at: i) = (evtBuf > at: i) ifFalse: [evtChanged := true]]. > evtChanged ifFalse: [^nil]]. > stamp := evtBuf second. > stamp = 0 ifTrue: [stamp := Time millisecondClockValue]. > position := evtBuf third @ evtBuf fourth. > buttons := evtBuf fifth. > modifiers := evtBuf sixth. > type := buttons = 0 > ifTrue: > [lastEventBuffer fifth = 0 ifTrue: [#mouseMove] > ifFalse: [#mouseUp]] > ifFalse: > [lastEventBuffer fifth = 0 > ifTrue: [#mouseDown] > ifFalse: [#mouseMove]]. > buttons := buttons bitOr: (modifiers bitShift: 3). > oldButtons := lastEventBuffer fifth > bitOr: (lastEventBuffer sixth bitShift: 3). > lastEventBuffer := evtBuf. > type == #mouseMove > ifTrue: > [trail := self mouseTrailFrom: evtBuf. > ^MouseMoveEvent basicNew > setType: type > startPoint: (self position) > endPoint: trail last > trail: trail > buttons: buttons > hand: self > stamp: stamp]. > ^MouseButtonEvent basicNew > setType: type > position: position > which: (oldButtons bitXor: buttons) > buttons: buttons > hand: self > stamp: stamp >

Feb. 22, 2012

Re: [Pharo-project] Nautilus Refactorings

by Luc Fabresse

2012/2/21 Camillo Bruni <camillobruni(a)gmail.com> > > On 2012-02-21, at 21:19, StÃ©phane Ducasse wrote: > > > Ben > > > > I like the suggestion of mariano and luc. > > I discussed with them. > > > > - opening by default on packages is better because it does not > force you to display the full > > hierarchy. > => add preference setting > > > > > - could you try to see if you can just display the packages and > hierarchy without swapping them? > => add preference setting > yes perfect. and by default do not swap ;-) Luc > > > > Stef > >>> One last thing: when you type the name of a class somewhere and you do > a cmd+b I think it would be much better if Nautilus open the "normal" > browser and not "hierarchy" one. > >> > >> having cmd+h for hierarchy would be great :) > >> > >> +9999999 > >> > >> to open a hierarchy when you do cmd+b is bad for me beacuse: > >> > >> 1) 99% of the times I browse that way, I want to see that class, and > 99% also the rest of the classes of that package, not the hierarchy > >> 2) I am used to that since the last..mm 3 years ;) > >> 3) Because it seems the hierarchy windows is slow in big cases > [Object browse] timeToRun 19225 so it took me 20 seconds to open the > window ;) > >> > >> Because of that, I much prefer cmd + to for a normal browse. I don't > pretend all agree, so I would be very happy when you have the setting. > Please let me know so that I can set it :) > >> > >> Cheers! > >> > >> > >> > >> Ben we should produce a configuration because this is important. > >> What you can do is at least load the baseline and snapshot only when > you will release on version for 1.4 and 1.5 > >>> > >>> > >>> On Mon, Feb 20, 2012 at 8:38 PM, Benjamin < > benjamin.vanryseghem.pharo(a)gmail.com> wrote: > >>> To be honest, if it works, I do not want to lose my time on > Configuration > >>> > >>> > >>> It shouldn't be done by hand, but generated by a tool :) > >>> > >>> > >>> Ben > >>> > >>> On Feb 20, 2012, at 8:06 PM, Mariano Martinez Peck wrote: > >>> > >>>> > >>>> > >>>> On Tue, Feb 14, 2012 at 6:39 PM, Benjamin < > benjamin.vanryseghem.pharo(a)gmail.com> wrote: > >>>> Hello guys, > >>>> > >>>> I know a some of you are waiting for the integration of the RB engine > into Nautilus. > >>>> > >>>> Some of them are already implemented, so if you wanna test them, here > is the gofer script > >>>> > >>>> Gofer new > >>>> url: 'http://ss3.gemstone.com/ss/Nautilus'; > >>>> package: 'ConfigurationOfNautilus'; > >>>> load. > >>>> > >>>> (Smalltalk at: #ConfigurationOfNautilusRefactoring) perform: > #loadDefault > >>>> > >>>> > >>>> > >>>> > >>>> So...that's the way of loading Nautilus with refactorings? > Wouldn't it be better to include RB dependencis in ConfigurationOfNautilus > and have a specific group there. So you can do for example > >>>> > >>>> ConfigurationOfNautilus project stableVersion load: > 'WithRefactorings'. > >>>> > >>>> ? > >>>> > >>>> BTW, I checked the ConfigurationOfNautilusRefactoring and it looks > you miss a critical feature of Metacello: project references :) From > ConfigurationOfNautilusRefactoring you can directly depend on > ConfigurationOfRB or ConfigurationOfNautilus rather than duplicating > everything in there. Don't tell Stef you didn't read the chapter hahahaha > >>>> > >>>> > >>>> > >>>> It loads everything. > >>>> > >>>> For now I have only done some refactorings for classes, so if you > popup the menu on a class, a new item named Refactoring should appear :) > >>>> > >>>> Moreover, the 'rename class' method is replaced by the RB one :) > >>>> > >>>> > >>>> Thanks in advance for your feedback, and if you want to participate, > you are more than welcome :) > >>>> > >>>> > >>>> Ben > >>>> > >>>> > >>>> > >>>> -- > >>>> Mariano > >>>> http://marianopeck.wordpress.com > >>>> > >>> > >>> > >>> > >>> > >>> -- > >>> Mariano > >>> http://marianopeck.wordpress.com > >>> > >> > >> > >> > >> > >> > >> -- > >> Mariano > >> http://marianopeck.wordpress.com > >> > > > > > > >

Feb. 22, 2012

Re: [Pharo-project] Netstyle experience (was Do not feed the trolls)

by StÃ©phane Ducasse

> > People might mistakenly think that we wanna change things solely for > the sake of change. But it is not like that. > We need these changes , need to fix our infrastructure, because > without solid basement you cannot build anything good. > Thanks Igor. Let us take a concrete example. I'm convinced that having support for multitouch event/ genie and others works (for iPad = $$$$) is important. If you happen to know how we can get this code plug and play let me know :) but I guess that you will not easily. But really read it! Really read it it is worth the 2 min you can people vs the days giro and me are spending there (and this is not about just coding but understanding the situation and building a better one). Because we are far from doing stuff for research. We are not doing research in interaction design! I could show you some of the compiler code too. Stef HandMorph>>handleEvent: anEvent | evt ofs | owner ifNil:[^self]. evt := anEvent. self logEventStats: evt. evt isMouse ifTrue:[ "just for record, to be used by capture block" lastMouseEvent := evt]. captureBlock ifNotNil: [ ^ captureBlock value: anEvent ]. evt isMouseOver ifTrue:[^self sendMouseEvent: evt]. self showDebugEvent: evt. "Notify listeners" self sendListenEvent: evt to: self eventListeners. evt isWindowEvent ifTrue: [ self sendEvent: evt focus: nil. ^self mouseOverHandler processMouseOver: lastMouseEvent]. evt isKeyboard ifTrue:[ self sendListenEvent: evt to: self keyboardListeners. self sendKeyboardEvent: evt. ^self mouseOverHandler processMouseOver: lastMouseEvent]. evt isDropEvent ifTrue:[ self sendEvent: evt focus: nil. ^self mouseOverHandler processMouseOver: lastMouseEvent]. evt isMouse ifTrue:[ self sendListenEvent: evt to: self mouseListeners. lastMouseEvent := evt]. "Check for pending drag or double click operations." mouseClickState ifNotNil:[ (mouseClickState handleEvent: evt from: self) ifFalse:[ "Possibly dispatched #click: or something and will not re-establish otherwise" ^self mouseOverHandler processMouseOver: lastMouseEvent]]. evt isMove ifTrue:[ self position: evt position. self sendMouseEvent: evt. ] ifFalse:[ "Issue a synthetic move event if we're not at the position of the event" (evt position = self position) ifFalse:[self moveToEvent: evt]. "Drop submorphs on button events" (self hasSubmorphs) ifTrue:[self dropMorphs: evt] ifFalse:[self sendMouseEvent: evt]. ]. self showMouseFocusEvent: evt. self mouseOverHandler processMouseOver: lastMouseEvent. HandMorph>>processEvents "Process user input events from the local input devices." | evt evtBuf type hadAny | ActiveEvent ifNotNil: ["Meaning that we were invoked from within an event response. Make sure z-order is up to date" self mouseOverHandler processMouseOver: lastMouseEvent]. hadAny := false. [(evtBuf := Sensor nextEvent) isNil] whileFalse: [evt := nil. "for unknown event types" type := evtBuf first. type = EventTypeMouse ifTrue: [recentModifiers := evtBuf sixth. evt := self generateMouseEvent: evtBuf]. type = EventTypeKeyboard ifTrue: [recentModifiers := evtBuf fifth. evt := self generateKeyboardEvent: evtBuf]. type = EventTypeDragDropFiles ifTrue: [evt := self generateDropFilesEvent: evtBuf]. type = EventTypeWindow ifTrue:[evt := self generateWindowEvent: evtBuf]. "All other events are ignored" (type ~= EventTypeDragDropFiles and: [evt isNil]) ifTrue: [^self]. evt isNil ifFalse: ["Finally, handle it" self handleEvent: evt. hadAny := true. "For better user feedback, return immediately after a mouse event has been processed." (evt isMouse and: [evt isMouseWheel not]) ifTrue: [^self]]]. "note: if we come here we didn't have any mouse events" mouseClickState notNil ifTrue: ["No mouse events during this cycle. Make sure click states time out accordingly" mouseClickState handleEvent: lastMouseEvent asMouseMove from: self]. hadAny ifFalse: ["No pending events. Make sure z-order is up to date" self mouseOverHandler processMouseOver: lastMouseEvent] HandMorph>>generateMouseEvent: evtBuf "Generate the appropriate mouse event for the given raw event buffer" | position buttons modifiers type trail stamp oldButtons evtChanged | evtBuf first = lastEventBuffer first ifTrue: ["Workaround for Mac VM bug, *always* generating 3 events on clicks" evtChanged := false. 3 to: evtBuf size do: [:i | (lastEventBuffer at: i) = (evtBuf at: i) ifFalse: [evtChanged := true]]. evtChanged ifFalse: [^nil]]. stamp := evtBuf second. stamp = 0 ifTrue: [stamp := Time millisecondClockValue]. position := evtBuf third @ evtBuf fourth. buttons := evtBuf fifth. modifiers := evtBuf sixth. type := buttons = 0 ifTrue: [lastEventBuffer fifth = 0 ifTrue: [#mouseMove] ifFalse: [#mouseUp]] ifFalse: [lastEventBuffer fifth = 0 ifTrue: [#mouseDown] ifFalse: [#mouseMove]]. buttons := buttons bitOr: (modifiers bitShift: 3). oldButtons := lastEventBuffer fifth bitOr: (lastEventBuffer sixth bitShift: 3). lastEventBuffer := evtBuf. type == #mouseMove ifTrue: [trail := self mouseTrailFrom: evtBuf. ^MouseMoveEvent basicNew setType: type startPoint: (self position) endPoint: trail last trail: trail buttons: buttons hand: self stamp: stamp]. ^MouseButtonEvent basicNew setType: type position: position which: (oldButtons bitXor: buttons) buttons: buttons hand: self stamp: stamp

Feb. 22, 2012

Re: [Pharo-project] Pharo VM

by StÃ©phane Ducasse

>> > Here some news: > We finally got windows slave up and running. So, now we can build Vms > for all 3 platforms and test them. Excellent news to me > > Now there are 2 things left before releasing updated VMs: > - test why windows VM crashing randomly - test why dave mason got mac vm crashing that much. > - create an job for building 1-click package. > > P.S. An automatic builds often detecting various discrepancies here > and there, since it doing everything from scratch every time, > which you usually don't do if run things manually. > Which is good, because it helps us to ensure that things we do are > reproducable, but it means having more work :) > > > > -- > Best regards, > Igor Stasenko. >

Feb. 22, 2012

Re: [Pharo-project] Proposal: coverage tests

by Guido Stepken

Well done, a real *masterpieche*! :-) Depreciated (marked as depreciated) classes could / should be moved either into a compatibility layer (sport) or, if only a few "apps" are using it, into the app itself, being slightly renamed for keeping up compatibility. This should work in a similar way by first identifying concerned apps, automatically moving - while renaming classes - into the app, exporting as new package. Does that make sense? How would u solve that? tnx in advance, Guido Stepken Am 21.02.2012 16:03 schrieb "Pavel Krivanek" <pavel.krivanek(a)gmail.com>: > Hi, > > what about to intrroduce tests that will test coverage of tests? Some > improved version of the code below. Are there some tool for Smalltalk > showing uncovered lines of code? There are such tools in Java world > :-) One little problem is that this code do not work on Linux because > of a VM error that cause test failures on CI server too. > > Cheers, > Pavel > > | class test trace classTrace result | > > class := Time. > test := TimeTest. > > trace := Dictionary new. > > thisContext runSimulated: [test suite run] contextAtEachStep: [ :current | > | cls sel methods bytecodes | > cls := current method methodClass. > sel := current method selector. > methods := trace at: cls ifAbsentPut: Dictionary new. > bytecodes := methods at: sel ifAbsentPut: Set new. > bytecodes add: current pc.] > > trace . > > result := String streamContents: [:s | > > classTrace := trace at: class ifAbsent: nil. > classTrace > ifNil: [ > s nextPutAll: 'Class ', class name, ' not called'; cr. ] > ifNotNil: [ > s nextPutAll: class name; cr. > class selectorsDo: [:sel | > | m usedBytecodes allBytecodes | > m := class >> sel. > usedBytecodes := (classTrace at: sel ifAbsent: Set > new) size. > allBytecodes := 0. > m symbolicLinesDo: [:pc :lineForPC | allBytecodes > := allBytecodes + 1 ].. > s tab; nextPutAll: sel; nextPutAll: ' - '; > nextPutAll: > (usedBytecodes / allBytecodes * 100) asFloat asString; nextPutAll: > '%'; cr. ]]. > ]. > result.. > >

Feb. 22, 2012

Re: [Pharo-project] Why do we use Pharo? a.k.a. rethinking Pharo marketing

by StÃ©phane Ducasse

On Feb 21, 2012, at 10:56 AM, Nick Ager wrote: > Pharo (or Smalltalk in general) is for me about *speed* of development. > > I agree 100% with GÃ¶ran. > > I want my programming environment to be able to translate my ideas into code as rapidly as possible. Smalltalk is the best environment I've found for that. > > "Programming at the speed of thought" I love that. Thanks for the idea. > I've been very inspired by the following talk about the importance of the immediacy of results: > > http://vimeo.com/36579366 > > > > > >

Feb. 22, 2012

Re: [Pharo-project] gl/cl interop

by Javier PimÃ¡s

Hi, I've been working on NB/OpenGL to make it work on linux. I already have a sample working on my machine that will upload this week. As for the alien vs ffi vs NB ffi. NB FFI is very flexible, as it implements 99% on the image side, and only depends on a single primitive from the VM side, which makes it easier to understand, modify and maintain. That doesn't mean it's perfect but it's really really good, and each day there's more work on it, adding functionality, documentation and examples. If you plan to make a wrapper, I'd strongly recommend you to use NB. There are plans to have some kind of compatibility with other FFIs in the future for cases were NB can't be used. Cheers, Javier On Tue, Feb 21, 2012 at 11:58 PM, chadwick <mathnoir(a)gmail.com> wrote: > Hi, I'm new to Pharo & interested in doing some OpenCL + OpenGL for > visualization. Looking around I'm confused by the differences between the > various OpenGL libs and Alien vs FFI vs NativeBoost. Years ago I did some > OpenGL-based GPGPU work in Squeak (OpenCobalt), but that's all out of date > I think. For interop I need to get hold of the current gl context (e.g.glxGetCurrentContext), > but according to other threads here that's not so easy in Squeak or Pharo. > I tried NativeBoost but it didn't have a Linux implementation. What's the > best way to proceed ? > -- Lic. Javier PimÃ¡s Ciudad de Buenos Aires

Feb. 22, 2012