View Single Post
Old 03-26-2024, 04:26 PM   #70
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 7,688
Karma: 5444398
Join Date: Nov 2009
Device: many
When we make decisions for Sigil, we try to put ourselves into the shoes of a typical user of Sigil. Luckily, Sigil's main developers and contributors all use Sigil extensively and have for quite some time.

But given how bloated most software has become, and given the limited amount of time we have to spend supporting and developing Sigil, we need to make tradeoffs of new features versus usefulness for the typical user.

My argument was that with judicial choice and use of clips (and because of Pareto's 20% of features handle 80% of needs) that there is no significant benefit for the typical user of Sigil for adding to the current number of clip icons on the toolbar. Especially if the user chooses clips that are not redundant to existing tools.

Is that subjective? Yes. But some users can and do "misuse" features at times. So we just can not cater to all feature requests. We must evaluate each one wearing our "typical user" shoes.

That is the thought process we go through for most new feature suggestions.

But as I said, open source gives you the power to change things how you want it without having to worry about making any other users happy.

You can easily clone from Sigil's master branch in github, add in your changes which are all concentrated in main.ui. Make your build. Then when a new release of Sigil happens, you can pull directly from our github repo into yours and it will happily merge in your main.ui changes or alert you as to any merge conflicts if it can't. Plus the Sigil codebase evolves slowly making conflicts even less likely.

So no worries.

Hope this explains things.

Last edited by KevinH; 03-26-2024 at 04:35 PM.
KevinH is offline   Reply With Quote