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

Re: [Pharo-project] free fonts

by Michael van der Gulik

On Mon, Dec 1, 2008 at 12:33 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > > On Nov 30, 2008, at 10:35 , StÃ©phane Ducasse wrote: > > http://www.pinvoke.com/font/ >> >> I think that for the demo mode we should get a better font since italic "" >> is not working well. >> > > Yes, and not only for the demo font, but *all* default fonts should be > reconsidered now that we have the machinery in place. > > I don't think that the fonts of www.pinvoke.com/font/ are particularly > well suited. > > From a mail I sent on September 22, considering the code font I wrote: > > I think Bitstream Vera Sans Mono would be quite good. > I slightly prefer Monaco, which is shipped with OS X, but I don't know its > license (http://en.wikipedia.org/wiki/Monaco_(typeface)<http://en.wikipedia.org/wiki/Monaco_%28typeface%29> > ). > > For an evaluation of programmer fonts see http://www.lowing.org/fonts/ > Another list can be found here: > http://wiki.macromates.com/Main/AlternativeFonts > The latter list, for example includes > http://www.ms-studio.com/FontSales/anonymous.html which looks nice too. > A variable-width font should be used rather than fixed-width fonts. Smalltalk has always used variable-width fonts; it makes stuff easier to read. When deciding on a font, you need to keep in mind the vertical positioning of the hash, colon, asterisk, up-arrow and left-arrow (if used) with respect to the text they precede or follow. Otherwise your 5*5 (multiplication, should be 5Ã5), #symbols, selectors:, variable â assignments, â return values etc can look silly. Gulik. -- http://people.squeakfoundation.org/person/mikevdg http://gulik.pbwiki.com/

Nov. 30, 2008

[Pharo-project] About ecompletion

by StÃ©phane Ducasse

Hi all I wanted to share that with you. I'm reading the PhD of Romain Robbes and he has an excellent chapter on measuring different strategies for code completion. One of the best algorithm is to keep a list with the recently modified methods and the messages they send. His benchmark shows a drastic improvement even compared with ecompletion with RoelTyper. So david do you store the recently modified methods globally for all the browsers? Is it easily accessible? He also mentioned that we get even better results by combining RoelTyper and then this approach... any taker? this is important to have much better editing tools. Stef

Nov. 30, 2008

[Pharo-project] [update] #10185

by Marcus Denker

- Issue 272: remove BOBTransformationMorph - Issue 356: Dockinbar broken (reason: ColorThemes) - Issue 269: FileList2 should be merged with FileList. (Fix provided by Hernan Morales) - Cleanups (etoys, unsent messages, preferences) - Postscript -- unloads packages: Installer, 39Deprecated, FlexibleVocablaries, Pinesoft-Removals-EToys, ToolBuilder-MVC -- remove preferences #timeStampsInMenuTitles #personalizedWorldMenu #abbreviatedBrowserButtons Here is a full list of removals: -------------------------------- FileList2, Everything from Installer* Smalltalk removeClassNamed: #Vocabulary! Smalltalk removeClassNamed: #BOBTransformationMorph! TilePadMorph removeSelector: #prepareToUndoDropOf:! TileMorph removeSelector: #scriptEdited! TilePadMorph removeSelector: #addCustomMenuItems:hand:! TilePadMorph removeSelector: #restoreDefaultTile! TilePadMorph removeSelector: #setToBearDefaultLiteral! TilePadMorph removeSelector: #setType:! TileMorph removeSelector: #slotName! StandardScriptingSystem removeSelector: #colorForType:! Slider removeSelector: #wantsSlot! SimpleHierarchicalListMorph removeSelector: #installModelIn:! PluggableTextMorph removeSelector: #installModelIn:! PluggableListMorph removeSelector: #installModelIn:! ScrollPane removeSelector: #wantsSlot! BlobMorph removeSelector: #installModelIn:! PolygonMorph removeSelector: #installModelIn:! PasteUpMorph removeSelector: #abandonVocabularyPreference! MorphicModel removeSelector: #compileAccessForSlot:! MorphicModel removeSelector: #compilePropagationMethods! MorphicModel removeSelector: #initString! MorphicModel removeSelector: #installModelIn:! MorphicModel removeSelector: #recomputeBounds! MorphicModel removeSelector: #slotName! MorphicModel removeSelector: #slotSelectorFor:! MorphicModel removeSelector: #wantsSlot! HandMorph removeSelector: #addKeyboardListener:! HandMorph removeSelector: #checkForMoreKeyboard! HandMorph removeSelector: #generateWindowEvent:! HandMorph removeSelector: #isCapturingGesturePoints! HandMorph removeSelector: #keyboardListeners:! HandMorph removeSelector: #removeKeyboardListener:! HandMorph removeSelector: #targetOffset:! Morph removeSelector: #altSpecialCursor3! Morph removeSelector: #beThisWorldsModel! Morph removeSelector: #choosePartName! Morph removeSelector: #imageFormWithout:andStopThere:! Morph removeSelector: #inAScrollPane! Morph removeSelector: #initString! Morph removeSelector: #installModelIn:! Morph removeSelector: #isModalShell! Morph removeSelector: #morphReport! Morph removeSelector: #morphReportFor:! Morph removeSelector: #morphReportFor:on:indent:! Morph removeSelector: #nameInModel! Morph removeSelector: #obtrudesBeyondContainer! Morph removeSelector: #okayToExtractEasily! Morph removeSelector: #textToPaste! Morph removeSelector: #yellowButtonGestureDictionaryOrName:! Preferences class removeSelector: #chooseInsertionPointColor! Preferences class removeSelector: #chooseKeyboardFocusColor! ColorTheme class removeSelector: #apply! ColorTheme class removeSelector: #applyTheme:! ColorTheme class removeSelector: #current:! ColorTheme class removeSelector: #defaultTheme! ColorTheme removeSelector: #apply! ColorTheme removeSelector: #balloonColor! ColorTheme removeSelector: #dark:! ColorTheme removeSelector: #defaultWorldColor! ColorTheme removeSelector: #dialogTextBoxBorderColor! ColorTheme removeSelector: #dialogTextBoxColor! ColorTheme removeSelector: #initialize! ColorTheme removeSelector: #insertionPointColor! ColorTheme removeSelector: #keyboardFocusColor! ColorTheme removeSelector: #labelForColor:! ColorTheme removeSelector: #light:! ColorTheme removeSelector: #textHighlightColor! CodeHolder removeSelector: #abbreviatedWordingFor:! Preferences class removeSelector: #abbreviatedBrowserButtons! Preferences class removeSelector: #chooseEToysFont! Preferences class removeSelector: #chooseEToysTitleFont! Preferences class removeSelector: #letUserPersonalizeMenu! Preferences class removeSelector: #personalizeUserMenu:! Preferences class removeSelector: #personalizedWorldMenu! Preferences class removeSelector: #timeStampsInMenuTitles! PasteUpMorph removeSelector: #yellowButtonClickOnDesktopWithEvent:! -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Nov. 30, 2008

Re: [Pharo-project] polymorph UI glitch

by Gary Chambers

Currently based on the default font. I'll change to use the relevant preferred font. Regards, Gary. ----- Original Message ----- From: "Igor Stasenko" <siguctua(a)gmail.com> To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> Sent: Sunday, November 30, 2008 4:19 PM Subject: Re: [Pharo-project] polymorph UI glitch > i'd like to add my 2 cents. > a diff-tools using odd fonts (or maybe not odd, but they look too > small as to me) > > http://picasaweb.google.com/lh/photo/4rpXn6Zdmv2QXkKu1m2Stg > > pharo 10166 > Polymorph-Tools-Diff-gvc.3 > windowz > > hmm.. maybe its because in font chooses i see only single font > available: Accuny :) > > Tried a more recent image - 10178, > a font chooser shows many true-type fonts (freetype working) > but still diff tools drawing text in same ugly font :( > > 2008/11/30 Gary Chambers <gazzaguru2(a)btinternet.com>: >> I've only seen that on existing windows in a fresh pickup of an image >> release... Not seen it with new windows. >> Tricky to track down what has caused the scrollbar frames to get >> misadjusted >> since new windows don't exhibit it. >> >> If you have found a case where a new window does this please pass along >> an >> image for investigation. >> >> Regards, Gary. >> >> ----- Original Message ----- From: "StÃ©phane Ducasse" >> <stephane.ducasse(a)inria.fr> >> To: "Pharo Development" <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Saturday, November 29, 2008 8:12 PM >> Subject: [Pharo-project] polymorph UI glitch >> >> >>> When I enlarged the window I got that. >>> >>> >> >> >> -------------------------------------------------------------------------------- >> >> >>> _______________________________________________ >>> 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 >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > -------------------------------------------------------------------------------- > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Nov. 30, 2008

Re: [Pharo-project] polymorph UI glitch

by Igor Stasenko

