May 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Pharo-users] Screencast on Tiling Window Manager

by Bernat Romagosa

What about the possibility of implementing shortcuts? A big part of the point of most of these WMs is to minimize the use of the rat ;) For example, in my WM you'd go c-t s to get an horizontal split, c-t S to get a vertical split, c-t t to switch between the two last used windows, c-t space to cycle through all open windows etc. Just a suggestion... Bernat. 2011/5/30 laurent laffont <laurent.laffont(a)gmail.com> > I've never used xmonad but if you provide an alternate layout > implementation (See TilingWM>>tileWindows: ) + tests :) I will merge it > using a Strategy Pattern. > > Laurent. > > On Sat, May 28, 2011 at 9:52 PM, Miguel Moquillon < > miguel.moquillon(a)gmail.com> wrote: > >> >> It is a cool project with which I could retrieve my habits from my window >> manager (I use xmonad) on my GNU/Linux machines. >> You talk about emacs as inspiration of your project; why don't take ideas >> from tiling window manager like xmonad, awesome or others? For exemple, they >> use the concept of layouts to provide several policy on tiling window >> management. >> >> Mig >> >> >> Le 28 mai 2011 Ã 00:15, laurent laffont <laurent.laffont(a)gmail.com> a >> Ã©crit : >> >> Here: <http://magaloma.blogspot.com/2011/05/tiling-window-manager.html> >> http://magaloma.blogspot.com/2011/05/tiling-window-manager.html >> >> Not really good, awful english (I'm tired :) but feedback is always >> welcome ! >> >> >> Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> >> >> Pharo Smalltalk Screencasts: <http://www.pharocasts.com/> >> http://www.pharocasts.com/ >> Blog: <http://magaloma.blogspot.com/>http://magaloma.blogspot.com/ >> Developer group: <http://cara74.seasidehosting.st> >> http://cara74.seasidehosting.st >> >> >

May 30, 2011

Re: [Pharo-project] [Pharo-users] Screencast on Tiling Window Manager

by laurent laffont

I've never used xmonad but if you provide an alternate layout implementation (See TilingWM>>tileWindows: ) + tests :) I will merge it using a Strategy Pattern. Laurent. On Sat, May 28, 2011 at 9:52 PM, Miguel Moquillon < miguel.moquillon(a)gmail.com> wrote: > > It is a cool project with which I could retrieve my habits from my window > manager (I use xmonad) on my GNU/Linux machines. > You talk about emacs as inspiration of your project; why don't take ideas > from tiling window manager like xmonad, awesome or others? For exemple, they > use the concept of layouts to provide several policy on tiling window > management. > > Mig > > > Le 28 mai 2011 Ã 00:15, laurent laffont <laurent.laffont(a)gmail.com> a > Ã©crit : > > Here: <http://magaloma.blogspot.com/2011/05/tiling-window-manager.html> > http://magaloma.blogspot.com/2011/05/tiling-window-manager.html > > Not really good, awful english (I'm tired :) but feedback is always > welcome ! > > > Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> > > Pharo Smalltalk Screencasts: <http://www.pharocasts.com/> > http://www.pharocasts.com/ > Blog: <http://magaloma.blogspot.com/>http://magaloma.blogspot.com/ > Developer group: <http://cara74.seasidehosting.st> > http://cara74.seasidehosting.st > >

May 30, 2011

Re: [Pharo-project] Mocketry?

by laurent laffont

Note there's an HelpSystem book loaded with ConfigurationOfMocketry. Laurent. On Mon, May 30, 2011 at 4:26 AM, Dennis Schetinin <chaetal(a)gmail.com> wrote: > BTW, I've provided a tiny example in VW thread: > http://forum.world.st/Mocking-in-Unit-Tests-td3552082.html#a3554271 > > > 2011/5/27 Alexandre Bergel <alexandre.bergel(a)me.com> > >> Thanks Denis >> >> Alexandre >> >> >> On 27 May 2011, at 09:12, Denis Kudriashov wrote: >> >> > Hello >> > >> > See squeaksource wiki tab http://www.squeaksource.com/Mocketry.html >> > >> > And tests with class name like Acceptance is good I think. >> > >> > >> > >> > 2011/5/27 Alexandre Bergel <alexandre.bergel(a)me.com> >> > Hi! >> > >> > Following some discussion about Mocketry, I wanted to know more about >> it. >> > I've found >> > http://www.cincomsmalltalk.com/publicRepository/Mocketry(Bundle).html >> > >> > and the squeaksource project. I read the tests but this is a bit >> cryptic. >> > >> > In 5 minutes, I couldn't find what it was exactly about. >> > Any good url that google does not know about? >> > >> > Cheers, >> > Alexandre >> > -- >> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> > Alexandre Bergel http://www.bergel.eu >> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> > >> > >> > >> > >> > >> > >> > >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> > > > -- > Dennis Schetinin >

May 30, 2011

Re: [Pharo-project] TilingWM improvements

by laurent laffont

Hi GastÃ³n, I did not look at your change yet, sorry :), and I'm not sure to understand. Could you write a test to characterize this please ? I've implemented automatic refresh (see TilingWMSettings class>>initialize). May break the first time you load it if you have a version before the change. There's a first shot of GUI controls for world snapshot / navigation but it needs more work to be intuitive. Laurent. 2011/5/28 GastÃ³n Dall' Oglio <gaston.dalloglio(a)gmail.com> > Laurent, coincidere change this method (o part of): > > TilingWM>>newTopWindowBoundsInArea: aBlock > SystemWindow topWindow bounds: (aBlock value: world clearArea). > > to this one: > > TilingWM>>newTopWindowBoundsInArea: aBlock > | topWindow | > (topWindow := SystemWindow topWindow) isMaximized > ifTrue: [ topWindow expandBoxHit. topWindow bounds: (aBlock value: world > clearArea) ] > ifFalse: [ topWindow bounds: (aBlock value: topWindow bounds) ] > > > For one hand this solve the problem of maximized state on moved window, and > for other hand apply recursive "moving" of window based in their current > bounds (but not usable display area) if that is not in state maximize (I > choose this rule for my convenience). > > --- > > When I load new version of this package, I use the Settings to see new > version de la barra, but the old version keep visible too, and I use > SHIFT-ALT-Click to see the halos and remove this. Is possible clean up of > older versions of bar automatically? > > ---- > > And I see that you comming work in TWMWindowSnapshot :) I like it, I hate > wasting time accommodating the size and position of the windows manually > because I want to have another hearing, again and again! > > >

May 30, 2011

[Pharo-project] [TODO] 1.3

by Marcus Denker

Core: 5 http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.3 ==== 1907 Set with nil 4310 Cleanup stdio ServerMode preference 3974 [RPackage] rpackage do not update when adding a category 4209 Transcipt could still be improved a little more 4236 MultiByteFileStream doing double conversion on windows Full: 2 http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3-DevImage === 4245 Add file ArchiveViewer not working 4303 completion and tab key -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 30, 2011

Re: [Pharo-project] A radical proposal (to cut down dead code)

by StÃ©phane Ducasse

On May 30, 2011, at 1:58 AM, askoh wrote: > How far along are we with making good packages for Pharo? 60%?? To obtain what? What are your constraints? Did you try to unload packages? Our goal is to bootstrap an image and we will go there step by step. One step is to remove StringHolder and friends from the image and replace them by something less messy Stef > -- > View this message in context: http://forum.world.st/A-radical-proposal-to-cut-down-dead-code-tp3557448p35… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

May 30, 2011

Re: [Pharo-project] Mocketry?

by Dennis Schetinin

BTW, I've provided a tiny example in VW thread: http://forum.world.st/Mocking-in-Unit-Tests-td3552082.html#a3554271 2011/5/27 Alexandre Bergel <alexandre.bergel(a)me.com> > Thanks Denis > > Alexandre > > > On 27 May 2011, at 09:12, Denis Kudriashov wrote: > > > Hello > > > > See squeaksource wiki tab http://www.squeaksource.com/Mocketry.html > > > > And tests with class name like Acceptance is good I think. > > > > > > > > 2011/5/27 Alexandre Bergel <alexandre.bergel(a)me.com> > > Hi! > > > > Following some discussion about Mocketry, I wanted to know more about it. > > I've found > > http://www.cincomsmalltalk.com/publicRepository/Mocketry(Bundle).html > > > > and the squeaksource project. I read the tests but this is a bit cryptic. > > > > In 5 minutes, I couldn't find what it was exactly about. > > Any good url that google does not know about? > > > > Cheers, > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > -- Dennis Schetinin

May 30, 2011

Re: [Pharo-project] A radical proposal (to cut down dead code)

by askoh

How far along are we with making good packages for Pharo? 60%?? -- View this message in context: http://forum.world.st/A-radical-proposal-to-cut-down-dead-code-tp3557448p35… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 29, 2011

Re: [Pharo-project] A radical proposal (to cut down dead code)

by Schwab,Wilhelm K

Options are good, but one algorithm that tries to get it all right is probably asking for trouble. Dolphin has an elaborate stripper, but I found that slicing out unreferenced packages would typically give me a 4 MB or so executable. I was able to strip further, but it took time and raised the possibility of runtime failures. Which tests drive the stripping? They could easily be broader than strictly necessary, causing otherwise unneeded things to be retained. I agree with Stef that good packaging is the place to start. ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Markus Fritsche [fritsche.markus(a)googlemail.com] Sent: Sunday, May 29, 2011 4:57 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] A radical proposal (to cut down dead code) 2011/5/29 askoh <askoh(a)askoh.com>: > Is Spoon trying to do this? AFAIK, yes. As far as I understand, Craig is using a modified VM to identify sent messages and to automagically mirror them from a master to a slave image; making testcases very crucial in the process. To make a tailored image, you run all the testcases and the "needed" behavior automagically gets pushed/ pulled into the slave image. Save the slave, and you can run it indepentently. "Spoon" way - mark each sent message (within the vm) - execute a full test cycle - see what has been marked- "Tinkering way" - modify all CompiledMethods to send a "self registerAsSent: self selector object: self" by code and run a full test Two ways I could think off right now, not really deep into it.

May 29, 2011

Re: [Pharo-project] A radical proposal (to cut down dead code)

by Craig Latta

Hi Aik-Siong-- I agree with Markus that dead code is a huge problem, in its obstruction to understanding. > What is desirable is to remove dead code from application images that > are ready for distribution. VisualWorks has RuntimePackager to strip > the application image before distribution. Pharo should have > something like that. > > The alternative is to build an application by importing needed code > into a bare bone image. Is Spoon trying to do this? Yes. My intent is that no one need ever strip an image again. thanks, -C -- Craig Latta www.netjam.org/resume +31 06 2757 7177 + 1 415 287 3547

May 29, 2011