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

[Pharo-project] [update 1.3] #13217

by Marcus Denker

13217 ----- Issue 4273: finalisation of FT2Handles http://code.google.com/p/pharo/issues/detail?id=4273 Issue 4279: Little cleaning Paragraph/DisplayScanning http://code.google.com/p/pharo/issues/detail?id=4279 Issue 4284: remove TextMorph #drawOnTest: http://code.google.com/p/pharo/issues/detail?id=4284 Issue 4286: remove testSaveAndLoadImageSegmentToDiskWithGC: http://code.google.com/p/pharo/issues/detail?id=4286 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 26, 2011

Re: [Pharo-project] cog vm for iOS

by Igor Stasenko

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. :) > Hilaire > > Le 25/05/2011 18:29, Esteban Lorenzano a Ã©crit : >> Sorry, but no, this is not an option. >> A theme will never pass the apple quality check :( >> >> Esteban >> >> El 25/05/2011, a las 1:22p.m., Hilaire Fernandes escribiÃ³: >> >>> A third option could be to build a polymorph theme for iPAD. >>> This is an intermediate option I discussed a bit with Bert, to do a >>> DrGeo port for iPAD. >>> Frankly speaking if someone is interested to work with me on that >>> direction we may be able to produce something in our range and useful >>> for the community at large. >>> >>> Hilaire >>> >>> >>> >>> >>> Le 25/05/2011 18:01, Esteban Lorenzano a Ã©crit : >>>> Well... I'm going to use this post to talk a bit about Pharo in iOS, because it is more complex than "having a vm working" >>>> But first, a summary of where we stand: >>>> 1) The Stack VM is working with iPhone/iPad, but needs some minor adjustments (some tuning). >>>> One problem here is that I didn't integrate it to CMakeVMMaker (and as a consequence, to hudson), so build it is not a trivial task. But I will, as soon as some one jump and say "hey, I'm going to use it, for real!"... or as soon as I can find a free afternoon... it is planned (and I worked a little on this), but it is not a priority right now :) >>>> 2) The Cog (I mean, the jitter) will never work on iPad/iPhone, because of the apple license (clause 3.3.2) and because of the security sandbox policy. But I think the Stack VM can do a pretty job. No, I'm not going to prepare this just for recreational purposes because I do not have the time, and the community work I do should be spent in things the community can use... and I think that Eliot (who is, in fact, the one who can do this, I'm just a builder) will think similar :) >>>> >>>> So... if we have a vm running on iOS, why there is no a legion of fellow pharoers taking over the appstore? >>>> >>>> Well... because it is not enough. >>>> There are several problems, besides the vm working or not (to be fair, the interpreter vm works on iphone since at least two years, and John is the only one who succeed on pushing some nice smalltalk apps into the appstore). >>>> The main problem is that our morphic world is ok for desktop working, and some times for desktop commercial apps (like those of pinesoft), but it just can't be used to create real apps for the iPhone/iPad market. There are some exceptions, like some eToys work and probable the developing of games like "tic-tac-toe" or so... (I mean: graphic games who can be done with morphs). But as a general rule, you can't do a real app in pharo/squeak who runs in the iPhone/iPad and can be sold in the appstore. >>>> To overcome this problem, what John does is to create the full view in Cocoa, and "plug" the model to pharo/squeak images, using pharo as a module of a cocoa application. This can be done for several apps (and the fraction calculator is an example), but fails when you want a deeper interaction (because of the cost, not just in "programming time" but also the "translation time" between the cocoa app and pharo: it is just not good enough to bring a cool user experience (at least in all my experiments it was the case) >>>> >>>> There is another possible approach, who I think is the better in the long way, and that is what I was doing with Deimos project: using a bridge to construct, in pharo, real cocoa UI objects... the advantages with this are obvious. Nevertheless, there are also some problems with this approach: >>>> 1) last year I was working on this, and apple changed a clause. The result can be expressed as if they executed: 'deimos become: shit'. Months after they review the policy, but I was concentrated on Mars (the desktop equivalent to Deimos). I will continue this, but first I want to finish Mars, and also I need to solve the problem below: >>>> 2) there are also a performance problem with the ObjectiveC plugin and callbacks. In all my experiments, I never went below 70ms executing a callback from cocoa to pharo (and that's necessary, for example, to fill tables). The minimum time needed to have a cool "scroll" effect on tables is 40ms. Of course, iPhone 4 is better than 3gs... but the problem remains. The real thing is that ObjectiveC plugin relies on a semaphore communication model, and that's not good enough. So... I think the better approach here is to port FFI-Callback plugin (latest work of Eliot) to iOS. FFI-Callback plugin uses a whole different approach, who can overcome this performance issues (and some other who's not the case mention here). >>>> >>>> So... yes... I would love to finish this soon. But right now, other issues are top in priotity, and I just can't promise a release date. (Of course, the stackvm for iphone will be compiling on hudson some time soon... before ESUG for sure) >>>> >>>> hope this can explain all the status... :) >>>> >>>> cheers, >>>> Esteban >>>> >>>> El 25/05/2011, a las 11:56a.m., Igor Stasenko escribiÃ³: >>>> >>>>> On 25 May 2011 16:22, Steve Wirts <stevewirts(a)gmail.com> wrote: >>>>>> Hi All, >>>>>> Sorry if this topic has been covered in a previous email, I couldn't find >>>>>> anything conclusive so I'm posting it for my own clarity. >>>>>> I am a smalltalk programmer at heart but have been working in java at a java >>>>>> shop for sometime. Â Recently there's been a very strong directive from >>>>>> management to "get everything working on an iPad". >>>>>> I see a great opportunity to introduce pharo at the moment but need a way to >>>>>> deploy to iPad/iPhone devices. Â I'm not a c programmer and am overwhelmed at >>>>>> the thought of trying to build a cog vm for ios devices. >>>>>> >>>>>> Is there a binary package of cog vm for iPad/iPhone available somewhere? >>>>> >>>>> Ask Esteban! :) >>>>> >>>>> -- >>>>> Best regards, >>>>> Igor Stasenko AKA sig. >>>> >>>> >>>> >>> >>> >>> -- >>> Education 0.2 -- http://blog.ofset.org/hilaire >>> >>> >> >> >> > > > -- > Education 0.2 -- http://blog.ofset.org/hilaire > > > -- Best regards, Igor Stasenko AKA sig.