i'd like to add my 2 cents. a diff-tools using odd fonts (or maybe not odd, but they look too small as to me) http://picasaweb.google.com/lh/photo/4rpXn6Zdmv2QXkKu1m2Stg pharo 10166 Polymorph-Tools-Diff-gvc.3 windowz hmm.. maybe its because in font chooses i see only single font available: Accuny :) Tried a more recent image - 10178, a font chooser shows many true-type fonts (freetype working) but still diff tools drawing text in same ugly font :( 2008/11/30 Gary Chambers <gazzaguru2(a)btinternet.com>: > I've only seen that on existing windows in a fresh pickup of an image > release... Not seen it with new windows. > Tricky to track down what has caused the scrollbar frames to get misadjusted > since new windows don't exhibit it. > > If you have found a case where a new window does this please pass along an > image for investigation. > > Regards, Gary. > > ----- Original Message ----- From: "StÃ©phane Ducasse" > <stephane.ducasse(a)inria.fr> > To: "Pharo Development" <Pharo-project(a)lists.gforge.inria.fr> > Sent: Saturday, November 29, 2008 8:12 PM > Subject: [Pharo-project] polymorph UI glitch > > >> When I enlarged the window I got that. >> >> > > > -------------------------------------------------------------------------------- > > >> _______________________________________________ >> 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 > -- Best regards, Igor Stasenko AKA sig.

Nov. 30, 2008

Re: [Pharo-project] polymorph UI glitch

by Gary Chambers

I've only seen that on existing windows in a fresh pickup of an image release... Not seen it with new windows. Tricky to track down what has caused the scrollbar frames to get misadjusted since new windows don't exhibit it. If you have found a case where a new window does this please pass along an image for investigation. Regards, Gary. ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: "Pharo Development" <Pharo-project(a)lists.gforge.inria.fr> Sent: Saturday, November 29, 2008 8:12 PM Subject: [Pharo-project] polymorph UI glitch > When I enlarged the window I got that. > > -------------------------------------------------------------------------------- > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Nov. 30, 2008

Re: [Pharo-project] Bug when loading Seaside in 10178

by Gary Chambers

Finding the modal morph is quite tricky (requests for a dialog not specifically being tied to a system window), hence the trick! Clearly a few cases I missed... Will have a look. Regards, Gary. ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> Sent: Saturday, November 29, 2008 7:53 PM Subject: Re: [Pharo-project] Bug when loading Seaside in 10178 Apparently this is a problem with PSUIManager thisContext trick. We ended up with MCdefinitino compared using = with World. Stef On Nov 29, 2008, at 2:52 PM, Damien Pollet wrote: > Just loading Seaside 2.8a1 in pharo (core or dev, using universes or > MC) 10178, we get a strange from PSUIManager >> modalMorphâ¦ not clear > if it's pharo or MC or Seaside's faultâ¦ > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet > _______________________________________________ > 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

Nov. 30, 2008

Re: [Pharo-project] [ANN] prebuilt image #10178

by Gary Chambers

----- Original Message ----- From: "Marcus Denker" <denker(a)iam.unibe.ch> To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> Sent: Saturday, November 29, 2008 9:17 AM Subject: Re: [Pharo-project] [ANN] prebuilt image #10178 > > On 27.11.2008, at 22:26, Adrian Lienhard wrote: > >> Thanks for Polymorph, it rocks! :) >> >> On Nov 27, 2008, at 20:25 , Gary Chambers wrote: >> >>> My personal preference options, as different from the release... >>> >>> alternativeButtonsInScrollBars enabled >>> alwaysShowVScrollbar disabled >>> scrollBarsNarrow disabled >>> scrollBarsWithoutMenuButton enabled >>> mouseClickForKeyboardFocus enabled >> >> I like all the above preferences >> > yes! > >>> fadedBackgroundWindows disabled >> >> couldn't see a difference >> > > Only visible in Vistary. Only not much visible in Watery themes ;-) > >>> fastDragWindowForMorphic disabled (fast machine!) >>> fullScreenLeavesDeskMargins disabled >>> showSplitterHandles disabled >>> >>> useUndo disabled (potential cause of image cruft) >> >> I think undo is a must today (so if there is a problem we should try to >> fix it) > > This is morphic undo, not text-undo. > Indeed. Many time I have been hunting the obsoletes only to find them in the history... >> >> >>> generalizedYellowButtonMenu disabled (allows menu for taskbar items, >>> can override using Ctrl key) >>> >>> Additionally some might like showTextEditingState enabled, not me >>> though! >> >> I need this one, else I always get confused because I forget to save >> methods >> Preferences enable: #showTextEditingState >> >> These are the other preferences from above: >> >> Preferences enable: #alternativeButtonsInScrollBars. >> Preferences disable: #alwaysShowVScrollbar. >> Preferences disable: #scrollBarsNarrow. >> Preferences enable: #scrollBarsWithoutMenuButton. >> Preferences enable: #mouseClickForKeyboardFocus. >> Preferences disable: #fadedBackgroundWindows. >> Preferences disable: #fastDragWindowForMorphic. >> Preferences disable: #fullScreenLeavesDeskMargins. >> Preferences disable: #showSplitterHandles. >> Preferences enable: #generalizedYellowButtonMenu >> Preferences enable: #showTextEditingState >> >> Furthermore, I vote for: >> Preferences enable: #noWindowAnimationForClosing >> Preferences disable: #windowAnimation >> Preferences setPreference: #GlyphContrast toValue: 55 >> >> I really like the Watery 2 look (the style of the buttons could be >> improved, though). >> > Aye, buttons are tricky... mainly having them scale in size if forms are used (like the scrollbars) as opposed to gradients. Graidents are failry limited in the absence of performant generalised clipping shapes. Will get done eventually (to use forms). > Yes. > >> Cheers, >> Adrian >> >>> >>> >>> Regards, Gary. >>> >>> ----- Original Message ----- From: "Marcus Denker" <denker(a)iam.unibe.ch >>> > >>> To: "Pharo Development" <Pharo-project(a)lists.gforge.inria.fr> >>> Sent: Thursday, November 27, 2008 3:38 PM >>> Subject: [Pharo-project] [ANN] prebuilt image #10178 >>> >>> >>>> https://gforge.inria.fr/frs/download.php/11844/ Pharo0.1Core-10178.zip >>>> -- >>>> Marcus Denker -- denker(a)iam.unibe.ch >>>> http://www.iam.unibe.ch/~denker >>>> >>>> >>>> _______________________________________________ >>>> 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 >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Marcus Denker -- denker(a)iam.unibe.ch > http://www.iam.unibe.ch/~denker > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 30, 2008

Re: [Pharo-project] free fonts

by David Mitchell

Please don't include any font with ambiguous licensing! Wouldn't want to bring back a fonts clause to the license! On Sun, Nov 30, 2008 at 5:33 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > > On Nov 30, 2008, at 10:35 , StÃ©phane Ducasse wrote: > >> http://www.pinvoke.com/font/ >> >> I think that for the demo mode we should get a better font since italic "" >> is not working well. > > Yes, and not only for the demo font, but *all* default fonts should be > reconsidered now that we have the machinery in place. > > I don't think that the fonts of www.pinvoke.com/font/ are particularly well > suited. > > From a mail I sent on September 22, considering the code font I wrote: > > I think Bitstream Vera Sans Mono would be quite good. > I slightly prefer Monaco, which is shipped with OS X, but I don't know its > license (http://en.wikipedia.org/wiki/Monaco_(typeface)) > > For an evaluation of programmer fonts see http://www.lowing.org/fonts/ > Another list can be found here: > http://wiki.macromates.com/Main/AlternativeFonts > The latter list, for example includes > http://www.ms-studio.com/FontSales/anonymous.html which looks nice too. > > Adrian > > >> >> Now it would be great to have a set of free font for pharo. >> >> stef >> >> _______________________________________________ >> 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 >

Nov. 30, 2008

Re: [Pharo-project] OB Button colors

by Gary Chambers

It depends on the theme used. The Watery ones specifically standardise the window colours... I notice that OB does a lot to force colours rather than relying on the paneColor, hence the mismatches. Also, a few cases of #adoptPaneColor: where the superclass implementation is not called. I'm sure we can work together to iron out the wrinkles. Regards, Gary. ----- Original Message ----- From: "David RÃ¶thlisberger" <squeak(a)webcitas.ch> To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> Sent: Friday, November 28, 2008 1:16 PM Subject: Re: [Pharo-project] OB Button colors > >> When loading polymorph with Watery2 theme and SuperOB using the >> ScriptLoader the buttons in OB tend to become green again after some >> clicking ... > > hm, Polymorph doesn't seem to honor what you specify in > #defaultBackgroundColor of a model object for SystemWindow. Instead it > always uses this gray color, while OB is thinking that the default > background color it specifies gets used. > This is a problem of Polymorph I think, so I won't fix that in OB. > > Cheers, > David > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 30, 2008