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

Re: [Pharo-project] testing ui errors in headless mode

by Gary Chambers

Ok, didn't dig deep enough ;-) Regards, Gary ----- Original Message ----- From: "Igor Stasenko" <siguctua(a)gmail.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Thursday, May 26, 2011 4:42 PM Subject: Re: [Pharo-project] testing ui errors in headless mode On 26 May 2011 17:10, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: > Wonder what the default TooSet is in headless mode... > (since inspect goes via the tool set) > There is no ToolSet (it will be removed) All references to ToolSet will be replaced by Smalltalk tools blah blah idiom. (btw we need to integrate that) > Regards, Gary > > ----- Original Message ----- From: "Tudor Girba" <tudor(a)tudorgirba.com> > To: "Pharo-project(a)lists.gforge.inria.fr open-source Smalltalk" > <pharo-project(a)lists.gforge.inria.fr> > Sent: Thursday, May 26, 2011 4:03 PM > Subject: Re: [Pharo-project] testing ui errors in headless mode > > > Hi, > > I tried several ways to get my head around this problem, but I do not know > how to proceed. Can anyone help? > > Cheers, > Doru > > > On 25 May 2011, at 21:21, Tudor Girba wrote: > >> Hi, >> >> We have some smoke tests in Moose that basically spawn a UI and check for >> Error. >> >> This used to work when running headless in Pharo 1.2 but now they fail in >> Pharo 1.3. I believe this has to do with the new changes in the UI >> Manager, >> but I do not know what to do. >> >> To reproduce the problem, you can simply call a Pharo-1.3.image in >> headless mode and file in the attached st file that: >> >> - installs a simple test: >> HeadlessTest>>testStartup >> self shouldnt: [1 inspect] raise: Error >> >> - loads HudsonTools >> >> - runs the test and outputs the XML file report >> >> - although the test should pass, it raises the error: >> HeadlessStartupTest(TestCase)>>signalFailure: >> HeadlessStartupTest(TestCase)>>assert: >> HeadlessStartupTest(TestCase)>>shouldnt:raise: >> HeadlessStartupTest>>testStartup >> HeadlessStartupTest(TestCase)>>performTest >> >> >> Can anyone help? >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "What is more important: To be happy, or to make happy?" >> >> <headlesstest.st> > > -- > www.tudorgirba.com > > "It's not what we do that matters most, it's how we do it." > > > > -- Best regards, Igor Stasenko AKA sig.

May 26, 2011

Re: [Pharo-project] cog vm for iOS

by Casimiro de Almeida Barreto

Em 26-05-2011 09:02, Igor Stasenko escreveu: > On 25 May 2011 20:45, Hilaire Fernandes <hilaire.fernandes(a)gmail.com> wrote: >> I have no idea how hard it is to pass the apple check. >> It can indeed temper any effort doing a theme. >> > I think that i can express Apple's policy using single statement: > - why you using language X for your project, if you can implement same > in Objective C. > > :) > Clearly Apple has a restrictive police on development and commercialization of products for the iOS platform. It is not related only to development language/environment but also content. Apple censors and decides what can and what cannot be put in "their" (should be their customers) tablets/phones/iPods (kind: no porno, no political, no certain kinds of violence, etc). One thing that amazes me is that currently there are two contestants to the "Tablet & Smartphone World Grand Prix": iOS and Android but people in the SqueakVM/CogVM communities are centered only around a single "monopolist" manufacturer. IMHO it would be good to have SqueakVM/CogVM decently running in Android (>= 2.1). In the long term I think Android will win this "championship". My 2Â¢ CdAB >> Hilaire >> (...)

May 26, 2011

Re: [Pharo-project] testing ui errors in headless mode

by Igor Stasenko

On 26 May 2011 17:03, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I tried several ways to get my head around this problem, but I do not know how to proceed. Can anyone help? > > Cheers, > Doru > > > On 25 May 2011, at 21:21, Tudor Girba wrote: > >> Hi, >> >> We have some smoke tests in Moose that basically spawn a UI and check for Error. >> >> This used to work when running headless in Pharo 1.2 but now they fail in Pharo 1.3. I believe this has to do with the new changes in the UI Manager, but I do not know what to do. >> >> To reproduce the problem, you can simply call a Pharo-1.3.image in headless mode and file in the attached st file that: >> >> - installs a simple test: >> HeadlessTest>>testStartup >> Â Â Â self shouldnt: Â [1 inspect] raise: Â Error Tudor, your test is wrong. During image startup and in headless mode calling inspector will and should raise an error. Because inspecting object requires a presence of UI. But there's no UI in headless mode and prohibited from use during image startup phase, because you cannot start asking questions from user before properly initializing everything related to startup. Startup is called startup on purpose: is should not be interrupted nor require user's interaction. Assume that you don't have Morphic loaded in your image, then what you expect to happen if you do 1 inspect ? >> >> - loads HudsonTools >> >> - runs the test and outputs the XML file report >> >> - although the test should pass, it raises the error: >> HeadlessStartupTest(TestCase)>>signalFailure: >> HeadlessStartupTest(TestCase)>>assert: >> HeadlessStartupTest(TestCase)>>shouldnt:raise: >> HeadlessStartupTest>>testStartup >> HeadlessStartupTest(TestCase)>>performTest >> >> >> Can anyone help? >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "What is more important: To be happy, or to make happy?" >> >> <headlesstest.st> > > -- > www.tudorgirba.com > > "It's not what we do that matters most, it's how we do it." > > > -- Best regards, Igor Stasenko AKA sig.

May 26, 2011

Re: [Pharo-project] testing ui errors in headless mode

by Igor Stasenko

On 26 May 2011 17:10, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: > Wonder what the default TooSet is in headless mode... > (since inspect goes via the tool set) > There is no ToolSet (it will be removed) All references to ToolSet will be replaced by Smalltalk tools blah blah idiom. (btw we need to integrate that) > Regards, Gary > > ----- Original Message ----- From: "Tudor Girba" <tudor(a)tudorgirba.com> > To: "Pharo-project(a)lists.gforge.inria.fr open-source Smalltalk" > <pharo-project(a)lists.gforge.inria.fr> > Sent: Thursday, May 26, 2011 4:03 PM > Subject: Re: [Pharo-project] testing ui errors in headless mode > > > Hi, > > I tried several ways to get my head around this problem, but I do not know > how to proceed. Can anyone help? > > Cheers, > Doru > > > On 25 May 2011, at 21:21, Tudor Girba wrote: > >> Hi, >> >> We have some smoke tests in Moose that basically spawn a UI and check for >> Error. >> >> This used to work when running headless in Pharo 1.2 but now they fail in >> Pharo 1.3. I believe this has to do with the new changes in the UI Manager, >> but I do not know what to do. >> >> To reproduce the problem, you can simply call a Pharo-1.3.image in >> headless mode and file in the attached st file that: >> >> - installs a simple test: >> HeadlessTest>>testStartup >> self shouldnt: Â [1 inspect] raise: Â Error >> >> - loads HudsonTools >> >> - runs the test and outputs the XML file report >> >> - although the test should pass, it raises the error: >> HeadlessStartupTest(TestCase)>>signalFailure: >> HeadlessStartupTest(TestCase)>>assert: >> HeadlessStartupTest(TestCase)>>shouldnt:raise: >> HeadlessStartupTest>>testStartup >> HeadlessStartupTest(TestCase)>>performTest >> >> >> Can anyone help? >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "What is more important: To be happy, or to make happy?" >> >> <headlesstest.st> > > -- > www.tudorgirba.com > > "It's not what we do that matters most, it's how we do it." > > > > -- Best regards, Igor Stasenko AKA sig.

May 26, 2011

Re: [Pharo-project] tests ui errors in headless mode

by Igor Stasenko

