2021-06-27, 04:01 PM
Hey folks, thanks for the feedback. Paddy, it seems I missed your earlier question. Sorry about that.
Both requests are very good and interesting, thank you for those!
One main goal I have with Saillogger is to make it as simple as possible to use and make it "just work". In order to achieve that, I am trying to keep things as single stream as possible. As many of you probably develop software and are aware, one of hard things is to figure out how to make it work for as many people as possible without it becoming confusing and also very importantly, without breaking things in every new release. As combinations of configurations and differing behavior increase, complexity increases exponentially and testing becomes much harder, causing a lot of pain for users (and developers). Since this is a hobby project, and the time I can dedicate is limited, this is also especially important, at least at this stage of the development. So I try to come up with features that that are applicable to most, if not all user base. Admittedly, this is a bit hard to gauge. So, I'd love if you could log your requests at https://github.com/itemir/signalk-saillogger/issues, and vote on the things you'd like implemented. It would be super helpful!
Saillogger started as a hobby project for me, since I wanted an automated system to log our trip (initially on the California coast down to Mexico). Gradually usage has grown, and it is super exciting to see many users joining and many trips being logged every single day.
Both requests are very good and interesting, thank you for those!
One main goal I have with Saillogger is to make it as simple as possible to use and make it "just work". In order to achieve that, I am trying to keep things as single stream as possible. As many of you probably develop software and are aware, one of hard things is to figure out how to make it work for as many people as possible without it becoming confusing and also very importantly, without breaking things in every new release. As combinations of configurations and differing behavior increase, complexity increases exponentially and testing becomes much harder, causing a lot of pain for users (and developers). Since this is a hobby project, and the time I can dedicate is limited, this is also especially important, at least at this stage of the development. So I try to come up with features that that are applicable to most, if not all user base. Admittedly, this is a bit hard to gauge. So, I'd love if you could log your requests at https://github.com/itemir/signalk-saillogger/issues, and vote on the things you'd like implemented. It would be super helpful!
Saillogger started as a hobby project for me, since I wanted an automated system to log our trip (initially on the California coast down to Mexico). Gradually usage has grown, and it is super exciting to see many users joining and many trips being logged every single day.