> On 9/17/13 4:16 PM, Johannes Raggam wrote:
> So release plone.app.event 1.0 targeting Plone 4.3, and then work on the
> switch to plone.app.widgets for plone.app.event 2.x, targeting Plone 5?
sounds like a good plan!
--
programmatic web development
di(fh) johannes raggam / thet
python plone
Quoting David Glick (Plone) (2013-09-17 19:01:59)
> Currently we have way too many date and datetime widgets in core:
> - Archetypes
> - z3c.form
> - collective.z3cform.datetimewidget (added as an override of the default
> z3c.form one by plone.app.z3cform; uses jquerytools date picker)
> - plone.
On 9/17/13 4:16 PM, Johannes Raggam wrote:
plone.app.widgets.
i'll check this out at the buschenschanksprint this week. also
plone.formwidget.recurrence should become a plone.app.widgets pattern.
Great!
then we have to deprecate plone.formwidget.* for plone.app.event.
i'm unsure about how to
plone.app.widgets.
i'll check this out at the buschenschanksprint this week. also
plone.formwidget.recurrence should become a plone.app.widgets pattern.
then we have to deprecate plone.formwidget.* for plone.app.event.
i'm unsure about how to do with the 1.0 release of plone.app.event.
switching
Currently we have way too many date and datetime widgets in core:
- Archetypes
- z3c.form
- collective.z3cform.datetimewidget (added as an override of the default
z3c.form one by plone.app.z3cform; uses jquerytools date picker)
- plone.formwidget.datetime (added by plone.app.event; uses jqueryto
