search

KaotoIO / kaoto-ui

Frontend for the Kaoto project to provide an easy-to-use integration framework based on Apache Camel.
https://www.kaoto.io
Apache License 2.0
88 stars 44 forks source link

Kaoto npm Package #122

Closed kahboom closed 2 years ago

kahboom commented 2 years ago

As a user, I'd like to extend or embed Kaoto using a package published on the npm registry, and have access to the relevant typings (IKaoto).

Delawen commented 2 years ago

I would have this as a very very low priority. Embed Zimara in places like OpenShift Data Console makes sense. Embed it anywhere... that was not the original idea. Was it?

kahboom commented 2 years ago

But when it comes time to use it somewhere like the OpenShift Data Console or somewhere like the OpenShift Developer Console, how will they embed it if it has a sidebar and navbar, and they already have their own? For example, how we embed Atlasmap or Apicurio in Syndesis.

Delawen commented 2 years ago

The ability to embed Zimara means that there will not be an option to use generic extensions, only step extensions.

why?

kahboom commented 2 years ago

Because at the moment (at least, per the designs) the way you would access the generic extensions is through the sidebar. It would also be much easier to embed something that you wouldn't have to worry about the external application's navigation/routing, otherwise we open up a much more complicated setup. It's not impossible, of course, but maybe starting with a simpler implementation would be better.

kahboom commented 2 years ago

wait, why assign to me, I'd rather @mmelko did this one 😆

Delawen commented 2 years ago

Is this not the envelop thing?

kahboom commented 2 years ago

No this is for disabling the sidebar so that you can consume Kaoto in another application, for example, within an iFrame or as a federated module. With the sidebar and navbar that would not be very useful.

EDIT: More importantly, this would allow users to create step extension with proper typings and knowing what the Step Extension API offers/accepts.

kahboom commented 2 years ago

Closing as the scope for this issue was never clearly defined. It ended up getting narrowed down to just needing typings for the Kaoto Step Extension API, which was implemented recently (though needs to be documented).

kahboom commented 2 years ago

Actually, reopening as we will be needing this for https://github.com/KaotoIO/vscode-kaoto/issues/27

apupier commented 2 years ago

The idea is to have specific component for Kaoto editor so that it can be reused. it will respect the "mulitplying architecture" coming from kie-tools. it will allow to reuse their framework.

A proof of concept has been provided here https://github.com/thiagoelg/kie-tools/tree/vscode-kaoto/packages/kaoto-editor

The current need is to migrate to KaotoIO organization for ease and maintenance and avoid having to match/block Kogito release planning.

Files has been moved to this specific repository: https://github.com/KaotoIO/kaoto-component-library

Identified mandatory tasks:

Other identified tasks:

reported https://github.com/KaotoIO/kaoto-component-library/issues/8 to group these. This top-level issue was for the kaoto-ui to be available on npm.

apupier commented 2 years ago

Package has been published on npmjs registry, see https://www.npmjs.com/package/@kaoto/kaoto-ui