18,26c18,20 < There are three options-setting dialogs -- two for the regular user of the < Calendar Tool and one for the administrative user of the Calendar Tool < Administration program. The regular user options are covered first, followed < by options for the administrative user. <

< For both the regular and administration interfaces, the top group of items in < the `Options' menu correspond one-for-one with tabs in an options < dialog. When the user selects one of the menu items, the system displays the < dialog with the corresponding tab selected. For example, when the regular user --- > The items in the `Options' menu correspond one-for-one with tabs in an > options dialog. When the user selects one of the menu items, the dialog is > displayed with the corresponding tab selected. For example, when the user 28c22 < system displays the dialog shown in Figure 254. --- > system displays the dialog shown in Figure 257. 37c31 <

Figure 254: Options dialog.

--- >

Figure 257: Options dialog.

64a59,64 > The `Save As ...' and `Load ...' buttons allow the user to > save and load copies of option settings to and from files. Details of saving > and loading auxiliary data files are covered in > > Section 2.8.6 > 70c70 < `Cancel' in the option dialog clears all unapplied changes and removes --- > `Cancel' in the option dialog clears any unapplied changes and removes 72d71 < 74,84c73,82 < < Most option settings for the regular user are calendar-specific. That is, each < calendar has its own option settings. When more than one calendar is open, the < system provides a separate options dialog for each calendar. Whenever the user < executes the `Options' menu command, the system (re)displays an < options dialog for the current calendar. Each calendar uses a single options < dialog. This means that up to N options dialogs can be displayed at < any time, for N equal to the number of open calendars. When more than < one calendar is open, the calendar name appears by default in the banner of < each options dialog. The appearance or non-appearance of the calendar name in < window banners is controlled by an option setting, as described in --- > Option settings are calendar-specific. That is, each calendar has its own > option settings. When more than one calendar is open, the system provides a > separate options dialog for each calendar. Whenever the user executes the > `Options' menu command, the system (re)displays an options dialog for > the current calendar. Each calendar uses a single options dialog. This means > that up to N options dialogs can be displayed at any time, for > N equal to the number of open calendars. When more than one calendar > is open, the calendar name appears by default in the banner of each options > dialog. The appearance or non-appearance of the calendar name in window > banners is controled by an option setting, as described in 88,95d85 <

< For the regular user, there are four global option settings that are not < calendar-specific, but instead apply to the Calendar Tool operating session as < a whole. The dialog for these options is displayed using the `Global' < command in the options menu. These global options are described in < < Section 2.7.6. < 108c98 < Figure 254. --- > Figure 257. 115c105 < times. The default values for these settings are: 12-hour time, show both --- > times. The default values for these settings are 12-hour time, show both 118,122c108,109 < be from zero to three characters. When the user selects 24-hour clock, the < system disables the show AM, show PM, and AM/PM separator fields, but leaves < the settings of these fields unchanged. If the user subsequently re-selects < 12-hour clock, the AM/PM checkboxes and separator field are re-enabled, and < retain the settings from when the 12-hour setting was last in effect. --- > be from zero to three characters. When 24-hour clock is selected, the show > AM/PM and separator fields are disabled, but not cleared. 138c125 < four components. Table 11 indicates in which contexts dates are displayed and --- > four components. Table 12 indicates in which contexts dates are displayed and 153c140 < month, date, year --- > date, month, year 156c143 < day, month, date, year --- > day, date, month, year 159c146 < day, month, date, year --- > day, date, month, year 162c149 < month, date range, year --- > date range, month, year 171c158 < month (short or number), date, year --- > date, month (short or number), year 173c160 <

Table 11: Date display contexts. --- >

Table 12: Date display contexts. 185,186c172,173 < All four date-display list boxes have the same list of items, which is shown in < Figure 255. --- > The four date-display list boxes have the same list of items, which is shown in > Figure 258. 195c182 <

Figure 255: Date format combo box lists.

--- >

Figure 258: Date format combo box lists.

202c189 < Table 12 shows the three alternatives. --- > Table 13 shows the three alternatives. 244c231 <

Table 12: Day of the week formats. --- >

Table 13: Day of the week formats. 253,266c240,247 < In all cases, the day name is capitalized. <

< The fourth through sixth items specify the month name. The full name is the < complete spelling of the month, capitalized. The short name is the first three < letters of the month, capitalized. The month number is between 1 and 12. <

< The seventh list item is for the date number. It is an integer between 1 and < 28 to 31, depending on the number of days in the selected month. <

< The last two date-display items specify the year as four or two digits. When < the two-digit year format is selected, the two digits correspond to the current < century or the previous century, which ever century contains the decade nearest < the specified decade, where the decade is that specified by the first of the < two digits. --- > In all cases, the day name is capitalized. The fourth list item is for the > date number, which is always an integer between 1 and 31. The fifth through > seventh items specify the month name. The short name is the first three > letters of the month, capitalized; the month number is between 1 and 12. The > last two items specify the year as four or two digits. When the two-digit year > format is selected, the two digits correspond to the current century or the > previous century, which ever century contains the decade nearest the specified > decade, where the decade is that specified by the first of the two digits. 269,271c250,251 < month, date, and year. The values in the three boxes in the < `Separator' column must be at least one character each. The separator < defaults are ", ", " ", and ", ". --- > date, month, and year. The separators must be at least one character each. > The separator defaults are ", ", " ", and ", ". 312c292 < Figure 256 shows the user having changed the time and date option settings. --- > Figure 259 shows the user having changed the time and date option settings. 321c301 <

