ironmansoftware / powershell-universal

Issue tracker for PowerShell Universal
https://powershelluniversal.com
34 stars 2 forks source link

Docs: HowTo Build a Custom Component based on MUI Components and share them with the community #2166

Open donlent opened 1 year ago

donlent commented 1 year ago

Summary of the new feature / enhancement

As you can see many PSU customers ask for additional components that are not (yet) part of PSU. I'm one of them... πŸ€— And here is an uncomplete list of a couple examples that have been filed here in the issue tracker so far...

My requests: https://github.com/ironmansoftware/issues/issues/2005 https://github.com/ironmansoftware/issues/issues/2006 https://github.com/ironmansoftware/issues/issues/2093

Others requests: https://github.com/ironmansoftware/issues/issues/2164 https://github.com/ironmansoftware/issues/issues/2163 https://github.com/ironmansoftware/issues/issues/2162 https://github.com/ironmansoftware/issues/issues/2157 https://github.com/ironmansoftware/issues/issues/1878

You've already put some docs together here and there: https://docs.powershelluniversal.com/userinterfaces/dashboards/components/custom-components/building-custom-components https://blog.ironmansoftware.com/universal-dashboard-custom-components/

The problem? (at least mine πŸ˜… ): The examples show how to do it based on third party modules but not based on MUI components...

My appeal to you: From my understanding you'd like to let the community contribute to PSU if they want to... https://blog.ironmansoftware.com/powershell-universal-github-templates/ https://docs.powershelluniversal.com/userinterfaces/dashboards/marketplace

Personally I'd love to learn how to contribute to the community myself, by building custom componets which are based on MUI. First because I'm really willing to go further in this great project and second because you probably don't have time and interest on building all possibile MUI components people may ask for... I totally understand that because it's not your main focus probably...

So please, let us help you! πŸ™πŸ˜€

But you have to show us, how we can do it... and I think it's not missing a lot here based on your examples... πŸ˜‰

That said, I really hope you'll listen to this request and help us become a real commited PSU community that can lighten up your workload. πŸ’ͺ 😊

Kind regards, Don

Proposed technical implementation details (optional)

No response

adamdriscoll commented 1 year ago

@donlent - Thanks for this issue and the desire to help extending the platform. Currently, there isn't an easy way to extend MUI components. It would be possible to add new components but would require packaging a separate copy of MUI in order to do so. This could cause performance issues as it would have to download the MUI framework more than once.

That said, I like the idea of the flexibility and I think we may need to plan on how to provide support for this moving forward. Let me do some research\planning with the team to see if we can nail down a good way to efficiently provide this support.

donlent commented 1 year ago

@adamdriscoll Thanks a lot for your quick reply explaining the reasons why this hasn't been already done. Now it's more clear to me that it wasn't just a "missing example" but there are more complex reasons behind.

Sure thing! Take your time to see if this could be feasable sometimes or not. Obviously as already said I'd love to see such a thing coming... In any case I'll wait for your feedback whenever you have some more information on this topic.

In the meantime and as always, thanks a lot for your much appreciated commitment! It's really cool to see how PSU is becoming day by day a more feature rich solution for the customer needs πŸ‘ŒπŸ˜‰

Best regards, Don