Hi dirkhh,
All good points and yes, having a separate collector/repository is definitely a better approach.
I wasn't planning to add any charting in VisibleTesla because (a) there is already the visualization work that you and hans have in teslams which is more complete than anything I would do, and (b) I didn't want to add the complexity of having the app, a collector daemon, and a database.
When someone asked if I would at least add charting that happens while the app is running, I decided that is sounded manageable, would provide some basic capability, and would give me an excuse to look at JavaFX charting. That last part has not been as pleasant as I'd hoped
I'm going to get this basic approach working and then think about how to tie it into a separate data collector and repository.
Thanks for your continued feedback and advice,
Joe
All good points and yes, having a separate collector/repository is definitely a better approach.
I wasn't planning to add any charting in VisibleTesla because (a) there is already the visualization work that you and hans have in teslams which is more complete than anything I would do, and (b) I didn't want to add the complexity of having the app, a collector daemon, and a database.
When someone asked if I would at least add charting that happens while the app is running, I decided that is sounded manageable, would provide some basic capability, and would give me an excuse to look at JavaFX charting. That last part has not been as pleasant as I'd hoped
I'm going to get this basic approach working and then think about how to tie it into a separate data collector and repository.
Thanks for your continued feedback and advice,
Joe