Join forces with vscode-elements?

[justinfagnani]

I found both this project and https://github.com/vscode-elements/elements while looking for an alternative to Webview UI Toolkit. First of all, thanks for taking this on! As an extension developer who's using Lit, I really appreciate it.

It seems like vscode-community-ui-toolkit and vscode-elements share a similar approach. Both are based on Lit at least. vscode-elements seems to have more elements implemented as of now.

I wonder if more progress would be made if the two projects joined forces? Webview UI Toolkit was lacking a lot of higher-level components anyway, this could be a way to have more time to work on a lot of components that people were looking for like trees, tabs, and tables.

[estruyf]

@justinfagnani It is a good idea, and there are many components others would benefit from. However, we should not forget our original idea for this library. It was to create an easy migration path for the extensions using the VS Code UI toolkit without making too many code changes. Ideally, it would be a dependency update and reference update.

I already saw some components from the "vscode-elements" library, which use different names or properties. So, implementing the new library would require a bit more work.

That said, libraries can also coexist and improve each other. This is what we can see in so many toolkits/frameworks/... already. Another advantage is that we start from scratch, so we can now lay a new foundation that could solve other issues regarding styling, components, reusability, etc.

Feel free to join our Discord to keep the discussion going: https://discord.gg/wtv7wS2A79

@d13 @idoprz @hawkticehurst @kaje94 and anyone else, what is your take on it?

[idoprz]

Hi,
I'm in favor of consolidating the projects. I prefer to have single community driven project, even if it means that adoption of the library may be more complicated. In the long term joining forces will be more beneficial to all.