Sausalito Developer's Guide - Parent Directory

More documents

Recommendations

Info

2—2 Chapter 2: About The Sausalito Architecture Beta Draft 9. Copyright ' 2001. Cobalt Networks, Inc. All Rights Reserved. The Sausalito software architecture is an answer to the appliance concept. Sausalito allows Cobalt to provide a single back-end mechanism for monitoring and manipulating the system software. Through this mechanism, a very simple user interface can operate, while keeping the details of the backend system logically separate. This separation of interface and implementation is a cornerstone of reusable and reliable software design. This allows developers to have a stable exported interface that can be used in their applications for complete integration into the Cobalt environment. This is one of the major goals of Sausalito. Figure 2—1 provides a basic view of Sausalito architecture. The interface provides the glue between the user interface and back end. Figure 2—1 Overview of Sausalito The User Interface Defines the Appliance Appliances make complex systems very easy to use. The user interface plays a strong role in defining the appliance. Sausalito provides the foundation to build web-based user interface on the user interface layer. This layer communicates with users and routes information to and from the back-end. There are several components in the this layer: the navigation manager, User Interface Foundation Classes (UIFC) and stylist. Sausalito was designed to meet internationalization requirements. Sausalito supports users at different locales by working with European and Asian languages. The user interface layer uses a internationalization library to handle this requirement. For example, when the user interface needs to display Welcome to users who speaks German, it asks the internationalization library to get the translated string Willkommen to display to users.
Chapter 2: About The Sausalito Architecture 2—3 Beta Draft 11. Copyright ' 2001. Cobalt Networks, Inc. All Rights Reserved. Navigating Around The navigation manager component is designed to provide basic navigation capabilities to user interfaces. The idea is to separate data that defines the site map and the navigation managers that walk through the map. On a site map, each node denotes a page on the user interface and each page can have multiple widgets. Information about the nodes are stored in special files. Given a site map, it is up to navigation managers to determine how to walk through them. Different navigation managers can walk through the same site map differently. Some navigation manager can provide a step-by-step walk through while other can show the whole map as a tree structure so that users can pick the right node instantly. Building Pages Sausalito provides many utility libraries and UIFC as a widget set to build user interface pages from. One of the goals of UIFC is to provide consistency among different pages on a user interface. This is extremely important for the interface s ease of use. For example, UIFC, fields that represent boolean selections always look the same. Otherwise, boolean selections can be represented as a checkbox, two radio buttons or a change-state-button. UIFC is object-oriented. Each widgets have their corresponding classes. Also, UIFC is currently implemented in PHP. Developers must have a basic understanding of objectoriented programming and PHP before examining UIFC. PHP is a very easy-to-learn and versatile scripting language designed to build web pages. HtmlComponentFactory is a UIFC class that construct widgets and talk to the internationalization library. The basic task of this class is to instantiate UIFC widget classes in common ways and give them parameters of the desired locale. This is the first class to understand within UIFC. ServerScriptHelper is a utility class that simplifies page building. Its main job is to communicate with CCE for authentication and for getting user preferences. It also provides methods to make page building easy.
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: Chapter 2 About The Sausalito Archi
Page 23 and 24: Chapter 2: About The Sausalito Arch
Page 29 and 30: Chapter 3 User Interface Chapter Co
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 71 and 72:
Chapter 5: Introducing The Cobalt C
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
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?