Figure 256: Changes to time and date options.

--- >

Figure 259: Changes to time and date options.

327c307 < user has made some option changes. Figure 257 shows the result of applying --- > user has made some option changes. Figure 260 shows the result of applying 337c317 <

Figure 257: Effects of time and date option changes on --- >

Figure 260: Effects of time and date option changes on 345c325 < Table 11. --- > Table 12. 356c336 < the system updates the display as shown in Figure 258. --- > the system updates the display as shown in Figure 261. 365c345 <

Figure 258: Fonts options tab.

--- >

Figure 261: Fonts options tab.

397c377 < Section 2.13.5.3 --- > Section 2.13.5.2 407,411c387 < No other control of text coloring is available, the coloring being black except < for the coloring defined by categories, as defined in < < Section 2.5.5. < --- > No other control of text coloring is available. 418c394 < Figure 259 shows the user having changed font option settings. --- > Figure 262 shows the user having changed font option settings. 427c403 <

Figure 259: Changes to font options.

--- >

Figure 262: Changes to font options.

432c408 < Figure 260 shows the result of applying these changes on the monthly view shown --- > Figure 263 shows the result of applying these changes on the monthly view shown 435c411 < Figure 21. --- > Figure 22. 445c421 <

Figure 260: Monthly view with font changed applied.

--- >

Figure 263: Monthly view with font changed applied.

454c430 < Section 2.13.5.3. --- > Section 2.13.5.2. 465c441 < in the options dialog, the system updates the display as shown in Figure 261. --- > in the options dialog, the system updates the display as shown in Figure 264. 474c450 <

Figure 261: Scheduling options tab.

--- >

Figure 264: Scheduling options tab.

492,496c468,472 < dialog, the user presses one of the four dialog-type buttons to bring the < dialog up. When the user does so, the system displays a normal scheduling < dialog that is augmented for the purposes of setting default values. For < example, when the user presses the `Appointments ...' default-setting < button, the system displays the dialog shown in Figure 262. --- > dialog, the user presses one of the buttons to bring the dialog up. When the > user does so, the system displays a normal scheduling dialog that is augmented > for the purposes of setting default values. For example, when the user presses > the `Appointments ...' default-setting button, the system displays the > dialog shown in Figure 265. 505c481 <

Figure 262: Appointments scheduling defaults dialog.

--- >

Figure 265: Appointments scheduling defaults dialog.

513c489 < Figure 5. --- > Figure 6. 531c507 < Figure 263 shows the result of the user setting some appointment dialog --- > Figure 266 shows the result of the user setting some appointment dialog 541c517 <

Figure 263: Appointments scheduling defaults dialog with --- >

Figure 266: Appointments scheduling defaults dialog with 561c537 < Figure 263, --- > Figure 266, 568c544 < subsequent scheduling operations. For example, Figure 264 shows the default --- > subsequent scheduling operations. For example, Figure 267 shows the default 570c546 < Figure 263. --- > Figure 266. 580c556 <

Figure 264: Appointments dialog with updated default --- >

Figure 267: Appointments dialog with updated default 592c568 < `Recurring' on. Figure 264 also reflects the changes to date format --- > `Recurring' on. Figure 267 also reflects the changes to date format 595c571 < Figure 256. --- > Figure 259. 598c574 < The built-in default values for all scheduling dialogs are defined when the --- > The initial default values for all scheduling dialogs are defined when the 603,604c579,580 < ). Table 13 shows the initial default values for all fields in all four types < of scheduled item. --- > ). Table 14 shows the default values for all fields in all four types of > scheduled item. 660c636 <

Table 13: Default field values for all four types of --- >

