On Feb 22, 2017, at 1:41 AM, pd-list-request@lists.iem.at wrote:
The primary goal is to make Pd(-vanilla)'s appearance consistent across platforms. Part of that is that box sizes don't change when switching platforms. As a side effect of this fix, patches also don't change appearance when switching between Pd flavors (Do we still need to care about Pd-extended, since it's been phased out?).
From what I gathered from the "Pd Metrics on Xubuntu 16 04 02 LTS" thread, the following steps are required to achieve that goal:
Adjustments of the font metrics. It seems we can just take the ones from Pd-extended.
Use the same font on all platforms. Pd apparently looks for "DejaVu Sans Mono" first, so that is the one we should make available everywhere.
I’d suggest joining in the “dejavu” branch on Github: https://github.com/pure-data/pure-data/pull/42 https://github.com/pure-data/pure-data/pull/42
On Linux, it's the task of Pd's package maintainers that DejaVu is installed when Pd is to be installed. If I'm not mistaken, DejaVu is installed per default on all Debian derivatives, so we do not have to care about them.
Yup
On Windows, the font is missing and the Pd installer could be adapted to install the font along with Pd.
That would be the easiest solution. A more complicated but perhaps better solution is to load the font locally when running the GUI.
On macOS, I don’t know what the required steps would be.
I’ve already provided them in the branch. This is working for Mac.
I propose that before we submit any fixes to Miller we are absolutely certain that the adapted font metrics are correct in that the resulting box sizes are consistent for all available font sizes (8, 10, 12, 16, 24, 36). And when testing this, we make sure that Pd uses "DejaVu Sans Mono". Only then we submit any fix.
Yes. Testing has already been happening see: https://github.com/pure-data/pure-data/wiki/Crossplatform-font-metrics-%26-c... https://github.com/pure-data/pure-data/wiki/Crossplatform-font-metrics-&-comparisons
If we find good font metrics, I'll submit a fix to the NSIS installer script, so that installing DejaVu is part of the Pd installation process on Windows. Yet, I'm not sure whether it is enough to simply drop the font files into %windir%\Fonts or whether the font needs to be registered somewhere.
Note, I’ve added DejaVu Sans Mono to a “font” folder in the dejavu branch.
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
Hi Dan,
Note, I’ve added DejaVu Sans Mono to a “font” folder in the dejavu branch.
On windows I noticed huge differences & trouble placing only “DejaVuSansMono.ttf”
These 2 have to be included:
DejaVuSansMono.ttf DejaVuSansMono-Bold.ttf
Can you test on Mac ?
Mensaje telepatico asistido por maquinas.
From: Pd-list pd-list-bounces@lists.iem.at on behalf of Dan Wilcox danomatika@gmail.com Sent: Wednesday, February 22, 2017 7:35 PM To: Roman Haefeli Cc: Pd-List Subject: Re: [PD] Cross-platform uniform GUI rendering of patches.
On Feb 22, 2017, at 1:41 AM, pd-list-request@lists.iem.atmailto:pd-list-request@lists.iem.at wrote:
The primary goal is to make Pd(-vanilla)'s appearance consistent across platforms. Part of that is that box sizes don't change when switching platforms. As a side effect of this fix, patches also don't change appearance when switching between Pd flavors (Do we still need to care about Pd-extended, since it's been phased out?).
From what I gathered from the "Pd Metrics on Xubuntu 16 04 02 LTS"
thread, the following steps are required to achieve that goal:
Adjustments of the font metrics. It seems we can just take the ones from Pd-extended.
Use the same font on all platforms. Pd apparently looks for "DejaVu Sans Mono" first, so that is the one we should make available everywhere.
I’d suggest joining in the “dejavu” branch on Github: https://github.com/pure-data/pure-data/pull/42
On Linux, it's the task of Pd's package maintainers that DejaVu is installed when Pd is to be installed. If I'm not mistaken, DejaVu is installed per default on all Debian derivatives, so we do not have to care about them.
Yup
On Windows, the font is missing and the Pd installer could be adapted to install the font along with Pd.
That would be the easiest solution. A more complicated but perhaps better solution is to load the font locally when running the GUI.
On macOS, I don’t know what the required steps would be.
I’ve already provided them in the branch. This is working for Mac.
I propose that before we submit any fixes to Miller we are absolutely certain that the adapted font metrics are correct in that the resulting box sizes are consistent for all available font sizes (8, 10, 12, 16, 24, 36). And when testing this, we make sure that Pd uses "DejaVu Sans Mono". Only then we submit any fix.
Yes. Testing has already been happening see: https://github.com/pure-data/pure-data/wiki/Crossplatform-font-metrics-%26-c...https://github.com/pure-data/pure-data/wiki/Crossplatform-font-metrics-&-comparisons
If we find good font metrics, I'll submit a fix to the NSIS installer script, so that installing DejaVu is part of the Pd installation process on Windows. Yet, I'm not sure whether it is enough to simply drop the font files into %windir%\Fonts or whether the font needs to be registered somewhere.
Note, I’ve added DejaVu Sans Mono to a “font” folder in the dejavu branch.
Dan Wilcox @danomatikahttp://twitter.com/danomatika danomatika.comhttp://danomatika.com robotcowboy.comhttp://robotcowboy.com
In the source code for Pd, I have also changed the default font weight to “normal”, so there shouldn’t be a need for the bold version. I have to fix the Windows build to be able to see it for myself next, though.
On Feb 22, 2017, at 1:32 PM, Lucas Cordiviola lucarda27@hotmail.com wrote:
Hi Dan,
Note, I’ve added DejaVu Sans Mono to a “font” folder in the dejavu branch.
On windows I noticed huge differences & trouble placing only “DejaVuSansMono.ttf”
These 2 have to be included:
DejaVuSansMono.ttf DejaVuSansMono-Bold.ttf
Can you test on Mac ?
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
Well, but what would happen if some use the -font-weight bold.
Anyway I think there's trouble shipping only one.
My tests are done with this zip pkg:
http://lucarda.com.ar/x/pdfont.zip
It has extended font metrics & TWAPI for loading the fonts.
Try it, you will see the font mess if only one is shipped.
uninnstall your dejavu before tests.
more info inside "Dan-read-this.txt"
Salutti, Lucarda.
Mensaje telepatico asistido por maquinas.
From: Dan Wilcox danomatika@gmail.com Sent: Wednesday, February 22, 2017 9:06 PM To: Lucas Cordiviola Cc: Roman Haefeli; Pd-List Subject: Re: [PD] Cross-platform uniform GUI rendering of patches.
In the source code for Pd, I have also changed the default font weight to “normal”, so there shouldn’t be a need for the bold version. I have to fix the Windows build to be able to see it for myself next, though.
On Feb 22, 2017, at 1:32 PM, Lucas Cordiviola <lucarda27@hotmail.commailto:lucarda27@hotmail.com> wrote:
Hi Dan,
Note, I’ve added DejaVu Sans Mono to a “font” folder in the dejavu branch.
On windows I noticed huge differences & trouble placing only “DejaVuSansMono.ttf”
These 2 have to be included:
DejaVuSansMono.ttf DejaVuSansMono-Bold.ttf
Can you test on Mac ?
Dan Wilcox @danomatikahttp://twitter.com/danomatika danomatika.comhttp://danomatika.com robotcowboy.comhttp://robotcowboy.com
On Mit, 2017-02-22 at 14:06 -0700, Dan Wilcox wrote:
In the source code for Pd, I have also changed the default font weight to “normal”, so there shouldn’t be a need for the bold version. I have to fix the Windows build to be able to see it for myself next, though.
Isn't changing the font weight a separate issue from fixing consistent appearance across platforms, in that the font weight is a design decision while using the same font and working font metrics are a bug fix?
I propose that changing the font weight is treated as a separate step. Miller probably consciously chose bold weight and we shouldn't treat it as a bug. Personally, I'm not even in favor of font weight normal, though I hardly care.
Roman
2017-02-22 19:20 GMT-03:00 Roman Haefeli reduzent@gmail.com:
Miller probably consciously chose bold weight and we shouldn't treat it as a bug.
Hi, what you're missing is that this is different for each platform... Mac OS doesn't have it bold, while the others do (and while Extended and Pd-L2ork/Purr Data also do not). So it is an inconsistency and a bug.
cheers
On 2017-02-22 23:34, Alexandre Torres Porres wrote:
Hi, what you're missing is that this is different for each platform... Mac OS doesn't have it bold, while the others do (and while Extended and Pd-L2ork/Purr Data also do not). So it is an inconsistency and a bug.
IIRC, the reason for the inconsistency is because it was explicitely requested. the linux fraction of Pd users weighed in heavily for bold, whereas OSX and W32 users tended to regular.
anyhow, i agree that all GUIs of Pd should consistently use the same **bold** font.
tfgmasdr IOhannes
2017-02-23 5:15 GMT-03:00 IOhannes m zmoelnig zmoelnig@iem.at:
IIRC, the reason for the inconsistency is because it was explicitely requested. The linux fraction of Pd users weighed in heavily for bold, whereas OSX and W32 users tended to regular.
I'm getting bold by default on windows... so that doesn't add up.
anyhow, i agree that all GUIs of Pd should consistently use the same **bold** font.
I thought the agreement was to go for normal font in all systems, which is also how it goes for Extended/Purr Data
cheers
On Don, 2017-02-23 at 11:55 -0300, Alexandre Torres Porres wrote:
anyhow, i agree that all GUIs of Pd should consistently use the same **bold** font.
I thought the agreement was to go for normal font in all systems, which is also how it goes for Extended/Purr Data
Citation please.
Roman
-
Alexandre Torres Porres -
Dan Wilcox -
IOhannes m zmoelnig -
Lucas Cordiviola -
Roman Haefeli