casainho said:
stancecoke said:
Sad to read, that you want to quit this project....
I think there's no problem with the Java Tool, it makes the firmware usable for people who don't have computer skills like you or me
If there's a bug in the Java Tool, I can fix it easily. But for this we need the feedback of the users.
I think Basia is using your master. I don't know anyone who uses my fork...
Seems that more people want to use the firmware. I think would be good to have a good documentation and force users to read it before asking for help. Other way I think will be to much work and repetitive questions.
I think it would be more important to unify things. Not knowing the structure of the project and the different parts seems to be the main source of confusion. I know it's not my place to demand things, but it would definitely improve understanding among newbies.
Multiple forks, separate documentations, different branches, several ways to create configs (including outdated ones!)... I'm not surprised that people are confused.
Multiple forks: Yours and Stancecoke's. Ideally (really, ideally) you would merge them and have a #define to switch between different behaviors at compile time.
Separate documentations: Why is there
this with almost no content, and
this? Then the Windows instructions
here which look completely different. Plus there's Stancecoke's German docs page. This should all be in one place, with different languages kept in sync as best as possible. A Wiki would be ideal, as it encourages others to contribute aswell and allows for corrections and improvements.
Different branches: They are necessary, I know that. Maybe add to the documentation how they differ from the main branch.
Config files: I understand the need to have a Windows tool for those not comfortable editing header files. But as we could see multiple times now, it needs to be kept in sync with features and changes at all times to be useful. Either that, or just force people to edit the header file. Which would be less comfortable, but better in the long run (with appropiate documentation)