24-hour times input (23:00,02:00). This gives us the num of hours of difference, taking into account that if something goes until 5:01, it is one more hour long than if it goes until 5:00 DEPRECATED: this is really something one should do leveraging existing tcl capabilities. Plain clock idioms can do the same in a more generic and reliable way.

Switches:

-start_time (required)

-end_time (required)

See Also:

• clock

Partial Call Graph (max 5 caller/called nodes):

Testcases:

No testcase defined.

Check if a time is midnight. This might be replaced by clock idioms in the future, but is currently the way we decide e.g. if an event is an all-day event.

Parameters:

time (required)

See Also:

• dt_no_time_p

Partial Call Graph (max 5 caller/called nodes):

Testcases:

dt_midnight_p

This decides whether an item is without a time, which is also our definition of an all-day event.

Switches:

-start_time (required)

-end_time (required)

Partial Call Graph (max 5 caller/called nodes):

Testcases:

dt_midnight_p

Returns a calendar for a specific day, with details supplied by hour. Defaults to today. DEPRECATED: this proc uses hardcoded markup and is therefore difficult to style. It is also not localized. Many of the date operations happening here have now good tcl support through the clock api, which would make this code probably faster. Future reimplementations should leverage the templating system more.

Switches:

-calendar_details (optional)

-date (optional)

-hour_template (optional, defaults to "$display_hour")

-start_hour (optional, defaults to "0")

-end_hour (optional, defaults to "23")

-show_nav (optional, defaults to "1")

-prev_nav_template (optional, defaults to "<a href="?date=[ns_urlencode $yesterday]"><img border="0" src="[dt_left_arrow]" alt="[_ acs-datetime.back_one_day]"></a>")

-next_nav_template (optional, defaults to "<a href="?date=[ns_urlencode $tomorrow]"><img border="0" src="[dt_right_arrow]" alt="[_ acs-datetime.forward_one_day]"></a>")

-master_bgcolor (optional, defaults to "black")

-header_bgcolor (optional, defaults to "black")

-header_text_color (optional, defaults to "white")

-header_text_size (optional, defaults to "+2")

-calendar_width (optional, defaults to "100%")

-day_bgcolor (optional, defaults to "#DDDDDD")

-today_bgcolor (optional, defaults to "yellow")

-day_text_color (optional, defaults to "white")

-empty_bgcolor (optional, defaults to "white")

-overlap_p (optional, defaults to "0")

See Also:

• /doc/acs-templating/
• /doc/acs-lang/
• clock

Partial Call Graph (max 5 caller/called nodes):

Testcases:

No testcase defined.

create a listing widget for lists (ben) I would like to ask forgiveness from the coding gods for this proc. Right now this is a big hack to make the schedule look a lot like the SloanSpace v1.0 display. Once we have thought this through a bit more, I will generalize this proc. I promise. Please forgive me. DEPRECATED: time is up Ben. This proc uses hardcoded markup and is therefore difficult to style. It is also not fully localized. Future reimplementations should leverage the templating system more.

Switches:

-calendar_details (required)

-item_template (optional, defaults to "$item")

-start_date (optional)

-end_date (optional)

-order_by (optional)

-url_template (optional, defaults to "?order_by=$order_by")

See Also:

• /doc/acs-templating/
• /doc/acs-lang/

Partial Call Graph (max 5 caller/called nodes):

Testcases:

No testcase defined.

Returns a calendar for a specific week, with details supplied by Julian date. Defaults to this week. To specify details for the individual days (if large_calendar_p is set) put data in an ns_set calendar_details. The key is the Julian date of the day, and the value is a string (possibly with HTML formatting) that represents the details. The variables in the templates are: - day_template: julian,day,date,pretty_date - next_week_template: - prev_week_template: DEPRECATED: this proc uses hardcoded markup and is therefore difficult to style. It is also not localized. Many of the date operations happening here have now good tcl support through the clock api, which would make this code probably faster and certainly portable (Oracle query is missing). Future reimplementations should leverage the templating system more.

Switches:

-calendar_details (optional)

-date (optional)

-large_calendar_p (optional, defaults to "1")

-master_bgcolor (optional)

-header_bgcolor (optional)

-header_text_color (optional, defaults to "white")

-header_text_size (optional, defaults to "+2")

-day_template (optional, defaults to "<!--$julian-->$day")

-day_header_size (optional, defaults to "2")

-day_header_bgcolor (optional, defaults to "#666666")

-calendar_width (optional, defaults to "100%")

-day_bgcolor (optional, defaults to "#DCDCDC")

-today_bgcolor (optional, defaults to "#FFF8DC")

-day_text_color (optional, defaults to "white")

-empty_bgcolor (optional, defaults to "white")

-next_week_template (optional)

-prev_week_template (optional)

-prev_next_links_in_title (optional, defaults to "0")

-fill_all_days (optional, defaults to "0")

See Also:

• /doc/acs-templating/
• /doc/acs-lang/
• clock

Partial Call Graph (max 5 caller/called nodes):

Testcases:

No testcase defined.