Re: Removal of plugins and collab from FontForge

On April 1, 2019 03:20:50 PM [email protected] wrote:
> On the general issue of parity: there's a big difference between
> removing the existing functionality and keeping the level of support in
> both the same. I'm about to add support for genericGlyphChange onto
> fontforge.glyph. Should I /not/ do this unless and until I implement the
> equivalent in the scripting language? Wouldn't it be kind of a nightmare
> to invoke anyway, given the lack of keyword parameters or a hash table?

Try if you can, but if not, better to add what you can, than nothing at 
all.


_______________________________________________
fontforge-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html