January 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] about and:and: and and:

by StÃ©phane Ducasse

hi nicolas I saw that you apply some automatic refactoring in squeak about and:and: -> and: and I wanted to know. Is and: more optimized than and:and: (I imagine that) but I would like to know for sure. Stef

Jan. 4, 2010

Re: [Pharo-project] Issue 1692: MNU when tried to navigate pop up menus with the keyboard

by Mariano Martinez Peck

On Mon, Jan 4, 2010 at 7:58 AM, Alain Plantec <alain.plantec(a)free.fr> wrote: > Mariano Martinez Peck a Ã©crit : > > Hi Alain: This bug seems related with the new preference architecture. > indeed, I will check that very soon. > Cool. Take it easy. No one is rushing :) > Alain > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 4, 2010

Re: [Pharo-project] Issue 1692: MNU when tried to navigate pop up menus with the keyboard

by Alain Plantec

Mariano Martinez Peck a Ã©crit : > Hi Alain: This bug seems related with the new preference architecture. indeed, I will check that very soon. Alain

Jan. 4, 2010

Re: [Pharo-project] Beginner question :) search and replace in String

by Levente Uzonyi

On Fri, 1 Jan 2010, Adrian Kuhn wrote: > Levente Uzonyi <leves@...> writes: > >>> Personally, I would love to have a #gsub:with: on String. It is short and >>> uses established vocabulary. >> >> Please no, smalltalk is not awk or ruby and noone should expect that >> these cryptic function names are well known. Message names should be >> as descriptive as possible, this enables understanding the code without >> documentation. Short message names have no advantage, we are not in the >> 80's. > > I dare to disagree :) > > Growing a language *and* compressing it. > > There is two directions for natural growth of a language. Composing complex > expressions from simple ones (see Guy Steele's classic OOPSLA keynote) *and* > shortening the name of often the most common operations. The latter is clearly > something that should happen overtime as an evolutionary process and not up > front. Akira Tanaka refers to this as the "huffman coding" of API design. I Why didn't it happen to smalltalk? I guess because the language tries to mimic natural languages. Btw I can't come up with a language that changed it's core library function names to shorter ones. > have written about that on my blog [1]. I read your blog post and I think that your suggestions are not generally useful. In smalltalk where you can print, inspect and explore any object Object >> #p is not really useful. Logging to Transcript is a bad practice anyway. Object >> #h instead of #halt? You must be kidding. Saving 3 letters when you have code completion? List = OrderedCollection? List new ===> an OrderedCollection() ? Which is more readable? List new << 'Lorem' << 'ipsum' << 'dolor' vs { 'Lorem'. 'ipsum'. 'dolor' } 'Expected <1p> but got <2p> (using <3s>)' e: value e: expected e: symbol vs 'Expected <1p> but got <2p> (using <3s>)' expandMacrosWithArguments: { value. expected. symbol } 'Regex are aaaaaaaaaawesome!' =~ 'a*wesome'r vs 'Regex are aaaaaaaaaawesome!' matchesRegex: 'a*wesome' (Most of the time I use #format: instead of #expandMacros* and never seen any code using #expandMacros* that wasn't written by me, your code is the first. Possibly because it has no documentation/examples.) > > So method names should initially be as descriptive as possible, but often used > method names should get a short alias. In 80 when Smalltalk was fresh, > #copyReplaceAll:with: was a revolutionary short "huffman encoding" for like 20 > lines of C (or worse) code. Smalltalk was visionary in using long method names #copyReplaceAll:with: is just a library method, a C library could have a similar function, but C libraries can't be explored like smalltalk libraries. In C you have to look up the docs or google a bit to find a function that fits your needs. In smalltalk you can browse the class hierarchy or in squeak/pharo you can use the MethodFinder besides the docs and the internet. > in the 80ies, but to each anti-thesis there is a synthesis. Today we are 30 > years later, and "gsub" has established itself as a generally known name for > replacing all occurrences of a pattern in a string. IMHO it has evolved from People familiar with awk or ruby will know what gsub does but others won't. Levente > what once used to be a cryptic function name to a proper programming term of > its own. > > We can think of other mebbe more Smalltalkesque huffman codings also, eg > > 'foobarqux' at: 'bar' put: 'XYZ'. > > with a double dispatch on the parameter of the #at: keyword, this would even > open up the API of String for unlimited extensions by clients without > cluttering it with dozens of new messages. So you could use integers, strings, > regeces, et cetera... > > Well, just brainstorming :) > > --AA > > > [1]: http://www.iam.unibe.ch/~akuhn/blog/2009/one-letter-method-names/ > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 4, 2010

