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

[Pharo-project] is there a way to avoid all the #tryNamedPrimitive:with: * in ProtoObject
by Mariano Martinez Peck Jan. 24, 2012

Jan. 24, 2012

Hi guys. I usually like to take a look to ProtoObject and see what is really needed for the minimal object. But having 30% of the methods being #tryNamedPrimitive:with: * is not fun. So...I wonder, do you think there could be another way so that to avoid having all those methods in ProtoObject ? Thanks -- Mariano http://marianopeck.wordpress.com

3 7

Re: [Pharo-project] Fwd: [squeak-dev] ANN: OpenGL + NativeBoost + Mac ==> success
by Lawson English Jan. 24, 2012

Jan. 24, 2012

Kool. So how could I make the entire World a drawing surface so that I could use the OpenGL drawing throughout the entire squeak/pharo OS window, instead of within another window? Could a 2D/3D mashup like I have in this video be accomplished? The fps is too slow to be useable for most things, at this point: http://www.youtube.com/watch?v=nSLZKIXeXR4 On 1/23/12 3:00 PM, Hans-Martin Mosner wrote: > Am 23.01.2012 18:03, schrieb Lawson English: >> Is there a way to directly draw to the system window using OpenGL so that intermediate software blitting is eliminated? >> > The opengl context is already drawing directly to the screen (or rather, to the back buffer managed by opengl). > There is no intermediate software blitting involved AFAIK. > > Cheers, > Hans-Martin > >

1 0

[Pharo-project] System Update auto Merge
by Camillo Bruni Jan. 23, 2012

Jan. 23, 2012

Hi everyone, I wonder if it would make sense if System Update would perform auto merging? I think if there are no merge conflicts you should not get any notifications from System Update. In any case I will program an Option for this in the Setting Browser. best cami

2 2

[Pharo-project] Live Ruby on rails tutorial sites
by Lawson English Jan. 23, 2012

Jan. 23, 2012

This is the kind of thing that seaside needs to have to attract more people. http://railsforzombies.org/ Lawson

1 0

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

Jan. 23, 2012

---------- Forwarded message ---------- From: Igor Stasenko <siguctua(a)gmail.com> Date: 23 January 2012 01:26 Subject: Re: [squeak-dev] ANN: OpenGL + NativeBoost + Mac ==> success To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> On 22 January 2012 15:13, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Jan 22, 2012, at 1:29 PM, Lawson English wrote: > >> On 1/22/12 3:07 AM, StÃ©phane Ducasse wrote: >>> did you notice that you can save the image in the middle of the animation and it will continue on restart :) >> >> >> I didn't notice that. However, a there were several things I did notice: >> >> 1) you could have more than one GL Morph open at once. However, if you resized one Â GL morph window, the drawing area of the other would resize. > > Indeed :) > yeah. it looks like i don't switching current GL context when resizing, which affects currently active context. >> 2) large windows tended to leave a lot of artifacts behind during movement (the video shows this towards the end). there is two "modes" to blit on Morphic display - one is just copy directly to Display, and another is to separate form and then draw that form as usual. so, these artefact is not related to OpenGL per se, but mainly to how you make rendered results appear integrated in morphic. >> 3) creating more than one window would sometimes evoke the debugger. Proceeding eventually would create GL morph windows but they might or might not have valid contents. >> 4) saving occasionally caused errors, but the save continued anyway and restarting the image didn't show any problems. >> everything is in your hands :) >> I see an awful lot of potential for OpenGL on Squeak/Pharo. >> >> Of course, being involved iwth SiliconSqueak, I hope that we can transcend all current technologies and eventually create something truly different and better. >> >> Lawson >> -- Best regards, Igor Stasenko. -- Best regards, Igor Stasenko.

2 1

[Pharo-project] Ann: OmniBrowser stable for 1.4 with RB
by Guillermo Polito Jan. 23, 2012

Jan. 23, 2012

I've updated the configuration of OmniBrowser so It can load with the last version of RB. (ConfigurationOfOmniBrowser project version: #stable) load: #( 'Dev' 'Dev Tests'). BTW, I've fixed a deprecation on RB (#withBlanksTrimmed -> #trimBoth) and posted it into PharoTaskForces, since I don't have grants to write into PharoRB. All tests are green and It's working fine :). This version is freezed for anyone who wants to use it. I'll be working to update OB to Lukas's latest chanes from now on. Bye! Guille

7 26

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

Jan. 23, 2012

On Mon, Jan 23, 2012 at 11:21 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Jan 23, 2012, at 1:18 AM, Fernando Olivero wrote: > >> 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. > > Now more time to answer. > Indeed HandMorph looks to me like having too many responsibility > Â Â Â Â - transform low level event into high level > Â Â Â Â - manage the Morphic interaction loops > Â Â Â Â - looks like a cursor > YES! this design favors the sharing of the above responsibilities between the user interface and its peripherals. > >> The GUserInterface listens to VM events, and process them as they arrive. >> >> GUserInterface>>process: aSensorEvent dispatches to either the mouse >> or the keyboard. > > Â Â Â Â in what we are putting in place we use double dispatch because > Â Â Â Â we want to be able to plug new event > >> 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. > > > interesting. Indeed it looks to me that using a state pattern should be a nice way to > handle the Morphic logic > > Now I do not understand the arrows to the big Mouse. > When a MouseState reacts to a given event, such the MouseDragging reacting to #up: aDisplayPoint, it sends messages to the Mouse, such as #drop:at:, #clicked:at:, #secondaryclicked:at:. > I like the idea that you dispatch to the peripherals now what we encounter > with igor is that handMorph need to keep the previous system event and modifiers > so is the distribution to Mouse, Keyboard supporting that? yes, the last mouse event needs to be stored, to be able to decode wether the sensor input event is a mouse up or a mouse down . But this is stored by the Mouse.SURELY, we should improve how the VM encodes the OS Event, this shouldn't be needed! . The keyboard doesn't need such mechanism. > Fernando if you have a look at EventModel > we are asking ourselves the following questions: > Â Â Â Â - HostMenu management looks not the way we want (right now it hijacks low level event and produce event to simulate) > Â Â Â Â we are thinking that the HandMorph (or User Interface in your case should be responsible for deciding to publish menu > Â Â Â Â as host menu and host menu should be able to call the same code than default menu. > > Â Â Â Â - We want to look at the API of InputEventSensor (using event but) Â and SystemInputEventAnnouncer (using events!) > Â Â Â Â and check the various users and fix them because we do not want the system to rely on InputEventSensor and its eventBuf > I've looked at the EventModel, quite nice design. I will adapt the design proposed above to it, the only difference is that GUserInterface , GMouse and GKeyboard will process a SystemInputEvent instead of a raw event buffer encoded in an Array. Which will ease and standardize the dispatching amongst the peripherals.

2 1

Re: [Pharo-project] experiment with UbiquiTalk
by Noury Bouraqadi Jan. 23, 2012

Jan. 23, 2012

Hi Estaban, On 20 janv. 2012, at 19:20, Esteban Lorenzano wrote: > Hi Noury, > > I have some free time (not much) before moving to Lille, and I wanted to experiment a bit with UbiquiTalk... > Cool. > I installed all in a Pharo 1.3 image, but now I don't know where to start... As I see, there is an example there, but I don't know how it is supposed to work... > Can you guide me on where to look? > There's some documentation available is online. It's old, though I believe it should be okay. http://vst.mines-douai.fr/UbiquiTalk In squeak, there were a GUI that was working. The main entry point for it is: UTHostMainGUI. Otherwise, from the model side, the main entry point is UTHost that refers to the current image. It holds multiple services. Each service has server-side and client-side code. Once a client connects to a server (discovery based on IGMP), it gets the list of services. A client can launch a service and get the client-side code of it installed on the fly. The last one who experimented with UbiquiTalk was Sean. He could load it on Pharo, though I don't remember how far he went. Hope it helps, Noury -- http://twitter.com/#!/NouryBouraqadi http://www.kroobe.com/profile/noury Afin de contribuer au respect de l'environnement, merci de n'imprimer ce courriel qu'en cas de necessite Please consider the environment before you print

1 0

[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