March 2014 - Pharo-dev - lists.pharo.org

[ANN] RenoirSt 1.0.0 Release for Pharo 3.0

by Gabriel Cotelli

Hi, I'm announcing the first official release of RenoirSt, a DSL enabling programmatic cascading style sheet generation for Pharo. For the impatient, you can load it in your 3.0 image evaluating: Gofer it url: 'http://smalltalkhub.com/mc/gcotelli/RenoirSt/main'; configurationOf: 'RenoirSt'; loadStable or download a ready to use image from the Contribution CI Server<https://ci.inria.fr/pharo-contribution/job/RenoirSt/> ( a ConfigurationBrowser option comming soon). Visit the project page <http://gcotelli.github.io/RenoirSt/> and GitHub repository <https://github.com/gcotelli/RenoirSt> for more information on the supported and planned features, and check-out the online tutorial.<https://github.com/gcotelli/RenoirSt/blob/stable/docs/tutorial/Tutorial%20-…> I hope you find it useful. Feel free to ask any questions, suggest ideas and improvements, or report bugs (the issue tracker is in GitHub). Gabriel

March 11, 2014

Re: [Pharo-dev] Touch Events VM changes

by Sergi Reyner

2014-03-11 11:54 GMT+00:00 J.F. Rick <self(a)je77.com>: > Hi Sergi, > > Based on my experience developing touch interfaces since 2007, I believe > in touch. > DonÂ´t get me wrong, I like touch and non-traditional interfaces in general. In fact there are five android devices at home, counting phones and tablets. I also experimented with voice and webcam control for my home theatre. I just think that they are optimal for some scenarios and not-so-optimal for others, and that it wouldnÂ´t be an improvement to make all devices touch-only. As you yourself point out: > You just have to take advantage of what touch does well (faster, more > precise routes; multi-touch gestures; bimanual interaction) and stay clear > of things it does poorly (precise touch down, covering the target with the > finger). > Both have their strengths and weaknesses. Mice have multiple buttons (I use the wheel and the back/forward buttons a lot, both for those functions and as configurable controls in certain games) and are easily identifiable as distinct input devices, while touch interfaces allow more direct (not necessarily precise) control over the actions, taking things like pointer acceleration out of the equation. Almost everyone can draw a lowercase 'g' on a touch screen, but doing it with a mouse takes some skill (well, and a decent mouse). As a more concrete use case, trying to craft some pixel art in a touch device can quickly become tedious. I certainly wouldnÂ´t mind at all having one or two tactile screens in my desk. That said, I once had an interesting conversation with a costumer, in which she told me that she couldnÂ´t play World of Warcraft with her tactile screen because random passing-by insects kept pressing her skills/spells buttons at the worst times :) Cheers, Sergi

March 11, 2014

Re: [Pharo-dev] Touch Events VM changes

by Igor Stasenko

Jeff, since you running linux you can look at what we have done with Ronie not long ago. Basically we changed VM and removed all window/event management code and instead do everything at image side. I think it would be good if you can try and add multi-touch events support to the code. If you wanna try, you need to build new VM first, and follow this: https://pharo.fogbugz.com/f/cases/12743/OSWindow-integration Then you can look at OSWindow package (its X11 part) and see what is needed to support multi-touch events. You should build VM from sources taken from here: https://github.com/ronsaldo/pharo-vm On 11 March 2014 11:37, J.F. Rick <self(a)je77.com> wrote: > As we move from mouse-keyboard devices to touch-based ones, it would be > nice if we could unify touch development across the different Pharo > platforms (iOS, Android, Windows 8, Linux, etc.), so that we can start to > build touch-aware widgets and frameworks. Currently, there's a lot of > interest but no unified movement. For instance, I've got a very nice > multi-touch 27" computer that I run in Linux. I develop the applications in > Pharo but I currently use a hack to get the touch events: I use OSProcess > to start the mtdev2tuio application that takes touch input and sends it via > TUIO. I then use a UDP socket to read the events on Pharo. If I am to share > my work, I need to get beyond the hack. I (or rather Igor as I watched) > investigated the possibility of using NativeBoost calls to do the same, but > it would not work since mtdev2tuio has to run as superuser, meaning Pharo > would have to run as superuser. We came to the conclusion that this must be > a VM-level change. > > I'm not a VM hacker but would like to reach the people who maintain the > linux and windows VM to see if this might not be a reasonable addition to > the standard VM. There does seem to be standard support for touch events in > XFree86, so it shouldn't be too large a change on Linux. I assume that > Windows 8 similarly makes touch events available. Is this the right place > to ask or is there another mailing list (e.g., the cog-vm)? > > Cheers, > > Jeff > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick > -- Best regards, Igor Stasenko.

