Sausalito Developer's Guide - Parent Directory

More documents

Recommendations

Info

3—4 Chapter 3: User Interface Beta Draft 11. Copyright ' 2001. Cobalt Networks, Inc. All Rights Reserved. Node E has no parent Node F has no parent Node G’s parent is F Node H’s parent is G Node I’s parent is G and J Node J has no parent The site map looks like Figure 3—1 Figure 3—1 Site Map A B C E G J The collapsible list navigation manager presents a site map in a collapsible list format and lets users navigate by clicking on items on the list. Users can expand or collapse parents to show and hide the children nodes, respectively. To use the collapsible list, users needs to supply the root node of the site. For example, using the above site map as an example with A as root, the collapsible list will look like: Item B Item C Item D F D H I Note that the node A and E are not being shown. This is because node A is the root and there is no path to descend down from the root to node E. The nodes F, G, H, I and J are not shown either because they are on a separate branch.
Chapter 3: User Interface 3—5 Beta Draft 11. Copyright ' 2001. Cobalt Networks, Inc. All Rights Reserved. The URL for collapsible list navigation manager is at /nav/cList.php. It needs a root parameter that specifies the id of the root. Therefore, use it like http:///nav/cList.php?root=. The flow navigation manager allows users to navigate forward or backward through a site map. Conditional branches for forward are supported. The root node needs to be supplied to the flow navigation manager and that becomes the first step of the flow. Take the above site map as an example with F as the root. Navigation starts at F. Users can move forward to G. No moving backward is allowed on the root node. At G, users can move backward to F or forward to either H or I. Moving to H or I depends on a condition check at G. At H or I, users can move back to G or finish the navigation. Note that users at I cannot move backward to J. Conditional forward is supported by a JavaScript interface. At the node where a conditional forward is necessary, that is, G in the above example, a getNextItemId()JavaScript function must be specified in the content page. This function should return the id of the next node when it is called with no parameters. Error checking is supported. When an user wants to move forward, all the submitHandler()s of all the form elements of the content page are called with no parameters. The forward operation proceeds only if all the submitHandler()s return true. If you use UIFC to build your content page, submitHandler()s are automatically defined. During the forward operation, after error checking is done at the front end, the form on the content page is submitted. The handler of the form submit should tell flow navigation manager if submission is successful or not. If successful, navigation moves to the next node. Otherwise, it stays at the same node. To notify the navigation manager, the form handler should return a page which sets the JavaScript variable flow_success to true or false, with true indicating success. Note that this variable is automatically handled by the toHandlerHtml() method of the ServerScriptHelper class. The URL for flow navigation manager is at /nav/flow.php. The root parameter needs to be supplied, so use something like http:///nav/flow.php?root=. Single navigation manager only supports one single node and does not allow users to navigate into other nodes. The URL for single navigation manager is at /nav/single.php. The root parameter needs to be supplied, so use something like http:///nav/single.php?root=.
Page 1 and 2: Sausalito Developer’s Guide Beta
Page 3 and 4: Contents iii Acknowledgements . . .
Page 5 and 6: Contents v Syntax: PROPERTY . . . .
Page 7 and 8: Contents vii Usage . . . . . . . .
Page 9 and 10: Contents ix removeIcon. . . . . . .
Page 11 and 12: Contents xi The BYE Command. . . .
Page 13 and 14: Chapter 1 Introducing The Sausalito
Page 15 and 16: Chapter 1: Introducing The Sausalit
Page 17 and 18: Chapter 1: Introducing The Sausalit
Page 19 and 20: Chapter 2 About The Sausalito Archi
Page 21 and 22: Chapter 2: About The Sausalito Arch
Page 29 and 30: Chapter 3 User Interface Chapter Co
Page 31: Chapter 3: User Interface 3—3 Bet
Page 35 and 36: Chapter 3: User Interface 3—7 Bet
Page 37 and 38: Chapter 3: User Interface 3—9 Bet
Page 39 and 40: Chapter 3: User Interface 3—11 Be
Page 41 and 42: Chapter 4 Using i18n and l10n in Sa
Page 43 and 44: Chapter 4: Using i18n and l10n in S
Page 57 and 58: Chapter 5 Introducing The Cobalt Co
Page 59 and 60: Chapter 5: Introducing The Cobalt C
Page 83 and 84:
Chapter 5: Introducing The Cobalt C
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Chapter 6 Making Sausalito-Aware Ap
Page 107 and 108:
Chapter 6: Making Sausalito-Aware A
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Appendix A User Interface Foundatio
Page 131 and 132:
Appendix A: User Interface Foundati
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Appendix B Utility Classes ArrayPac
Page 201 and 202:
Appendix B: Utility Classes B—3 B
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Appendix C l About Style Style File
Page 209 and 210:
Appendix C: About Style C—3 Beta
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Appendix D Base Data Types Scalar W
Page 237 and 238:
Appendix D: Base Data Types D—3 B
Page 239 and 240:
Appendix D: Base Data Types D—5 B
Page 241 and 242:
Appendix E Cobalt System Configurat
Page 243 and 244:
Appendix E: Cobalt System Configura
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Appendix F CCE Class Definitions Ch
Page 255 and 256:
Appendix F: CCE Class Definitions F
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Index Symbols .pkg file format 6-1
Page 263 and 264:
event_object( ) 5-42 event_oid( ) 5
Page 265:
MacAddress A-28 MailListName A-28 M
show all

Sausalito Developer's Guide - Parent Directory

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?