You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you build Calendars and other Date/Time-Widgets, properties with a date-time builtin type might be useful.
Here are a few suggestions how a builtin type date-time could look like:
Implementation wise I think that perhaps this needs to be feature conditional and we could wrap icu_calendar’s Date<AnyCalendar>. We’d also wrap that in C++ maybe, or is there something else we should use instead?
Yes it should be a feature because there might not even be a system clock on certain MCUs :) Wrapping icu_calendar Date<AnyCalendar> and exposing it as an FFI should be fine. Although it might be good to use std::time in C++ to save a few CPU cycles?
When you build Calendars and other Date/Time-Widgets, properties with a
date-time
builtin type might be useful.Here are a few suggestions how a builtin type
date-time
could look like:date-time
should behave similar to a JavaScript Date object with convenience functions:hours() -> int
,minutes() -> int
,month_name() -> string
to_string(format: string) -> string
:date-time.to_string("DD/MM/YYYY")
,date-time.to_string("hh:mm:ss")
to_locale_string(locale: string) -> string
:Additionally, there could also be a
DateTime
namespace to hold functions to constructdate-time
instances:DateTime.now()
DateTime.new(year: int, month: int, day: int, hours: int, minutes: int, seconds: int)
Comments/Suggestions welcome!
The text was updated successfully, but these errors were encountered: