You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At this time we can go forward and implement generation from templates.
Hopefully I will return from my vacation in middle of January and will start that 😄
Additional info: #6
About API stabilization:
I think we can start as is and try new in process of templates generation implementation. @julianoes@JonasVautherin if you will have any questions and suggestions related for current API (in develop branch) or any other - please create new issues or requests and I will try to answer as fast as possible
The text was updated successfully, but these errors were encountered:
The idea is that once you have written the templates, then all the changes coming in the core C++ implementation can propagate automatically to the language bindings. That's how we manage to keep MAVSDK-Java, MAVSDK-Python, MAVSDK-Swift up-to-date: most of the work is done in MAVSDK-C++.
Also note that historically we started by using gRPC to talk between MAVSDK-* and MAVSDK-C++, but it could use FFIs. I think it would actually be our preferred approach today.
At this time we can go forward and implement generation from templates.
Hopefully I will return from my vacation in middle of January and will start that 😄
Additional info: #6
About
API
stabilization:I think we can start as is and try new in process of templates generation implementation.
@julianoes @JonasVautherin if you will have any questions and suggestions related for current
API
(in develop branch) or any other - please create new issues or requests and I will try to answer as fast as possibleThe text was updated successfully, but these errors were encountered: