TouchPortalAPI is no longer being maintained by the original dev. I have considered either writing my own C# API Library or taking over maintenance of TouchPortalAPI through my fork, however, this also presents an opportunity to just re-write the code using a language that is more portable than C#.
So what does this mean for the current version?
With the exception of #18, I will still be work on fixing bugs in the older version up until I get feature parity with the new version. New features will likely not get implemented on either version until I achieve feature parity unless the feature is necessary to address usability issues.
What does this mean for the re-written version?
Switching to the re-written version may be a bit more involved than just upgrading the plugin. I will try to make the switch as painless as possible, but I can't make any guarantees. The new version will also be useless for most people until I achieve feature parity between the two versions. That said, I would prefer if people helped test the re-written version to make sure that it is as bug free as possible. I will also be using a programming language that is more portable than C# currently is. This may allow the plugin to work on Macs, but this is by no means a commitment to officially support platforms other than Windows.
When will the re-written version be released?
When it is done. I've been quite busy as of late and I don't really know how much time I will be able to spend on this. I also want to spend time thinking about how everything will come together instead of just starting to write code and seeing where that gets me. Hopefully, the more thoughtful approach will mean that it will be easier for me to maintain the re-written version.
TouchPortalAPI is no longer being maintained by the original dev. I have considered either writing my own C# API Library or taking over maintenance of TouchPortalAPI through my fork, however, this also presents an opportunity to just re-write the code using a language that is more portable than C#.
So what does this mean for the current version?
With the exception of #18, I will still be work on fixing bugs in the older version up until I get feature parity with the new version. New features will likely not get implemented on either version until I achieve feature parity unless the feature is necessary to address usability issues.
What does this mean for the re-written version?
Switching to the re-written version may be a bit more involved than just upgrading the plugin. I will try to make the switch as painless as possible, but I can't make any guarantees. The new version will also be useless for most people until I achieve feature parity between the two versions. That said, I would prefer if people helped test the re-written version to make sure that it is as bug free as possible. I will also be using a programming language that is more portable than C# currently is. This may allow the plugin to work on Macs, but this is by no means a commitment to officially support platforms other than Windows.
When will the re-written version be released?
When it is done. I've been quite busy as of late and I don't really know how much time I will be able to spend on this. I also want to spend time thinking about how everything will come together instead of just starting to write code and seeing where that gets me. Hopefully, the more thoughtful approach will mean that it will be easier for me to maintain the re-written version.