Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document Steps to follow to onboard Custom Editor into Plugin Registry #22854

Closed
maheshrajrp opened this issue Feb 28, 2024 · 5 comments
Closed
Assignees
Labels
area/editors area/plugin-registry kind/question Questions that haven't been identified as being feature requests or bugs. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@maheshrajrp
Copy link

maheshrajrp commented Feb 28, 2024

Summary

Hi All,

We have a custom Eclipse Theia Editor Implementation similar to old Che-Theia, however there isn't any proper documentation on how to onboard a custom editor into plugin registry. I can see we have documentation to add plugins, but not editor. A proper documentation would really help.

Thanks

Relevant information

No response

@maheshrajrp maheshrajrp added the kind/question Questions that haven't been identified as being feature requests or bugs. label Feb 28, 2024
@ibuziuk
Copy link
Member

ibuziuk commented Feb 28, 2024

@svor maybe you can take a look

@svor
Copy link
Contributor

svor commented Mar 7, 2024

@maheshrajrp hello, I've just merged a PR with changes that provides some explanation of haw to contribute new editor into the plugin registry repository: https://github.com/eclipse-che/che-plugin-registry/blob/main/CONTRIBUTE.md#adding-a-che-editor-to-che

Hope this helps a bit. If you want me to look into anything further just let me know!

@maheshrajrp
Copy link
Author

hi @svor
thanks for documenting, I have a few questions, probably basic ones I guess, not sure if we have a documentation for these. like for example, I can see for Jupyter there's just one component mentioned in schema whereas, in the second one we have the-code-injector, che-code-runtime-description, in short, what is a component, why do we need it, and what is the use case when we might need multiple components. Also, the same for commands and events, why and when do we need it? in short, having an explanation on how to create a plugin and thoughts that needs to be put into when creating one should really help alot to newbie users like me.

Also, we have @l0rd repo for trying out theia, where he had mentioned "Only works with libc v3 images (doesn't work with current universal developer image that is based on UBI8)", I'm figuring out the parts of the repo, and I have questions related to this. Maybe could we provide a disclaimer similar to that, helping us understand when and why there can be such issue ?

Repo URL:
https://github.com/l0rd/theia-editor/tree/main

Maybe I am asking for too much, I dont know. I'll leave you to be the judge of it. But these are the main questions I have right now

@svor
Copy link
Contributor

svor commented Mar 8, 2024

I'd say it depends on the editor

in the second one we have the-code-injector, che-code-runtime-description, in short, what is a component, why do we need it, and what is the use case when we might need multiple components. Also, the same for commands and events, why and when do we need it?

@RomanNikitenko @azatsarynnyy can you help with this

@dkwon17 dkwon17 moved this from Unplanned Tasks to 📅 Planned in Eclipse Che Team A Backlog Mar 13, 2024
@dkwon17 dkwon17 moved this from 📅 Planned to 📋 Backlog in Eclipse Che Team A Backlog Mar 13, 2024
@che-bot
Copy link
Contributor

che-bot commented Nov 21, 2024

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 21, 2024
@che-bot che-bot closed this as completed Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/editors area/plugin-registry kind/question Questions that haven't been identified as being feature requests or bugs. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants