You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's already many cool enhancements identified .
I would like to extend that list with some more. But I think I might be better to share some ideas before creating any issues. I would like to know what do you think about them, if they'd add some value to Gnofract4d.
The goal is to know what users of Gnofract4d expect it to be in the future, and what should be the focus of development.
Here is a list of identified "problems" and possible solutions. Some of them are already proposed, others have been discussed in a different context:
Installation is complicated for regular users, and they also have to struggle with dependencies:
Regarding to the installation process, and trying to improve this process and make it possible for any user (with or without technical skills), I would suggest take into consideration the option of building and distributing binary packages for different Linux distros. I think it would be great if an automatic process would be in charge of this process, for example, «Open Build Service».
There's already many cool enhancements identified .
I would like to extend that list with some more. But I think I might be better to share some ideas before creating any issues. I would like to know what do you think about them, if they'd add some value to Gnofract4d.
The goal is to know what users of Gnofract4d expect it to be in the future, and what should be the focus of development.
Here is a list of identified "problems" and possible solutions. Some of them are already proposed, others have been discussed in a different context:
Installation is complicated for regular users, and they also have to struggle with dependencies:
calculation speed
zoom level limitation
user interface feedback
formula language complexity and lack of documentation
we don't have any usage statistics (see Statistics about users? #163 )
The text was updated successfully, but these errors were encountered: