[PLAN] Agenda for disqussion.

[iberdinsky-skilld]

Current application, Open API, Swagger.

https://refine.dev/

https://axios-http.com/

https://chakra-ui.com/

https://www.openapis.org/

https://swagger.io/tools/swagger-ui/

https://rjsf-team.github.io/react-jsonschema-form/docs/

Extend json form with:

• Chakra UI Form (default)

  https://rjsf-team.github.io/react-jsonschema-form/docs/advanced-customization/custom-themes

• Form without styles. Naked RJSF

• Form with custom UI Schema

  https://silly-cat-5303aa.netlify.app/actions/enumeration/action

  https://rjsf-team.github.io/react-jsonschema-form/docs/api-reference/uiSchema/

• Form with custom UI Widget

  https://rjsf-team.github.io/react-jsonschema-form/docs/advanced-customization/custom-widgets-fields

• Custom Webcomponent loaded

Alternatives. Webcomponents (Lit client)

https://github.com/json-schema-form-element/jsfe

https://jsfe.js.org/Sink/AllFeatures

https://shoelace.style/

Websockets (Async API) Refine Live provider.

• Dynamic lists.
• Dynamic running actions
• Stdout example.

https://www.asyncapi.com/en

https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API

https://refine.dev/docs/realtime/live-provider/

TODO.

• [x] Define app core technology.

• [x] Define rest/async workflow.

[davidferlay]

Ideas of feartures / roadmap :

• list actions list/page/run/stdout etc > Kind of done
• list launchr commands brought by native plugins (as opposed to action file)
• action should bring it's "UI" file ?
• action to start web-ui (listed in a special way in UI) > plasmactl action to start UI
• platform configuration files (require some special domain behavior)
  • for init stuff > see kb
  • for regularly updated configs > see integration skills
• integration/cognition workflow low code
• package management (compose.yaml)

[iberdinsky-skilld]

Refactor current code.

We have added some changes to the existing backend code. They need to be tested and refactoring may be necessary.

PRs:

• https://github.com/launchrctl/web/pull/15
• https://github.com/launchrctl/web/pull/22
• https://github.com/launchrctl/web/pull/31

Also, the original code contains a lot of "to do" tags, they are also worth noting.

Launchr/plasma features to disquss for next iteration for web ui.

Action to start web-ui (listed in a special way in UI) > plasmactl action to start UI

plasmactl build -p github.com/launchrctl/launchr@latest,github.com/launchrctl/web@latest -n plasmactl -o plasmactl

This command not working yet. We need to load client assets into build.

List launchr commands brought by native plugins (as opposed to action file)

@davidferlay

integration/cognition workflow low code

@davidferlay

Async Api

I added proof of concept here https://github.com/launchrctl/web/pull/37

Everything works but definitely needs to be done by a more advanced backender. We also may need to use go channels to know when action started and when finished.

It can use same as OpenApi code generator https://github.com/lerenn/asyncapi-codegen

We can continue this work in parallel with development in OpenApi because working with an asynchronous backend is very simple in refine.dev so client app can be switched pretty easy.

Flows

I added a few ideas of what the home page could look like

• We can display them in groups using the action ID.
• We can add interactive elements inside cards
• We can add effects as we run, synchronously or asynchronously https://attio.com/product/automations nice effect for inspiration. more ideas: https://reactflow.dev/showcase
• We can add a configuration file ui-compose.yaml with actions group hierarchy.

Brand customisation.

If we suppose this app be used by various people/companies we should be able to provide different levels of ui customisation. Can be optional file web-ui.yaml with option to setup

• Logo
• Branding colors
• Fonts
• etc.

[iberdinsky-skilld]

Flow disqussion

• Platforms switcher
• Structure of tree.
• Edges start/finish.
• Colors of groups.
• Rignt off-canvas bar. Data source. Tags. UI Form

[iberdinsky-skilld]

Sidebar behaviour.

• Directory structure. 3 level types now: Directory/Application/Action
• Iteraction. On click directory/application/Action. When second for sidebar shoud be opened? What display in every type?
• Actions Tab. Iterations/search
• Should second sidebar be modal?

ReactFlow behaviour.

• Kostia Demo.
• Autolayout.
• Iteractions.

Flow tab.

• Config.
• Order sequence / Sequence indicator

Terminal styles approach.

• Demo in https://github.com/launchrctl/web/pull/45/files

Current state of backend.

TBD

[iberdinsky-skilld]

https://github.com/launchrctl/launchr/issues/26