To simulate running test in headless mode, use following: | old | old := UIManager default. UIManager default: old nonInteractiveManager. [ 1 inspect. ] ensure: [ UIManager default: old ] and so, if you don't handle the error.. image will quit and error logged to PharoDebug.log : THERE_BE_DRAGONS_HERE MessageNotUnderstood: NonInteractiveUIManager>>openInspector:asMorphOn:withLabel: 26 May 2011 7:31:32 pm VM: Mac OS - intel - 1066 - Croquet Closure Cog VM [CoInterpreter VMMaker-oscog-MarianoMartinezPeck.66] NBCog VM 4.0.0 Image: Pharo1.3a [Latest update: #13204] NonInteractiveUIManager(Object)>>doesNotUnderstand: #openInspector:asMorphOn:withLabel: Receiver: a NonInteractiveUIManager Arguments and temporary variables: aMessage: openInspector: Inspector asMorphOn: 1 withLabel: 'SmallInteger: 1' exception: MessageNotUnderstood: NonInteractiveUIManager>>openInspector:asMorph...etc... resumeValue: nil Receiver's instance variables: uiManager: a MorphicUIManager doNotQuitOnRestart: false You can also turn on #snapshotErrorImage setting, then on unhandled error, before quit an image will be saved (with different version) and if you open that image you will see that error in debugger. On 25 May 2011 21:21, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > We have some smoke tests in Moose that basically spawn a UI and check for Error. > > This used to work when running headless in Pharo 1.2 but now they fail in Pharo 1.3. I believe this has to do with the new changes in the UI Manager, but I do not know what to do. > > To reproduce the problem, you can simply call a Pharo-1.3.image in headless mode and file in the attached st file that: > > - installs a simple test: > HeadlessTest>>testStartup > Â Â Â Â self shouldnt: Â [1 inspect] raise: Â Error > > - loads HudsonTools > > - runs the test and outputs the XML file report > > - although the test should pass, it raises the error: > HeadlessStartupTest(TestCase)>>signalFailure: > HeadlessStartupTest(TestCase)>>assert: > HeadlessStartupTest(TestCase)>>shouldnt:raise: > HeadlessStartupTest>>testStartup > HeadlessStartupTest(TestCase)>>performTest > > > Can anyone help? > > Cheers, > Doru > > -- > www.tudorgirba.com > > "What is more important: To be happy, or to make happy?" > > -- Best regards, Igor Stasenko AKA sig.

May 26, 2011

Re: [Pharo-project] testing ui errors in headless mode

by Gary Chambers

Wonder what the default TooSet is in headless mode... (since inspect goes via the tool set) Regards, Gary ----- Original Message ----- From: "Tudor Girba" <tudor(a)tudorgirba.com> To: "Pharo-project(a)lists.gforge.inria.fr open-source Smalltalk" <pharo-project(a)lists.gforge.inria.fr> Sent: Thursday, May 26, 2011 4:03 PM Subject: Re: [Pharo-project] testing ui errors in headless mode Hi, I tried several ways to get my head around this problem, but I do not know how to proceed. Can anyone help? Cheers, Doru On 25 May 2011, at 21:21, Tudor Girba wrote: > Hi, > > We have some smoke tests in Moose that basically spawn a UI and check for > Error. > > This used to work when running headless in Pharo 1.2 but now they fail in > Pharo 1.3. I believe this has to do with the new changes in the UI > Manager, but I do not know what to do. > > To reproduce the problem, you can simply call a Pharo-1.3.image in > headless mode and file in the attached st file that: > > - installs a simple test: > HeadlessTest>>testStartup > self shouldnt: [1 inspect] raise: Error > > - loads HudsonTools > > - runs the test and outputs the XML file report > > - although the test should pass, it raises the error: > HeadlessStartupTest(TestCase)>>signalFailure: > HeadlessStartupTest(TestCase)>>assert: > HeadlessStartupTest(TestCase)>>shouldnt:raise: > HeadlessStartupTest>>testStartup > HeadlessStartupTest(TestCase)>>performTest > > > Can anyone help? > > Cheers, > Doru > > -- > www.tudorgirba.com > > "What is more important: To be happy, or to make happy?" > > <headlesstest.st> -- www.tudorgirba.com "It's not what we do that matters most, it's how we do it."