Table 14: Default field values for all four types of 672c648 < 5, --- > 6, 675c651 < 83, --- > 84, 678c654 < 123, --- > 124, 682c658 < 127 --- > 128 686,701c662,672 < < The two radio buttons in the scheduling defaults tab ( < < < Figure 261 < < ) are used to select the values that appear in scheduling dialogs when they are < reopened after having been opened one or more times previously. The first < selection specifies that values in reopened dialogs are those that were entered < by the user the last time the dialog was open. The second radio button < selection specifies that values in reopened dialogs are the dialog defaults, < independent of the most-recently entered values. A scheduling dialog is < considered to be "re"opened when the user re-executes a scheduling command < after having executed `Cancel' or `Close' in the previously- < open dialog. Deiconifying or moving an already open dialog to the front on the < screen does not constitute reopening in this context. --- > The two radio buttons in the defaults tab are used to select the values that > appear in scheduling dialogs when they are reopened after having been opened > one or more times previously. The first selection specifies that values in > reopened dialogs are those that were entered by the user the last time the > dialog was open. The second radio button selection specifies that values in > reopened dialogs are the dialog defaults, independent of the most-recently > entered values. A scheduling dialog is considered to be "re"opened when the > user re-executes a scheduling command after having executed `Cancel' > or `Close' in the previously-open dialog. Deiconifying or moving an > already open dialog to the front on the screen does not constitute reopening in > this context. 710c681 < options dialog as shown in Figure 265. --- > options dialog as shown in Figure 268. 719c690 <

Figure 265: Scheduling overlaps options tab.

--- >

Figure 268: Scheduling overlaps options tab.

733c704 < the system displays a dialog of the form shown in Figure 266. --- > the system displays a dialog of the form shown in Figure 269. 742c713 <

Figure 266: Overlapping item warning.

--- >

Figure 269: Overlapping item warning.

764c735 < 2.13.5.4 --- > 2.13.5.3 785c756 < options dialog as shown in Figure 267. --- > options dialog as shown in Figure 270. 794c765 <

Figure 267: Scheduling meetings options tab.

--- >

Figure 270: Scheduling meetings options tab.

852c823 < options dialog as shown in Figure 268. --- > options dialog as shown in Figure 271. 861c832 <

Figure 268: Scheduling reminders options tab.

--- >

Figure 271: Scheduling reminders options tab.

895,896c866,867 < Default settings for the time the reminder dialog appears initially are defined < in the scheduling defaults options, described in --- > Default settings for time the reminder dialog appears initially are defined in > the scheduling defaults options, described in 909c880 < the system updates the display as shown in Figure 269. --- > the system updates the display as shown in Figure 272. 918c889 <

Figure 269: Viewing options tab.

--- >

Figure 272: Viewing options tab.

926,927c897 < the < item view for each type of scheduled item. The default values are as --- > the item view for each type of scheduled item. The default values are as 934c904 < illustrated fully in Sections --- > illustrated in Sections 942c912 < respectively. Figures 270 through 273 show the presentation of these settings --- > respectively. Figures 273 through 276 show the presentation of these settings 952c922 <

Figure 270: Viewing day options tab.

--- >

Figure 273: Viewing day options tab.

965c935 <

Figure 271: Viewing week options tab.

--- >

Figure 274: Viewing week options tab.

979c949 <

Figure 272: Viewing month options tab.

--- >

Figure 275: Viewing month options tab.

992c962 <

Figure 273: Viewing year options tab.

--- >

Figure 276: Viewing year options tab.

1007,1009c977,986 < Viewing lists options provide control over the commands in the `View < Lists' submenu. When the user selects the `lists' tab within the < `Viewing' tab, the system updates the display as shown in Figure 274. --- > Explain how the format of all five third-tier tabs is similar. Also > explain that these options work a heck of a lot like custom lists. In fact, > the only fundamentally new functionality in a custom list is the ability to > have two or three types of items in the same list. Also, the ability to name > custom lists is handy, since there's only a single default behavior for each > type of list, but with custom list naming we can have multiple selectable > listing behaviors. So, bottom line, the custom list functionality is not a > huge add-on above list options, but it's fine since custom lists and options > all work nicely alike. > 1018c995 <

Figure 274: Viewing lists options tab.

--- >

Figure 277: Viewing lists options tab.

1023,1047d999 < All five subtabs for list viewing are similar in format. Each contains a < subset of the information in the custom lists dialog, presented in < < Section 2.3.3.6. < < The settings in each subtab allow the user to define the default format for < each of the five types of lists -- appointments, meetings, tasks, events, and < all items. The specific meaning of the subtab settings is as described in < Section 2.3.3.6. The difference between the list viewing options compared to < the custom list settings is that the options apply to all lists that are < displayed by the top five the commands in the `View Lists' menu ( < < Figure 37 < < ), whereas the custom list settings apply to a single specific custom list. < < To be clear, < < the list viewing options apply to all lists displayed with the top five < `View Lists' menu commands, never to a custom list. In contrast, the < view settings for any particular custom list apply to that list only, not to < any list displayed with the top five menu commands, nor to any other custom < list. <

< Figures 275 through 278 show the other four subtabs for viewing lists options. 1057c1009 <

Figure 275: Viewing meetings lists options tab.

--- >

Figure 278: Viewing meetings lists options tab.

1071c1023 <

Figure 276: Viewing tasks lists options tab.

--- >

Figure 279: Viewing tasks lists options tab.

1085c1037 <

Figure 277: Viewing events lists options tab.

--- >

Figure 280: Viewing events lists options tab.

1099c1051 <

Figure 278: Viewing all-items lists options tab.

--- >

Figure 281: Viewing all-items lists options tab.

1104a1057,1084 >

> OLD FODDER (from here to end of subsection): >

> The length of each of the four categories of list is controlled by the dialog > shown in figure 282. The dialog controls allow the user to specify the number > of items before and after a specified date. For example, the dialog settings > shown in Figure 282 show the user having specified the following format for the > display of item lists: >

>

> Hmm ... now that I'm doing this, I'm thinking that maybe we should just > make this part of the regular filtering section, so that we maintain > orthogonality. We need to think about this. An immediate question in this > regard is do we really need to provide both a list-length feature as well as > start/end date means to specify the number of items in a list. Curiously, this > is pretty much the same concept as specifying start/end versus start/duration > item lengths. > 1111,1112c1091 < When the user selects the `Windows' tab within the `Viewing' < tab, the system updates the display as shown in Figure 279. --- > 1121c1100 <

Figure 279: Viewing windows options tab.

--- >

Figure 282: Viewing windows options tab.

1127,1168c1106,1107 < The `Initial Windowing Mode' specifies the default setting for the < window modes described in < < Section 2.3.6.2. < < The items in the windowing-mode option menu are the same as in the windowing- < mode submenu shown in < < Figure 71 < < -- Two-Window, Per-Level, and Multi-Window. The default is Per-Level. The < effect of each of these settings is described fully in < < Section 2.3.6.2. < <

< The `Magnetization' option specifies the default proximity and spacing < for the magnetization features described in < < Section 2.3.6.3. < <

< The `Window Positioning' radio buttons specify the way successive < display windows appear on the screen. When the `Calendar Tool policy' < is on, the window placement is as follows: <

    <
  1. < After the menubar, the next display window is placed with its top border ten < pixels below the bottom of the menubar, and with its left border aligned with < the left border of the menubar. <
  2. < Thereafter, the top left corner of each successive display window appears down < and to the right of the most recently displayed previous window. The downward < and rightward spacing is two times the height of the display window banner, < which value is dependent on the operating environment in which the Calendar < Tool is running. <
  3. < Whenever the downward and/or rightward displacement would cause the top left < corner of the window to be off the screen, the window is placed so that its top < left corner is at the top left corner of the screen. Successive windows < thereafter are placed down and to the right. <
--- > Cal Tool policy is realative to menubar, staggered down and to the right in > multi-window mode. 1170,1183c1109,1110 < When the `OS Policy' radio button is on, successive display windows < are placed per the placement policy of the window manager of the underlying < operating system. Specific control options for this placement policy must be < set at the operating system level, if possible. <

< The three radio buttons under `Show current calendar name in window < banners' specify when the name of the current calendar appears in display < window banners. Placement of the calendar name within the banner is described < in < < Section 2.3.6.5. < < The `in menubar banner only' setting does not apply to view windows < for other-user and group calendars, since the banners of these windows --- > The `in menbar banner only' setting does not apply to view windows for > other-user and group calendars, since the banners of these windows 1186,1192c1113,1115 < The two radio buttons under `Show active filter name in window < banners' specify in which display window banners the currently active < filter name appears, if a filter is active. Placement of the filter name < within the banner is described in < < Section 2.3.6.5. < --- > `In all windows' means all windows of the current user, not other > users or groups, which is consistent with the most recent clarification of the > specialness of other user and group windows). 1200,1201c1123,1127 < When the user selects the `Miscellaneous' tab within the < `Viewing' tab, the system updates the display as shown in Figure 280. --- > Add `External Email Program' and explain that it's the program launched > when contacting the admin; it's not launched from the cal tool for receiving > any notifications, only for sending. If possilbe, the system will > determine the user's preferred or default email program by querying the > underlying operating environment, and use 1210c1136 <

