- Pharo-dev - lists.pharo.org

[Pharo-project] Redesign of Mouse/Touch/Gestures/Keyboard events neccessary?
by Guido Stepken Jan. 23, 2012

Jan. 23, 2012

Hi! When i look at Apple Hardware Shop i find "Magic Mouse". This cheap mouse has a "surface", hat works like a touch screen, accepts multitouch, 2,3 finger gestures, pressure sensor (over widening fingercontactformsize, like ipad does) scrollwheel emulation, even replaces special 3D input devices, used for CAD. In about one year from now there won't be any classic keyboard/mouse/screen hardware and software available, all OS for desktop will have complex finger/gesture/approach/video sensors tightly integrated into the os. My OS even puts a window in front, when i look at it, i don't even need to move my mouse over or even klick into that hidden window. Furthermore, new OS have received a "multiuseronedesktop" function, where a second, third and forth person might have their own input devices assigned, e.g. several programmers typing in one text window (simultaneous pair programming, no need to handover keyboard) or typing from above, e.g. on Microsofts new touch table, produced by Samsung. 4 Users sitting in front of a table, typing on touch or virtually assigned Bluetooth keyboard, turning windows to show each other. In a few years this will be standard even in schools, at work, in restaurants, people sitting, eating, playing chess or multiuser pong. As i could read, the Pharo chief designers have even removed the turn window angle functionality, that was implemented in squeak, WHY THAT??? Instead i would like to have virtually assigned touch keyboards to turnable windows. New touch tables go up to recognize 60 fingers at the same time. Approach sensors, gyro, video : My mobile has built in such thing. Pretty nice, my phone "sees itself approaching my ear", unlocking the microphone and speaker on incoming phone call. Thats built in in Android 4.0. Approach sensors trigger videoinput to recognize gestures or - like in newer HP and Lenovo notebooks activate powerdown state, when user leaves and reactivates, when user comes back. It can differ between "user reading" and "user absent". Thats already built in, becomes standard soon in all notebooks with windows 8. So far my report of "state of the art of software programming". feel inspired, Guido Stepken

1 0

[Pharo-project] Rethinking the event's handling in Gaucho/Morphic
by Fernando Olivero Jan. 23, 2012

Jan. 23, 2012

Hi, in the context of the new UI framework i'm developing for Gaucho, i've decided to design the event handling part as follows: The entry point to the framework is an instance of aGUserInterface , which collaborates with a set of peripherals: in the standard case it holds a: 1)aGDisplay 2) aGMouse and 3) aGKeyboard. The GUserInterface listens to VM events, and process them as they arrive. GUserInterface>>process: aSensorEvent dispatches to either the mouse or the keyboard. GKeyboard>>process: distinguishes between keyDown, keyUp, and keystrokes, and reacts accordingly. GMouse>>process: finds the proper reaction depending on the context of the mouse. The keyboard handling logic is quite simple. The mouse is significantly more complicated, because the mouse events produce a different action depending on the current "mode" of the mouse. I modeled this problem, using the State pattern, depicted by the attached FSM. For example: if a #up: 10@10 arrives, and the mouse is on "dragging mode", would result in the evaluation of the message GMouse>>dropped: aGShape at: aDisplayPoint. The usage of the state pattern, simplifies the coding of the reaction to each of the mouse events (#up:, #move:, #down:,#secondaryDown:), according to the mouse's context. And provides a hook for altering/augmenting the behavior as well. There's no need to reify the events in the design, events are generated by the user, encoded by the VM, decoded by the GUserInterface and dispatched to the proper peripheral device. Other Peripheral devices can be easily be attached, for now i'm sticking to the standard display, keyboard and three button mouse. Changes to the VM may still be needed to encode the User actions of the external device, but in the image would be straightforward to "plug and unplug" devices. I'm interested in hearing your opinions or remarks on the design, or if i've omitted a state or transition from the FSM. Thanks in advance, Fernando pd: An intersesting side effect is that i can test low level mouse actions, such as drag and drop, hovering and unhovering, etc.., resulting in a more robust framework. pd: Soon i will release the framework, still working on make it render with Athens.

2 2

[Pharo-project] [ANN] Spotlight like morph for pharo
by Esteban Lorenzano Jan. 23, 2012

Jan. 23, 2012

