Re: Making Python3 the default
Skef Iterum <[email protected]> Tue, 4 Jun 2019 10:40:00 -0700
| Newsgroups | gmane.comp.fonts.fontforge.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============0378408259503879991==
Content-Type: multipart/alternative;
boundary="------------B5644309EE4E5FDEEAD96280"
Content-Language: en-US
This is a multi-part message in MIME format.
--------------B5644309EE4E5FDEEAD96280
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
I've thought about this a little bit. It points down the road of a text
or array/dictionary structure "language" for specifying custom dialogs.
If there were already such a thing in wide use, FontForge could grab or
borrow it. That might be a sensible project, and could be supported into
the future. However, poking around I didn't find anything like that in
use. Since it's such an obvious direction that makes me suspect that
other projects have gone further down that road and then abandoned it.
Anyway, there's another viable approach that would be easier to support
-- probably pretty straightforward. Using RPyC (or whatever equivalent)
one could start an external process and communicate back and forth with
it. It could then use whatever graphics layer it wanted. The FontForge
side support you'd want to make things clean would be:
1. An interface for retrieving window dimensions relative to the screen
(tricky in some cases), and
2. An interface for a modal "grab" and "ungrab", to temporarily freeze
the interface on the FontForge side.
Like adding support for GTK, this would let you do almost anything,
including add non-modal windows if you wanted.
Skef
On 6/4/19 5:06 AM, Abraham Lee wrote:
> Hey, Fred!
>
> On Mon, Jun 3, 2019 at 4:17 AM Fred Brennan <[email protected]
> <mailto:[email protected]>> wrote:
>
> We talked about getting PyGTK support in https://github.com/fontforge/
> fontforge/issues/3663
> <https://github.com/fontforge/fontforge/issues/3663>, which might
> interest you considering your interest in
> using foreign GUI platforms inside FontForge's python interface.
>
>
> Whatever works, but if energy would be spent better on other things
> that need to be done first, that’s ok, too. This is a wishlist thing
> for me.
>
> My particular usage would prefer, at least, to be able to make
> slightly more populated input popups where I can have text inputs,
> drop downs, radio buttons, etc., all in a single window. At the
> moment, using the few popup types available, I have to use anywhere
> from 2-6 individual input text boxes because the popup only allows for
> one at a time. It’s not a huge deal, just a convenience thing.
>
> Ideally, being able to have a live connection between the outline
> editor and a separate input popup, that would allow me to “apply” an
> affect (similar to the current transform GUI) would be nice, but not
> critical.
>
> I’m grateful for whatever can be done since I have about 30-50 plugins
> I regularly use and being able to streamline them would be great, but
> don’t feel like this needs to be top priority. This change to Python 3
> is a good one and it finally gives me a solid reason to port my own
> code to Python 3.
>
> Best,
> Abraham
>
>
> _______________________________________________
> fontforge-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/fontforge-devel
> http://fontforge.10959.n7.nabble.com/Developer-f3.html
--------------B5644309EE4E5FDEEAD96280
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I've thought about this a little bit. It points down the road of
a text or array/dictionary structure "language" for specifying
custom dialogs. <br>
</p>
<p>If there were already such a thing in wide use, FontForge could
grab or borrow it. That might be a sensible project, and could be
supported into the future. However, poking around I didn't find
anything like that in use. Since it's such an obvious direction
that makes me suspect that other projects have gone further down
that road and then abandoned it.</p>
<p>Anyway, there's another viable approach that would be easier to
support -- probably pretty straightforward. Using RPyC (or
whatever equivalent) one could start an external process and
communicate back and forth with it. It could then use whatever
graphics layer it wanted. The FontForge side support you'd want to
make things clean would be:</p>
<ol>
<li>An interface for retrieving window dimensions relative to the
screen (tricky in some cases), and</li>
<li>An interface for a modal "grab" and "ungrab", to temporarily
freeze the interface on the FontForge side.</li>
</ol>
<p>Like adding support for GTK, this would let you do almost
anything, including add non-modal windows if you wanted. <br>
</p>
<p>Skef<br>
</p>
<p>On 6/4/19 5:06 AM, Abraham Lee wrote:<br>
</p>
<blockquote type="cite"
cite="mid:CAHAQwh3CU10r-5UC7T0twoEX942g+j=g=gDMBvW+rAw-fFk1_g@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div>
<div dir="auto">Hey, Fred!<br>
</div>
</div>
<div><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Jun 3, 2019 at 4:17
AM Fred Brennan <<a href="mailto:[email protected]"
moz-do-not-send="true">[email protected]</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">We talked
about getting PyGTK support in <a
href="https://github.com/fontforge/fontforge/issues/3663"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://github.com/fontforge/<br>
fontforge/issues/3663</a>, which might interest you
considering your interest in <br>
using foreign GUI platforms inside FontForge's python
interface.</blockquote>
<div dir="auto"><br>
</div>
<div dir="auto">
<div dir="auto">
<div dir="auto">Whatever works, but if energy would be
spent better on other things that need to be done first,
that’s ok, too. This is a wishlist thing for me. </div>
<div dir="auto"><br>
</div>
<div dir="auto">My particular usage would prefer, at
least, to be able to make slightly more populated input
popups where I can have text inputs, drop downs, radio
buttons, etc., all in a single window. At the moment,
using the few popup types available, I have to use
anywhere from 2-6 individual input text boxes because
the popup only allows for one at a time. It’s not a huge
deal, just a convenience thing.</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Ideally, being able to have a live
connection between the outline editor and a separate input
popup, that would allow me to “apply” an affect (similar
to the current transform GUI) would be nice, but not
critical.</div>
<div dir="auto"><br>
</div>
<div dir="auto">I’m grateful for whatever can be done since
I have about 30-50 plugins I regularly use and being able
to streamline them would be great, but don’t feel like
this needs to be top priority. This change to Python 3 is
a good one and it finally gives me a solid reason to port
my own code to Python 3.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Best,</div>
<div dir="auto">Abraham</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
fontforge-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/fontforge-devel">https://lists.sourceforge.net/lists/listinfo/fontforge-devel</a>
<a class="moz-txt-link-freetext" href="http://fontforge.10959.n7.nabble.com/Developer-f3.html">http://fontforge.10959.n7.nabble.com/Developer-f3.html</a>
</pre>
</blockquote>
</body>
</html>
--------------B5644309EE4E5FDEEAD96280--
--===============0378408259503879991==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
--===============0378408259503879991==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
fontforge-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html
--===============0378408259503879991==--