Re: [fontforge-devel] Making Python3 the default

[Abraham L. <tis...@gm...>]

Hey, Fred!

On Mon, Jun 3, 2019 at 4:17 AM Fred Brennan <cop...@ki...> 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

>