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

Re: [Pharo-project] Announcement real problems - please read and comment.

by StÃ©phane Ducasse

Gofer new squeaksource: 'PharoTaskForces'; package: 'ConfigurationOfRPackage'; load ConfigurationOfRPackage project load: '1.0' load RPackage in latest 1.3 Stef On Apr 1, 2011, at 10:36 PM, Henrik Sperre Johansen wrote: > On 01.04.2011 21:07, StÃ©phane Ducasse wrote: >> Hi guys >> >> We found a problem with ben and RPackage. >> Here is the scenario and may be you can help us finding the right solutions. >> >> Nautilus renames a class >> the class got renamed >> -> an announcement is raised >> - nautilus gets notified, it asks rpackageOrganizer (which also listens to the same event) >> -> rpackageOrg breaks because the class if was referting to does not exist anymore. > This sounds like mess in logic. > You ask package of class that is in the process of being renamed? > Why would you expect this to work? > Use more announcements to represent multiple steps in renaming process, for example both ClassRenaming and ClassRenamed. > Changing it's package is something you do as an action that should be _part_ of renaming, while updating it's location is something you would do _after_ renaming is complete. > >> Problem 2 >> If rappckageOrganizer would be reached before Nautilus we would not get any problem (beside the problem 1). >> >> - we spent one hour playing with alternatives. >> We thought that if RPackage would points to classes a rename would not break the system. >> While this is true for class, the same problem will occur for method rename since compiled method are not shared and a new compiled method >> is compiled. >> >> - If RPackage was as deep inside the system as superclass/subclass, the invariant would be directly maintained by the system >> and we would not have to rely on announcement. But now we should find a solution. >> >> >> may be we should be able to say that an announcement has a priority. >> Typically we would like to say that when RPackageOrganizer register interests it should be served first. >> we could have a systemLevel priority that could be specified on registration. >> >> what do you think? > Bad, bad, bad, bad, baaaaaad idea. > I know from experience that once you concede that announcement listener order should matter, you are setting yourself up to fail. > Although you know one listener _HAS_ to respond first, there will always be someone else who want to respond "firstester". > Not to mention the logic in this case becomes next to impossible to follow/debug/ maintain, as you've already experienced. > > For a proper solution, introduce more Announcements for actions which should happen in different phases of a process, as explained above. > > Cheers, > Henry > > PS. I was unable to load RPackage. > The initialize method of PackageOrganizer in RPackage-Core calls registerInterestToSystemAnnouncement, which is an extensions in RPackage-SystemIntegration. > > PPS. There's a neat method called #on:send:to:, which would be perfect for the different actions in RPackage-SystemIntegration. > > PPPS. Is the code for Nautilus available anywhere? >

April 2, 2011

Re: [Pharo-project] Issue 3854 in pharo: Move taskbar methods from Project to PasteUpMorph

by pharo＠googlecode.com

Updates: Status: Closed Comment #3 on issue 3854 by marcus.d...(a)gmail.com: Move taskbar methods from Project to PasteUpMorph http://code.google.com/p/pharo/issues/detail?id=3854 in 13130

April 2, 2011

Re: [Pharo-project] Issue 3938 in pharo: Fix ugly flashing in list morph

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3938 by marcus.d...(a)gmail.com: Fix ugly flashing in list morph http://code.google.com/p/pharo/issues/detail?id=3938 in 13130

April 2, 2011

Re: [Pharo-project] Issue 3921 in pharo: due to *graphics package, we lost some string changes

by pharo＠googlecode.com

Updates: Status: Closed Comment #4 on issue 3921 by marcus.d...(a)gmail.com: due to *graphics package, we lost some string changes http://code.google.com/p/pharo/issues/detail?id=3921 in 13130

April 2, 2011

Re: [Pharo-project] Issue 3938 in pharo: Fix ugly flashing in list morph

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #1 on issue 3938 by marcus.d...(a)gmail.com: Fix ugly flashing in list morph http://code.google.com/p/pharo/issues/detail?id=3938 (No comment was entered for this change.)

April 2, 2011

Re: [Pharo-project] Issue 3921 in pharo: due to *graphics package, we lost some string changes

by pharo＠googlecode.com

Updates: Status: FixToInclude Labels: Milestone-1.3 Comment #3 on issue 3921 by marcus.d...(a)gmail.com: due to *graphics package, we lost some string changes http://code.google.com/p/pharo/issues/detail?id=3921 lost method attached Attachments: String-displayOnattextColor.st 389 bytes

April 2, 2011

Re: [Pharo-project] who is using softSqueak and standard Squeak

by laurent laffont

