How to use now slide out drawer in a user plugin

[sarg3nt]

Hey devs! Been trying to figure out how to use the new slide out drawer in one of our plugins. The thing looks super sweet and we'd love to use it. Is it exposed to plugins? If so, how?

[illume]

I think this is the example plugin for that: https://github.com/kubernetes-sigs/headlamp/blob/main/plugins/examples/ui-panels/src/index.tsx

cc @sniok

[sniok]

This is a relatively new Activity feature, API is not yet exposed to plugins. Could you share how you want to use it? This would help us make better APIs for plugins.

[sarg3nt]

Howdy. TBH, was just trying to make our plugins look native. Currently we are using the dialog to show grids.
Here's some examples.
This is for the user manager we wrote.

So, if this is not planned then no worries.

Big question. Have you thought about making all the components of Headlamp be plugins? Meaning, making the plugin architecture the way everything is done, internal and external. No idea what that would do to perf and your dev experience. Would ensure that plugin devs have the same experience as native apps though. And we'd have lots of examples! :)

[sniok]

Howdy. TBH, was just trying to make our plugins look native. Currently we are using the dialog to show grids. Here's some examples. This is for the user manager we wrote.

Thanks for sharing! That looks like a perfect use case for the "native" drawer.

So, if this is not planned then no worries.

Hopefully we can get this in the next release. There's a draft PR here

Big question. Have you thought about making all the components of Headlamp be plugins? Meaning, making the plugin architecture the way everything is done, internal and external. No idea what that would do to perf and your dev experience. Would ensure that plugin devs have the same experience as native apps though. And we'd have lots of examples! :)

In the perfect world that's exactly how headlamp would've worked, small core with all features implemented as plugins. And some parts are developed like that, for example Plugin Catalog in the desktop app is just a plugin. But it can be hard and we're trying to be mindful of exposing as much functionality as possible to plugins, while also providing stable API without breaking changes.