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

Re: [Pharo-project] Problems with Strike fonts

by Alain Plantec

Mariano Martinez Peck a Ã©crit : > Thanks Henrik. However, I tried what you told me and still is ugly :( maybe you could try with the dejavu from www.squeaksource.com/DejaVu Alain > > Any idea? > > Thanks > > Mariano

Jan. 8, 2010

[Pharo-project] [update 1.1] #11142

by StÃ©phane Ducasse

11142 ----- - Issue 1755: The debugger doesnt show custom messages - Issue 1754: Remove class discovery feature from ImageSegment - Issue 1756: Cleanup of isolationLevel Stef

Jan. 8, 2010

[Pharo-project] Problems saving the image on SIGTERM

by Damien Pollet

Hi, Chaff is a tiny class to intercept the SIGTERM signal and save the image http://www.squeaksource.com/Chaff.html Several problems: - OSProcess accessor forwardSigTern will only work once. Once the VM has registered a handler for a given signal, it can't clean it up or register another semaphore, until the image restarts. - If I have a process waiting on the semaphore, but the image quits for a different reason, I guess when it restarts, the process will still be there but the semaphore will be invalidâ¦ what's a good way to handle that ? - OSProcess does not seem to be able to register signal handlers at all on the Cocoa VM (5.2b9) Cheers, -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Jan. 8, 2010

Re: [Pharo-project] Problems with Strike fonts

by Henrik Johansen

On Jan 8, 2010, at 4:24 25PM, Mariano Martinez Peck wrote: > Thanks Henrik. However, I tried what you told me and still is ugly :( > > Any idea? > > Thanks > > Mariano Try setting Code Font to italic though, bolded message names in browsers will now look nice, where they previously where fugly :) To fix the text you mentioned, you additionally need to remove the call to isSynthetic: true from StrikeFont >> makeUnderlinedGlyphs. (Synthetic is only valid if the emphasis alters character width, which underlining it does not) Cheers, Henry > > On Fri, Jan 8, 2010 at 4:15 PM, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > The fix is easy, add at end of StrikeFont>>createDejaVu: > > oblique derivativeFont: boldOblique at: 1. > oblique derivativeFont: oblique at: 2. > oblique derivativeFont: boldOblique at: 3. > boldOblique derivativeFont: boldOblique at: 1. > boldOblique derivativeFont: boldOblique at: 2. > boldOblique derivativeFont: boldOblique at: 3. > > > The evaluate StrikeFont installDejaVu > > and voila! you using the bitmapped versions instead of making derived Oblique Oblique fonts, or deriving Bold Oblique font version from Oblique fonts manually. > > Cheers, > Henry > > > On Jan 8, 2010, at 3:23 51PM, Adrian Lienhard wrote: > > > It seems that emphasized strike fonts do not render properly? > > > > Anyway, we planned to put back the FreeType deja vu fonts for the > > Pharo image (but keep the strike fonts installed for PharoCore). Since > > syntax highlighting is only delivered with Pharo, the problem will not > > be apparent anymore. > > > > Adrian > > > > On Jan 8, 2010, at 15:11 , Mariano Martinez Peck wrote: > > > >> Thanks Stef, I wanted to see if you were paying attention ;) > >> > >> hahahah > >> > >> On Fri, Jan 8, 2010 at 3:03 PM, Alexandre Bergel > >> <alexandre(a)bergel.eu>wrote: > >> > >>> No screenshto attached > >>> > >>> Alexandre > >>> > >>> > >>> On 8 Jan 2010, at 10:43, Mariano Martinez Peck wrote: > >>> > >>>> Weeks ago Lukas reported an issue with StrikeFonts width. I don't > >>>> know if it is the same, but in the latest dev with StrikeFonts > >>>> (pharo1.0-10502-rc1dev09.12.2) you cannot even understand the text. > >>>> > >>>> Look the attached screenshot ? What do you think it says ? > >>>> > >>>> Ok, it says: "OCompleti" > >>>> > >>>> I am the only one that see that ? > >>>> > >>>> cheers > >>>> > >>>> mariano > >>>> _______________________________________________ > >>>> Pharo-project mailing list > >>>> Pharo-project(a)lists.gforge.inria.fr > >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>> > >>> -- > >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > >>> Alexandre Bergel http://www.bergel.eu > >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > >>> > >>> > >>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> Pharo-project(a)lists.gforge.inria.fr > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>> > >> <Picture 2.png>_______________________________________________ > >> 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 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 8, 2010

Re: [Pharo-project] Cannot merge anymore in PharoCore 11140

by Marcus Denker

On Jan 8, 2010, at 5:32 PM, Mariano Martinez Peck wrote: > Yes, puting again that method it works. > > Marcus we should check because maybe with the move of 11140 or 11139 we loose more methods. > We just discovered that because we saw it, but maybe there are other problems. Could you check ? I will check. PackageInfo is *broken*. Completelely. Marcus

Jan. 8, 2010

Re: [Pharo-project] Cannot merge anymore in PharoCore 11140

by Marcus Denker

On Jan 8, 2010, at 5:27 PM, Mariano Martinez Peck wrote: > We lost MCMergeResolutionRequest >> defaultAction Hmm.... I think this was categorized to be part of *PolyMorph... (as it calls a method that is categorized like that) all this PackageInfo crap does not work. Marcus

Jan. 8, 2010

[Pharo-project] [update 11141]

by Mariano Martinez Peck

PharoCore1.1ALPHA Latest update: #11141 we can merge again

Jan. 8, 2010

Re: [Pharo-project] Cannot merge anymore in PharoCore 11140

by Mariano Martinez Peck

Yes, puting again that method it works. Marcus we should check because maybe with the move of 11140 or 11139 we loose more methods. We just discovered that because we saw it, but maybe there are other problems. Could you check ? Thanks Mariano On Fri, Jan 8, 2010 at 5:27 PM, Mariano Martinez Peck <marianopeck(a)gmail.com > wrote: > We lost MCMergeResolutionRequest >> defaultAction > > > > > On Fri, Jan 8, 2010 at 5:21 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> Try to merge any slice from Inbox, it search, it diffs but no popup with >> the merge is raised. >> >> Cheers >> >> Mariano >> > >

Jan. 8, 2010

Re: [Pharo-project] Cannot merge anymore in PharoCore 11140

by Mariano Martinez Peck

We lost MCMergeResolutionRequest >> defaultAction On Fri, Jan 8, 2010 at 5:21 PM, Mariano Martinez Peck <marianopeck(a)gmail.com > wrote: > Try to merge any slice from Inbox, it search, it diffs but no popup with > the merge is raised. > > Cheers > > Mariano >

Jan. 8, 2010

[Pharo-project] Cannot merge anymore in PharoCore 11140

by Mariano Martinez Peck

Try to merge any slice from Inbox, it search, it diffs but no popup with the merge is raised. Cheers Mariano

Jan. 8, 2010