On Sat, Apr 2, 2011 at 10:14 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Apr 2, 2011, at 9:55 AM, laurent laffont wrote: > > Patrick, > > I think we should have a ConfigurationOfPharoThemes with all the themes you > have made + current ones. I can help (may be a good subject for a our weekly > coding-dojo) > > PharoCore should have only one theme I think. > > > And in turn this means that pharo full has *all* of them? Nonono... it has > already *far* too much stuff nobody cares about. > I'm not saying that Pharo should have all of them. We can have: - ConfigurationOfPharoThemes project latestVersion load:#default => load the most used themes (ex: Glamour + Watery2) - for Pharo Full - ConfigurationOfPharoThemes project latestVersion load:#softSqueak for the few (?) people who want to use softSqueak for example. So ConfigurationOfPharoThemes will be an easy way to reference all working themes Laurent. > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

April 2, 2011

Re: [Pharo-project] fancier tab morph

by StÃ©phane Ducasse

Excellent I like the idea that the widgets gradually improves (as all the other parts of the system). Stef On Apr 2, 2011, at 9:30 AM, Tudor Girba wrote: > This would be the idea. Gary has reviewed it briefly and said that it looks Ok and we should integrate it in the TabMorph (right now I use subclassing). > > Gary said that he will take a closer look at it soon. > > Cheers, > Doru > > > On 2 Apr 2011, at 09:25, StÃ©phane Ducasse wrote: > >> Doru what about integrating it in 1.3? >> >> Stef >> >> On Apr 2, 2011, at 8:34 AM, Tudor Girba wrote: >> >>> Hi, >>> >>> In the context of Glamour, I worked on a Morphic tab widget a bit more and here is the status (see the screenshots for some examples): >>> - it computes the pages lazily only when you want to first show the page >>> - it provides the possibility of closing the tab >>> - it offers the possibility of rendering a toolbar for each page displayed to the right of the pages. >>> >>> If you want to play with them, you can: >>> - download the latest moose image: >>> http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/… >>> >>> - execute the following to get an example of closable tabs: >>> GLMBasicExamples new accumulator openOn: 42 >>> >>> - execute the following to get an example of tabs with different toolbars attached (to the right): >>> GLMBasicExamples new tabsWithDifferentActions openOn: 42 >>> >>> >>> There are still a couple of issues left: >>> - When the title of a tab is too large, it pushes the bounds of the pane beyond what is visible. >>> - Also, when we have multiple tabs, they again go overboard. >>> - Similar things happen with the toolbar. >>> >>> However, the good news is that Gary is looking into this :) >>> >>> Cheers, >>> Doru >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Relationships are of two kinds: those we choose and those that happen. They both matter." >>> >>> <ClosableTab.png><TabWithActions.png> >> >> > > -- > www.tudorgirba.com > > "Presenting is storytelling." > >

April 2, 2011

Re: [Pharo-project] who is using softSqueak and standard Squeak

by Marcus Denker

On Apr 2, 2011, at 9:55 AM, laurent laffont wrote: > Patrick, > > I think we should have a ConfigurationOfPharoThemes with all the themes you have made + current ones. I can help (may be a good subject for a our weekly coding-dojo) > > PharoCore should have only one theme I think. > And in turn this means that pharo full has *all* of them? Nonono... it has already *far* too much stuff nobody cares about. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 2, 2011

Re: [Pharo-project] who is using softSqueak and standard Squeak

by laurent laffont

Patrick, I think we should have a ConfigurationOfPharoThemes with all the themes you have made + current ones. I can help (may be a good subject for a our weekly coding-dojo) PharoCore should have only one theme I think. Laurent. On Sat, Apr 2, 2011 at 9:24 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > Thanks. I will remove the old theme and keep this one. > > Stef > On Apr 2, 2011, at 1:24 AM, Patrick Barroca wrote: > > > Hello, > > > > > > I published the theme on squeaksource, it loads in 1.2 and 1.3. > > Repo is http://www.squeaksource.com/PBASandbox > > > > I named it StandardUITheme, > > > > > > > > On Fri, Apr 1, 2011 at 8:57 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > > Thanks > > > > I want to rename, repackage, glamourous and remove the bubble oriented > color squeak look and keep one old sq colored for now. > > On Apr 1, 2011, at 3:04 PM, Patrick Barroca wrote: > > > > > Hello, > > > > > > Just to say that I have now a simple theme extending UITheme with the > look of Glamourous and the support of squeak windows colour management. > > > > > > Since I worked in 1.2 I have yet to verify how this load in Pharo 1.3 > and then I will publish it ;) > > > > > > On Wed, Mar 30, 2011 at 3:50 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > > > > My first look yesterday night taught me that different windows colour > management is a basic behaviour of UITheme via #patchworkUIThemeColorFor:. > > > > If I simply subclass UITheme and do nothing more I get more or less a > standard squeak theme with coloured windows minus some fills and borders > styles. > > > > > > > > From here I think I could try to make a simple theme with the look of > Glamourous one with support for squeak windows colour management. > > > > Is this the right direction ? > > > > > > yes :) > > > I plan to refactor/clean the theme package too. > > > So if you have results let us know. > > > > > > Stef > > > > > > > > > > > > -- > > > Patrick Barroca > > > > > > > > > > -- > > Patrick Barroca > > <PharoScreenshot.2.png> > > >

April 2, 2011