May 26, 2011

Re: [Pharo-project] Tiling windows

by GastÃ³n Dall' Oglio

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. > > - 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 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... > > - 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. > > 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

[Pharo-project] [update 1.3] #13216 (redone)

by Marcus Denker

***PLEASE USE THIS INSTEAD OF THE OTHER 13216*** 13216 ----- Issue 4276: Clean up ToolsBuilder a little... http://code.google.com/p/pharo/issues/detail?id=4276 Issue 4277: cleaning and fixing textMorph http://code.google.com/p/pharo/issues/detail?id=4277 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 26, 2011

Re: [Pharo-project] [Pharo-users] [update 1.3] #13216

by Marcus Denker

On Wed, May 25, 2011 at 10:15 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > 13216 > ----- > > - Â Issue 4277: Â cleaning and fixing textMorph. > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4277 > - Â Issue 4272: Â commandLineInput on Windows > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4272 > - Issue 4276: Â Clean up ToolsBuilder a little... > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4276 > - Issue 4233: Â to get stdout and others > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4233 > > you will get a popup but this is normal. There were some dirty packages and I did not see that > when I started. I will retract this update as it is broken. We will add the issues back later again in a new update (13217 likely, as I want to do a quick update to check that retracting was successful) -- Marcus DenkerÂ --Â denker(a)acm.org http://www.marcusdenker.de

May 26, 2011

[Pharo-project] Changes in SerialPort, VM and image [WAS] Re: [Vm-dev] Re: Questions of understanding

by Mariano Martinez Peck

