xml fi les consisting of the code for custom tabs should be accessible to clients.
?– Web sites mentioned in the code should be available to clients.
?– You can add graphics to differentiate the tabs, provided they are in .png format and
are either 16?—16 or 32?—32 pixels.
?– You can have a maximum of 32 tabs (however, you may not need that many; the
objective is not to overload the messenger client, but to provide some dynamic
content).
Let??™s look at the XML fi le closely to understand the tags that are used (see Table A.2).
Figure A.6 HTML Page Displayed through a Custom Tab
Customizing the MOC Client ??? Appendix A 413
Table A.2 Custom Tabs XML File
Code Description
Identifi es the XML fi le
, Opening and closing tags for the tab data
, Opening and closing tags to identify
information for individual tabs
, Location of the graphics for the
Tab button
, Name of the tab
, Opening and closing tags for the small
text balloon that appears when the user
moves the mouse over a tab
, Opening and closing tags that point to
the Web site URL to be displayed inside
the tab
, Optional parameter that passes user
information (currently logged in)
, User??™s contact ID
, Tag to inform whether the information
should be available when the user is
logged in to MOC from inside or outside
the network.
Pages:
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418