Flexx lacks of a lot of features about flexx

[NolanG241]

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

[almarklein]

Thanks for the suggestions 👍

[jrversteegh]

@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]

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