May 26, 2011

Re: [Pharo-project] testing ui errors in headless mode

by Tudor Girba

Hi, I tried several ways to get my head around this problem, but I do not know how to proceed. Can anyone help? Cheers, Doru On 25 May 2011, at 21:21, Tudor Girba wrote: > Hi, > > We have some smoke tests in Moose that basically spawn a UI and check for Error. > > This used to work when running headless in Pharo 1.2 but now they fail in Pharo 1.3. I believe this has to do with the new changes in the UI Manager, but I do not know what to do. > > To reproduce the problem, you can simply call a Pharo-1.3.image in headless mode and file in the attached st file that: > > - installs a simple test: > HeadlessTest>>testStartup > self shouldnt: [1 inspect] raise: Error > > - loads HudsonTools > > - runs the test and outputs the XML file report > > - although the test should pass, it raises the error: > HeadlessStartupTest(TestCase)>>signalFailure: > HeadlessStartupTest(TestCase)>>assert: > HeadlessStartupTest(TestCase)>>shouldnt:raise: > HeadlessStartupTest>>testStartup > HeadlessStartupTest(TestCase)>>performTest > > > Can anyone help? > > Cheers, > Doru > > -- > www.tudorgirba.com > > "What is more important: To be happy, or to make happy?" > > <headlesstest.st> -- www.tudorgirba.com "It's not what we do that matters most, it's how we do it."

May 26, 2011

[Pharo-project] Increasing the performances of a Seaside application

by Olivier Auverlot

Hello, In the next weeks, I hope that I will start my first application with Seaside. The first version is ready. It's a set of REST web services. Now, I'm doing differents stress tests for evaluating the charge that my product can support. I'm using Pharo 1.2.1, Seaside, Seaside-REST, SqueakDBX, LDAPlayer and XML-Parser. For the connector, I use AJPPharoAdaptator for the link between my program and Apache. Have you ideas or good practices for optimising the performances of a Seaside application ? Of course, I can installing my application on differents servers and made load balancing but I think that the first thing that I must improve is the code himself. Working faster with a database and a LDAP are the first problems that I want resolve. Someone worked on the pools of connections ? What are the errors that I must avoid making ? It's a large subject but it could be benefit to share experience in the search of performance. Best regards Olivier ;-) www.auverlot.fr

May 26, 2011

Re: [Pharo-project] Tiling windows

by GastÃ³n Dall' Oglio

