glitchapp {l Wrote}:Unless you have a very static idea for the software you are writting, constructive feedback could sometimes help make it even better.
I agree. This is why I ask for constructive feedback, and I have made some improvements based on this feedback already, and some that I cannot do at this time.
The things I think can improve does not require to read the documentation because I'm not talking about the code and no matter which parameters are required, you can always provide them with different methods and not just the terminal.
That is partially true, but still it would help to know which parameters are required and how they work in order to suggest improvements.
The problem is that I do not have a icon.
I've seen on other threads that someone have created severals for you, you can always improve them in the future.
Yes, and I have collected them at
http://zzo38computer.org/freeheromesh/logos/. The dimensions are wrong, and I am not sure that they are that good, but if necessary I can use one anyways (fixing the dimensions if necessary, too; or making one based on it if that would be better), at least temporarily.
I decided that specifying by command-line arguments is better
That's fine and that's your opinion. I think that the real question here is, is it better for who? If you want the tool to be played for a wide audience then I disagree with it, but that's my constructive opinion.
Better for many users, but not everyone likes it. I hope that we can have both ways in case some people like other way (or even if some people who do like to use both).
If you intend to have a separate launcher even a menu written in bash script will do the work (at least till something more sophisticated is written).
Still it asks: What exactly should be displayed? (Files could be installed anywhere. I suppose a version using AppImage could look in its own directory, and in the AppImage's own home directory (if it exists); however, I am not entirely sure.) What if you want to editing vs playing, etc? (Editing requires non-composite puzzle sets; playing is possible with either composite or non-composite, but composite will be easier to deal with.) There are other questions too, to decide how to make it; these are only some, but I do have some ideas, but I do not have all of the ideas.
I have not tried writing menus in bash scripts before, although I can try (but I am not sure that it is necessarily any good).
A future launcher program might have a place to install puzzle sets (both for the user and for the system), and optionally access catalog services (at the user's request), as well as allowing accessing other directories if wanted.
(Note that the existing implementation already checks for symlinks and works correctly in this situation, so it is possible for a menu that looks in a specific directory even if that directory contains symlinks to the real puzzle set files.)
I hope this feedback helps!
Some of it does; thank you.