Figure 280: Viewing miscellaneous options tab.

--- >

Figure 283: Viewing miscellaneous options tab.

1215,1304d1140 < The `Initial View When Open' radio buttons allow the user to select < which calendar view(s) appear initially when the user opens the calendar with < the `File->Open' command ( < < Section 2.8.2 < < ), or when the calendar name appears in the `names of open calendars' < list in the Settings file that the system loads at start-up (Sections < < 2.8.1 < < and < < 2.8.5 < < ). The default for the initial-view option is the month view. If < `none' is selected, there is no initial view for this calendar, i.e., < when the calendar is opened it becomes current, its name appears in the < Calendars list, but there is no initial display window. If < `Day' is selected, the calendar is opened with the daily view of < today's date. If the `week', `month', or `year' < radio button is selected, the calendar is opened at that level, with today's < date highlighted. When `per most recently saved settings' is < selected, the initial view(s) are those saved in the `state of open < windows' setting for this calendar; this setting is saved whenever the < user executes `File->Save', as described in < < Section 2.8.4. < <

< Typically, when the user selects `per most recently saved settings', < the initial view for the calendar is the same as when the user last closed the < calendar or last exited the Calendar Tool. This is the case because it is < presumably typical that the user saves the calendar before closing it or < exiting. <

< When the user invokes the Calendar Tool with one or more calendar files as < arguments, the effects of the initial view settings at start-up time are as < shown in Table 14. < <
<
<

<
< < < < < < < < <
Initial View Setting < Effect with respect to calendar file arguments <
none < < the presence of arguments overrides the none setting; all argument files < are opened at the month view level, with today's date highlighted; windows are < placed on the screen per the current window placement option setting <
< day, week, month, or year < < each argument file is opened at the selected view level <
< per most recently saved settings < < all argument files are first opened at the month view level, with today's date < highlighted, per current window placement option; then the settings are used to < further populate the initial display, except that if the settings include the < month view for any already-opened argument calendar, that month-view setting is < ignored <
< view status as of most recent close < < same effect as `per most recently saved settings' <
<

Table 14: Effects of initial view settings when tool is < invoked with file arguments. <
<

<

< <
< <

< < < Section 2.15.2 < < covers details of invoking the Calendar Tool with calendar file arguments. 1306,1311c1142,1149 < The radio buttons for `System-Defined Events' specify whether to show < or hide such events in all calendar and list views. System-defined events are < holidays and other pre-defined calendar dates, as defined in < < Section 2.11.16. < --- > Re. `Initial View' level, to be consistent with the way > things are explained in specific-date-viewing, the default level cannot be at > the item level. Nor do I think it makes particularly good sense to have it be > some list. Therefore, the default initial view level is one of four day > through year levels, and perhaps a "no window" option. Remember also the bit > about the initialization file and how it deals with the default view level > always happening, including how a "no window" option value affects things > initialization-filewise. 1313c1151 < --- > 1315c1153 < 2.7.5. Administrative Options, for the Regular User --- > 2.7.5. Administrative Options 1320c1158 < the system updates the display as shown in Figure 281. --- > the system updates the display as shown in Figure 284. 1325c1163 < --- > 1329c1167 <

Figure 281: Administrative options tab.

--- >

Figure 284: Administrative options tab.

1336,1340c1174,1177 < whenever a calendar is opened. When the default setting of `yes' is < selected, every time the user executes `File Open' for a calendar, the < system tries to connect to the central host associated with that calendar, if < there is an associated host. Details of host association and connection are < covered in --- > whenever the calendar is open. When the default setting of `yes' is > selected, every time the user executes `File Open' for the current > calendar, the system tries to connect with the associated central host. > Details of host association and connection are covered in 1345,1350c1182,1189 < does not establish a host connection when a calendar is open, requiring that < the user establish the connection explicitly with the host `Connect' < command, as described in < < Section 2.6.6.1. < --- > does not establish a host connection when the calendar is open, requiring that > the user establish the connection explictly with the host `Connect' > command. >

> Add options for default caltool user ID and password. These are the ones > tried first for connect. NOT -- IDs and passwds are now in connect dialog. NOT > NOt -- they're not in the connect dialog, so we do want options here for > default ID and passwd. 1354,1506c1193,1195 < mode in the regular-user Calendar Tool. For administrative users running the < Calendar Tool Administration program, there are additional administrative < options, as described in < < Section 2.7.7. < < < <

< 2.7.6. Global Session-Wide Options <

< <