2011/5/26 laurent laffont <laurent.laffont(a)gmail.com> > 2011/5/26 GastÃ³n Dall' Oglio <gaston.dalloglio(a)gmail.com> > >> >> >> 2011/5/26 laurent laffont <laurent.laffont(a)gmail.com> >> >>> GastÃ²n, >>> >>> I've downloaded the new version - thanks a lot for contributing, it >>> brings fun :) >>> >>> Some comment: >>> >>> - tiling browsers don't work any more with >>> OB, WMWithAnOBBrowserAndDockingBarsTest does not create an OBBrowser anymore >>> but a Browser >>> >> >> In 1.3 core there's not OBBrowser, then, when trying to modify a method >> with reference to OBBrowser obtained an error. So I remove their references. >> > > > I see. I will refactor this so it will be compatible with Core and still > work with OB (quite easy). > This would be great, because now I think, in a core are never the most useful tools (Seaside control panel, memory monitor), and TWM should know about them in some way (you apply a pattern to solve this problem?). > > > >> - you've changed TilingWM>>visibleWindows to TilingWM>>windows. The >>> "visible" was not innocent, because tileVisibleWindows cares about windows >>> that are not minimized. On the other side, tileWorkspaces tile all >>> workspaces, minimized or not. So I think in final we may have: >>> >>> #tileVisibleWindows >>> #tileWindows (maybe #tileAllWindows is a better name) >>> #tileVisibleWorkspaces >>> #tileWorkspaces / #tileAllWorkspaces >>> ...... >>> >>> >> Please, see you the comment in de versiÃ³n 5 of de package, "Now all botton >> tile visibles windows.". I think it's better to just get organized visible >> windows, even when done on a particular kind (such as workspaces). For this >> is that the word was redundant now visible. >> > > > I will think about this. > When you have many windows, minimizing them is the way to let them "suspended", therefore I think it should be organized only visibles. > > > - I will add tests to TWMBar finally as it seems to grow >>> >>> - I want TilingWM to be 100% test coverage >>> >> >> Sorry, give me some time for learn about this... >> > > > Don't hesitate to ask. > > ok. > > - Balloon and spaces for TWMBar is a good idea - we need to make this work >>> effectively :) >>> >>> >> yes >> >> >>> - Great to have all the buttons per type of applications ! >>> >> >> it is still very rudimentary way to filter the windows, but it was helpful >> to learn about the hierarchy of classes 1.3, in regard to the Models for >> example. >> > > > Indeed I've disable TaskBarMorph in my image as it's useless now :) > Great!!! I'll be honest, this is my first serious development in Squeak / Pharo, so it gives me much encouragement your comment, there is still much to learn and improve, but it is very encouraging to devote time to something that might be useful to others. > > > Laurent. > > >> >> >>> >>> I've merge some of your changes in TWM-LaurentLaffont.5 >>> >> >> >> :) >> >> >>> >>> >>> Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> >>> >>> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ >>> Blog: http://magaloma.blogspot.com/ >>> Developer group: http://cara74.seasidehosting.st >>> >>> >>> >>> 2011/5/26 GastÃ³n Dall' Oglio <gaston.dalloglio(a)gmail.com> >>> >>>> >>>> >>>> 2011/5/25 laurent laffont <laurent.laffont(a)gmail.com> >>>> >>>>> 2011/5/25 GastÃ³n Dall' Oglio <gaston.dalloglio(a)gmail.com> >>>>> >>>>>> Excelent! >>>>>> >>>>>> IMHO, it's better that's not integrated to TaskBarMorph, lets it free >>>>>> :) >>>>>> For example, click in unused space of the TWMBar and you can move it >>>>>> around you wish in the screen, similar to use DockingBarMorph>>beFloating. I >>>>>> attach screenshot. >>>>>> >>>>>> Laurent, I improved (or not? :)) your work, if you think that is bad >>>>>> for TWM simply undo it ;) >>>>>> >>>>> >>>>> Feel free to play. Just try to write tests for TilingWM please :) >>>>> >>>>> >>>> ok. I load a new version to ss. Now teh button tile visible windows >>>> only. I fixed the test... >>>> >>>> >>>>> For TWMBar I'm not sure this will be a final GUI. Ideally all will be >>>>> keyboard driven, I have to play with KeyMapping. >>>>> >>>>> >>>> yes, sure. >>>> >>>> >>>>> I also think the UI theme Patrick has cleaned fits better with >>>>> TilingWM: >>>>> >>>>> To try it: >>>>> >>>>> Gofer it >>>>> squeaksource: 'PBASandbox'; >>>>> package: 'PBSandbox'; >>>>> load. >>>>> StandardUITheme beCurrent. >>>>> >>>>> See screenshot. >>>>> >>>>> >>>>> >>>> I try, yes. >>>> >>>> >>>>> Patrick, could you push this with a nice package name ? >>>>> >>>>> >>>>> Laurent. >>>>> >>>>> >>>>> >>>>>> 2011/5/25 laurent laffont <laurent.laffont(a)gmail.com> >>>>>> >>>>>>> Now there's a button to open the world menu. >>>>>>> >>>>>>> Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> >>>>>>> >>>>>>> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ >>>>>>> Blog: http://magaloma.blogspot.com/ >>>>>>> Developer group: http://cara74.seasidehosting.st >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, May 25, 2011 at 11:20 AM, laurent laffont < >>>>>>> laurent.laffont(a)gmail.com> wrote: >>>>>>> >>>>>>>> On Wed, May 25, 2011 at 11:06 AM, StÃ©phane Ducasse < >>>>>>>> stephane.ducasse(a)inria.fr> wrote: >>>>>>>> >>>>>>>>> I do not understand. >>>>>>>>> >>>>>>>>> how can I get a browser? >>>>>>>>> >>>>>>>> >>>>>>>> Hey, this is just a start :) I will add a button to open the world >>>>>>>> menu. >>>>>>>> >>>>>>>> >>>>>>>> once this is one is created I get the browser full screen >>>>>>>>> but then how do I get a chance to create a new one if I want. >>>>>>>>> >>>>>>>>> dividing the browsers based on the screen size results in rather >>>>>>>>> small browsers :) >>>>>>>>> >>>>>>>> >>>>>>>> yes, but because browsers waste space IMHO. Maybe we could get rid >>>>>>>> of windows borders when tiled. >>>>>>>> >>>>>>>> Laurent. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> Stef >>>>>>>>> >>>>>>>>> >>>>>>>>> > TWMBar new open. >>>>>>>>> > >>>>>>>>> > The real manager is TilingWM. Try: >>>>>>>>> > >>>>>>>>> > (TilingWM forWorld: World) tileVisibleWindows. >>>>>>>>> > (TilingWM forWorld: World) tileBrowsers. >>>>>>>>> > (TilingWM forWorld: World) tileWorkspaces. >>>>>>>>> > >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >

