Sausalito Developer's Guide - Parent Directory

More documents

Recommendations

Info

2—10 Chapter 2: About The Sausalito Architecture Beta Draft 9. Copyright ' 2001. Cobalt Networks, Inc. All Rights Reserved. CCE is not a mechanism for a user interface to trigger system events. The user interface should not rely on any knowledge of the handlers that are registered on an event. CCE is not a replacement for other security mechanisms. While Sausalito tries to be secure and cautious in all cases, it should not forego other security methods. CCE is not a replacement for a good backups. Much of the system’s data is stored in files on the system, not in CODB. Protect your data and back up regularly.
Chapter 3 User Interface Chapter Contents Introducing the User Interface Navigation System Styles Libraries Example Changing the Style Sausalito is Cobalt s first fully open programming interface. It is designed to enable thirdparty developers to create applications that are seamlessly integrated into the look and feel of Sausalito-based appliances. One of the layers within Sausalito is the user interface, which enables you to: ¥ Manipulate navigation with navigation managers and site maps ¥ Manipulate look-and-feel style ¥ Build user interfaces pages that are consistent with Sausalito-based systems How the Navigation System Works The navigation system is a sub-system within the user interface that manages navigation through site maps. The system consist of site maps and navigation managers. The navigation system on Sausalito is a dynamic system. It is generated from a set of files that define navigation nodes. By linking these nodes together, a site map is formed. Users can construct site maps by adding and removing nodes. These site maps are then interpreted by navigation managers. Whenever a user logs in to the user interface, navigation managers use the site map to govern how the user navigates.
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 27: Chapter 2: About The Sausalito Arch
Page 31 and 32: Chapter 3: User Interface 3—3 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 79 and 80:
Chapter 5: Introducing The Cobalt C
Page 81 and 82:
Page 83 and 84:
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

Create successful ePaper yourself

Delete template?

Save as template?