< When the regular user selects the `Global' command in the < `Options' menu, the system displays the dialog shown in Figure 282. < <
<
<

< <

< <

<

Figure 282: Global options dialog.

<
< <
< <

< `Initial View for New Calendars' specifies the initial view when the < user creates a calendar with the `File->New' command, or when the < system creates a new calendar after having been invoked from the operating < environment with no file argument(s). If `Day' is selected, a new < calendar is opened with the daily view of today's date. If any of the other < three radio buttons is selected, the new calendar is opened at that level, with < today's date highlighted. <

< The option for `External email program' allows the user to select the < application program to be used by the Calendar Tool for the purposes of < electronic mail communication. The only circumstance in which an external < email program is launched from the Calendar Tool is when the user executes the < `Contact Admin' command, as described in < < Section 2.6.6.5. < < When possible, the Calendar Tool queries the underlying operating environment < to determine the identity of the user's preferred email program. When such < determination is made, the system inserts the name of the program as the < default value in the `External Email Program' field. If the user's < preferred email program cannot be determined, the field is blank. <

< The option for `External Web Browser' allows the user to select the < application program to be used by the Calendar Tool for the purposes of web < browsing. The only circumstance in which an external web browser is launched < from the Calendar Tool is when the user chooses to view the minutes associated < with a meeting, as described in < < Section 2.5.1.2. < < When possible, the Calendar Tool queries the underlying operating environment < to determine the identity of the user's preferred web browser. When such < determination is made, the system inserts the name of the web browser as the < default value in the `External Web Browser' field. If the user's < preferred web browser cannot be determined, the field is blank. <

< The option for `Location of Calendar Tool user directory' allows the < user to change the location of that directory. As explained in < < Section 2.8.1, < < the default location is ".CalendarTool" under the user's home < directory. This default location appears as the initial setting in the options < dialog. Once applied, a change in directory location takes effect after the < user exits and restarts the Calendar Tool. This is the only option that < requires a restart. <

< A change of directory location does does not change the location of < files in the original user directory. The files must be moved or copied as < desired, using the normal file management commands of the underlying operating < environment. The system does not validate the directory until the restart is < performed. If the changed-to directory is invalid or contains invalid files, < the system responds as described < < Section 2.8.12. < <

< The `Apply', `Clear', and `Cancel' buttons in the < global options dialog behave the same as in the multi-tab option dialog < described in the preceding sections. The `Save' button becomes < enabled when the user edits one or more dialog fields. For example, Figure 283 < shows the user having entered values for the email program, web browser, and < location of the user directory. < <
<
<

< <

< <

<

Figure 283: Changes to global options.

<
< <
< <

< When the user presses the enabled `Save' button, the system saves the < contents of the dialog into the Calendar Tool Settings file. Only the < global settings portion of `Settings' is affected by this save, with < all other portions of the settings file left unchanged. Details of < Settings file contents and related commands are covered in Sections < < 2.8.1 < < and < < 2.8.5. < < Unsaved changes can also be saved using the `Save Settings' command in < the `File' menu, also described in < < Section 2.8.5. < < The `Save' button is disabled when the user has made no edits, or < changed edited fields back to their most recently-saved values. <

< When the user applies or saves the global options, the system validates that < the `Location of Calendar Tool user directory' is an existing < directory that is readable and writable by the user. If this validation fails, < the system displays an appropriate error message, as described in < < Section 2.12.10. < < The system performs no validation of the email program or external web browser < when options are applied or saved. If these are not valid executable programs, < the error condition will arise when the user attempts to invoke the programs in < the contexts of their use, which are, respectively, contacting a Calendar Tool < administrator ( < < Section 2.6.6.5 < < ) and viewing the minutes for a meeting ( < < Section 2.4.1.1 < < ). If an execution error arises in those contexts, the system displays an < appropriate error, as described in Sections < < < < and < < --- > mode for regular users. For adminstrative users running the Calendar Tool > Adminstration program, there are additional administrative options, as > described in the immediately following section of the requirements. 1510c1199 < 2.7.7. Options in the Calendar Tool Administration Program --- > 2.7.6. Options in the Calendar Tool Administration Program 1514,1579c1203,1249 < When the administrative user of Calendar Tool Administration selects the < `Times and Dates' item in the administrative `Options' menu, < the system displays the dialog shown in Figure 284. < <
<
<

< <

< <

<

Figure 284: Options dialog for Calendar Tool Administration. <

<
< <
< < Compared to the options dialog for the regular Calendar Tool, there are two < fewer tabs. The three tabs in Figure 284 correspond to the three items in the < administrative options menu, shown in < < Figure 4. < < The `Scheduling' and `Viewing' tabs are missing, since the < administration program does not perform the calendar scheduling or viewing < operations that are available in the Calendar Tool. <

