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

Re: [Pharo-project] Blinking Cursor - (WAS: Enhanced StrikeFonts (antiAliasing , subPixel AA))

by StÃ©phane Ducasse

http://code.google.com/p/pharo/issues/detail?id=1039 Stef On Aug 5, 2009, at 10:24 AM, Torsten Bergmann wrote: > <BlinkingCursor.1.cs>

Aug. 5, 2009

Re: [Pharo-project] Blinking Cursor - (WAS: Enhanced StrikeFonts (antiAliasing , subPixel AA))

by StÃ©phane Ducasse

On Aug 5, 2009, at 10:24 AM, Torsten Bergmann wrote: > Hi there, > > attached is a "blinking cursor" implementation for Pharo > ported/inspired from/by the Morphic Text improvements done by > Andreas [1]. cool! > The more general question I have is: > is it "legally" possible to port and include stuff like this from the > new "squeak trunk" into pharo? Andreas is not (yet) on the list of > License Agreement Signers. > > Does anyone know if the new "squeak trunk" is already MIT license? I do not know how Squeak manage their MITness. May be ask andreas. I would like to see code moving between forks not stopped because of license. For CUIS code juan signed the pharo license agreement. Stef > > Thanks > Torsten > > [1] http://lists.squeakfoundation.org/pipermail/squeak-dev/2009-August/138025.h… > > > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > <BlinkingCursor.1.cs>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 5, 2009

Re: [Pharo-project] Enhanced StrikeFonts (antiAliasing , subPixel AA)

by StÃ©phane Ducasse

I have the impression that in case you want to have to run your vm on system not having the freeType plugin. Relying less on C code is a nice option (especially when a guy did all the work). Often people are telling us that we should not do everything in Smalltalk but there this is a nice solution and all in Smalltalk. Stef >> Concerning the fonts, I wonder what the win is, now that we have >> FreeType? Not that I don't like Juan's solution (I even proposed it >> some time ago for Pharo but then others preferred FreeType). When >> would FreeType not work and you would fall back to Juan's fonts? >> >> Adrian > > > On Aug 5, 2009, at 09:50 , StÃ©phane Ducasse wrote: > >> Henrik >> >> here is my answer: so I would really like to get enhanced >> strikefonts in pharo. >> Now I would like to have the point of view of the font experts. >> >> http://code.google.com/p/pharo/issues/detail?id=1037 >> >> >>>> Hi Stef, >>>> >>>> StÃ©phane Ducasse wrote: >>>>> Hi juan >>>>> >>>>> Ideally in Pharo I would really like to be able to have really >>>>> nice fonts without relying >>>>> on external plugin. Now I do not know too much about fonts. >>>>> Do you know that we could have the best of both worlds: >>>>> - your idea >>>>> - freetype. >>>>> >>>>> Stef >>>> >>>> Yes, I don't see any reason for not doing so. Load the attached. >>>> First 'preliminaries', then the big one. >>>> >>>> Enjoy! >>>> >>>> Cheers, >>>> Juan Vuletich >> >> >> <EnhancedStrikeFontsForPharo.zip> >> >> >> >> >> On Aug 4, 2009, at 8:05 PM, StÃ©phane Ducasse wrote: >> >>> From: Juan Vuletich <juan <at> jvuletich.org> >>> Subject: [Ann] Enhanced StrikeFonts (antiAliasing , subPixel AA) >>> Newsgroups: gmane.comp.lang.smalltalk.squeak.general >>> Date: 2009-08-03 21:52:47 GMT (20 hours and 12 minutes ago) >>> Hi Folks, >>> >>> If you update to the latest trunk, you'll load Graphics-jmv.53, >>> Morphic-jmv.138 and System-jmv.118. This is the support for anti >>> aliased >>> StrikeFonts from Cuis. The new 'BitmapDejaVu' font of point size 9 >>> is >>> set as default. I only included size 9 (reg, italic, bold, bold >>> italic) >>> to avoid using too much space in the image. If people want, more >>> sizes >>> can be added. >>> >>> To do proper antialiasing / subpixel AA _without_ requiring new >>> BitBlt >>> modes, I use RGBMul BitBlt rule, and a second pass with RGBAdd rule. >>> Text looks very good, in any combination of font and background >>> colors, >>> even at lower Display depths and / or glyphs depths. >>> >>> By default underscore and caret are shown as in standard ASCII. If >>> you >>> prefer the classic ST-80 left and up arrow, evaluate 'StrikeFont >>> useLeftArrow'. To go back to the default, evaluate 'StrikeFont >>> useUnderscore'. I also added 2 preferences #subPixelRenderFonts and >>> #subPixelRenderColorFonts (both default to true). >>> >>> Andreas, thanks for all your help! >>> >>> Comments are welcome. >>> >>> Cheers, >>> Juan Vuletich >>> >>> _______________________________________________ >>> 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