On Thu, May 26, 2011 at 3:58 AM, David T. Lewis <lewis(a)mail.msen.com> wrote: > > For the SerialPlugin, there are two enhancements that will be found > in VMMaker and Squeak that should be added to Cog and to Pharo: > > 1) The named serial port updates are documented at > <http://bugs.squeak.org/view.php?id=7266> > > 2) A separate bug fix for SerialPlugin on Unix is at > <http://bugs.squeak.org/view.php?id=7610> > > The VMMaker updates are in class SerialPlugin. These can probably > be copied directly from VMMaker trunk to the oscog branch using an > MC browser. > > The platforms source changes can probably be copied directly from > Subversion trunk to the branches/cog tree, although I have not looked > at them to verify this (the platforms cog branch has changes in various > places, so some merging might be required). Note that the platforms > changes must be supported for all platforms, not just unix. > > I think that the image changes have already been copied from Squeak > to Pharo. If not, just copy class SerialPort. > > Thanks a lot Dave for the detailed answer :) > Dave > > On Wed, May 25, 2011 at 10:41:33AM +0200, Mariano Martinez Peck wrote: > > > > I have no idea. Maybe someone in the VM mailing list can help you. > > > > Cheers > > > > 2011/5/25 Friedrich Dominicus <frido(a)q-software-solutions.de> > > > > > Mariano Martinez Peck <marianopeck(a)gmail.com> writes: > > > > > > > > https://gitorious.org/cogvm/blessed/blobs/master/platforms/unix/plugins/ > > > > SerialPlugin/sqUnixSerial.c > > > This code contains the old implementaton of the Serial Plugin not the > > > extensions of things like openPortByName. The Serail Plugin I'm talking > > > about has the following implementation on the Smalltalk Size > > > > > > > > > > > > -- > > > Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim > > > Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus > > > > > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

May 26, 2011

Re: [Pharo-project] [Seaside] Re: Re: ESUG SummerTalk - Fuel, binary object serializer

by Martin Dias

Hi Yanni, On Wed, May 25, 2011 at 1:10 PM, Yanni Chiu <yanni(a)rogers.com> wrote: > On 25/05/11 11:53 AM, Mariano Martinez Peck wrote: > >> >> Sorry Yanni, I didn't follow. Could you please explain a bit more? what >> do you want to serialize? do you want to be able to choose some classes >> as light and some as non-light? where do you want to materialize ? in >> the same image or in another one ? When you said discard....what would >> you do with the instances of those non-light classes for example? you >> don't materialize them? and what happens to the objects that were >> pointing to them ? why would be the scenario useful for ? security ? >> > > ==== > Yes, security. Here's my first post again, with different formatting: > > In another use case, I'd like to serialize from one image, and deserialize > in another image - *under end user control*. [e.g. web app] > > > The issue here is that "nasty" code could be introduced: > - capture the Fuel output > - deserialize, add nasty code, re-serialize > - then send onward for import to image. > > Would it be possible to have some sort of "virus" filter? > ==== > > So a simple "safe-mode" option on de-serialization would probably be > sufficient. It is a good point. For the moment, when you deserialize a full class into the image, their methods are created, and bytecodes are copied from the stream without any validation check. Anyway, you could deserialize the class, run your own validations, and then install the class (I mean, add the class to Smalltalk globals, do the class initialization, run announcements). > > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >

May 26, 2011

Re: [Pharo-project] Do we freeze 1.3?

by Igor Stasenko

On 25 May 2011 19:50, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On May 25, 2011, at 7:41 PM, laurent laffont wrote: > >> Is 1.3 will be a release of one or two images finally ? >> > > Two, as changing it would mean doing that instead of a release. (remember, a "release" is just a snapshot of what is done, it > should never require anything do be done other than what is there. Hmm... don't know if that's understandable ;-) > Clearly.. > So we just freeze what is ther *now*, and then move on to 1.4. And there than we can do things. > > >> Laurent >> >> >> On Wed, May 25, 2011 at 11:29 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> Hello, >> >> 1.3 seems to stabilize... >> >> Â Â Â Â http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.3 >> >> just 12 issues left. >> >> We could freeze soon. >> >> >> -- >> Marcus Denker Â -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> >> > > -- > Marcus Denker Â -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > -- Best regards, Igor Stasenko AKA sig.

May 26, 2011

Re: [Pharo-project] Tiling windows

by laurent laffont

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 - 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 ...... - I will add tests to TWMBar finally as it seems to grow - I want TilingWM to be 100% test coverage - Balloon and spaces for TWMBar is a good idea - we need to make this work effectively :) - Great to have all the buttons per type of applications ! 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 GastÃ³n Dall' Oglio

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