< The content of the `Times and Dates' tab in the administrative options < is identical with that tab in the regular-user options. These options also < have exactly the same functional effect as in the regular-user interface. The < appearance of times and dates in the Calendar Tool Administration program is < more limited than in the regular-user Calendar Tool. In particular, the only < place that times and dates appear in the administrative interface is in the < location bookings, described in < < Section 2.6.4. < < This means that the time and date option settings are less significant for the < administrative user, though again, their effect where visible is the same as < for the regular user. <

< When the administrator selects the `Fonts' tab in the administrative < options dialog, the system updates the display as shown in Figure 285. < <
<
<

< <

< <

<

Figure 285: Fonts options tab in the administrative options. <

<
< <
< < This tab is again identical in content and function to the one in the regular- < user interface. Since the appearance of scheduled items is very limited in the < administrative interface, the effect of the scheduled-item font setting is < limited. In particular, the only place where scheduled items are shown in the < administrative interface are in the location booking for a meeting (see Figure < < Figure 228 < < ). --- > NOTE: There needs to be a place for privileged admin-specific options, in > particular these: > > OK, it looks like the entire admin tab needs to be expanded for versions of the > options dialog that is displayed from within the caltool admin program. It > almost certainly needs subtabs, more-or-less correspondent to the items on the > privileged admin menu. > >

> The options dialog that runs under Calendar Tool Administration has the same > overall format as for regular users, except that the buttons along the bottom > of the dialog are limited to, Save, Clear, and > Cancel. > > There separate dialog `Save' and there is no `Apply' button. > Since there are no calendar viewing commands in the Calendar Tool > Administration program, setting options does not apply to a calendar being > viewed, but to the initial default values for those options for Calendar Tool > users, as stored in the Options file. >

> NOTE: This paragraph needs to be fixed per the latest and greatest options > set up. The default option values set by the administrator are available > to users in two ways. When running the Calendar Tool, the user can select the > `Defaults' button in the `Options' dialog. This allows the > user to set options to the default values set by an administrator, as described > > above. > >

> The other way that administrator-set options values are made available to > regular users is through a Calendar Tool program distribution created by the > administrator. That is, when an administrator creates a program distribution > using the `Admin Distribution' command, the option values that have > been set by the administrator are installed in the distribution program as the > defaults for that program. 1581,1582c1251,1260 < When the administrator selects the `Administrative' tab in the options < dialog, the system updates the display as shown in Figure 286. --- > Here's the deal for "inheritance" of options: >

    >
  1. > First global options are set. >
  2. > Then user-specific options are set, possibly overriding admin options. >
  3. > Finally, calendar-specific options are set, possibly overriding either of the > previous levels. >
1584,1595c1262 <
<
<
< <

< <

<

Figure 286: Administrator version of the Administrative < options Tab.

<
< <
--- > Here's some fodder axed on 11aug03 from the Admin section: 1597,1598c1264 < Here the option settings are fundamentally different than for the regular-user < interface. --- > .sh 3 "Global Options" 1600,1614c1266,1292 < The `Default calendar size limit' specifies the default maximum size < of all user and group calendars on the central host. The default can be < overridden for individual users or groups by changing the size limit for those < individuals, as explained in < < Section 2.6.5.5. < <

< The option for `Time to complete meeting scheduling while other users < waiting' is explained in < < Section 2.4.1.6.9. < < The administrator can change the time from the default of 2 minutes, if < desired. The value must be between 1 and 15 minutes, inclusive. --- > Explain how the first three kind of options are ?all? settable by user and > are therefore explained in the next section. The difference between what the > admin does versus what a regular user does is that under `Admin->Global > Options', the admin is setting the global defaults for all users, some or all > of which may be changed by users on an individual basis. I think it's also > worth mentioning that an admin can be a regular user if she wants to be. I.e., > there need not be a special user account that is "the" admin; there can be if > that's how a group of users wants to set things up, but there need not be. If > an admin wants to be are regular user, she needs to be aware that functions > performed under the `Admin' menu have potentially global effects, and must > exercise according care in the execution of the functions. >

> The Admin options are viewable by regular users but settable only by system > admins, so they're described here in this section of the requirements. > > .sh 4 "Administrative Options" > > .sh 5 "Root System Administrator" > > .sh 5 "Group Leader Privileges" >

