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

[Pharo-project] Re: Re: Re: [ANN] Demo with both Truetype +Polymorph

by Andrew Tween

Note that with a one-click app distribution, it isn't necessary to embed the fonts in the image. FreeType Plus looks for a folder named Fonts relative to the .image file, and loads any fonts it finds from there. Putting the font file(s) into the Fonts folder has these advantages... 1.The image isn't bloated. (embedding a 20Mb font file would grow the image by 20Mb) So, the default font could be a large Unicode one, for example 2.Easier to create a one-click app for distribution. 3.Easier to install the font files into the OS so that other applications can also use them. 4. Free fonts that don't allow embedding can be used (e.g. Bitstream). This widens the choice of available free fonts. The advantage to embedding the font file in the image is that it moves around with the .image file. Which for a one-click app isn't really an advantage at all :) Cheers, Andy

Sept. 23, 2008

[Pharo-project] On Icons

by Lukas Renggli

> OB-Enhancements version 0.203 I am horrified with all these colored icons on methods. That's worse than in the old browser with the button that had 8 different colors depending on the state of the method. - I don't want to see part of the "contents" of a method as an icon. The super-icon is useless, it only hides valuable information (for example that there is a sub-implementation). If I want to know if a method calls super (and when) I need to look at the method anyway. - The same is for abstract method icon. When browsing the protocol/interface I don't need to know that. I am more interested if any of the subclasses override it. - The same for extension methods. I see that, because it is in a different protocol and because its name is in italic (the same as with the extension classes). I don't need yet another icon. The only valuable thing for me as a developer is to know if there is a super/sub implementation of a method. And maybe if there are halts inside. The rest I can find out with one click or less, if necessary. This would greatly improve the interface. The browser starts to be really messy. Furthermore I would like to define my own icons for classes, for example Seaside component should have its own icon. So instead of hardcoding this into OB itself why not asking the class for an icon, as this is done in VW for example. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Sept. 23, 2008

[Pharo-project] Re: Re: Re: [ANN] Demo with both Truetype + Polymorph

by Andrew Tween

Hi Damien, "Damien Cassou" <damien.cassou(a)gmail.com> wrote in message news:6ac749c10809222228v1ea27511uab4ccafc9795e0dc@mail.gmail.com... > On Tue, Sep 23, 2008 at 1:02 AM, Andrew Tween <amtween(a)hotmail.com> wrote: >> The default font should be sensible and generally acceptable, but since >> everyone can change that and choose their own favourite font from those >> available in their operating system, does it really matter what the >> default >> is? > > Yes it does really matter. Please take time to choose a very good > looking default font, it is the one that will be used by most users. :) I agree that 'very good' is better than 'acceptable' :) The options, as I see them, are :- A. Redistribute a font so that everybody sees the exact same default, regardless of Operating System. B. Don't redistribute a font; but instead use a different font from each Operating System (e.g. Mac=Lucida, Windows=Arial, Linux=Free Sans, etc) Regardless of which font(s) are chosen, some decisions are best left to the Designer because the fonts should look good within the Pharo theme. i.e. How large should the window title font be? Should it be bold, italic? Other decisions are best made by developers. i.e. should the code font be monospaced? should it be serif, or sans-serif Here is an approach that could work... 1. Decide upon whether option A (redistribute), or option B (use OS fonts) is best. 2. If option A is chosen, find a few freely redistributable fonts, then let the Designer choose the ones that work best with the Pharo theme. And for option B, let the Designer choose the fonts from each OS that work best with the Pharo theme. 3. The developers then choose the code font(s) Of course, the choice isn't strictly either/or. It is possible to redistribute a font AND use the OS fonts. e.g. ListFont => Mac=Lucida, Windows=Arial, neitherFontAvailableOnOS=use redistributed font. Codefont => use redistributed font on all OS Cheers, Andy > > -- > 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 >

Sept. 23, 2008

[Pharo-project] Product Brand Pharo

by Torsten Bergmann

