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

Re: [Pharo-project] Underscores in selectors

by Schwab,Wilhelm K

Helloa all, I'd really like to second Mariano's request for a work-around, and I might even be able to post one shortly. I did not write it, but it tweaks (at least the old) scanner to accept underscores in any but the first position of a selector. That might meet Mariano's need, and would cover most of mine related to RDBs as well. For external interfacing, it would further be important to be able to use them in class names, but nobody gave me a workaround for that :) One thing that I wonder about is whether Shout will adapt with the change??? I will look for it and apply shortly and just see what happens. If it works, I'll spread it around. I should have tried it in Pharo a long time ago. I'll try to report back in an hour or two. Bill ________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck Sent: Monday, May 18, 2009 7:58 AM To: Pharo Development Subject: [Pharo-project] Underscores in selectors Hi folks! I am trying to make Glorp work on Pharo but I am having problems with '_' in selectors. The standard of tables with databases involve _ when having more than a word. Example TB_BANK_ACCOUNT. Glorp needs a method like this: tableForTB_BANK_ACCOUNT In pharo 250 it works, but in latests Pharo releases this doesn't work. I know Stef said it could be for 1.1 but I need to ask: is there a workaround a hack or a quick fix so that I can progress with the port of GLORP ? can this have to be with new compiler ? Thanks Mariano

May 18, 2009

[Pharo-project] Line breaks lost when copy from clipboard on mac

by Adrian Lienhard

When I copy text with line breaks from outside Pharo into a Pharo workspace all line breaks are lost and replaced by a rectangle. In version 10259 it was still working, and in version 10262 it is broken (I don't have images in between, but if it helps I can find out in exactly which version the problem was introduced). When I inspect the pasted string, in the working version the line break is character value 13, in the current, broken version it is 10. Is this related to the Unicode changes? http://code.google.com/p/pharo/issues/detail?id=823 Adrian ___________________ http://www.adrian-lienhard.ch/

May 18, 2009

[Pharo-project] Underscores in selectors

by Mariano Martinez Peck

Hi folks! I am trying to make Glorp work on Pharo but I am having problems with '_' in selectors. The standard of tables with databases involve _ when having more than a word. Example TB_BANK_ACCOUNT. Glorp needs a method like this: tableForTB_BANK_ACCOUNT In pharo 250 it works, but in latests Pharo releases this doesn't work. I know Stef said it could be for 1.1 but I need to ask: is there a workaround a hack or a quick fix so that I can progress with the port of GLORP ? can this have to be with new compiler ? Thanks Mariano

May 18, 2009

Re: [Pharo-project] New Pharo based on core 10309 with antialiased fonts

by Adrian Lienhard

Much better! ;) I would also make the title font sans serif, but that's not critical. Cheers, Adrian On May 18, 2009, at 14:02 , Damien Cassou wrote: > On Mon, May 18, 2009 at 1:51 PM, Adrian Lienhard <adi(a)netstyle.ch> > wrote: >> I agree with Lukas, Bill, and Simon (that is, to change the default >> font to DejaVu Sans). > > Ok, here is the new version. What do you think? > > font := LogicalFont familyName: 'DejaVu Sans' pointSize: 10. > codeFont := LogicalFont familyName: 'DejaVu Sans Mono' pointSize: 9. > titleFont := LogicalFont familyName: 'DejaVu Serif' pointSize: 11. > > Preferences setListFontTo: font. > Preferences setMenuFontTo: font. > Preferences setCodeFontTo: codeFont. > Preferences setButtonFontTo: font. > Preferences setSystemFontTo: font. > Preferences setWindowTitleFontTo: titleFont. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular > by not having them." James Iry > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 18, 2009

[Pharo-project] question about OCompletion

by Gabriel Brunstein

How can I change the packages that I am working on with OCompletion? I think it is included in the last version of pharo so I could't specify it during the installation.

May 18, 2009

[Pharo-project] MNU Error in Class Browser (Package Browser)

by Alexandr Batalshikov

Hello, right mouse click in low frame (with code definition) of Class Browser raise error window "MessageNotUnderstood: OBTextSelection:" with first line "OBTextSelection(Object)>>doesNotUderstand: #isClassNode" after press "Debug" button I got another error window: "Error: Invalid utf8 input detected". I use pharo0.1-10309dev09.05.3.image on Windows XP Russian Edition. / Alexander.

May 18, 2009

Re: [Pharo-project] New Pharo based on core 10309 with antialiased fonts

by Henrik Johansen

Seems like an ok default to me. Personally though, I'm not too fond of the book-style serif, and will probably change mine to: font := LogicalFont familyName: 'DejaVu Sans' pointSize: 9. codeFont := LogicalFont familyName: 'DejaVu Sans Mono' pointSize: 9. titleFont := (LogicalFont familyName: 'DejaVu Sans' pointSize: 10) emphasis: 1. On a related topic, the current implementation of FreetypeFont>> hash is rather... simplistic. Haven't had time to check if it impacts performance considerably for a "bad" font policy (using multiple fonts with same size) though. Cheers, Henry Damien Cassou skrev: > On Mon, May 18, 2009 at 1:51 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > > I agree with Lukas, Bill, and Simon (that is, to change the default > > font to DejaVu Sans). > > Ok, here is the new version. What do you think? > > font := LogicalFont familyName: 'DejaVu Sans' pointSize: 10. > codeFont := LogicalFont familyName: 'DejaVu Sans Mono' pointSize: 9. > titleFont := LogicalFont familyName: 'DejaVu Serif' pointSize: 11. > > Preferences setListFontTo: font. > Preferences setMenuFontTo: font. > Preferences setCodeFontTo: codeFont. > Preferences setButtonFontTo: font. > Preferences setSystemFontTo: font. > Preferences setWindowTitleFontTo: titleFont. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry > > ------------------------------------------------------------------------ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 18, 2009

Re: [Pharo-project] New Pharo based on core 10309 with antialiased fonts

by Schwab,Wilhelm K

Damien, I suspect you would reach at least sensible even without our help (or is it interference<g>), but I agree that serifs are a bit noisy, and I like to see my code in monospace. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Damien Cassou Sent: Monday, May 18, 2009 6:27 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] New Pharo based on core 10309 with antialiased fonts On Mon, May 18, 2009 at 1:24 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > I agree about about sans serif, and for code, even prefer a mono-spaced font. Â However, I believe there is a code snipet somewhere that changes the fonts to whatever is desired. Yes, this is the snipet I've just given and which can also be found at: http://code.google.com/p/pharo/wiki/CodeSnippets. However, the problem here is to select a sensible default. That's why I'm looking for your opinion. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 18, 2009

Re: [Pharo-project] New Pharo based on core 10309 with antialiased fonts

by Damien Cassou

On Mon, May 18, 2009 at 1:51 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > I agree with Lukas, Bill, and Simon (that is, to change the default > font to DejaVu Sans). Ok, here is the new version. What do you think? font := LogicalFont familyName: 'DejaVu Sans' pointSize: 10. codeFont := LogicalFont familyName: 'DejaVu Sans Mono' pointSize: 9. titleFont := LogicalFont familyName: 'DejaVu Serif' pointSize: 11. Preferences setListFontTo: font. Preferences setMenuFontTo: font. Preferences setCodeFontTo: codeFont. Preferences setButtonFontTo: font. Preferences setSystemFontTo: font. Preferences setWindowTitleFontTo: titleFont. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

May 18, 2009

Re: [Pharo-project] Toolsets?

by Damien Cassou

On Mon, May 18, 2009 at 1:40 PM, Simon Denier <Simon.Denier(a)inria.fr> wrote: > What is the best way to customize my own toolset? Create a subclass of > StandardToolset? Yes > BTW, where can I find a comparison between the three existing > toolsets? (standard, dev, OT) There are no comparison. What I can tell you: - Standard: uses the standard tools that are provided with the Core - OT: uses ob-based inspectors, debuggers, explorers... - dev: uses OT if present and tries to maximize the use of OB for the browsers Please send us the toolset you create in order to merge the changes and have everyone benefit from your work. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

May 18, 2009