View Single Post
Old 10-28-2015, 11:46 AM   #4
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: 8,849
Karma: 6120478
Join Date: Nov 2009
Device: many
Hi,

Quote:
Originally Posted by Arios View Post
what can simplify software maintenance ? And if some features like BV have to be sacrificed to achieve this result, it is a good tradeoff.
Good point. From a software maintenance point of view, removing Xerces, reducing the number of third party software pieces, removing boost, etc all helped immensely in that regard. Then making embedded python a build time tool (not part of the tree) instead of how it was originally planned, helped too.

Other things similar to that would be:

1. removing BookView
2. removing support for Python 2.7 plugins (after helping to port them)
3. removing prettyprint and making it a plugin

These would all simplify Sigil maintenance but at the same time, these all work now and could reasonably be kept working **if** they are important to users.

So I guess I am looking for guidance from users, which of these features are important to them, what we should keep, and which should go away to simplify things over the long run.

Thanks,

KevinH
KevinH is offline   Reply With Quote