trackball-python VS django-components

They’re incredibly easy to get going with a raspberry pi, Pimoroni provides a python library that takes basically no time to get going. There’s a script in their examples folder, evdev-mouse.py that translates trackball movements and presses to mouse movements and left clicks.

The same can be said of a React frontend that talks to a JSON API. There is some structure, organization, and convention to the API endpoints, one-way data flow, and so on. Otherwise it’s chaos.

On our most recent project we do the same with Django and HTMX. Organized endpoints by component. Composable, reusable server-side components with django-components [1]. And we’ve been orders of magnitude more productive, shipping more in 1-2 months than we did the previous 12-18 months working with React.

[1] https://github.com/EmilStenstrom/django-components

Yes. Or django-components

I use django-components to break templates into very small pieces, and never had any of the issues you describe.

I've been reading about django-components and #slippers components, but don't know about combining Pre or PostCSS, Tailwind or XXX for styling and how to keep the whole thing as simple to maintain as possible. Not willing to go the Bootstrap route, but need to structure a compromise.

I had used this project for creating components https://github.com/EmilStenstrom/django-components/

Also, for simpler cases I include partial templates.

In React it is as simple Django with https://github.com/EmilStenstrom/django-components installed {% component_block "button" intent="primary" %} Now everyone using Django would have to create their own components, they also have to do this in React which is a waste.

I felt the ux around registering new components to be much stronger with https://github.com/EmilStenstrom/django-components although I do like how slippers uses attributes

That said, you might find this package interesting: https://github.com/EmilStenstrom/django-components/