-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modularization #54
Closed
Comments
I think this would be a really nice addition to the SDK! |
ChristopheCVB
added
enhancement
New feature or request
and removed
to specify
labels
Nov 30, 2022
— with
Volta.net
ChristopheCVB
added a commit
that referenced
this issue
Dec 4, 2022
Draft
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current way of handling actions works great for small plugins, however, for larger ones, it gets a bit messy.
Add the possibility for Actions and Connectors to be classes that extend something from the SDK.
Basically an abstract class such as:
TPAction
would extend it as isTPConnector
would extend it and also add the necessary implementation to handle the ConnectorValueDevelopers would then have to register those to the
TouchPortalPlugin
before connectingThe text was updated successfully, but these errors were encountered: