Added the errors panel to display when an error is hit and made the readme more actionable. Hopefully the pipeline of the demo gif serves as usage instructions.
I’ve baked in a lot of error handling and messages that the troubleshooting shouldn’t really occur as much as the messages serve as indicators of what needs to be done.

Changelog

• Enhance troubleshooting formatting
• Updated README.md
• Error panel, release versioning + demo gif
• The feelings update

Codename: The Feelings Update

This update mostly focuses on QoL and the overall feel of the plugin. So the status bar now shows initialization progress and there were tweaks to the wakatime download after v2 release tweaked how the internal/normal config saved cli_version. The wakatime_cli should now properly download and extract on most architectures and removed cases of redownloading the same version of semantic versioning. Internal config is now parsed and appended with the proper versioning and checked with a tuple to verify which version is the latest in semantic versioning.
Goals:
status change [√]
errors panel []

Changelog

• The feelings update

Main extension script had been modified to better handle errors and display logic had been added to give the extension a nicer visual and alert the user when the script catches an error. Still you can’t catch what you don’t know so I’ll add some troubleshooting steps and better guides to the repo. Big shoutout to all the feedback I’ve been given as the major pain point seemed to be the tool was under explained and when it didn’t work you were lost. Hopefully the display and modified readme will help to lower that barrier a bit.

One small issue I’ve seen but been unable to recreate is a delay of a couple of minutes before the project is recognized on hackatime, unsure if this is intended behavior and may be a can of beans to open later

Changelog:

• Clarify installation steps in README (4e2cdda)
• Error Display State Logic (a936ac4)
• tMerge branch ‘main’ of https://github.com/BioSh0cked/WakatimeTD (c57b9df)
• Compiled v0.2.0 (de58cd5)

The logic was reviewed and corrected to better fit the logic control as stated in the WakaTime documentation for plugins. It now correctly logs the correct flags and pushes according to the states isWrite flag flow. I’ve kept the python file in even though the .tox component no longer references it to allow for easier version control and editing as well as more direct access to viewable components. This project has collected a lot of dust and I’ve put of really working on it due to a difficult schedule and lacking drive to allow for all system architectures. Now that I have more time on my hands if there’s any bugs or system incompatibilities please leave a comment here or open an issue on the github page so I can readily patch new versions.

One feature I’m already thinking of is adding some visual to the component to spice things up, feel free to put some suggestions into my head mind-control style!

Commit

• Write logic (7ddabf0)
• Compiled .tox and removed .py dependancy (4f8f877)
• Add README for plugin (5b8acac)

Created popDialog for prompting api key when missing from config. My plans for next session are going to be balancing how it’s displayed a little as currently it appears in the top-right corner which is not the best. The logic for sending heartbeats needs to be tweaked to activate flags on edit actions and write on save. I’ll also check if additional info like os attributes and plugin name are being sent properly.

Commit

• KeyDialog Complete (78868f2)

Merging hackatime projects, unfortunately still missing time from initially setting up TD but what can you do.
Quite ironic that the best example for the usefulness of this project is itself.

Fixed the path for entity and started the ui components for the input window if missing an api key.
Feat:

• Entity logic fix + partial api prompt (e0633a4)

First devlog yay!

Finally got a heartbeat to be sent so figured I’d need to get logging, I always feel weird writing a devlog before anything works preliminarily.
Almost gave up on this project before this first devlog
There was EXTREME issues with having the base comp recognize and promote the extension dat. There is a lot of very niche and specific hierarchy that needs to be implemented to have Touchdesigner recognize the functions that is not very well documented. Many hours spent on obscure docs and videos to get a slapstick method going to have the extension called as a module.

Checkpoint commits:

• Initial Commit (5681bd5)
• Bedtime commit (47033ea)
• First heartbeat success (8d00c63)