May 26, 2011

Re: [Pharo-project] Tiling windows

by laurent laffont

2011/5/26 GastÃ³n Dall' Oglio <gaston.dalloglio(a)gmail.com> > > > 2011/5/26 laurent laffont <laurent.laffont(a)gmail.com> > >> GastÃ²n, >> >> I've downloaded the new version - thanks a lot for contributing, it brings >> fun :) >> >> Some comment: >> >> - tiling browsers don't work any more with >> OB, WMWithAnOBBrowserAndDockingBarsTest does not create an OBBrowser anymore >> but a Browser >> > > In 1.3 core there's not OBBrowser, then, when trying to modify a method > with reference to OBBrowser obtained an error. So I remove their references. > I see. I will refactor this so it will be compatible with Core and still work with OB (quite easy). > - you've changed TilingWM>>visibleWindows to TilingWM>>windows. The >> "visible" was not innocent, because tileVisibleWindows cares about windows >> that are not minimized. On the other side, tileWorkspaces tile all >> workspaces, minimized or not. So I think in final we may have: >> >> #tileVisibleWindows >> #tileWindows (maybe #tileAllWindows is a better name) >> #tileVisibleWorkspaces >> #tileWorkspaces / #tileAllWorkspaces >> ...... >> >> > Please, see you the comment in de versiÃ³n 5 of de package, "Now all botton > tile visibles windows.". I think it's better to just get organized visible > windows, even when done on a particular kind (such as workspaces). For this > is that the word was redundant now visible. > I will think about this. - I will add tests to TWMBar finally as it seems to grow >> >> - I want TilingWM to be 100% test coverage >> > > Sorry, give me some time for learn about this... > Don't hesitate to ask. - Balloon and spaces for TWMBar is a good idea - we need to make this work >> effectively :) >> >> > yes > > >> - Great to have all the buttons per type of applications ! >> > > it is still very rudimentary way to filter the windows, but it was helpful > to learn about the hierarchy of classes 1.3, in regard to the Models for > example. > Indeed I've disable TaskBarMorph in my image as it's useless now :) Laurent. > > >> >> I've merge some of your changes in TWM-LaurentLaffont.5 >> > > > :) > > >> >> >> Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> >> >> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ >> Blog: http://magaloma.blogspot.com/ >> Developer group: http://cara74.seasidehosting.st >> >> >> >> 2011/5/26 GastÃ³n Dall' Oglio <gaston.dalloglio(a)gmail.com> >> >>> >>> >>> 2011/5/25 laurent laffont <laurent.laffont(a)gmail.com> >>> >>>> 2011/5/25 GastÃ³n Dall' Oglio <gaston.dalloglio(a)gmail.com> >>>> >>>>> Excelent! >>>>> >>>>> IMHO, it's better that's not integrated to TaskBarMorph, lets it free >>>>> :) >>>>> For example, click in unused space of the TWMBar and you can move it >>>>> around you wish in the screen, similar to use DockingBarMorph>>beFloating. I >>>>> attach screenshot. >>>>> >>>>> Laurent, I improved (or not? :)) your work, if you think that is bad >>>>> for TWM simply undo it ;) >>>>> >>>> >>>> Feel free to play. Just try to write tests for TilingWM please :) >>>> >>>> >>> ok. I load a new version to ss. Now teh button tile visible windows only. >>> I fixed the test... >>> >>> >>>> For TWMBar I'm not sure this will be a final GUI. Ideally all will be >>>> keyboard driven, I have to play with KeyMapping. >>>> >>>> >>> yes, sure. >>> >>> >>>> I also think the UI theme Patrick has cleaned fits better with TilingWM: >>>> >>>> To try it: >>>> >>>> Gofer it >>>> squeaksource: 'PBASandbox'; >>>> package: 'PBSandbox'; >>>> load. >>>> StandardUITheme beCurrent. >>>> >>>> See screenshot. >>>> >>>> >>>> >>> I try, yes. >>> >>> >>>> Patrick, could you push this with a nice package name ? >>>> >>>> >>>> Laurent. >>>> >>>> >>>> >>>>> 2011/5/25 laurent laffont <laurent.laffont(a)gmail.com> >>>>> >>>>>> Now there's a button to open the world menu. >>>>>> >>>>>> Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> >>>>>> >>>>>> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ >>>>>> Blog: http://magaloma.blogspot.com/ >>>>>> Developer group: http://cara74.seasidehosting.st >>>>>> >>>>>> >>>>>> >>>>>> On Wed, May 25, 2011 at 11:20 AM, laurent laffont < >>>>>> laurent.laffont(a)gmail.com> wrote: >>>>>> >>>>>>> On Wed, May 25, 2011 at 11:06 AM, StÃ©phane Ducasse < >>>>>>> stephane.ducasse(a)inria.fr> wrote: >>>>>>> >>>>>>>> I do not understand. >>>>>>>> >>>>>>>> how can I get a browser? >>>>>>>> >>>>>>> >>>>>>> Hey, this is just a start :) I will add a button to open the world >>>>>>> menu. >>>>>>> >>>>>>> >>>>>>> once this is one is created I get the browser full screen >>>>>>>> but then how do I get a chance to create a new one if I want. >>>>>>>> >>>>>>>> dividing the browsers based on the screen size results in rather >>>>>>>> small browsers :) >>>>>>>> >>>>>>> >>>>>>> yes, but because browsers waste space IMHO. Maybe we could get rid of >>>>>>> windows borders when tiled. >>>>>>> >>>>>>> Laurent. >>>>>>> >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> Stef >>>>>>>> >>>>>>>> >>>>>>>> > TWMBar new open. >>>>>>>> > >>>>>>>> > The real manager is TilingWM. Try: >>>>>>>> > >>>>>>>> > (TilingWM forWorld: World) tileVisibleWindows. >>>>>>>> > (TilingWM forWorld: World) tileBrowsers. >>>>>>>> > (TilingWM forWorld: World) tileWorkspaces. >>>>>>>> > >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >

May 26, 2011