Markus wrote >One question: is the splash-screen really needed? Adrien wrote: >I don't see the point of a splash screen. I completely agree that it is useless in the sense of loading screen showing the progress for the standard pharo image. Maybe it makes more sense for the "slower" TrueType image where a progress bar currently shows the font updates. But this is not possible since the Squeak VM does not (yet) support an updating splash progress in the native splash window driven by Smalltalk code. But a splash can also be done "image side only" anyway. But that's not the point. I suggested to provide a splash screen more from the branding/marketing point of view - even if it is technically useless. At least I want to know what others think about it. A splash screen typically shows the Logo and some version information and people rember/recognize/identify the software through that. Some applications have an option to disable the splash or show it only on the first startup. Eclipse for instance uses a slightly modified splash screen theme for each yearly full release (Europa, Ganymede, ...) - nice idea since the user knows which one is started when the disk is full with different versions. Sure we should drop the splash screen from the technical point of view - but it would be a nice idea to have the welcome screen of each Pharo release with a slightly modified theme to see if it is a core, developer image, ... We dont have to clone native apps/Java IDE's - but at least we can learn a little bit about branding/marketing and how good design can attract more people. Take another example - will you find a Smalltalk IDE with good looking Wizards these days? >From the Smalltalkers point of view (knowing about #subclass: messages) it's technically useless and will bloat the image - but I've seen many newbies blaming Smalltalk to be that complicated the first time they just click around and search for the Class/Package wizard. Squeak is also not very supportive if one needs help - there is a help menu but no real help/documentation. That does not mean we should have the splash screen or spend the whole day implementing Wizards - but at least we should discuss and think about what the first impression for others/non Smalltalkers will be and how we can help them to take first hurdles and enjoy the power of Smalltalk... Bye Torsten -- GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen! Jetzt dabei sein: http://www.shortview.de/wasistshortview.php?mc=sv_ext_mf@gmx

Sept. 23, 2008

Re: [Pharo-project] Re: Re: [ANN] Demo with both Truetype + Polymorph

by StÃ©phane Ducasse

>> 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. > > Good list, thanks. > > The default font should be sensible and generally acceptable, but > since everyone can change that and choose their own favourite font > from those available in their operating system, does it really > matter what the default is? No the default should be free and good. Because most of the people will not change it and this is what we see first. > > > Note that it is possible to set each default to be a list of fonts, > and whichever is found first will be used. e.g. > > Preferences > setListFontTo: (LogicalFont > familyName: 'Monaco' > fallbackFamilyNames: #('Segoe UI'. 'Helvetica'. 'Accuny') > pointSize: 8) > >> On Sep 22, 2008, at 23:34 , Andrew Tween wrote: >> >>> >>> "Matthew Fulmer" <tapplek(a)gmail.com> wrote in message news:20080922205627.GJ20335@tacobell >>> ... >>>> On Sun, Sep 21, 2008 at 10:38:48PM +0200, Marcus Denker wrote: >>>>> Here is a Demo with TrueType fonts and Polymorph installed (only >>>>> tested on Mac). >>>> >>>> I don't know about you, but whatever font is being used in that >>>> image is really ugly. It is grey instead of black, and hence >>>> lowers contrast a bit of the text in the image. Or maybe it is >>>> too thin, and the AA is being clever and making it grey. >>> >>> It is a direct copy of Bitstream Vera Sans, renamed as Squeak >>> Sans, and with the embedding flags changed to enable it to be >>> legally embedded in an application. The license for the Bitstream >>> fonts allows them to be altered in any way, so long as the name >>> is changed. >>> >>> Try experimenting with the preferences; i.e. contrast, hinting mode. >>> >>> If you find a font that you like, then please post the name of >>> the font and a screenshot. >>> There may be a similar free font that can be used instead. >>> >>> Cheers, >>> Andy >>> >>>> >>>> -- >>>> Matthew Fulmer -- http://mtfulmer.wordpress.com/ >>> >>> >>> >>> _______________________________________________ >>> 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 >

Sept. 23, 2008

Re: [Pharo-project] Halt once; workspace(?) menu

by StÃ©phane Ducasse

On Sep 23, 2008, at 1:20 AM, Bill Schwab wrote: > A couple of quick thoughts based on the Polymorph/TT image: > > (1) Halt-once looks like it is built into the image as a mode. It > is a > VERY useful concept, but Dolphin has long had a goodie that provides > the > feature as a class, used something along the lines of the following: > > abandonHopeAllYeWhoRaiseEndlessWalkbacksHere > self someUnfortunateConditionDetected ifTrue:[ > Once do:[ self halt. ]. > " > Once reset. > " > ]. I do not see the difference between that and what we have. Just the fact that this is class? > Any takers? I did not write it, but I think we will find it > licensed in > a friendly way, or it could be easily reconstructed, if not improved > by > having registered instances, allowing independent conditional > breakpoints, and all in code, or as I like to say "done in the > language, > not TO the language." > > > (2) The extended search sub-menu. At the really picky level (ignore > if > there is ANY problem with this), it might be nicer to pop out a > submenu > vs. jumping to another menu. > > > Bill > > > > > > > Wilhelm K. Schwab, Ph.D. > University of Florida > Department of Anesthesiology > PO Box 100254 > Gainesville, FL 32610-0254 > > Email: bschwab(a)anest.ufl.edu > Tel: (352) 273-6785 > FAX: (352) 392-7029 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 23, 2008

[Pharo-project] First pharo-dev with limited package set

by Damien Cassou

Hi, I've just released the first pharo-dev which contains a limited package set. See http://code.google.com/p/pharo/wiki/Packages for the list of packages we want in Pharo. You can download the image at https://gforge.inria.fr/frs/download.php/7404/pharo0.1-10074dev08.09.2.zip. Here is the list of packages included in this release: AST version 160 eCompletion version 0.90 OB-Enhancements version 0.203 OmniBrowser version 0.416 OmniBrowser-Morphic version 0.52 OmniBrowser-Refactory version 1.0 OmniBrowser-Regex version 0.9.1 OmniBrowser-Standard version 0.346 Pharo packages version 0.3 Refactoring Core version 5 RoelTyper version 0.60 Shout version 3.15-tween.72 ShoutWorkspace version 1-tween.2 VBRegex version 1.9 -- 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)

Sept. 23, 2008

Re: [Pharo-project] Re: Re: [ANN] Demo with both Truetype + Polymorph

by Damien Cassou

On Tue, Sep 23, 2008 at 1:02 AM, Andrew Tween <amtween(a)hotmail.com> wrote: > The default font should be sensible and generally acceptable, but since > everyone can change that and choose their own favourite font from those > available in their operating system, does it really matter what the default > is? Yes it does really matter. Please take time to choose a very good looking default font, it is the one that will be used by most users. -- 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)

