Sunsetting justpy

[WolfgangFahl]

justpy has been a great project and our goal to reach 1000 stars soon was reached now.
Given that nicegui is somewhat of a fork of justpy and is much more successful with >4000 stars there is not much use to try to build on justpy and move it further.

Therefore I intend to close most issues now that ask for enhancements pointing to nicegui as an alternative that might implement these features and concentrate on helping people migrate to nicegui or keep their existing justpy code running for a while.

justpy 0.13 seems to be sufficiently stable to not cause too many worries.

What do you think?

[freemant2000]

What does @elimintz think? Is he also migrating to NiceGUI?

[msrkala]

Yes, one should think pragmatically.

[WolfgangFahl]

Just released version 14.0 after checking that the github and jenkins CI still works. Migration guide hints are welcome - just add articles to the discussion if you successfully migrated code from justpy to nicegui.

[freemant2000]

If someone needs help fixing existing bugs in justpy, he/she may contact me. I have been teaching a high schooler Python programming and he is largely capable of fixing most bugs under my guidance.

[freemant2000]

My student has upgraded the html_component in justpy to Vue 3. You can see the test html file at https://github.com/GavinLeongMO/justpy/blob/master/tests/html_component_test_page.html .

[sandeep-gh]

Hi @freemant2000, I thought justpy was already at Vue3. In any case, were there any API level changes when moving to Vue3 or did we have to simply update the corresponding libraries.

I published a fork/extension/enhancement to justpy which is using svelte as frontend library. However, I am planning to bring back Vue engine back. We should coordinate, if there are api level changes. There are inefficiencies in the current Justpy that I have addressed in my repo. It would be good to upgrade to Vue3 there as well.

[freemant2000]

Sure. We intend to keep the internal justpy protocol unchanged while upgrading to Vue v3, so the components and existing justpy code should continue to work.

[WolfgangFahl]

I made justpy's demo available as components in the nicegui solutions bazaar at http://ngdemo.bitplan.com/components/justpy-org_justpy

So if you need any of these "components" converted to justpy please file an issue in https://github.com/WolfgangFahl/nicegui_widgets/issues/new/choose

[bitnom]

Are there any benefits to justpy over nicegui? I read the nicegui readme but it doesn't go into much detail about the differences.

[falkoschindler]

In short, NiceGUI

• uses current versions of Vue, Quasar and Tailwind,
• is based on FastAPI and supports all of its features,
• has a larger and more active community, and
• is actively developed and maintained.

The number of UI elements might also be larger, but it's hard to say for sure. The intention was also to create more high-level elements than HTML's basic div, a, ... Have a look into the documentation where you'll find lots of interactive demos showcasing features.

[freemant2000]

Certainly, for example, I am teaching my students web technologies (html, css, js) and Python, so Justpy allows them to work all these. With NiceGUI, HTML is kind of hidden away, so they would be learning just yet another UI framework.

[WolfgangFahl]

at http://ngdemo.bitplan.com/solutions you can see how the community is evolving. The components in justpy have not been really components in the past but just examples from the tutorial. A component base approach is much more feasible with nicegui.