Aug. 5, 2009

Re: [Pharo-project] file dialog

by Tudor Girba

Thanks Mariano, The following code works: UIManager default chooseFileMatching: #('mse') label: 'Import model from MSE file.'. The problem is indeed that you have to pass a valid set of extensions, so * is not allowed. Anyway, it works for the moment but perhaps it should be changed to: FileDialogWindow>>validExtensions: aList "Set the filter for the files to be those with the given extensions." aList notEmpty ifTrue: [self defaultExtension: aList first]. self fileSelectionBlock: [:de | de isDirectory ifTrue: [self showDirectoriesInFileList] ifFalse: [(self fileNamePattern match: de name) and: [ aList contains: [:each | each match: (FileDirectory extensionFor: de name asLowercase) ] ]]] On the other hand the fileNamePattern seems to already have the job of filtering, so I do not really understand why we need aList. Cheers, Doru On 5 Aug 2009, at 09:39, StÃ©phane Ducasse wrote: > if you have a fix tag it 1.0 ;) > > Stef > > On Aug 5, 2009, at 12:56 AM, Mariano Martinez Peck wrote: > >> >> >> On Tue, Aug 4, 2009 at 7:32 PM, Tudor Girba <girba(a)iam.unibe.ch> >> wrote: >> Hi, >> >> I need to load a file from the disk. >> >> I am invoking: >> UIManager default >> chooseFileMatching: '*.mse' >> label: 'Import model from MSE file.'. >> >> The problem is that I do not see any files, even though I have files >> with .mse ending in the directory. Also, even if I pass '*.*' I still >> cannot see the files (only the directories). >> >> Could anyone tell me what I am doing wrong? >> >> I could reproduce it and debugging I noticed that >> >> FileDialogWindow>>validExtensions: aList >> "Set the filter for the files to be those with the given >> extensions." >> >> aList notEmpty >> ifTrue: [self defaultExtension: aList first]. >> self fileSelectionBlock: [:de | >> de isDirectory >> ifTrue: [self showDirectoriesInFileList] >> ifFalse: [(self fileNamePattern match: de name) and: [ >> aList includes: (FileDirectory extensionFor: >> de name asLowercase)]]] >> >> >> I think there can be a problem with this method. Here, aList will be >> '*.*' and as you can imagine that string doesn't includes any of the >> extensions. Perhaps we can change that include for a match: or >> something like that. To see this, remove the line >> aList includes: (FileDirectory extensionFor: de name asLowercase >> >> and you will see that now all the files are shown. >> >> we should open a ticket but I don't know if this should be 1.0 tag >> >> best, >> >> Mariano >> >> >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "Next time you see your life passing by, say 'hi' and get to know >> her." >> >> >> >> >> _______________________________________________ >> 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 -- www.tudorgirba.com "What is more important: To be happy, or to make happy?"

Aug. 5, 2009

[Pharo-project] Blinking Cursor - (WAS: Enhanced StrikeFonts (antiAliasing , subPixel AA))

by Torsten Bergmann

Hi there, attached is a "blinking cursor" implementation for Pharo ported/inspired from/by the Morphic Text improvements done by Andreas [1]. The more general question I have is: is it "legally" possible to port and include stuff like this from the new "squeak trunk" into pharo? Andreas is not (yet) on the list of License Agreement Signers. Does anyone know if the new "squeak trunk" is already MIT license? Thanks Torsten [1] http://lists.squeakfoundation.org/pipermail/squeak-dev/2009-August/138025.h… -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

Aug. 5, 2009

Re: [Pharo-project] Enhanced StrikeFonts (antiAliasing , subPixel AA)

by Adrian Lienhard

> Concerning the fonts, I wonder what the win is, now that we have > FreeType? Not that I don't like Juan's solution (I even proposed it > some time ago for Pharo but then others preferred FreeType). When > would FreeType not work and you would fall back to Juan's fonts? > > Adrian On Aug 5, 2009, at 09:50 , StÃ©phane Ducasse wrote: > Henrik > > here is my answer: so I would really like to get enhanced > strikefonts in pharo. > Now I would like to have the point of view of the font experts. > > http://code.google.com/p/pharo/issues/detail?id=1037 > > >>> Hi Stef, >>> >>> StÃ©phane Ducasse wrote: >>>> Hi juan >>>> >>>> Ideally in Pharo I would really like to be able to have really >>>> nice fonts without relying >>>> on external plugin. Now I do not know too much about fonts. >>>> Do you know that we could have the best of both worlds: >>>> - your idea >>>> - freetype. >>>> >>>> Stef >>> >>> Yes, I don't see any reason for not doing so. Load the attached. >>> First 'preliminaries', then the big one. >>> >>> Enjoy! >>> >>> Cheers, >>> Juan Vuletich > > > <EnhancedStrikeFontsForPharo.zip> > > > > > On Aug 4, 2009, at 8:05 PM, StÃ©phane Ducasse wrote: > >> From: Juan Vuletich <juan <at> jvuletich.org> >> Subject: [Ann] Enhanced StrikeFonts (antiAliasing , subPixel AA) >> Newsgroups: gmane.comp.lang.smalltalk.squeak.general >> Date: 2009-08-03 21:52:47 GMT (20 hours and 12 minutes ago) >> Hi Folks, >> >> If you update to the latest trunk, you'll load Graphics-jmv.53, >> Morphic-jmv.138 and System-jmv.118. This is the support for anti >> aliased >> StrikeFonts from Cuis. The new 'BitmapDejaVu' font of point size 9 is >> set as default. I only included size 9 (reg, italic, bold, bold >> italic) >> to avoid using too much space in the image. If people want, more >> sizes >> can be added. >> >> To do proper antialiasing / subpixel AA _without_ requiring new >> BitBlt >> modes, I use RGBMul BitBlt rule, and a second pass with RGBAdd rule. >> Text looks very good, in any combination of font and background >> colors, >> even at lower Display depths and / or glyphs depths. >> >> By default underscore and caret are shown as in standard ASCII. If >> you >> prefer the classic ST-80 left and up arrow, evaluate 'StrikeFont >> useLeftArrow'. To go back to the default, evaluate 'StrikeFont >> useUnderscore'. I also added 2 preferences #subPixelRenderFonts and >> #subPixelRenderColorFonts (both default to true). >> >> Andreas, thanks for all your help! >> >> Comments are welcome. >> >> Cheers, >> Juan Vuletich >> >> _______________________________________________ >> 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

Aug. 5, 2009

Re: [Pharo-project] Enhanced StrikeFonts (antiAliasing , subPixel AA)

by StÃ©phane Ducasse

From: Andreas Raab <andreas.raab <at> gmx.de> Subject: Morphic Text Improvements Newsgroups: gmane.comp.lang.smalltalk.squeak.general Date: 2009-08-05 07:17:29 GMT (56 minutes ago) Folks - With our pretty new fonts, I felt the need to include some of our older text improvements and fixes. If you update from the trunk, you will notice that: a) Text now has a more regular blinking insertion point instead of the virtually invisible something before. b) Text displayed with a non-default style always uses the correct default font; text copied and pasted between editors with different text styles has no strange effects on the text size. c) The line height of empty text is correct (for example in FillInTheBlanks - this is much more noticable with blinking cursors). I don't expect any fallout with these changes because they've been used quite a while and are pretty solid, but since text behavior can sometimes have odd side effects, please keep an eye open and let me know if you find any strange behavior. Enjoy, - Andreas

