July 2008 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] How to see the changes of a particular slice?

by Norbert Hartl

On Wed, 2008-07-23 at 10:05 +0200, Damien Cassou wrote: > Hi, > > is there a way to see all the changes that are included in a > particular SLICE? Clicking on Changes does not show anything, which > seems ok because the package is empty. Use "merge". That shows you the complete changes for all dependent packages . Norbert

July 23, 2008

[Pharo-project] How to see the changes of a particular slice?

by Damien Cassou

Hi, is there a way to see all the changes that are included in a particular SLICE? Clicking on Changes does not show anything, which seems ok because the package is empty. -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

July 23, 2008

Re: [Pharo-project] Problem with July release

by Michael Rueger

Adrian Lienhard wrote: > Hi Damien, > > It looks like a MC load problem because the method was moved from a > method extension from the EToys package into the Morph package when it > was changed due to a patch. Also in my image that I built from the > update stream the method was lost although the Morphic package was loaded. > > I just published the package again to the inbox so in the next update > the method will come back. I updated #123 to track this change. > > I also Verified your change > http://code.google.com/p/pharo/issues/detail?id=118 The only way to reliably avoid these problems to load both packages through a config map. Michael

July 22, 2008

Re: [Pharo-project] Improving the GUI

by StÃ©phane Ducasse

On Jul 21, 2008, at 11:22 AM, Janko MivÅ¡ek wrote: > Dear all, > > I remember well my first impression with Squeak a year or so ago and > all troubles I had then and have them actually still. > > Yes, it is a look&feel problem. And more feel than look. Look are > fonts etc. while feel are menus, basic window handling, mouse > buttons, controls behaving as closer to target OS as user is > accustomized of, user interface consistency and behavior as > expected, etc. > > I therefore propose to start with "feel" part of user experience > first and my priority would be: > > - swapMouseButtons preset depending on target OS (this one is > probably the most annoying thing for newcomers!) > - window controls (minimize/maximize, close) and their order > more in line with mainstream rules > - better menus as Adrian proposed > - more overall consistency of menus (for instance: inspect/explore > always on the same place in menu: or on the top or on the bottom) > - merging inspector into explorer and having only Inspect > - ctrl-mouse left behavior = select! (also very annoying one!) > - do we really need those window controls, coming up with ctrl-left > mouse? (rotate etc? halos?) Yes I always wanted to disable them. > > > Those feel troubles I have are on Linux and mostly the same on > Windows but are probably different on Mac. > > Best regards > Janko > > > Adrian Lienhard wrote: >> Hi, >> I'd like to get your opinion about how we could improve the GUI. I >> believe that even a few small changes will make a significant >> difference, especially for new people that come to Pharo. Just the >> cleaned up world menu is such a relief... >> Here a three suggestions: >> Better fonts >> ---------------- >> I think the current code font is not a good one and it is too small >> (for today's screen resolutions). I like for example the font used >> in TextMate, which is Monaco 12, a monotype font. The page http://www.lowing.org/fonts/ >> gives some samples for good code fonts. I've tried out the other >> fonts in the Pharo image like the BitstreamVeraSansMono but they >> are all very blurry. Just not good enough. I'm not a font expert, >> so I don't know what the options for a better font are. >> Better menus >> ------------------------------- >> Current problems: >> - bad organization menus only work when you have learned where >> something is located >> - duplicated entries e.g., Appearance is both in the top level >> world menu and in the submenu Help >> - useless entries e.g., set font, set style etc. in the >> context menu are useless since code is never styled >> - defective entries: e.g., "Make project link" in the context >> menu does not work >> Larger windows >> ------------------------------- >> The default size of windows is usually too small. Often, after >> opening a window I have to resize it. For example the hierarchy >> browser shows only the 5 first classes. >> Any other ideas what could be improved in the short term? I'm >> looking for stuff that we can do now without having to rewrite the >> whole system... >> Cheers, >> Adrian >> ___________________ >> http://www.adrian-lienhard.ch/ >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Janko MivÅ¡ek > Svetovalec za informatiko > Eranova d.o.o. > Ljubljana, Slovenija > www.eranova.si > tel: 01 514 22 55 > faks: 01 514 22 56 > gsm: 031 674 565 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 22, 2008

[Pharo-project] Fwd: Feedback

by StÃ©phane Ducasse

Begin forwarded message: > From: David RÃ¶thlisberger <squeak(a)webcitas.ch> > Date: July 21, 2008 1:44:23 PM CEDT > To: OmniBrowser developers <ob-dev(a)wiresong.ca> > Subject: Re: Feedback > Reply-To: OmniBrowser developers <ob-dev(a)wiresong.ca> > > > >> could you publish a new complete list of packages and their versions? > > here it is: > > > Installer wiresong > project: 'ob'; > install: 'OmniBrowser-dr.413'; > install: 'OB-Morphic-dr.49'; > install: 'OB-Standard-dr.344'; > install: 'OB-Enhancements-dr.191'; > install: 'OB-Refactory-lr.85'. > > > David > _______________________________________________ > ob-dev mailing list > ob-dev(a)wiresong.ca > http://mail.wiresong.ca/mailman/listinfo/ob-dev >

July 22, 2008

[Pharo-project] Some more work on #115 "Remove old HTML generation"

by Adrian Lienhard

Hi Damien I worked a bit more on this and did the following: in addition to previous version by Damien - remove #command: senders and implementors - remove method references to deleted methods in MessageFinder - remove String>>asHtml, which in turn required to... - remove an etoys related mail message class (FancyMailComposition), which required to - remove some code in EToys (tell a friend feature) Do you want to have a look what I did? I changed the issue back to Fixed for now. http://code.google.com/p/pharo/issues/detail?id=115 Adrian

July 22, 2008

Re: [Pharo-project] Problem with July release

by Adrian Lienhard

Hi Damien, It looks like a MC load problem because the method was moved from a method extension from the EToys package into the Morph package when it was changed due to a patch. Also in my image that I built from the update stream the method was lost although the Morphic package was loaded. I just published the package again to the inbox so in the next update the method will come back. I updated #123 to track this change. I also Verified your change http://code.google.com/p/pharo/issues/detail?id=118 Cheers, Adrian On Jul 22, 2008, at 12:03 , Adrian Lienhard wrote: > Thanks for pointing out. Will have a look in the evening. > Adrian > > On Jul 22, 2008, at 09:22 , Damien Cassou wrote: > >> See http://code.google.com/p/pharo/issues/detail?id=123 >> >> -- >> Damien Cassou >> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good >> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 22, 2008

Re: [Pharo-project] Problem with July release

by Adrian Lienhard

Thanks for pointing out. Will have a look in the evening. Adrian On Jul 22, 2008, at 09:22 , Damien Cassou wrote: > See http://code.google.com/p/pharo/issues/detail?id=123 > > -- > Damien Cassou > Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 22, 2008

[Pharo-project] Problem with July release

by Damien Cassou

See http://code.google.com/p/pharo/issues/detail?id=123 -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

July 22, 2008

Re: [Pharo-project] Google code RSS feeds

by Norbert Hartl

On Mon, 2008-07-21 at 23:27 +0200, Adrian Lienhard wrote: > There are now RSS feeds available to track the issues or wiki changes. > See http://google-code-updates.blogspot.com/2008/07/new-feeds-for-project-hosti… > Very good. This way you can easily get the comments people make :) One reason to use a rss reader after years. http://code.google.com/feeds/p/pharo/issueupdates/basic Great, Norbert

July 22, 2008