March 11, 2014

Re: [Pharo-dev] [Pharo-users] Tiling Window Manager in 3.0: working but still issues with WorldMorph

by Laurent Laffont

Thanks a lot Phil. I will try to have a look. Laurent Le samedi 8 mars 2014, 11:57:30 phil(a)highoctane.be a Ã©crit : > TWM works in 3.0 after some work on icons and updating menus. > > Gofer new > smalltalkhubUser: 'LaurentLaffont' project: 'TilingWindowManager'; > configuration; > load. > > ((Smalltalk at:#ConfigurationOfTilingWindowManager) project version: '3.0') > load > > You can also use > > ((Smalltalk at:#ConfigurationOfTilingWindowManager) project version: > #development) load > > but this will for sure change over time. > > There is the World management icon which is still there and it looks like > it can create worlds but switching between them just breaks havoc. > > Maybe should we just remove that feature from TWM as 3.0 doesn't seem to be > multiworld friendly. > > Nothing done on tests nor themeing (which appears to be not that working > well in 3.0 either due to theming changes); > > At least the thing is back :-) [I missed it...] > > Phil

March 11, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30793 Home: https://github.com/pharo-project/pharo-core

March 11, 2014

[pharo-project/pharo-core] 8418a3: 30793

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 8418a3fb5bba1056099d38b5e6759db327437dea https://github.com/pharo-project/pharo-core/commit/8418a3fb5bba1056099d38b5… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-03-11 (Tue, 11 Mar 2014) Changed paths: M Kernel.package/ContextPart.class/instance/controlling/runUntilErrorOrReturnFrom_.st A OpalCompiler-Core.package/OCASTTranslatorForEffect.class/instance/visitor-double dispatching/visitLiteralArrayNode_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script446.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30793.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Spec-Debugger.package/SpecDebugger.class/instance/updating/updateContextInspectorFromContext_.st M Spec-Debugger.package/SpecDebugger.class/instance/updating/updateInspectorsFromContext_.st A Spec-Debugger.package/SpecDebugger.class/instance/updating/updateReceiverInspectorFromContext_.st Log Message: ----------- 30793 5041 ContextPart>>#runUntilErrorOrReturnFrom: https://pharo.fogbugz.com/f/cases/5041 12722 #ifNil:#ifNotNil: must return a value? https://pharo.fogbugz.com/f/cases/12722 12699 Debugger clears selection on update https://pharo.fogbugz.com/f/cases/12699 http://files.pharo.org/image/30/30793.zip

March 11, 2014

Re: [Pharo-dev] Touch Events VM changes

by J.F. Rick

Hi Sergi, Based on my experience developing touch interfaces since 2007, I believe in touch. I believe it will be the future of interfaces and I believe it can be better than mouse-keyboard interfaces. That said, it is not there yet. Now is the time to innovate and get it there so that touch interfaces won't be poor replicas of their desktop forebears. Currently, text entry is a real problem for touch exclusive devices, but there is progress being made on that front. We don't have the answer yet but I think it will be a significantly different landscape in five years. In regards to touch vs physical pointers, this is not as large of a problem as people make it out to be. It is just that our widgets tend to be created for mouse-based interfaces and therefore don't transition well to touch. Interfaces designed with touch in mind can be just as smooth (if not smoother) as mouse-based interfaces. You just have to take advantage of what touch does well (faster, more precise routes; multi-touch gestures; bimanual interaction) and stay clear of things it does poorly (precise touch down, covering the target with the finger). Cheers, Jeff On Tue, Mar 11, 2014 at 12:34 PM, Sergi Reyner <sergi.reyner(a)gmail.com>wrote: > 2014-03-11 10:37 GMT+00:00 J.F. Rick <self(a)je77.com>: > > As we move from mouse-keyboard devices to touch-based ones > > > I certainly hope that "we" refers to a small group of people, unless we > get onscreen keyboards as good as physical ones, feedback included. The > same goes for touch versus physical pointer :) > > Cheers, > Sergi > -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

March 11, 2014

Access to MetaRepoForPharo30

by Gabriel Cotelli

Hi guys, can you add me as a contributor to the MetaRepoForPharo30 project? My sthub user is gcotelli Gabriel

March 11, 2014

Re: [Pharo-dev] Touch Events VM changes

by J.F. Rick

Definitely agreed on the strategy of processing the raw events on the image side as that will be much more flexible. But, we still need the VM to send the raw events. I'll check on the vm-dev list. I think I'm already subscribed to it. Cheers, Jeff On Tue, Mar 11, 2014 at 12:03 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > Hi, > > I agree that we need a unified event model. Now... our vision is to solve > that in image side, not in vm (and vm should send the raw events "as is"). > The reason of why we want it in image is easy: image means pharo, and it > means more hands (or eyes) over it. Then is easier to maintain :) > Anyway, we are slowly working on it (See Igor & Ronnie work around > OSWindow). But is probably too slow :) > > Esteban > > On 11 Mar 2014, at 11:37, J.F. Rick <self(a)je77.com> wrote: > > As we move from mouse-keyboard devices to touch-based ones, it would be > nice if we could unify touch development across the different Pharo > platforms (iOS, Android, Windows 8, Linux, etc.), so that we can start to > build touch-aware widgets and frameworks. Currently, there's a lot of > interest but no unified movement. For instance, I've got a very nice > multi-touch 27" computer that I run in Linux. I develop the applications in > Pharo but I currently use a hack to get the touch events: I use OSProcess > to start the mtdev2tuio application that takes touch input and sends it via > TUIO. I then use a UDP socket to read the events on Pharo. If I am to share > my work, I need to get beyond the hack. I (or rather Igor as I watched) > investigated the possibility of using NativeBoost calls to do the same, but > it would not work since mtdev2tuio has to run as superuser, meaning Pharo > would have to run as superuser. We came to the conclusion that this must be > a VM-level change. > > I'm not a VM hacker but would like to reach the people who maintain the > linux and windows VM to see if this might not be a reasonable addition to > the standard VM. There does seem to be standard support for touch events in > XFree86, so it shouldn't be too large a change on Linux. I assume that > Windows 8 similarly makes touch events available. Is this the right place > to ask or is there another mailing list (e.g., the cog-vm)? > > Cheers, > > Jeff > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick > > > -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