[Pharo-project] Issues in 1.1 (was: Re: [update 1.1] #11126 - 27 (final ...))

by Levente Uzonyi

On Wed, 30 Dec 2009, StÃ©phane Ducasse wrote: > BIG THANKS igor!!! > > 11127 > ----- > > - Issue 1690: New Method Trailer part 7 (cs 9) There are still some issues. Some methods (for example TPureBehavior >> #addTraitSelector:withMethod:) still use the old trailer bytes #(0 0 0 0). These should be removed asap (I had to make some surgery with #become: to compile the new version.) Levente > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 4, 2010

Re: [Pharo-project] Issue 1692: MNU when tried to navigate pop up menus with the keyboard

by Mariano Martinez Peck

Hi Alain: This bug seems related with the new preference architecture. Look the method before your change was: MenuMorph >> drawOn: super drawOn: aCanvas. (ActiveHand notNil and: [ActiveHand keyboardFocus == self] and: [self rootMenu hasProperty: #hasUsedKeyboard]) ifTrue: [ aCanvas frameAndFillRectangle: self innerBounds fillColor: Color transparent borderWidth: Preferences menuBorderWidth borderColor: Preferences keyboardFocusColor ]. Now it is: drawOn: aCanvas "Draw the menu. Add keyboard-focus feedback if appropriate" super drawOn: aCanvas. (ActiveHand notNil and: [ActiveHand keyboardFocus == self] and: [self rootMenu hasProperty: #hasUsedKeyboard]) ifTrue: [ aCanvas frameAndFillRectangle: self innerBounds fillColor: Color transparent borderWidth: self theme settings menuBorderWidth borderColor: self theme settings menuBorderColor. ]. The problem is that "self theme settings menuBorderColor" is returned #raised and thus, the DNU with isTransparent. The problem is that flatMenu is nil. Solutions ? - Change " self theme settings menuBorderColor." for "Preference keyboardFocusColor" NOOOOO TO THIS SOLUTION!!! - Change to hardcore a color, something like: "borderColor: Color lightGray" This is all I can help :) Cheers Mariano On Fri, Dec 25, 2009 at 11:13 PM, Francisco Ortiz PeÃ±aloza < patchinko(a)gmail.com> wrote: > Pharo image: Pharo-core > Pharo core version: PharoCore1.1ALPHA Latest update: #11116 > Virtual machine used: Squeak 4.2.2beta1U | Cocoa Squeak 5.0.0b9 64*32 > > Steps to reproduce: > 1. Open a pop up using your mouse o pressing <esc> > 2. Try to select an action using your keyboard. Enter text to narrow > down your matching items or > using the arrow keys, neither work anymore. > > Francisco > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 3, 2010

[Pharo-project] Issue 1737: DNU when opening halo (core 1.1)

by Alain Plantec

It comes from the Preferences to settings refactoring. The fix simply consists in re-initializing HaloMorph ------ HaloMorph initialize ------ Alain

Jan. 3, 2010

[Pharo-project] [update 1.1] #11134

by StÃ©phane Ducasse

11134 ----- - Issue 1709: Enhanced TextDiffBuilder from squeak trunk. First part: tests Good night :)

Jan. 3, 2010

Re: [Pharo-project] [Fwd: DejaVu font from Cuis]

by Alain Plantec

Mariano Martinez Peck a Ã©crit : > > > 2010/1/3 Alain Plantec <alain.plantec(a)free.fr > <mailto:alain.plantec@free.fr>> > > > > Hi all, > > I've packaged the bitmap deja vu nice fonts from Cuis. > The Graphics-DejaVuFonts package is at > http://www.squeaksource.com/DejaVu. > Font are installed when you load the package (available sizes are > 5, 6, 7, 8, 9, 10, 11, 12 14, 17 and 22). > It can be unloaded without any problem (font are kept in the image). > What I suggest would to keep them as default font set in the core > and maybe remove the accuny one. > (I can make a package for accuny also so that is would be > reloadable if needed). > what do you think ? > > > Cool Alan!! I am really newbie with fonts. Would you mind explaining > me the difference between the new Strike Fonts we have in the latest > core images and this new fonts? Hi Mariano, When you load this package, new instances of StrikeFont are created and installed so that you can choose them with the FontChooser. The difference with current bitmap DejaVu sans is mainly that it provides more sizes. > They are just different fonts, no more than that? so yes > We will replace the Strike Fonts with these ? so no Cheers Alain > > Cheers > > Mariano > > > Alain > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > <mailto:Pharo-project@lists.gforge.inria.fr> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >

Jan. 3, 2010

Re: [Pharo-project] [Fwd: DejaVu font from Cuis]

by StÃ©phane Ducasse

On Jan 3, 2010, at 10:16 PM, Alain Plantec wrote: > > > From: Alain Plantec <alain.plantec(a)univ-brest.fr> > Date: January 3, 2010 10:15:21 PM GMT+01:00 > To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr> > Subject: DejaVu font from Cuis > Reply-To: alain.plantec(a)univ-brest.fr > > > Hi all, > > I've packaged the bitmap deja vu nice fonts from Cuis. > The Graphics-DejaVuFonts package is at http://www.squeaksource.com/DejaVu. > Font are installed when you load the package (available sizes are 5, 6, 7, 8, 9, 10, 11, 12 14, 17 and 22). > It can be unloaded without any problem (font are kept in the image). > What I suggest would to keep them as default font set in the core and maybe remove the accuny one. > (I can make a package for accuny also so that is would be reloadable if needed). > what do you think ? This is nice to have them as separate package. Good! Stef > > Alain > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 3, 2010