Pharo-dev
By thread
pharo-dev@lists.pharo.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
- 3 participants
- 144636 messages
Re: [Pharo-dev] athens font rendering and subpixel antialiasing
by Nicolai Hess
2015-02-02 11:23 GMT+01:00 Ben Coman <btc(a)openinworld.com>:
>
>
> On Mon, Feb 2, 2015 at 8:06 AM, Nicolai Hess <nicolaihess(a)web.de> wrote:
>
>> Ok, the best I could do:
>>
>> Sadly, it only works because I changed the default lcd_filter from cairo.
>> in cairo 1.7. was a public API for the lcd_filter.
>> since 1.8 this API is private again (the code for the different filter
>> settings is still there).
>>
>
>
> In trying to learn some background info, this found article [1] seems
> good, from which I learn:
>
> * Freely scalable it must be free from character drift.
>
> I guess this is what we want ?
>
> * Three main types of font rendering:
>
> * Hinting trades accuracy for consistency, and as a consequence of
> this, hinted text _accumulates character drift_ with hinted glyphs, often
> possessing different metrics to their un-hinted counterparts.
>
> So I guess we don't use hinting, which implies not freely scalable ?
>
> * Anti-aliasing results in output which is accurate but blurred,
> trading contrast for consistency and accuracy.
>
> * Sub-pixel-rendering exploits the physical geometry of LCD screens to
> increase the horizontal resolution of the device. Needs to be filtered to
> avoid color fringing and is incompatible with aggressive hinting strategies.
>
Yes, in the freetypeplugin settings, you can switch between Monitortype LCD
and CRT
>
> * Sub-pixel-positioning is a generalisation of anti-aliasing and/or
> sub-pixel-rendering to allow for more accurate glyph placement, and is
> incompatible with aggressive hinting strategies.
>
Yes, in the freetypeplugin settings, you can change the hinting style
Light/Normal/Full. With Full-Hinting there is no
subpixelantialising anymore.
Similiar options are available for cairo/freetype.
The settings for Monitortype and hinting have an influence on the rendering
in the freetype library *and* the postprocessing that
is done in pharos FreeTypePlugin.
The same for FreeType and Cairo
>
> That article [1] advises:
>
> * For sub-pixel-rendering to function correctly it is necessary to
> enable the patent encumbered LCD filtering API. Many distributions,
> including Debian, do this already and is generally not a problem.
>
> * Versions of Cairo before the 1.10 release use their own intra-pixel
> filter. As of 2009 there are two sets of patches available that update
> legacy releases of Cairo to use an FIR inter-pixel filter. The first set
> pre-dates the filtering interface in FreeType and uses a custom FIR filter
> with the coefficients outlined in Gib98. The second set of patches, by
> David Turner, take advantage of the FreeType filtering interface.
>
> * It is recommended that distributions upgrade to Cairo 1.10 where at
> all possible. Here [2] is a post on that.
>
> So btw, what version of Cario are we using? I see latest is version
> 1.12.18.
>
> [1] https://freddie.witherden.org/pages/font-rasterisation/#spo07
> [2] http://lists.cairographics.org/archives/cairo/2010-January/018859.html
>
>
>
>
>> You can choose between
>> FT_LCD_FILTER_NONE
>> FT_LCD_FILTER_LEGACY
>> FT_LCD_FILTER_LIGHT
>> FT_LCD_FILTER_DEFAULT
>>
>> the default is FT_LCD_FILTER_LEGACY
>> but for this (so far, the best) result I used
>> FT_LCD_FILTER_DEFAULT
>> But there is no public API for this function anymore, so I had to
>> change the code.
>>
>>
>> We have to discuss how we proceed.
>>
>> The problems:
>> font rendering looks ugly ( at least for small font size like for menus,
>> lists and codepanes)
>> font rendering looks different on windows and linux
>>
>> possible solutions:
>> change build options for Freetype on Windos (enable
>> FT_CONFIG_OPTION_SUBPIXEL_RENDERING, potential patent infringement?)
>> change default filter (patching cairo source)
>>
>> or we leave everything as it is.
>> I do not know, and I'm starting to lose all interest.
>>
>>
>> nicolai
>>
>>
>>
>> 2015-02-01 19:38 GMT+01:00 Nicolai Hess <nicolaihess(a)web.de>:
>>
>>> **** patents!
>>>
>>> Hours, and days digging in the code for font rendering with cairo.
>>> I tried to find out why this "colored" subpixel antialising is not
>>> working although
>>> all option settings are set (in cairo) and in the source code of cairo
>>> the FT_SetLCDFilter
>>> call is really used! But the output does is just the same as with
>>> CAIRO_ANTIALIAS_GRAY,
>>>
>>> ... until I found THIS in the freetype config:
>>>
>>> /* Uncomment the line below if you want to activate sub-pixel rendering */
>>> /* (a.k.a. LCD rendering, or ClearType) in this build of the library. */
>>> /* */
>>> /* Note that this feature is covered by several Microsoft patents */
>>> /* and should not be activated in any default build of the library. */
>>> /* */
>>> /* This macro has no impact on the FreeType API, only on its */
>>> /* _implementation_. For example, using FT_RENDER_MODE_LCD when calling */
>>> /* FT_Render_Glyph still generates a bitmap that is 3 times wider than */
>>> /* the original size in case this macro isn't defined; however, each */
>>> /* triplet of subpixels has R=G=B. */
>>>
>>>
>>>
>>>
>>> ARGH!
>>>
>>> It still does not look as good as with the pharos freetypeplugin, but AT
>>> LEAST it looks
>>> equally on windows and linux , yeh.
>>>
>>>
>>> attached are three screenshots comparing
>>> the different athens drawings with the freetypeplugin
>>> athens on linux vs ftplugin
>>> athens on windows vs ftplugin
>>> athens on windows with enabled FT_CONFIG_SUBPIXEL_RENDERING vs ftplugin
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> 2015-01-31 10:18 GMT+01:00 stepharo <stepharo(a)free.fr>:
>>>
>>>>
>>>> In athens, there are "hints" you can set.
>>>> (CairoFontOptions/hintMetricsOff/hintMetricsOn/hintStyleFull ....)
>>>> I played a bit with different settings. Changing this settings change
>>>> the output, but I can not get it to look
>>>> like with the freetype plugin. I understand that this can not look
>>>> equally, because the FreeTypePlugin and caire work differently,
>>>> but the athens result looks bad compared with the other one.
>>>>
>>>>
>>>>
>>>>> - Pixel fitting. (The aliasing going on at the top of characters) Put
>>>>> Hinting: None in FreeType advanced features, and you will probably see
>>>>> something similar to the Athens rendering.
>>>>>
>>>>
>>>> Yes, we can change the freetypeplugin setting and cairofontoption
>>>> setting to make the output look equally - ugly :)
>>>>
>>>>
>>>> Nicolai
>>>>
>>>> Igor explained to me that FreeType offers a degenerated mode that when
>>>> the font does have the information for bold, kerning,....
>>>> computes a "guessed and approximated" default. Cairo does not offer
>>>> this api else Athens would use it.
>>>> So what would be interesting is to test using font having all the
>>>> information to see if Cairo display well the fonts.
>>>>
>>>> Stef
>>>>
>>>
>>>
>>
>
Feb. 2, 2015
Re: [Pharo-dev] athens font rendering and subpixel antialiasing
by Igor Stasenko
On 2 February 2015 at 12:31, Nicolai Hess <nicolaihess(a)web.de> wrote:
>
> 2015-02-02 10:46 GMT+01:00 Igor Stasenko <siguctua(a)gmail.com>:
>
>>
>>
>> On 2 February 2015 at 01:06, Nicolai Hess <nicolaihess(a)web.de> wrote:
>>
>>> Ok, the best I could do:
>>>
>>> Sadly, it only works because I changed the default lcd_filter from cairo.
>>> in cairo 1.7. was a public API for the lcd_filter.
>>> since 1.8 this API is private again (the code for the different filter
>>> settings is still there).
>>> You can choose between
>>> FT_LCD_FILTER_NONE
>>> FT_LCD_FILTER_LEGACY
>>> FT_LCD_FILTER_LIGHT
>>> FT_LCD_FILTER_DEFAULT
>>>
>>> the default is FT_LCD_FILTER_LEGACY
>>> but for this (so far, the best) result I used
>>> FT_LCD_FILTER_DEFAULT
>>> But there is no public API for this function anymore, so I had to
>>> change the code.
>>>
>>>
>>> We have to discuss how we proceed.
>>>
>>> The problems:
>>> font rendering looks ugly ( at least for small font size like for menus,
>>> lists and codepanes)
>>> font rendering looks different on windows and linux
>>>
>>> possible solutions:
>>> change build options for Freetype on Windos (enable
>>> FT_CONFIG_OPTION_SUBPIXEL_RENDERING, potential patent infringement?)
>>> change default filter (patching cairo source)
>>>
>>> or we leave everything as it is.
>>> I do not know, and I'm starting to lose all interest.
>>>
>>
>> I guess, to understand what happens, best would be to write a small C app,
>> that does the rendering.. and see what goes where.
>> Something doesn't works there.. but i was unable to figure what or why.
>>
>> I doubt that changing freetype library build settings is right way to
>> deal with issue,
>> because
>> a) both cairo/freetype used on linux out of the box
>>
>
> But I think freetype on linux has this config enabled (and in fact, the
> rendering looks
> different on windows and linux until I changed that option for windows)
> and I read somewhere, that ubunut(or other distributions?) patched cairo,
> just
> to get this filter setting api back.
>
>
>
>> b) many many apps, using these libs to render with subpixel quality.
>>
>
> This is what drives me crazy, doing text rendering right, is difficult
> yes, but this is
> the reason why we are using dedicated libraries.
>
>
Then, my guess, making it work on linux would be the first step.
Changing build options for building cairo/freetype libs for our VMs is not
a big deal then, as long as we will know how to do things properly.
>
>
>>
>>
>> --
>> Best regards,
>> Igor Stasenko.
>>
>
>
--
Best regards,
Igor Stasenko.
Feb. 2, 2015
Re: [Pharo-dev] athens font rendering and subpixel antialiasing
by Nicolai Hess
2015-02-02 11:13 GMT+01:00 phil(a)highoctane.be <phil(a)highoctane.be>:
>
>
> On Mon, Feb 2, 2015 at 10:51 AM, Sven Van Caekenberghe <sven(a)stfx.eu>
> wrote:
>
>>
>> > On 02 Feb 2015, at 01:06, Nicolai Hess <nicolaihess(a)web.de> wrote:
>> >
>> > I do not know, and I'm starting to lose all interest.
>>
>> Nicolai,
>>
>> Please don't give up.
>>
>
> Yeah, don't. You rock.
>
:)
Thanks
>
>> You are doing great work and we are all *very* impressed with your
>> attitude/drive/motivation, especially since you are covering such a wide
>> range of subjects. I know that the hard thing right now is that you do not
>> find enough sparring partners (that goes for others tackling different
>> issues as well).
>
>
>> Sven
>>
>
> Phil
>
>
>
>
>
>
Feb. 2, 2015
Re: [Pharo-dev] athens font rendering and subpixel antialiasing
by Nicolai Hess
2015-02-02 10:46 GMT+01:00 Igor Stasenko <siguctua(a)gmail.com>:
>
>
> On 2 February 2015 at 01:06, Nicolai Hess <nicolaihess(a)web.de> wrote:
>
>> Ok, the best I could do:
>>
>> Sadly, it only works because I changed the default lcd_filter from cairo.
>> in cairo 1.7. was a public API for the lcd_filter.
>> since 1.8 this API is private again (the code for the different filter
>> settings is still there).
>> You can choose between
>> FT_LCD_FILTER_NONE
>> FT_LCD_FILTER_LEGACY
>> FT_LCD_FILTER_LIGHT
>> FT_LCD_FILTER_DEFAULT
>>
>> the default is FT_LCD_FILTER_LEGACY
>> but for this (so far, the best) result I used
>> FT_LCD_FILTER_DEFAULT
>> But there is no public API for this function anymore, so I had to
>> change the code.
>>
>>
>> We have to discuss how we proceed.
>>
>> The problems:
>> font rendering looks ugly ( at least for small font size like for menus,
>> lists and codepanes)
>> font rendering looks different on windows and linux
>>
>> possible solutions:
>> change build options for Freetype on Windos (enable
>> FT_CONFIG_OPTION_SUBPIXEL_RENDERING, potential patent infringement?)
>> change default filter (patching cairo source)
>>
>> or we leave everything as it is.
>> I do not know, and I'm starting to lose all interest.
>>
>
> I guess, to understand what happens, best would be to write a small C app,
> that does the rendering.. and see what goes where.
> Something doesn't works there.. but i was unable to figure what or why.
>
> I doubt that changing freetype library build settings is right way to deal
> with issue,
> because
> a) both cairo/freetype used on linux out of the box
>
But I think freetype on linux has this config enabled (and in fact, the
rendering looks
different on windows and linux until I changed that option for windows)
and I read somewhere, that ubunut(or other distributions?) patched cairo,
just
to get this filter setting api back.
> b) many many apps, using these libs to render with subpixel quality.
>
This is what drives me crazy, doing text rendering right, is difficult
yes, but this is
the reason why we are using dedicated libraries.
>
>
> --
> Best regards,
> Igor Stasenko.
>
Feb. 2, 2015
Re: [Pharo-dev] athens font rendering and subpixel antialiasing
by Sven Van Caekenberghe
> On 02 Feb 2015, at 11:40, stepharo <stepharo(a)free.fr> wrote:
>
> + 10000 ^ 10000
You mean, + 10000 ** 10000, right ;-)
> Stef
> Le 2/2/15 10:51, Sven Van Caekenberghe a écrit :
>>> On 02 Feb 2015, at 01:06, Nicolai Hess <nicolaihess(a)web.de> wrote:
>>>
>>> I do not know, and I'm starting to lose all interest.
>> Nicolai,
>>
>> Please don't give up.
>>
>> You are doing great work and we are all *very* impressed with your attitude/drive/motivation, especially since you are covering such a wide range of subjects. I know that the hard thing right now is that you do not find enough sparring partners (that goes for others tackling different issues as well).
>>
>> Sven
>>
>>
>
>
Feb. 2, 2015
Re: [Pharo-dev] athens font rendering and subpixel antialiasing
by stepharo
+ 10000 ^ 10000
Stef
Le 2/2/15 10:51, Sven Van Caekenberghe a écrit :
>> On 02 Feb 2015, at 01:06, Nicolai Hess <nicolaihess(a)web.de> wrote:
>>
>> I do not know, and I'm starting to lose all interest.
> Nicolai,
>
> Please don't give up.
>
> You are doing great work and we are all *very* impressed with your attitude/drive/motivation, especially since you are covering such a wide range of subjects. I know that the hard thing right now is that you do not find enough sparring partners (that goes for others tackling different issues as well).
>
> Sven
>
>
Feb. 2, 2015
Re: [Pharo-dev] athens font rendering and subpixel antialiasing
by Igor Stasenko
On 2 February 2015 at 11:23, Ben Coman <btc(a)openinworld.com> wrote:
>
>
> On Mon, Feb 2, 2015 at 8:06 AM, Nicolai Hess <nicolaihess(a)web.de> wrote:
>
>> Ok, the best I could do:
>>
>> Sadly, it only works because I changed the default lcd_filter from cairo.
>> in cairo 1.7. was a public API for the lcd_filter.
>> since 1.8 this API is private again (the code for the different filter
>> settings is still there).
>>
>
>
> In trying to learn some background info, this found article [1] seems
> good, from which I learn:
>
> * Freely scalable it must be free from character drift.
>
> I guess this is what we want ?
>
> * Three main types of font rendering:
>
> * Hinting trades accuracy for consistency, and as a consequence of
> this, hinted text _accumulates character drift_ with hinted glyphs, often
> possessing different metrics to their un-hinted counterparts.
>
> So I guess we don't use hinting, which implies not freely scalable ?
>
> * Anti-aliasing results in output which is accurate but blurred,
> trading contrast for consistency and accuracy.
>
> * Sub-pixel-rendering exploits the physical geometry of LCD screens to
> increase the horizontal resolution of the device. Needs to be filtered to
> avoid color fringing and is incompatible with aggressive hinting strategies.
>
> * Sub-pixel-positioning is a generalisation of anti-aliasing and/or
> sub-pixel-rendering to allow for more accurate glyph placement, and is
> incompatible with aggressive hinting strategies.
>
> That article [1] advises:
>
> * For sub-pixel-rendering to function correctly it is necessary to
> enable the patent encumbered LCD filtering API. Many distributions,
> including Debian, do this already and is generally not a problem.
>
> * Versions of Cairo before the 1.10 release use their own intra-pixel
> filter. As of 2009 there are two sets of patches available that update
> legacy releases of Cairo to use an FIR inter-pixel filter. The first set
> pre-dates the filtering interface in FreeType and uses a custom FIR filter
> with the coefficients outlined in Gib98. The second set of patches, by
> David Turner, take advantage of the FreeType filtering interface.
>
> * It is recommended that distributions upgrade to Cairo 1.10 where at
> all possible. Here [2] is a post on that.
>
> So btw, what version of Cario are we using? I see latest is version
> 1.12.18.
>
>
CMCairo>>downloadURL
^ 'http://www.cairographics.org/releases/cairo-1.12.14.tar.xz'
> [1] https://freddie.witherden.org/pages/font-rasterisation/#spo07
> [2] http://lists.cairographics.org/archives/cairo/2010-January/018859.html
>
>
>
>
>> You can choose between
>> FT_LCD_FILTER_NONE
>> FT_LCD_FILTER_LEGACY
>> FT_LCD_FILTER_LIGHT
>> FT_LCD_FILTER_DEFAULT
>>
>> the default is FT_LCD_FILTER_LEGACY
>> but for this (so far, the best) result I used
>> FT_LCD_FILTER_DEFAULT
>> But there is no public API for this function anymore, so I had to
>> change the code.
>>
>>
>> We have to discuss how we proceed.
>>
>> The problems:
>> font rendering looks ugly ( at least for small font size like for menus,
>> lists and codepanes)
>> font rendering looks different on windows and linux
>>
>> possible solutions:
>> change build options for Freetype on Windos (enable
>> FT_CONFIG_OPTION_SUBPIXEL_RENDERING, potential patent infringement?)
>> change default filter (patching cairo source)
>>
>> or we leave everything as it is.
>> I do not know, and I'm starting to lose all interest.
>>
>>
>> nicolai
>>
>>
>>
>> 2015-02-01 19:38 GMT+01:00 Nicolai Hess <nicolaihess(a)web.de>:
>>
>>> **** patents!
>>>
>>> Hours, and days digging in the code for font rendering with cairo.
>>> I tried to find out why this "colored" subpixel antialising is not
>>> working although
>>> all option settings are set (in cairo) and in the source code of cairo
>>> the FT_SetLCDFilter
>>> call is really used! But the output does is just the same as with
>>> CAIRO_ANTIALIAS_GRAY,
>>>
>>> ... until I found THIS in the freetype config:
>>>
>>> /* Uncomment the line below if you want to activate sub-pixel rendering */
>>> /* (a.k.a. LCD rendering, or ClearType) in this build of the library. */
>>> /* */
>>> /* Note that this feature is covered by several Microsoft patents */
>>> /* and should not be activated in any default build of the library. */
>>> /* */
>>> /* This macro has no impact on the FreeType API, only on its */
>>> /* _implementation_. For example, using FT_RENDER_MODE_LCD when calling */
>>> /* FT_Render_Glyph still generates a bitmap that is 3 times wider than */
>>> /* the original size in case this macro isn't defined; however, each */
>>> /* triplet of subpixels has R=G=B. */
>>>
>>>
>>>
>>>
>>> ARGH!
>>>
>>> It still does not look as good as with the pharos freetypeplugin, but AT
>>> LEAST it looks
>>> equally on windows and linux , yeh.
>>>
>>>
>>> attached are three screenshots comparing
>>> the different athens drawings with the freetypeplugin
>>> athens on linux vs ftplugin
>>> athens on windows vs ftplugin
>>> athens on windows with enabled FT_CONFIG_SUBPIXEL_RENDERING vs ftplugin
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> 2015-01-31 10:18 GMT+01:00 stepharo <stepharo(a)free.fr>:
>>>
>>>>
>>>> In athens, there are "hints" you can set.
>>>> (CairoFontOptions/hintMetricsOff/hintMetricsOn/hintStyleFull ....)
>>>> I played a bit with different settings. Changing this settings change
>>>> the output, but I can not get it to look
>>>> like with the freetype plugin. I understand that this can not look
>>>> equally, because the FreeTypePlugin and caire work differently,
>>>> but the athens result looks bad compared with the other one.
>>>>
>>>>
>>>>
>>>>> - Pixel fitting. (The aliasing going on at the top of characters) Put
>>>>> Hinting: None in FreeType advanced features, and you will probably see
>>>>> something similar to the Athens rendering.
>>>>>
>>>>
>>>> Yes, we can change the freetypeplugin setting and cairofontoption
>>>> setting to make the output look equally - ugly :)
>>>>
>>>>
>>>> Nicolai
>>>>
>>>> Igor explained to me that FreeType offers a degenerated mode that when
>>>> the font does have the information for bold, kerning,....
>>>> computes a "guessed and approximated" default. Cairo does not offer
>>>> this api else Athens would use it.
>>>> So what would be interesting is to test using font having all the
>>>> information to see if Cairo display well the fonts.
>>>>
>>>> Stef
>>>>
>>>
>>>
>>
>
--
Best regards,
Igor Stasenko.
Feb. 2, 2015
Internship at Thales
by Marcus Denker
There is an offering at Thales for an internship for a student (in france):
> Thank you for your interest in a career with Thales. Below you will find a link to the job that you found on the mobile website. When clicked, this link will allow you to view the job details again and Apply for the job.
>
>
> STAGE Multi fenêtrage sous Pharo Smalltalk (Logiciel) (H\F) <http://jobs.thalesgroup.co.uk/fr/france/software-engineering/jobid6338665-s…>
Job ID: 1413963
Job Location: Brest, Bretagne, France
Position Type: Software Engineering
Business Unit: Thales Systemes Aeroportes S.A.
Post Date: 01/12/2015
Partout où des décisions critiques doivent être prises, Thales est présent. Sur les marchés que nous servons - aéronautique, espace, transport terrestre, sécurité, défense -, nous assurons la maîtrise de la « chaîne de décision critique » pour aider nos clients àchoisir la meilleure option et àagir en conséquence. L’expertise de ses 65 000 collaborateurs, sa puissance technologique et sa présence opérationnelle dans 56 pays font ainsi de Thales un acteur clé de la sécurité des citoyens, des infrastructures et des Etats. <>
La Global Business Unit Systèmes de Mission de Défense, leader européen et troisième acteur mondial sur ses marchés par sa taille et son niveau technologique, conçoit des équipements et des systèmes de mission pour avions, hélicoptères et drones militaires, bâtiments de surface et lutte sous la mer. Elle propose également une offre complète de services de maintenance en condition opérationnelle.
Thales Systèmes Aéroportés, filiale du Groupe Thales (3200 collaborateurs) regroupe différents domaines d’activités : systèmes de mission pour avions de mission et drones, Radars aéroportés de combat et surveillance, Systèmes de Guerre Electronique (air, terre, mer, espace), Soutien et Service Client.
Dans le cadre de notre développement, nous recherchons un(e) :
STAGE : Multi-fenêtrage sous Pharo Smalltalk (Logiciel) – H/F
Basé(e) àBrest (29)
Contexte :
Notre entité développe régulièrement des maquettes d’interfaces homme-machine (IHM) innovantes. L’innovation se situe autant au niveau de l’ergonomie qu’au niveau du design graphique visuel ou des éléments d’interaction. Le maquettage est souvent utilisé en séance avec les opérationnels, d’où l’emploi d’un langage dynamique comme Smalltalk qui permet la modification rapide (et en séance) du code et des éléments d’interaction.
Le maquettage/prototypage des interfaces Homme-Machine est donc actuellement réalisé sous SMOCK, un framework de maquettage développé en Smalltalk. Smalltalk Pharo est un excellent candidat pour la plateforme finale d'exécution du framework de maquettage/prototypage, cependant, certaines limitations de Pharo nous empêchent de l'utiliser de manière industrielle.
Missions :
Nous souhaitons expérimenter un environnement de maquettage sous Pharo, cependant, cette dernière limite l’affichage des IHM àl’intérieur d'une seule fenêtre de l'OS. Nous souhaitons, en relation avec la communauté Pharo, développer le multi-fenêtrage. Le stagiaire devra implémenter un mécanisme permettant l'ouverture et gestion de fenêtres multiples dans les OS Windows et Linux àminima. Une réutilisation de code existant dans la communauté Pharo et une reversion de code en OpenSource est envisageable.
Le candidat sera l'interlocuteur entre Thales et la communauté Pharo. Le candidat évaluera différentes solutions de multi- fenêtrage sous différents critères (performance, robustesse de la solution, portabilité de la solution...). La solution devra anticiper le futur et prévoir d'afficher des contenus visuels variés (vidéo, primitives de dessin 2D, OpenGL...).
L'objectif sera de développer un prototype IHM multi-fenêtres de démonstration sur Pharo afin de démontrer les nouvelles capacités et un aperçu des performances.
Formation souhaitée : Master 2 Pro ou 3ème année d'Ecole d'Ingénieur.
Connaissances souhaitées :
Le stagiaire devra avoir une connaissance du Smalltalk ou être motivé par l’apprentissage de celui-ci. Il devra ensuite être motivé par la conception d’interface homme machine de nouvelles générations et novatrices.
Période souhaitée et durée : àpartir de janvier 2015 pour une durée de 6 mois.
Feb. 2, 2015
Re: [Pharo-dev] athens font rendering and subpixel antialiasing
by Ben Coman
On Mon, Feb 2, 2015 at 8:06 AM, Nicolai Hess <nicolaihess(a)web.de> wrote:
> Ok, the best I could do:
>
> Sadly, it only works because I changed the default lcd_filter from cairo.
> in cairo 1.7. was a public API for the lcd_filter.
> since 1.8 this API is private again (the code for the different filter
> settings is still there).
>
In trying to learn some background info, this found article [1] seems good,
from which I learn:
* Freely scalable it must be free from character drift.
I guess this is what we want ?
* Three main types of font rendering:
* Hinting trades accuracy for consistency, and as a consequence of this,
hinted text _accumulates character drift_ with hinted glyphs, often
possessing different metrics to their un-hinted counterparts.
So I guess we don't use hinting, which implies not freely scalable ?
* Anti-aliasing results in output which is accurate but blurred, trading
contrast for consistency and accuracy.
* Sub-pixel-rendering exploits the physical geometry of LCD screens to
increase the horizontal resolution of the device. Needs to be filtered to
avoid color fringing and is incompatible with aggressive hinting strategies.
* Sub-pixel-positioning is a generalisation of anti-aliasing and/or
sub-pixel-rendering to allow for more accurate glyph placement, and is
incompatible with aggressive hinting strategies.
That article [1] advises:
* For sub-pixel-rendering to function correctly it is necessary to
enable the patent encumbered LCD filtering API. Many distributions,
including Debian, do this already and is generally not a problem.
* Versions of Cairo before the 1.10 release use their own intra-pixel
filter. As of 2009 there are two sets of patches available that update
legacy releases of Cairo to use an FIR inter-pixel filter. The first set
pre-dates the filtering interface in FreeType and uses a custom FIR filter
with the coefficients outlined in Gib98. The second set of patches, by
David Turner, take advantage of the FreeType filtering interface.
* It is recommended that distributions upgrade to Cairo 1.10 where at
all possible. Here [2] is a post on that.
So btw, what version of Cario are we using? I see latest is version
1.12.18.
[1] https://freddie.witherden.org/pages/font-rasterisation/#spo07
[2] http://lists.cairographics.org/archives/cairo/2010-January/018859.html
> You can choose between
> FT_LCD_FILTER_NONE
> FT_LCD_FILTER_LEGACY
> FT_LCD_FILTER_LIGHT
> FT_LCD_FILTER_DEFAULT
>
> the default is FT_LCD_FILTER_LEGACY
> but for this (so far, the best) result I used
> FT_LCD_FILTER_DEFAULT
> But there is no public API for this function anymore, so I had to
> change the code.
>
>
> We have to discuss how we proceed.
>
> The problems:
> font rendering looks ugly ( at least for small font size like for menus,
> lists and codepanes)
> font rendering looks different on windows and linux
>
> possible solutions:
> change build options for Freetype on Windos (enable
> FT_CONFIG_OPTION_SUBPIXEL_RENDERING, potential patent infringement?)
> change default filter (patching cairo source)
>
> or we leave everything as it is.
> I do not know, and I'm starting to lose all interest.
>
>
> nicolai
>
>
>
> 2015-02-01 19:38 GMT+01:00 Nicolai Hess <nicolaihess(a)web.de>:
>
>> **** patents!
>>
>> Hours, and days digging in the code for font rendering with cairo.
>> I tried to find out why this "colored" subpixel antialising is not
>> working although
>> all option settings are set (in cairo) and in the source code of cairo
>> the FT_SetLCDFilter
>> call is really used! But the output does is just the same as with
>> CAIRO_ANTIALIAS_GRAY,
>>
>> ... until I found THIS in the freetype config:
>>
>> /* Uncomment the line below if you want to activate sub-pixel rendering */
>> /* (a.k.a. LCD rendering, or ClearType) in this build of the library. */
>> /* */
>> /* Note that this feature is covered by several Microsoft patents */
>> /* and should not be activated in any default build of the library. */
>> /* */
>> /* This macro has no impact on the FreeType API, only on its */
>> /* _implementation_. For example, using FT_RENDER_MODE_LCD when calling */
>> /* FT_Render_Glyph still generates a bitmap that is 3 times wider than */
>> /* the original size in case this macro isn't defined; however, each */
>> /* triplet of subpixels has R=G=B. */
>>
>>
>>
>>
>> ARGH!
>>
>> It still does not look as good as with the pharos freetypeplugin, but AT
>> LEAST it looks
>> equally on windows and linux , yeh.
>>
>>
>> attached are three screenshots comparing
>> the different athens drawings with the freetypeplugin
>> athens on linux vs ftplugin
>> athens on windows vs ftplugin
>> athens on windows with enabled FT_CONFIG_SUBPIXEL_RENDERING vs ftplugin
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> 2015-01-31 10:18 GMT+01:00 stepharo <stepharo(a)free.fr>:
>>
>>>
>>> In athens, there are "hints" you can set.
>>> (CairoFontOptions/hintMetricsOff/hintMetricsOn/hintStyleFull ....)
>>> I played a bit with different settings. Changing this settings change
>>> the output, but I can not get it to look
>>> like with the freetype plugin. I understand that this can not look
>>> equally, because the FreeTypePlugin and caire work differently,
>>> but the athens result looks bad compared with the other one.
>>>
>>>
>>>
>>>> - Pixel fitting. (The aliasing going on at the top of characters) Put
>>>> Hinting: None in FreeType advanced features, and you will probably see
>>>> something similar to the Athens rendering.
>>>>
>>>
>>> Yes, we can change the freetypeplugin setting and cairofontoption
>>> setting to make the output look equally - ugly :)
>>>
>>>
>>> Nicolai
>>>
>>> Igor explained to me that FreeType offers a degenerated mode that when
>>> the font does have the information for bold, kerning,....
>>> computes a "guessed and approximated" default. Cairo does not offer this
>>> api else Athens would use it.
>>> So what would be interesting is to test using font having all the
>>> information to see if Cairo display well the fonts.
>>>
>>> Stef
>>>
>>
>>
>
Feb. 2, 2015
Re: [Pharo-dev] athens font rendering and subpixel antialiasing
by philï¼ highoctane.be
On Mon, Feb 2, 2015 at 10:51 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote:
>
> > On 02 Feb 2015, at 01:06, Nicolai Hess <nicolaihess(a)web.de> wrote:
> >
> > I do not know, and I'm starting to lose all interest.
>
> Nicolai,
>
> Please don't give up.
>
Yeah, don't. You rock.
>
> You are doing great work and we are all *very* impressed with your
> attitude/drive/motivation, especially since you are covering such a wide
> range of subjects. I know that the hard thing right now is that you do not
> find enough sparring partners (that goes for others tackling different
> issues as well).
> Sven
>
Phil
Feb. 2, 2015