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

Re: [Pharo-project] changes with announcements ?

by Igor Stasenko

On 27 May 2011 12:05, Cyrille Delaunay <cy.delaunay(a)gmail.com> wrote: > Hello, > Today I experimented some strange behaviours with announcements that I > didn't have in some previous moose images (moose in now based on Pharo > 1.3). > I think that there was some changes related to announcements in pharo > recently, but I could not be sure it is related. > At one point in my code I have: > browser on: AnnouncementClass send: #actionSelector > browser announce: anAnnouncementClass. > .... > .... > The behaviour I have is like if #actionSelector was executed asynchronously > from the rest of the code below 'browser announce: ...' . > Not sure but there is maybe something with exception signals. If any signal > is emited in #actionSelector it will not execute the rest of the method. > I was at least able to write a test that do not pass in latest pharo 1.3 > Gofer new > squeaksource: 'DelaunayTmpStuffs'; > package: 'ExampleAnnouncementProblems'; > load. It was because on:fork: cuts the stack. If you signaling exception in your code, you should handle it before leaving your #actionSelector method. Otherwise you may put the rest recipients of announcement in danger and that's why there #on:fork: to prevent that. -- Best regards, Igor Stasenko AKA sig.

May 27, 2011

[Pharo-project] [update 1.3] #13219

by Marcus Denker

13219 ----- Issue 4294: With only one Paragraph class, there is no need for #paragraphClass http://code.google.com/p/pharo/issues/detail?id=4294 Issue 4272: commandLineInput on Windows http://code.google.com/p/pharo/issues/detail?id=4272 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 27, 2011

[Pharo-project] 1.3 vs. 1.4

by Marcus Denker

Hi, I defined a 1.4 milestone and move things there: http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.4 We have the following things in 1.3: 4087 UndefinedObject(Object)>>doesNotUnderstand: #findNextHandlerContextStarting 3167 Workspace loading from a file, file chooser ignores path 3974 [RPackage] rpackage do not update when adding a category 4209 Transcipt could still be improved a little more 4287 Two tests related to on:fork: fail in Hudson 4296 Strange behavior with announcements 4236 MultiByteFileStream doing double conversion on windows 3341 use #= for integer comparison instead of #== 1907 Set with nil 1915 Making ToolSet more flexible 2986 DemoMode should not change Fonts only sizes 3917 Make all uses of SystemWindow go thru UIManger. 4233 to get stdout and others http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.3 Some of these I think we should consider to move to 1.4 and focus on getting 1.3 stable... -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 27, 2011

Re: [Pharo-project] changes with announcements ?

by Cyrille Delaunay

I entered an Issue: http://code.google.com/p/pharo/issues/detail?id=4296 2011/5/27 Cyrille Delaunay <cy.delaunay(a)gmail.com> > Hello, > > Today I experimented some strange behaviours with announcements that I > didn't have in some previous moose images (moose in now based on Pharo > 1.3). > I think that there was some changes related to announcements in pharo > recently, but I could not be sure it is related. > > At one point in my code I have: > > browser on: AnnouncementClass send: #actionSelector > browser announce: anAnnouncementClass. > .... > .... > > The behaviour I have is like if #actionSelector was executed asynchronously > from the rest of the code below 'browser announce: ...' . > Not sure but there is maybe something with exception signals. If any signal > is emited in #actionSelector it will not execute the rest of the method. > > I was at least able to write a test that do not pass in latest pharo 1.3 > > Gofer new > squeaksource: 'DelaunayTmpStuffs'; > package: 'ExampleAnnouncementProblems'; > load. >

May 27, 2011

[Pharo-project] changes with announcements ?

by Cyrille Delaunay

Hello, Today I experimented some strange behaviours with announcements that I didn't have in some previous moose images (moose in now based on Pharo 1.3). I think that there was some changes related to announcements in pharo recently, but I could not be sure it is related. At one point in my code I have: browser on: AnnouncementClass send: #actionSelector browser announce: anAnnouncementClass. .... .... The behaviour I have is like if #actionSelector was executed asynchronously from the rest of the code below 'browser announce: ...' . Not sure but there is maybe something with exception signals. If any signal is emited in #actionSelector it will not execute the rest of the method. I was at least able to write a test that do not pass in latest pharo 1.3 Gofer new squeaksource: 'DelaunayTmpStuffs'; package: 'ExampleAnnouncementProblems'; load.

May 27, 2011

Re: [Pharo-project] [Pharo-users] [COTDC] 68#2 MultiTextComposer

by Alain Plantec

yes, this is exactly what I was thinking about. but I will first comment for 1.3 cleaning is more for 1.4 now that 1.3 is about to be freezed. Alain Le 27/05/2011 08:31, Marcus Denker a Ã©crit : > On May 26, 2011, at 10:34 PM, laurent laffont wrote: > >> Alain, you know this too :) ? >> >> Laurent >> >> On Wed, May 25, 2011 at 10:51 PM, laurent laffont<laurent.laffont(a)gmail.com> wrote: >> Today: MultiTextComposer > One of the problems of the text rendering stuff is that the internationalization was just hacked > on top but never integrated. > > e.g. there is > > NewParagraph / MultiNewParagraph > TextComposer / MultiTextComposer > > and two CharacterScanner hierarchies (MultiCharacterScanner , CharacterScanner) > that seem to be copies yet randomly are used both... > > Just cleaning up would help a lot. And I would not be astonished if it would get even > faster just by cleaning up. (e.g. I removed an isKindOf: MultiNewParagraph from the main > text display routine yesterday...) > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

May 27, 2011

Re: [Pharo-project] [Pharo-users] [COTDC] 68#2 MultiTextComposer

by Marcus Denker

On May 26, 2011, at 10:34 PM, laurent laffont wrote: > Alain, you know this too :) ? > > Laurent > > On Wed, May 25, 2011 at 10:51 PM, laurent laffont <laurent.laffont(a)gmail.com> wrote: > Today: MultiTextComposer One of the problems of the text rendering stuff is that the internationalization was just hacked on top but never integrated. e.g. there is NewParagraph / MultiNewParagraph TextComposer / MultiTextComposer and two CharacterScanner hierarchies (MultiCharacterScanner , CharacterScanner) that seem to be copies yet randomly are used both... Just cleaning up would help a lot. And I would not be astonished if it would get even faster just by cleaning up. (e.g. I removed an isKindOf: MultiNewParagraph from the main text display routine yesterday...) Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 27, 2011

Re: [Pharo-project] Tiling windows

by laurent laffont

Now added top window placement Ã la OptimizeLayout. Need to find nice icons. Someone ? Laurent. 2011/5/26 GastÃ³n Dall' Oglio <gaston.dalloglio(a)gmail.com> > :) > > > 2011/5/26 laurent laffont <laurent.laffont(a)gmail.com> > >> - Now loads in PharoCore >> - more tests >> - fill all space even if number of windows is not square. >> >> 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/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 27, 2011

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

by Marcus Denker

On May 26, 2011, at 11:24 PM, StÃ©phane Ducasse wrote: > marcus > > I can check the problem that stefan mentioned since I should change anyway the initialize method > Ok, so I focus on other things from the list: http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.3 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 27, 2011

[Pharo-project] [update 1.3] #13218

by Marcus Denker

13218 ----- Issue 4289: TextLineInterval only referenced from unsent methods http://code.google.com/p/pharo/issues/detail?id=4289 Issue 4288: Remove unneeded check in #currentCursor: http://code.google.com/p/pharo/issues/detail?id=4288 Issue 4278: cleanup methods not needed... http://code.google.com/p/pharo/issues/detail?id=4278 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 27, 2011