We could provide .general
, .advanced
, .updates
and maybe .license
:
Since almost everyone would have a
General
preference tab. I wonder if we should ship with aPreferenableGeneral
type thing that has all these fields already filled out. My goal is to require the least amount of boilerplate possible to set up a preferences window. Thoughts?We could do this for
Advanced
too. And eventually even ship some localizations for those, so users don't have to care about that either.
(Originally posted by @sindresorhus in #6)
There is a $60.00 open bounty on this issue. Add more on Issuehunt.
- Checkout the Issuehunt explorer to discover more funded issues.
- Need some help from other developers? Add your repositories on Issuehunt to raise funds.
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
You're funding impactful open source efforts
You want to contribute to this effort
You want to get funding like this too