Sept. 23, 2008

[Pharo-project] Halt once; workspace(?) menu

by Bill Schwab

A couple of quick thoughts based on the Polymorph/TT image: (1) Halt-once looks like it is built into the image as a mode. It is a VERY useful concept, but Dolphin has long had a goodie that provides the feature as a class, used something along the lines of the following: abandonHopeAllYeWhoRaiseEndlessWalkbacksHere self someUnfortunateConditionDetected ifTrue:[ Once do:[ self halt. ]. " Once reset. " ]. Any takers? I did not write it, but I think we will find it licensed in a friendly way, or it could be easily reconstructed, if not improved by having registered instances, allowing independent conditional breakpoints, and all in code, or as I like to say "done in the language, not TO the language." (2) The extended search sub-menu. At the really picky level (ignore if there is ANY problem with this), it might be nicer to pop out a submenu vs. jumping to another menu. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029

Sept. 22, 2008

[Pharo-project] Re: Re: [ANN] Demo with both Truetype + Polymorph

by Andrew Tween

"Adrian Lienhard" <adi(a)netstyle.ch> wrote in message news:B0867552-5166-4E76-8FDA-CF1B88883158@netstyle.ch... >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)) I haven't checked, but I would guess that it is owned by Apple and the license prohibits its redistribution. > > 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. Good list, thanks. The default font should be sensible and generally acceptable, but since everyone can change that and choose their own favourite font from those available in their operating system, does it really matter what the default is? Note that it is possible to set each default to be a list of fonts, and whichever is found first will be used. e.g. Preferences setListFontTo: (LogicalFont familyName: 'Monaco' fallbackFamilyNames: #('Segoe UI'. 'Helvetica'. 'Accuny') pointSize: 8) In this way, a Mac user will see Monaco , a Windows Vista user will see Segoe UI (the Vista default), and other OS users will see Helvetica or, as a last resort, the Accuny strike font. Cheers, Andy > > Adrian > > > On Sep 22, 2008, at 23:34 , Andrew Tween wrote: > >> >> "Matthew Fulmer" <tapplek(a)gmail.com> wrote >> in message news:20080922205627.GJ20335@tacobell ... >>> On Sun, Sep 21, 2008 at 10:38:48PM +0200, Marcus Denker wrote: >>>> Here is a Demo with TrueType fonts and Polymorph installed (only >>>> tested on Mac). >>> >>> I don't know about you, but whatever font is being used in that >>> image is really ugly. It is grey instead of black, and hence >>> lowers contrast a bit of the text in the image. Or maybe it is >>> too thin, and the AA is being clever and making it grey. >> >> It is a direct copy of Bitstream Vera Sans, renamed as Squeak Sans, and >> with the embedding flags changed to enable it to be legally embedded in >> an application. The license for the Bitstream fonts allows them to be >> altered in any way, so long as the name is changed. >> >> Try experimenting with the preferences; i.e. contrast, hinting mode. >> >> If you find a font that you like, then please post the name of the font >> and a screenshot. >> There may be a similar free font that can be used instead. >> >> Cheers, >> Andy >> >>> >>> -- >>> Matthew Fulmer -- http://mtfulmer.wordpress.com/ >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 22, 2008