-
Notifications
You must be signed in to change notification settings - Fork 9
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Provide a datetimepicker instead of just a datepicker #83
Comments
@mueslo Could you elaborate on some examples to show how relevant this is? |
It is required for some tasks that need to be executed on a specific time of a day. For example moving a user. |
The old The project is undergoing a few structural changes (dropping the jQuery + even bootstrap dependency), but it's not clear when v6 will arrive. Judging by the blog article the developer seems to have the right priorities and is actually interested in building something stable + maintainable. Pragmatically speaking, we don't even care about a nice UI, having the functionality is the main goal. |
Judging by Eonasdan/tempus-dominus#2326 and the state of the |
There's been an update in a blog post yesterday. No time line, but sounds like it could be released in the next few months or perhaps even weeks. |
v6 is in beta 5 and judging by the examples it seems pretty usable. We can even utilize the format/parse hooks to enforce an ISO-8601 text representation instead of the default |
We need this for some reason to import the tempus-dominus module. `classic` is considered legacy, anyway: > This used to be TypeScript’s default resolution strategy. Nowadays, > this strategy is mainly present for backward compatibility. src: https://www.typescriptlang.org/docs/handbook/module-resolution.html#classic Refs #83
The current POC html skeleton is: <form>
<div
class='input-group'
data-td-target-input='nearest'
data-td-target-toggle='nearest'
data-role="datetimepicker"
>
<input
class='form-control'
aria-label="some date time"
id="datetimepicker1"
data-td-target='#datetimepicker1'
/>
<button
class="btn btn-outline-secondary"
type="button"
data-td-toggle="datetimepicker"
>
<span class='fa-solid fa-calendar'></span>
</button>
</div>
</form> |
This was double quoting things, ie kept things a little _too_ safe. Refs agdsn/pycroft#83.
Unfortunately we have to make this hard-coded distinction, because we can only pass `render_kw` from the outside, and it's not quite clear on which HTML element they need to end up. Refs agdsn/pycroft#83
We need this for some reason to import the tempus-dominus module. `classic` is considered legacy, anyway: > This used to be TypeScript’s default resolution strategy. Nowadays, > this strategy is mainly present for backward compatibility. src: https://www.typescriptlang.org/docs/handbook/module-resolution.html#classic Refs #83
FWIW, the tempus dominus picker was really, really underwhelming in terms of basic UX. It did not seem to behave properly on tab-out, didn't always close when pressing on some other part of the area, etc. Googling around, flatpickr seems like a good alternative. |
In some cases it is necessary to specify a datetime, not just a date.
The text was updated successfully, but these errors were encountered: