Peter wrote:
However, since all text output (except for TextBox/RichTextBox) go through
a theme driver, you could create a theme that uses pango instead of
DrawString to do the output, and p/invoke pango inside the theme code.
TextBox is a bit different, due to the extra work involved in figuring
Hi,Can we run mono's implementation of Windows Forms on Windows? I ask because our application needs Pango, and this is apparently supported by mono's WF, but is not by
MS.Net. In order to get Pango, we have been trying to get our app running using GTK#.
Trying, and growing old at an accelerated
Hello,
Can we run mono's implementation of Windows Forms on Windows?
Yes.
I ask because our application needs Pango, and this is apparently
supported by mono's WF, but is not by MS.Net. In order to get Pango,
we have been trying to get our app running using GTK#.
Mono's WF does not use
Miguel,
thanks for the reply.
I think it might be about the same amount of work using Pango in Win32
with Winforms than with Mono (or were you thinking that the widgets were
being rendered with Pango?)
Yes, we actually want to be able to render a complex non-Roman script
as part of a
Yes, we actually want to be able to render a complex non-Roman script
as part of a localized UI. We want to be able to handle scripts that
Microsoft does not yet support, such as Myanmar (Burmese). Pango does
handle these, because it supports SIL Graphite text rendering.
So, we'd need to get MWF
