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
The whole scripts dev environment should be moved from GCS resources to uavos/apx-fw repo as module and generate apxfw with resources, latter copied and extracted by GCS as other firmware metadata.
The goal is to each node to have separate script dev environment embedded in apxfw file as other metadata. When GCS user edits a script - GCS copies dev env from corresponding apxfw. Thus, allowing each node to have its own API with fallbacks to older versions and other nodes (f.ex. nav).
The text was updated successfully, but these errors were encountered:
The whole scripts dev environment should be moved from GCS resources to uavos/apx-fw repo as
module
and generateapxfw
with resources, latter copied and extracted by GCS as other firmware metadata.The goal is to each
node
to have separate scriptdev environment
embedded inapxfw
file as other metadata. When GCS user edits a script - GCS copies dev env from corresponding apxfw. Thus, allowing each node to have its own API with fallbacks to older versions and other nodes (f.ex. nav).The text was updated successfully, but these errors were encountered: