Quote:
Originally Posted by lordeagle
Sorry for the inconvenience. I think I started with PRs back to the original repository. But some-when I changed the work mode:
- PRs took a lot of time to be answered
- I started to make big changes without taking the time for alignment
- I made my first baby steps with RUST; so my efforts are surely far from perfect
- Releases, Changelogs, Actions pipelines was something I missed, and took me to a level where I needed control over the repo.
So I opted for the easy way to have progress. Having a single source of truth was sort of always the plan. But I didn't get much feedback on the work and thought there's no demand. If someone is willing to have the lead here, I'll gladly share my work or open it up for others to contribute.
 |
No need to apologise, just a shame if treasure is buried. I am merely a follower in your path, thanks to einkanchovies and AI coding tools, I have made an entry into programming that otherwise wouldnt have been possible. About the pull request, I understand, I made my own pull request and was rejected ha. Working on my fork has given me the opportunity to dip my toes, even if no one uses it will have been useful to me. I no longer have a use case for the program either lol as an android eink device > kobo, and I came here as an aspiring vibe coder rather than consumer ,and perhaps to share the result with someone who might wanna collaborate
https://github.com/noobyme/kobovncvi...ain/client/src
My fork:Features I have added/working on:Scaling, Gui, Padding, Touch input, general bug fixing(droidvnc errors, over-updates crashing the device), custom a2 encoding. Many features were added purely by AI, others guided by AI. I cant really have claimed to have implemented on my own