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
We are still using the old actions, dialogs, and forms APIs for the Create and Properties actions. We need to re-implement these two actions using the new Actions and Overlays APIs respectively, as well as adding some new API for registering form controls.
This requires re-implementing our legacy form-generation code, which is currently implemented in Angular. This took the properties of an object and auto-generated a form based on them, which was rendered into the popup dialog that shows when the user initiates the Create or Properties actions.
Additionally, developers can provide optional metadata about how each property should be rendered in a form by referencing a control, and providing some control-specific options when an object type is registered. This metadata, if provided, is used to render the appropriate form controls for each object property
Here are someexamples of types that provide additional form rendering metadata about their properties.
Although our new Types API supports this form control metadata when types are registered, the controls themselves are defined in Angular JS. We will need to re-implement all of the form controls as Vue components.
We will also need some new API to allow developers (including us) to register form controls. This could be something like:
openmct.forms.addControl('colorPicker',{show(element){// A render function},destroy(){// A destroy function}});
It will probably also need events for when values change, etc.
Testing instructions:
create all objects using create menu and verify all fields in create form work as expected.
Update values for each creatable object from tree using 'Edit Properties' and verify all fields in create form work as expected.
Create display layout add text and image objects (verify form works while creating those) and also update values for those items (verify form also works in update case)
The text was updated successfully, but these errors were encountered:
We are still using the old actions, dialogs, and forms APIs for the Create and Properties actions. We need to re-implement these two actions using the new Actions and Overlays APIs respectively, as well as adding some new API for registering form controls.
This requires re-implementing our legacy form-generation code, which is currently implemented in Angular. This took the properties of an object and auto-generated a form based on them, which was rendered into the popup dialog that shows when the user initiates the Create or Properties actions.
Additionally, developers can provide optional metadata about how each property should be rendered in a form by referencing a
control
, and providing some control-specific options when an object type is registered. This metadata, if provided, is used to render the appropriate form controls for each object propertyHere are some examples of types that provide additional form rendering metadata about their properties.
Although our new Types API supports this form control metadata when types are registered, the controls themselves are defined in Angular JS. We will need to re-implement all of the form controls as Vue components.
We will also need some new API to allow developers (including us) to register form controls. This could be something like:
It will probably also need events for when values change, etc.
Testing instructions:
The text was updated successfully, but these errors were encountered: