Ticket #901 (closed Enhancement: fixed)

Opened 9 years ago

Last modified 8 years ago

Add Date, Time, DateTime types to standard distro

Reported by: jri Owned by: jri
Priority: Major Milestone: Release 4.8
Component: DeepaMehta Standard Distribution Version: 4.7
Keywords: Cc: dgf, Malte, JuergeN
Complexity: 5 Area:


The DM Standard Distribution should come with generic Date, Time, and DateTime types for other types to build upon.

This could be realized in a separate module dm4-datetime.

The current dm4-time module should be renamed to dm4-timestamps then for better differentiation.

Change History

comment:1 Changed 9 years ago by jri

  • Status changed from new to accepted

comment:2 Changed 9 years ago by Jörg Richter <jri@…>

In ea77609fbcb57e5ff3f0124f36ba05733e6c1a5b/deepamehta:

Add dm4-datetime module (#901).

New types:


See #901.

comment:3 Changed 9 years ago by Jörg Richter <jri@…>

In e14a99ffe2496afdbe35e459e24ee01813d4a218/deepamehta:

Change date order: month, day, year (#901).

See #901.

comment:4 Changed 9 years ago by Jörg Richter <jri@…>

In f85ca91b74f9c29f9c6ea335b836a76fb47c269c/deepamehta:

Datetime model: add label configs (#901).

See #901.

comment:5 Changed 9 years ago by Jörg Richter <jri@…>

In 03825bbceb9f322cb4579d56b2235d5881c1af71/deepamehta:

Add dm4-events and dm4-datetime to distro.

See #901.
See #902.

comment:6 Changed 9 years ago by Jörg Richter <jri@…>

In ca5e613a8ca280d6e85f1e2ce8dfd37ac01629e7/deepamehta:

Date/Time? model: define childs via assoc def...

because we want pulldown menus.

See #901.

comment:7 Changed 9 years ago by Jörg Richter <jri@…>

In a0eb6751ec4acb241d7b5cbcab44bc4a48ec4578/deepamehta:

Datetime: model fields as number (#901).

Month, Day, Year, Hour, Minute are Number fields (formerly Text).

See #901.

comment:8 Changed 9 years ago by Jörg Richter <jri@…>

In 78a9ca13681da8011e0d981d02ec00a56a512e77/deepamehta:

Datetime: combobox shows month names (#901).

"Jan", "Feb", "Mar", ...

Note: at the moment this applies only to comboboxes, that is when the detail panel is in form mode.
Does not yet apply for detail panel info mode, or canvas rendering.

See #901.

comment:9 Changed 9 years ago by Jörg Richter <jri@…>

In 5e08c3abcac89f51b8b5717a43c014f4d024d563/deepamehta:

Date/Time? detail panel layout (#901).

In the detail panel the Month/Day/Year? fields as well as the Hour/Minute? fields are respectively layouted in a row (instead of on top of each other). Applies to both, info mode and form mode.

This gives a much more pleasant user experience, in particular e.g. for Event topics (part of the Events module) which employ a lot of date/time information.

The layout is defined solely via CSS (see #929).

Example for the Month/Day/Year? fields:

/* === Date === */

.dm4\.datetime\.year {
    display: inline-block;

.dm4\.datetime\.year {
    margin-top: 0 !important;
    margin-left: 1em;

/* Form */

.dm4\.datetime\.month input,
.dm4\.datetime\.day   input {
    width: 2em !important;

.dm4\.datetime\.year input {
    width: 3em !important;

See #901.

comment:10 Changed 9 years ago by Jörg Richter <jri@…>

In ad746cd4b301f8ce5c3fdf7ca504610780b6eab2/deepamehta:

Date/Time?: tweak CSS (#901).

The layout is proper also if a Year field is used outside the context of a Date field.

E.g. the CROWD model (#914) uses Year as "Year of publication".

See #901

comment:11 Changed 8 years ago by Jörg Richter <jri@…>

In 40536033215ca82c8a86ba2c41726d5b3dd44589/deepamehta:

DateTime? CSS fix: align empty fields (#901).

The Month/Day/Year? field are properly aligned also if a field is left empty.

See #901

comment:12 Changed 8 years ago by jri

  • Status changed from accepted to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.