Aug. 5, 2009

Re: [Pharo-project] Pharo responseless when debugger steps into DNU in Seaside app

by Johan Brichau

Hi Lukas, No, this is Seaside2.8a1-pmm.593 (which is included in the Pharo download image) On 05 Aug 2009, at 10:01, Lukas Renggli wrote: > What version of Seaside is this? > > There are several debugger related bugs in Seaside 2.9a4: > <http://code.google.com/p/seaside/issues/list?q=debugger>. > > Lukas > > 2009/8/5 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> >> On Aug 4, 2009, at 8:33 PM, Johan Brichau wrote: >> >>> Hi everyone, >>> >>> I'm getting a problem debugging Seaside applications in latest >>> Pharo. >>> >>> When stepping with the debugger through the execution of a seaside >>> application and encountering a message not understood, the entire >>> Pharo system freezes and is totally unresponsive. It does not show >>> that a DNU occurs, it simply becomes unresponsive when trying to >>> step >>> over the message that does not exist. I have to force quit. >>> >>> The problem can easily be recreated by changing a seaside >>> component's >>> render method such that a DNU occurs. Next, choose to debug the >>> problem and restart the context. Now start stepping through the >>> method >>> and the system freezes when you try to step into the message that is >>> not understood. The system freezes and does not show you a DNU. >>> >>> It seems to be a Pharo-Seaside problem since I do not have the same >>> problem when doing this outside of Seaside applications. >>> >>> I'm using Pharo 09.7.5 (with seaside) and did a system update just >>> now. >>> >>> I'm trying to drill down to the source of the problem but if anyone >>> has any ideas.... >> >> Thanks this is important. >> Can you open a bug entry report? >> I go some problem with the system not been able to spawn a debugger >> but I was waiting to get the beta version. >> >> Stef >> >>> >>> ---------------------------- >>> Johan Brichau >>> johan.brichau(a)uclouvain.be >>> >>> >>> >>> >>> >>> _______________________________________________ >>> 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 >> > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ---------------------------- Johan Brichau johan.brichau(a)uclouvain.be

Aug. 5, 2009

Re: [Pharo-project] Pharo responseless when debugger steps into DNU in Seaside app

by Johan Brichau

On 05 Aug 2009, at 09:37, StÃ©phane Ducasse wrote: > Can you open a bug entry report? I just did that right now. I wanted to drill down in the problem a bit further before entering the ticket. The additional info is in the bug report (1038). It seems the DNU is handled by Seaside code since it pops up in the browser (as it normally does). However, you cannot do anything beyond that point... ---------------------------- Johan Brichau johan.brichau(a)uclouvain.be

Aug. 5, 2009

[Pharo-project] preferences?

by StÃ©phane Ducasse

This is nice to see that we are also copied :) At ESUG it would be good to see the next step in preference cleaning. Stef From: Andreas Raab <andreas.raab <at> gmx.de> Subject: Preference Pragmas redux Newsgroups: gmane.comp.lang.smalltalk.squeak.general Date: 2009-08-05 04:52:16 GMT (3 hours and 7 minutes ago) Folks - I've just pushed a version of preference pragmas into the trunk. With preference pragmas, you no longer need to litter Preferences with loose methods that confuse Monticello and don't get uninstalled. With preference pragmas, you define your preferences locally (for example as class variables) and provide an annotation that can be discovered automatically. A sample preference looks like here: MyClass>>samplePref <preference: 'Sample Preference' category: 'My Application' description: 'A sample preference in my application' type: #Boolean> ^SamplePref The following types of preferences are currently supported: #Boolean, #String, #Number, and #Color. When a preference is changed, the accompanying setter method is called. Preference pragmas will help us get rid of most of the dependencies between Preferences and the rest of the world. New preference browsers or entire implementations can easily be written without introducing unnecessary dependencies by virtue of discovering the annotation. Cheers, - Andreas

Aug. 5, 2009