Thanks, but the keyboard design is basically ripping off iOS and Android. Once it works, I'll share.
Cheers, Jeff On Tue, Feb 25, 2014 at 3:52 PM, Tudor Girba <[email protected]> wrote: > This is a beautiful looking keyboard :) > > Doru > > > On Tue, Feb 25, 2014 at 2:45 PM, J.F. Rick <[email protected]> wrote: > >> Here's an updated bug for this: >> https://pharo.fogbugz.com/f/cases/12777/Athens-font-cacheing-bug >> >> Cheers, >> >> Jeff >> >> >> On Tue, Feb 25, 2014 at 2:33 PM, Vincent Blondeau < >> [email protected]> wrote: >> >>> Hi Pharoers, >>> >>> We are encounter a problem with text displaying under Roassal. >>> Roassal is a Moose tool to make some graphics visualisations, >>> principally graphs. >>> Some visualisations are displaying some text, like : >>> >>> - ROMondrianExample new centeredText >>> - ROMondrianExample new temporaryEdges >>> - ROMondrianExample new labeledRectangle >>> >>> They use AthensCanvas to render. >>> >>> Since the beginning of February, we experiment very strange problems >>> with font displaying. See by yourself : >>> >>> What we expect : >>> >>> What we have : >>> >>> You can see that the letters in each word are not of the same size. >>> (To reproduce do : "ROMondrianExample new labeledRectangle" in a fresh >>> Moose image : >>> https://ci.inria.fr/moose/job/moose-5.0/lastSuccessfulBuild/artifact/moose-5.0.zip >>> ) >>> >>> We thought it was a font problem. So we updated the fonts to use this >>> one : >>> LogicalFont familyName: StandardFonts defaultFont familyName pointSize: >>> aSize >>> which is the default system font. (The fonts are located in >>> ROFontOrganizerAthens). >>> >>> But the problem was not solved. >>> >>> After some searches, we saw that Roassal (via the ROAthensCanvas) uses >>> AthensCairoCanvas and this class has been changed begin February to use >>> native boost. >>> The closed issue related is : >>> >>> 12765 Athens font rendering missing letters and missizing others >>> https://pharo.fogbugz.com/f/cases/12765 >>> >>> That should resolve the problem instead of created one ;) >>> >>> >>> So if we load the older packages of Athens-Core and Athens-Cairo (before >>> the issue resolution): >>> >>> Name: Athens-Core-MarcusDenker.34 >>> Author: MarcusDenker >>> Time: 5 July 2013, 10:59:47.206954 am >>> UUID: e844b2d4-b091-42a4-9be0-17101dcdbd30 >>> Ancestors: Athens-Core-MarcusDenker.33, Athens-Core-ErwanDouaille.33 >>> >>> Name: Athens-Cairo-MarcusDenker.51 >>> Author: MarcusDenker >>> Time: 26 August 2013, 4:03:06.190096 pm >>> UUID: 9e1bfddb-67f7-4a36-864d-11060b8b6881 >>> Ancestors: Athens-Cairo-SebastianTleye.50 >>> >>> we have no problem of font displaying ! >>> >>> The question is : >>> What we should adapt in Roassal to support this new implementation of >>> Athens ? Or is Athens (by the native boost primitives) broken ? >>> >>> Thanks in advance ! >>> >>> >>> Vincent BLONDEAU >>> >>> >>> >>> >> >> >> -- >> Jochen "Jeff" Rick, Ph.D. >> http://www.je77.com/ >> Skype ID: jochenrick >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick
<<inline: image/png>>
<<inline: image/png>>
