MFEK / glif

A stand-alone glyph viewer and editor (UFO .glif). (ꞵ quality)
Apache License 2.0
190 stars 14 forks source link

"Industry Compatible" dialog idea #385

Open ctrlcctrlv opened 1 year ago

ctrlcctrlv commented 1 year ago

When you first download and install Blender it gives you an option for "Industry Compatible" settings, which basically means it tries to work as much like the most popular proprietary editors by default. I really like this and have used it because I used Maya before getting into Blender.

Could MFEK have an "Industry Compatible" settings mode and a "FontForge" settings mode to choose from for new users running the program for the first time?

Screenshot 2023-03-22 at 6 35 10 PM

You also get a list of themes to choose from, which I like:

Screenshot 2023-03-22 at 6 35 54 PM

Originally posted by @eliheuer in https://github.com/MFEK/glif/issues/384#issuecomment-1480465988

ctrlcctrlv commented 1 year ago

Could MFEK have an "Industry Compatible" settings mode and a "FontForge" settings mode to choose from for new users running the program for the first time? They could choose a theme as well. Basically copy exactly what Blender does here. The "Quick Setup" window only shows up if there aren't already MFEK files in the ~/.config directory.

Originally posted by @eliheuer in https://github.com/MFEK/glif/issues/384#issuecomment-1480468078

ctrlcctrlv commented 1 year ago

I'm opening this up to wider feedback.

What could I mention that would make you think of the names of the proprietary products made by e.g. @/glyphsapp, @/fontlab, @/roboFont, etc., without naming the product?

image

https://twitter.com/MFEKglif/status/1638724643790938113

eliheuer commented 1 year ago

I like the idea of user setting stored as a TOML file that can go in ~/.config/MFEK/.

ctrlcctrlv commented 1 year ago

@eliheuer this one would be a global setting yes. probably it belongs in ~/.config/MFEK/locale.conf.toml. Because it's the same type of issue as locale.

ctrlcctrlv commented 1 year ago

Even the constant names I'm going to have to mess with though so as not to mention their precious, precious babies lol. Probably something like locales::proprietary::G, ..::MF, ...::FL, ...FLB, ...libre::FONTFORGE{2012,_MASTER}.

ctrlcctrlv commented 1 year ago

Ugh didn't know they all had GitHub accounts. If I mentioned your proprietary product this is in no way an action item for you, there's no kind of legal assurance you can make that would change my mind on not naming you besides making your product free software, as capitalist corporations exist to enrich their shareholders and have a fiduciary duty to do that so even if you're cool now who knows about later. And, further to this, even if you give me the right you can't give other projects based on mine the right, and I don't want to give future maintainers more work. Easier not to name you at all. Make your products libre kthx