ERP5Form/Formulator: Minimal support of Zope4's ZMI
Only the most used forms are updated
-
Maintainer
cc @kazuhiko
I am using Zope4 already for a new ERP5 development, the formulator ZMI was too ugly and I thought it was easy to make it better. It was not :) but I feel it's a bit better. The main improvements over the same on Zope2 is that it's using monospaced fonts and larger fields, this should help with TALES expressions.
I tried two approaches, one with the same tables and another one with more "modern" html (without table for the layout) on normal field TALES. I'm thinking of changing the normal field TALES to use the same tables as others.
The checkboxes are a bit ugly , but I feel it's good enough.
What do you think ?
normal field TALES
proxyfield
proxyfield TALES
-
These changes will not break Zope2 compatibility, right ?
I tried two approaches, one with the same tables and another one with more "modern" html (without table for the layout) on normal field TALES. I'm thinking of changing the normal field TALES to use the same tables as others.
As Zope4's ZMI still uses table layout, we can follow it here as well, I think.
https://github.com/infrae/Products.Formulator/commits/master
The upstream does not have any change in ZMI forms. It would be good to contribute our changes...?
-
Maintainer
ah thanks I already forgot about Zope 2 :) it works on zope2 and it looks like this, I feel it's a bit better than before, because of the monospace fonts
I did not know formulator was on github, I thought it was completely abandoned. There have been a 10 years gap in the commit history
but it seems these days there have been some changes again and there might be python3 support coming ( https://github.com/infrae/Products.Formulator/issues/1 ). I think we have really a lot of patches on formulator (many custom fields, "render_view" API for non editable fields, open office support) it's like a different product so I don't think it's worth trying to use the upstream version. I'll see if I can send a patch, but this is not really a priority, just doing this for ERP5 has already taken much more time that what I was supposed to spend :)