Contrib.social

Join forces and reduce duplicate effort?

Open on Drupal.org →
Created on 26 June 2019, about 5 years ago
Updated 8 May 2023, about 1 year ago

Hi smart_date maintainers,

I just happened to discover this module. Sounds like it *heavily* overlaps with the work I did in datetime_extras → with the daterange_duration widget for core daterange fields. See #2845081: Provide a datetime_range widget to define end time via a duration offset →

It also overlaps with the work on a "compact" daterange formatter:
https://www.drupal.org/project/daterange_compact →
#2834016: Add 'Compact' datetime range formatter →

And it's yet another thing trying to solve "all-day":
https://www.drupal.org/project/date_all_day →
#3021557: Make date_all_day a set of widgets and formatters for core's datetime_range field type →
#2734255: Support a per-instance "all-day" option for datetime and datetime range fields →
...

Wondering what the chances are of working together to reduce duplication instead of continuing to fragment the (already heavily fragmented) ecosystem for dates and times in D8.

There are now a series of issues sprinkled through the d.o issue tracker for trying to get smart_date to work with calendar, fullcalendar_views, etc. All of that already "works" if you use core daterange fields and the duration widget I wrote.

I appreciate how hard it is to coordinate with other people, all the moving parts, etc. I completely understand the desire to "start over and get it all working from scratch how I want it to work". I obviously can't stop you from continuing down the path of having your own project. But I wish you had found all this prior work before you started writing "smart_date", and put the effort into solving the open issues, not starting an entirely independent (incompatible) effort.

Thoughts on if/how to proceed and coordinate? Would love to join forces and help make datetime_extras (and eventually core itself) support all this goodness, instead of continuing the path of fragmentation and incompatibility.

Thanks,
-Derek

🌱 Plan
Status

Active

Version

1.0

Component

Miscellaneous

Created by

🇺🇸United States dww

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Comment about 1 year ago →
    🇨🇦Canada colan Toronto 🇨🇦

    Could we get a status update on this now that v4 is out? I'm wondering what's changed with respect to this issue.

  • Comment about 1 year ago →
    🇨🇦Canada mandclu

    Thanks for surfacing this issue again.

    I am definitely still open to collaboration, and in fact my work on the Date Augmenter API → was inspired by the discussion in this thread, in the spirit of developing date formatting capabilities that are agnostic of the formatter being used.

    Almost three years later, I think it's worth re-examining if Datetime Extras is the best place to collaborate. There hasn't been a release for that module since this thread went quiet, or even an issue resolved.

    Would it make more sense to open one or more core issues about upgraded datetime elements, e.g. widgets and formatters? There might still be time to get these into core as experimental in D10, with an eye to getting them stable for D11.

  • Comment about 1 year ago →
    🇨🇦Canada colan Toronto 🇨🇦

    @mpdonadio → was the person to ask back then, but not sure he's still working on this stuff. He's on this thread though so maybe he'll respond. (If not, there's always his contact form.)

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024