March 11, 2014

Re: [Pharo-dev] Touch Events VM changes

by ClÃ©ment Bera

Hello, the right place is vm-dev. I put it in CC. Regards, 2014-03-11 11:37 GMT+01:00 J.F. Rick <self(a)je77.com>: > As we move from mouse-keyboard devices to touch-based ones, it would be > nice if we could unify touch development across the different Pharo > platforms (iOS, Android, Windows 8, Linux, etc.), so that we can start to > build touch-aware widgets and frameworks. Currently, there's a lot of > interest but no unified movement. For instance, I've got a very nice > multi-touch 27" computer that I run in Linux. I develop the applications in > Pharo but I currently use a hack to get the touch events: I use OSProcess > to start the mtdev2tuio application that takes touch input and sends it via > TUIO. I then use a UDP socket to read the events on Pharo. If I am to share > my work, I need to get beyond the hack. I (or rather Igor as I watched) > investigated the possibility of using NativeBoost calls to do the same, but > it would not work since mtdev2tuio has to run as superuser, meaning Pharo > would have to run as superuser. We came to the conclusion that this must be > a VM-level change. > > I'm not a VM hacker but would like to reach the people who maintain the > linux and windows VM to see if this might not be a reasonable addition to > the standard VM. There does seem to be standard support for touch events in > XFree86, so it shouldn't be too large a change on Linux. I assume that > Windows 8 similarly makes touch events available. Is this the right place > to ask or is there another mailing list (e.g., the cog-vm)? > > Cheers, > > Jeff > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick >

March 11, 2014