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

primeui to SVELTE #297

Open
crisgol opened this issue Mar 17, 2020 · 70 comments
Open

primeui to SVELTE #297

crisgol opened this issue Mar 17, 2020 · 70 comments

Comments

@crisgol
Copy link

crisgol commented Mar 17, 2020

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

@hugotown
Copy link

x2

@erbaafidotama
Copy link

i hope

@SaeAccess
Copy link

x3

@samdoeswork
Copy link

samdoeswork commented Jun 8, 2021

x4

@VanshCodes
Copy link

Waiting ..

@laith43d
Copy link

x6

@miepian
Copy link

miepian commented Jul 15, 2021

x7

@fabiot21
Copy link

x9

@MrKotov
Copy link

MrKotov commented Oct 29, 2021

x10

@kyjus25
Copy link

kyjus25 commented Nov 17, 2021

x11

@charlie17
Copy link

X12

@crisgol
Copy link
Author

crisgol commented Dec 10, 2021

Please .. prime ui tô svelte kit

@kyjus25
Copy link

kyjus25 commented Dec 10, 2021

I have been very tempted to make a Prime Svelte 3rd party fork myself, but I lack the time it would take to maintain it afterwards.

@euberdeveloper
Copy link

x14

@iozcelik
Copy link

x16

@kyjus25
Copy link

kyjus25 commented Feb 4, 2022

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.

@juanlopez87
Copy link

x17

@lroal
Copy link

lroal commented Jun 8, 2022

x18

@PhouvanhKCSV
Copy link

x19

@aguwf
Copy link

aguwf commented Jul 1, 2022

x20

@Bonenk
Copy link

Bonenk commented Jul 1, 2022

X21

@ZiadJ
Copy link

ZiadJ commented Jul 22, 2022

x22

@shahriar350
Copy link

X23

@olb-openminds
Copy link

x24

@paschelino
Copy link

x25

@alexrequeno
Copy link

x26

@GA-MO
Copy link

GA-MO commented Sep 27, 2022

x27

@octgsoftware
Copy link

x28

@mrtcntn
Copy link

mrtcntn commented Oct 27, 2022

x29

@dbyzero
Copy link

dbyzero commented Mar 17, 2023

x39

@kyjus25
Copy link

kyjus25 commented Mar 17, 2023

PrimeSvelte would win the hackathon 👉👈

@safinea
Copy link

safinea commented Apr 26, 2023

x40 - The world needs and deserves PrimeSvelte... 🙏

@dmnhld
Copy link

dmnhld commented May 30, 2023

x41

@kyjus25
Copy link

kyjus25 commented Jun 7, 2023

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

Screenshot 2023-06-07 at 2 43 40 PM

@NG2705-Murali
Copy link

x42

@codingstark-dev
Copy link

x43

@katerlol
Copy link

katerlol commented Oct 4, 2023

x44

@octgsoftware
Copy link

x45

@Max-F-Helm
Copy link

x46

@feisalramar
Copy link

x47

@ZiadJ
Copy link

ZiadJ commented Nov 7, 2023

https://twitter.com/cagataycivici/status/1666090548380450816
Screenshot 2023-06-07 at 2 43 40 PM

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.

@tbdrz
Copy link

tbdrz commented Nov 16, 2023

x48

@Blindheit
Copy link

x49

@dbyzero
Copy link

dbyzero commented Nov 23, 2023

But a version providing web component exists, we can directly use it in Svelte right ?

@rmzluish
Copy link

x50

@frikExcellent
Copy link

x51

@champ7champ
Copy link

x52

@dajester2013
Copy link

x53

@flasapp
Copy link

flasapp commented Jan 21, 2024

x54

@KaioPedro1
Copy link

x55

@jcarbou
Copy link

jcarbou commented Feb 18, 2024

x56

@christophstocker
Copy link

x57

@LeizarM
Copy link

LeizarM commented Mar 12, 2024

x58

@pkalkman
Copy link

X59

@alpap
Copy link

alpap commented Mar 27, 2024

X60

@camilodsilva
Copy link

X61

@0xluc
Copy link

0xluc commented Apr 5, 2024

x62

@naixatwork
Copy link

x63

@jcarbou
Copy link

jcarbou commented Apr 18, 2024

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

image

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
image

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

  • Ripple
  • Badge
  • Button
  • TextField
  • Tooltip

image

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests