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

Flexx lacks of a lot of features #735

Open
NolanG241 opened this issue Nov 18, 2022 · 4 comments
Open

Flexx lacks of a lot of features #735

NolanG241 opened this issue Nov 18, 2022 · 4 comments

Comments

@NolanG241
Copy link

hi,

after doing some tests and creating classes of my own to try and build a saas/spa with flexx,
i come to the conclusion that flexx lacks of a lot of features to archieve that for me.

here are some points:

  • simple data-binding between model-field, field-field
  • more form widgets (integer, number, decimal) with optional validations
  • form handling (error display/handling)
  • widgets for eg a toolbar, taskbar, desktop, window
  • speaking of window: moveable windows with close/min/max/... functionality

in the past i worked with Qooxdoo do build rich web interfaces,
but the development structure (having a javascript frontend (gui) and some server routines in a different language)
drove me to flexx.

having one framework for both server and frontend is really nice and i love python :)

greetings
nolan

@almarklein
Copy link
Member

Thanks for the suggestions 👍

@jrversteegh
Copy link
Contributor

@NolanG241 Good suggestions.
With respect to "data binding": I've worked a lot with Delphi, which has very extensive data binding options and I found these options tempt you into bad practice. In particular, they'll lure you into mixing UI functionality with business logic thus preventing you from for example implementing a more robust pattern like MVC.
The same is true for validations: should preferably be done server side imho, because validations typically are part of your model's requirements which should not be implemented by the UI. Historically this was done a lot, because communication between web client and server was either expensive/slow or hard to implement, but this is often no longer true these days. flexx' event handling system is extremely good at doing server side validation i.e. validation outside the context of the widget itself.

@NolanG241
Copy link
Author

okay,

i see the point. but then we need a validation procedure/handling on the python side to trigger events on which the form listens to display some errors.

while fiddling a litte bit more, i stumbled on the multi inheritance problem / missing feature.
it would be nice to somehow make mixins work, so it would be easier to add new functionality to existing flexx classes,
eg the possibility to hide or show widgets.

greetings
nolan

@NolanG241
Copy link
Author

hi,

i setup a repo of my own for testing different python gui web frameworks.

https://github.com/NolanG241/python_gui

my_flexx.app contains a dragable window test.

in common.flexx there are some form-model binding tests.

greetings nolan

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

No branches or pull requests

3 participants