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

Re: [Pharo-project] Very tiny fonts

by StÃ©phane Ducasse

visualizations. We would love to have such a tiny font. If I would know how to do that I would already have done it. Stef On Dec 2, 2009, at 10:19 PM, Adrian Lienhard wrote: > What is the point of a font so small that I can hardly read it? > > Or is it just me and I need new glasses? > > Adrian > > On Dec 2, 2009, at 18:09 , Marcus Denker wrote: > >> >> On Dec 2, 2009, at 6:06 PM, Marcus Denker wrote: >> >>> Hi, >>> >>> While discussing Visualisations, we realized we want *really* tiny >>> fonts... >>> >>> Here is a hand-drawn sub-pixel font that is just 5 pixels high... >>> >>> http://typophile.com/node/61920 >>> >>> >>> Now we need to make a font for Pharo... >> >> we should check in addition how good/bad freetype or the mac >> renderes tinty fonts from >> the standard truetype fonts. >> >> Marcus >> _______________________________________________ >> 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

Dec. 2, 2009

Re: [Pharo-project] Good article on font rendering and subpixel

by Igor Stasenko

2009/12/2 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> From: Damien Pollet <damien.pollet(a)inria.fr> >> >> >> http://www.antigrain.com/research/font_rasterization/index.html#FONT_RASTER… The project itself (AGG) looks quite interesting http://www.antigrain.com/doc/introduction/introduction.agdoc.html#toc0002 >> -- >> 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 > -- Best regards, Igor Stasenko AKA sig.

Dec. 2, 2009

Re: [Pharo-project] Very tiny fonts

by Adrian Lienhard

What is the point of a font so small that I can hardly read it? Or is it just me and I need new glasses? Adrian On Dec 2, 2009, at 18:09 , Marcus Denker wrote: > > On Dec 2, 2009, at 6:06 PM, Marcus Denker wrote: > >> Hi, >> >> While discussing Visualisations, we realized we want *really* tiny >> fonts... >> >> Here is a hand-drawn sub-pixel font that is just 5 pixels high... >> >> http://typophile.com/node/61920 >> >> >> Now we need to make a font for Pharo... > > we should check in addition how good/bad freetype or the mac > renderes tinty fonts from > the standard truetype fonts. > > Marcus > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 2, 2009

Re: [Pharo-project] Issue 332, 1489, 1529: arithmetic protocols extracted from core

by csrabak＠bol.com.br

Miguel, I've used the core image and just had it updated as the first bullet of instructions direct. I was just curious :-) Em 02/12/2009 16:42, Miguel Enrique CobÃ¡ Martinez < miguel.coba(a)gmail.com > escreveu: El miÃ©, 02-12-2009 a las 10:56 -0200, csrabak(a)bol.com.br escribiÃ³: > Em 02/12/2009 01:41, Simon Denier < Simon.Denier(a)inria.fr > escreveu: > > > > On 1 dÃ©c. 2009, at 21:07, csrabak(a)bol.com.br wrote: > > > > > I'm trying to follow the directions given at: > > >http://code.google.com/p/pharo/wiki/HowToContribute. > > > However, after the SLICE asks for the first comment, it freezes > > > the image and the small window "Writing definitions" stays at 50% > > > progress and nothing happens then. > > > Hi Cesar, I took your changeset and prepared a Slice, I did not > > have any problem. > > Nice to know, Simon. Just to understand how I can troubleshoot this: did you > empoly a core or dev image to do the Monticello stuff? > Always use a core image to prepare the SLICES. Cheers > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Miguel CobÃ¡ http://miguel.leugim.com.mx _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 2, 2009

Re: [Pharo-project] Why some packages are rejected from Test Coverage?

by StÃ©phane Ducasse

Good idea send code :) After you should pay attention that may be some packages may crash the system when run on coverage I did not try but I imagine that Array, Object and other kernel stuff may suffer. Stef

Dec. 2, 2009

Re: [Pharo-project] [Moose-dev] Re: popupView: is now working

by Alexandre Bergel

