Skip to content

Design form of Definitions #589

@andrewfstratton

Description

@andrewfstratton

The widget side is (mostly) done. Still to do -

  • Allow embedding (sub) definitions
    • to allow reuse, e.g. Press/release/either
    • ...some of these could be put in the library - though they would likely include html...
  • worked only for the blocks, did not work with the definition - i.e. definition name not set in sub structs

For the instance/action these are still options/in progress -

  • Better way to define Op including closure
    • could separate the runtime structure so could use reflection to go through all the fields(!)
    • Change Op to act on the run time structure
    • Use generator to construct the runtime parameters
    • Define interface that requires the Op to be defined
      • or possibly the lower levels?!

Also need to allow for -

  • Op might not be defined while creating a Quando component
  • A fall back op should be available that gives standard feedback
    • inc. log messages and editor visible

Need to consider using -

  • go generate
    • with a more code oriented approach
    • i.e. more standard code is generated that is called when needed - in a separate file in the package
    • how to define the data?
  • how to have an inventor editor approach for drag n drop the widgets (and maybe some boiler plate executable code)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions