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
plone.autoform.directives and more generic javascript #228
Conversation
else: | ||
# Plone 4 | ||
from plone.app.widgets.dx import DatetimeWidget | ||
from plone.app.widgets.dx import DatetimeFieldWidget |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if you skip Plone 4 support this can be removed as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
True - But removing Plone 4 support is more than that. I'd like to make a separate PR for that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, one after another.
I'm wondering if there is a programmatic way to be used in an upgrade step to "re-cook" javascript... |
|
@vincentfretin although it's from the plone-legacy bundle, but in Plone 5 it's different, no? |
Ah, I don't know about Plone 5. |
…ead of overriding the default Fieldwidget adapters.
This makes it easier to use same selectors also for derived behaviors.
…works also for derived classes.
…0.1.dev0, which is only available for Plone >= 5.1
what’s the state here? do we need some "cooking" or is this sufficient? |
This makes it easier to use same selectors also for derived behaviors.
plone.autoform.directives
for manipulating field widgets instead of overriding the default Fieldwidget adapters.