> The problem is that if you put it in the rendering code this will > basically get invoked every 30 ms. A more practical solution is to > use haltOnce. This is the same as halt, only that it is guarded by a > global flag. Just make sure that you enable it from the Debug world > menu. I am not expert in Morphic, but I feel there is a bug in how exceptions in Morph are handled. Create a subclass of Morph and put a "self halt" (or "1/0") in the drawOn: method. Open the morph and it will appear in red, telling that there is an error in the render loop. Now, for some reason, when blocks are heavily, the image freeze. I tried to isolate the error (i.e., without Mondrian), but I could not figure out how to do it. Alexandre > > Cheers, > Doru > > > On 2 Dec 2009, at 13:10, Johan Fabry wrote: > >> Hi Stef, >> this is the same behavior as what I reported in http://code.google.com/p/pharo/issues/detail?id=1525 >> and http://code.google.com/p/moose-technology/issues/detail?id=237 >> How to reproduce is also there. >> On 02 Dec 2009, at 08:30, StÃ©phane Ducasse wrote: >> >>> Do you have a example that we can reproduce? >>> >>> Stef >>> >>> On Dec 1, 2009, at 9:23 PM, Alexandre Bergel wrote: >>> >>>>> Regarding the problem with the number of arguments in the block. >>>>> Why is it crashing the image? >>>> >>>> The image is not crashing actually. It just hangs on forever >>>> without giving a chance to interrupt the process. >>>> >>>>> Anyway, you might want to use an approach similar to the >>>>> implementation of glamourValue: in Glamour. >>>> >>>> It could be a nice fix, but clearly not a general solution. The >>>> image hangs because of a bug in Squeak/Pharo. For some reason, >>>> the exception thrown by the virtual machine is not properly caught. >>>> This is a hard problem that will need to be fixed some days. >>>> >>>> Alexandre >> >> -- >> Johan Fabry >> jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry >> PLEIAD Lab - Computer Science Department (DCC) - University of Chile >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > www.tudorgirba.com > > "Relationships are of two kinds: those we choose and those that > happen. They both matter." > > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 2, 2009

[Pharo-project] Why some packages are rejected from Test Coverage?

by Mariano Martinez Peck

Ok, I see that there are some packages that are not able to be selected to run test coverage. I noticed that they were big packages and then I saw the method: TestRunner >> promptForPackages where you can see it rejects packages like Kernel, Collections, System, etc. I guess because Test Coverage may take long time in those big packages....but I don't know if that's a good reason to disable them. Maybe a popup saying "Are you sure you want to run Test Coverage over this package? It will take a lot of time" is better. At least VisualWorks does something similar. What do you think ? Cheers, Mariano

Dec. 2, 2009

Re: [Pharo-project] [Pharo-Project] Monticello package corrupted

by StÃ©phane Ducasse

no this is strange. May be a widestrign problem stef On Dec 2, 2009, at 8:07 PM, Hernan Wilkinson wrote: > Hi, > I'm moving code from Pharo to GLASS using Monticello, but in some > packages the code that is read by GLASS is not correct, it has 0s in > it. For example, instead of 'to' it has 't o ' (where spaces are > zeros) > If I try to unzip the monticello package, I get a CRC error on the > source file... > Does anybody heard about this error before? > > Thanks, > Hernan. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 2, 2009

Re: [Pharo-project] Time asMilliseconds...

by StÃ©phane Ducasse

On Dec 2, 2009, at 8:02 PM, Hernan Wilkinson wrote: > Hi Stef, > I just saw the mail. > I added the same line as you... that is how it was on previous Pharo versions strange I did not find it. Marcus reintroduced it in his latest release Stef ] > > Thanks! > Hernan. > > On Wed, Dec 2, 2009 at 8:41 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Hernan >> >> I checked and this method is not in Squeak3.9, squeaktrunk, >> Now we could easily add >> >> self asDuration asMilliSeconds >> >> I will do that >> >> >> On Dec 1, 2009, at 6:33 PM, Hernan Wilkinson wrote: >> >>> is not in the image anymore...is there a reason? >>> >>> Henan. >>> >>> _______________________________________________ >>> 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

Dec. 2, 2009

[Pharo-project] [Pharo-Project] Monticello package corrupted

by Hernan Wilkinson

Hi, I'm moving code from Pharo to GLASS using Monticello, but in some packages the code that is read by GLASS is not correct, it has 0s in it. For example, instead of 'to' it has 't o ' (where spaces are zeros) If I try to unzip the monticello package, I get a CRC error on the source file... Does anybody heard about this error before? Thanks, Hernan.

Dec. 2, 2009