> A bit of rationale: Since we're nixing pencil in, there was a bit of > thought just now that group leaders may not be all that necessary. However, > there are other useful reasons to have them. Also, I think it's reasonable to > say that group leaders are the only ones who can schedule meetings for which > online notification will be sent by the tool. So in effect what we've done is > demote pencil power in to notify power. 1616,1626c1294,1312 < The option for `Location of host repository directory' allows the < administrator to change the repository location. Details of the central host < repository and its location are covered in Sections < < 2.6 < < and < < 2.8.8. < < Figure 286 shows a typical default value for the repository location. --- > With that bit of rationale, here are the group leader privileges as we > currently see them: >

    >
  1. > Meeting notifications sent to attendees. >
  2. > 3jul02 NOTE: The following option is obsolete, given the details described in > the latest changing-and-deleting section, in particular the fact that a leader > cancels a meeting without deleting it by using the change operation instead of > delete. >
    > Cancellation notice sent when group leader deletes a meeting; deleted for non- > recurring, marked as CANCELED for recurring (maybe, or probably better just to > nuke it or maybe make this an option). >
  3. > Can add and remove members for group. >
> > .sh 5 "Platform-Dependent Options" 1628,1655c1314 < Once applied, a change in directory location takes effect after the < administrator exits and restarts the Calendar Tool Administration program. < This is the only administrative option that requires a restart. <

< Changing the location of the repository does not change the location < of the repository files and subdirectories. The files and subdirectories must < be moved or copied as desired, using the normal file-management commands of the < underlying operating environment. The system does not validate the directory < until the restart is performed. If the changed-to directory is invalid or < contains invalid files, the system responds as described < < Section 2.8.12. < <

< The default setting buttons under `Click on a button to set defaults for < that admin dialog' operate in the same manner as the default-setting < dialogs described in < < Section 2.7.3.1. < < That is, when the administrator selects one of the default-dialog buttons, the < system displays a normal administrative dialog that is augmented for the < purposes of setting default values. The two radio buttons under `Displayed < values when dialogs are reopened' have the same function as for regular- < users, as explained at the < < end of Section 2.7.3.1. < --- > As of 23jul02, I'm saying a firm (as possible with me) NO to this. 1657,1670c1316,1319 < The built-in default values for all administrative dialogs are defined when the < calendar tool is configured for installation (see < < Section 2.15 < < ). These values are illustrated in the figures of Sections < < 2.6.2 < < through < < 2.6.5 < < that show the initial state of each administrative dialog. --- > Although we'd like to avoid it, it may be necessary to at least plan for > platform-dependent options that may be needed for networking connections. If > at all possible, I'd like to avoid these. They sound like a cop out to > me. 1672c1321 < --- > 1674c1323 < 2.7.8. Restoring Built-In Default Settings --- > 2.7.7. Base Default Option Settings 1678,1708c1327,1330 < When the Calendar Tool and Calendar Tool Administration program are initially < installed, they have built-in default settings for all options. The values for < these built-in defaults are those that appear in each of the preceding figures < that show the initial state of the option tabs, and the global options dialog. <

< The built-in settings are overridden by any applied changes in the options < dialogs. The user (regular or administrator) can restore the built-in defaults < with the `Restore Defaults' command at the bottom of the < `Options' menu (both regular-user and administrative). When the user < executes this command, the system restores all options to their built-in < settings and applies the changes. In the case of the global options, the < system both applies and saves the changes. The result is that all tabs are < restored to their default states. <

< If the user wants to retain changed option settings before restoring defaults, < the user must execute a `Save' or `Save Settings' command in < the `File' menu. These commands save applied option settings in the < current calendar or a settings file, as described in Sections < < 2.8.4 < < , < < 2.8.5 < < , and < < 2.8.9. < < Restored defaults are not automatically saved. To do so, the user must execute < a save command. --- > The definition of this is as displayed in each of the initial tab figures > above. The base default settings are those defined internally within the > Calendar Tool application when it is initially installed. Can be overridden > when an admin creates a custom distribution. 1712c1334 < 2.7.9. Operating Environment Conventions --- > 2.7.8. Operating Environment Conventions 1717,1723c1339,1347 < of the functionality described in this Section (2.7) of the requirements. For < example, this functionality is classified as "Preferences" in some < environments, with conventions for the placement and layout of the Preferences < user interface. Implementors of the Calendar Tool may follow such conventions, < as long as the hierarchical organization and content of the options < functionality is maintained as described here. < --- > of the functionality described in > > Section 2.7 > > of the requirements. For example, this functionality is classified as > "Preferences" in some environments, with conventions for the placement and > layout of the Preference user interface. Implementors of the Calendar Tool may > follow such conventions, as long as the hierarchical organization and content > of the options functionality is maintained as described here.