is it possible to have a version of primeui for svelte?

<a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.github

primeui to SVELTE about primeui HOT 80 OPEN

crisgol commented on September 17, 2024 84

primeui to SVELTE

from primeui.

Comments (80)

cagataycivici commented on September 17, 2024 13

x38

from primeui.

kyjus25 commented on September 17, 2024 7

https://twitter.com/cagataycivici/status/1666090548380450816

from primeui.

ganjarsetia commented on September 17, 2024 3

https://twitter.com/cagataycivici/status/1617873847071408130

from primeui.

jcarbou commented on September 17, 2024 3

I started the migration of primereact to svelte using project name "jazzsvelte" (jazz is a lieutenant of optimus...). This is a temporary name. I use a private Github repository initialized with a clone of primereact. I removed the React & NextJs dependencies and add svelte svelteKit. The React source code direcrories are renamed with a "_" suffix to hav the references

My constaints

The svelte components must

generate the same DOM than React component
use the same css classes (compatibility with prime themes)
Use typescript (only .ts or .Svelte files)

Whath is already done ?

The documentation framework is migrated from "js / React / NextJs" to "typescipt / Svelte / SvelteKit" (except search tool)
The "Getting started" and "Information" pages are migrated

These components are migrated (including documenation pages but without playground)

Ripple
Badge
Button
TextField
Tooltip

A migration tool for components documentation automatically migrate 95% of the doc (from jsx to svelte files)

###To do###
So many things....

Migrate all components
Build (Rollup)
Testing
General documentation
...

I will clean up the project (the list of contibutors is still that of primreact projet...) and move it to public (I never do that).

from primeui.

kyjus25 commented on September 17, 2024 2

I started a private repo and recreated several components, but it is very very tedious to do on your own.

I noticed that Prime's components really build on top of eachother.

In order to have badges on buttons and avatars you have to first create a badge. You have to have a dropdown component before you can have a SplitButton, AutoComplete, or Dropdown. You have to create a Paginator before the Table component. The list goes on.

Creating the elements is the easy part, that's just a matter of inspecting Prime's examples and using the same classes. If you use the same classes it is compatible with any of their CSS packs. The hard part is finding out and building the tree of base components that all other components need. Not only that, but each component is so flexible. If you add a badge to a button, the classes applied and layout change.

It is definitely possible, but even after reverse-engineering all of it, you'd still be looking at full-time maintenance without Prime's help.

I think we can all agree that there are plenty of UI component libraries out there for Svelte or even tailwind. What we are really needing are form libraries. Validation libraries exist, but none that include form UI components like Prime does.

from primeui.

ZiadJ commented on September 17, 2024 2

https://twitter.com/cagataycivici/status/1666090548380450816

Svelte has caught up a lot of traction lately as opposed to web components as far as I know. I might be missing something but I'm curious about the reasons for dismissing Svelte and going for something less popular instead.

from primeui.