1 --------------------------------------------------------------------------------------
2 Notes for add-on developers:
3 --------------------------------------------------------------------------------------
4 All add-ons must add a "Valid" boolean value to every recognized parameter. The preflet will check if all values were recognized and if not it will ask the user if he wants to edit the interface anyway...
6 --------------------------------------------------------------------------------------
8 --------------------------------------------------------------------------------------
9 Tabs and Protocols (protocols are tabs):
10 DUN_TAB_ADDON_TYPE : pointer to DialUpAddon object
13 DUN_AUTHENTICATOR_ADDON_TYPE : BMessage with the following entries:
15 "KernelModule" : string
16 "TechnicalName" : string
17 "FriendlyName" : string
22 DUN_DEVICE_ADDON_TYPE : pointer to DialUpAddon object
24 Addons that must be deleted:
25 DUN_DELETE_ON_QUIT : pointer to DialUpAddon object - this will be deleted when the preflet quits
26 (you should register all your addons here, too)
29 --------------------------------------------------------------------------------------
30 Additional data in the BMessage object for add-ons:
31 --------------------------------------------------------------------------------------
32 DUN_MESSENGER : BMessenger - This messenger can be used to send messages to the preflet
33 DUN_TAB_VIEW_RECT : BRect - This rect should be used for tabs
34 DUN_DEVICE_VIEW_WIDTH : float - Maximum width a device add-on's view may have