Hi, I want to announce a little tool I made the other day (mainly because Mariano asked for it :) Do you remember algernon, that tool who was working in pharo 1.1 and is now obsolete? I used it all the time, and I always missed the ability to open browsers without having to type the class name in a workspace, or open a browser first, then look for the class. So, I created this: Gofer it squeaksource: 'Spotlight'; package: 'ConfigurationOfSpotlight'; load. ConfigurationOfSpotlight loadBleedingEdge. if you press shift+enter, you'll get a "spotlight" like morph, with a simple text input with OCompletion inside... is very simple and I think very useful. Of course it can be enhanced in a lot of ways... but let's here the community opinion first, and see if it worths to keep adding functionality.functionality. enjoy, Esteban ps: this is also an example of why I hate morphic so much (bah... current dirty implementation): I had to extend two classes just to change the editor used by a textmorph.... come on!!!!

2 1

[Pharo-project] Latest changes in FS
by Francois Stephany Jan. 22, 2012

Jan. 22, 2012

Hi Camillo, Thanks for the updates on FS :) It seems that you did not based FS-Core from Sean's latest version which introduce 'moveTo:'. Is there a reason ? To be honest, I'm a bit lost between the different versions of FS. Thanks ! Francois

3 3

[Pharo-project] [update 1.4] #14294
by StÃ©phane Ducasse Jan. 22, 2012

Jan. 22, 2012

14294 ----- - Issue 5168: TaskList switching raises exception. First Two. http://code.google.com/p/pharo/issues/detail?id=5168

1 0

[Pharo-project] [update 1.4] #14293
by StÃ©phane Ducasse Jan. 22, 2012

Jan. 22, 2012

14293 ----- - Issue 5168: TaskList switching raises exception. First part. http://code.google.com/p/pharo/issues/detail?id=5168 - Issue 1380: Method for block not found on stack in Debugger. Thanks Camillo Bruni. http://code.google.com/p/pharo/issues/detail?id=1380 - Issue 5199: All the methods in convenience-inspecting in ToolRegistry should be deprecated. Igor drinking tea and discussing on solution :). http://code.google.com/p/pharo/issues/detail?id=5199 Stef

1 0

[Pharo-project] [update 1.4] #14292
by StÃ©phane Ducasse Jan. 22, 2012

Jan. 22, 2012

14292 ----- - Issue 5141: We should remove InputEventPollingFetcher. InputEventSensor installEventSensorFramework Stef

1 0

Jan. 22, 2012

Some post fixes and revert :) Stef 14291 ----- - Issue 5183: Problem with PluggableListMorph. Thanks Benjamin van Ryseghem. Thanks for the fix benjamin. - Issue 5133: Editor >> cursorEnd: and cursorHome: does not work properly. Reverted the code because it was not ok.

1 0

Jan. 22, 2012

On Jan 22, 2012, at 11:04 AM, stephane ducasse wrote: On Jan 22, 2012, at 4:23 AM, Lawson English wrote: > I created a new video how to for installing NativeBoost OpenGL on Pharo 1.4 Smalltalk on the Mac: http://www.youtube.com/watch?v=RAvlIVG4biM > > Igor, your code is very nice. I think there's a lot of potential here for NativeBoost and OpenGL that might attract new classes of programmers to smalltalk. This is our goal. We want the complete environment to be zoomable and much more. We want a next generation of Smalltalk systems. > I'd be happy to help create demos and videos of what can be done. Thanks it will definitively help. I'm working on a document that really will give the keys to understand what we are doing. Soon available :) > > Lawson

1 0

[Pharo-project] ANN: OpenGL + NativeBoost + Mac ==> success
by Igor Stasenko Jan. 22, 2012

Jan. 22, 2012

Today i'm happy to announce that i can run my 2 years-old demo which i did when created NBOpenGL bindings first on Windows, working without ANY changes in code on Mac. The main hurdle with adding MacOsx support was that it is largely unknown platform to me , and there are 3 different ways to get there, namely CGL, Carbon and Cocoa. Fortunately CGL approach worked well, despite its a bit limited (you cannot create a windowed context, only fullscreen or offscreen one). But since i am using FBO's , it doesn't really matters. Of course it may make difference for people who want to use GL in different setup. In order to load project, take a fresh Pharo 1.4 image, load ConfigurationOfNBOpenGL package using MC from MCHttpRepository location: 'http://www.squeaksource.com/NBOpenGL' user: 'sig' password: '' or by Gofer it squeaksource: 'NBOpenGL'; package: 'ConfigurationOfNBOpenGL'; load and then issue: ConfigurationOfNBOpenGL project lastVersion load. Remember, that you have to use CogVM with NativeBoost plugin, which you can download from here: https://ci.lille.inria.fr/pharo/view/NativeBoost/job/NB-Cog-Mac-Carbon/last… If everything goes well, you should be able to run a demo by doing: GLTTRenderingDemo new openInWorld. P.S. @ Windows users: due to refactorings which i did, a windows-specific support code is currently broken. So please use older versions of packages (prior to this month). I will fix them very soon. -- Best regards, Igor Stasenko.

4 8