1--------------------------------------------------------------------------------------
2Notes for add-on developers:
3--------------------------------------------------------------------------------------
4All 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...
5
6--------------------------------------------------------------------------------------
7Add-on registration:
8--------------------------------------------------------------------------------------
9Tabs and Protocols (protocols are tabs):
10DUN_TAB_ADDON_TYPE : pointer to DialUpAddon object
11
12Authenticators:
13DUN_AUTHENTICATOR_ADDON_TYPE : BMessage with the following entries:
14{
15	"KernelModule" : string
16	"TechnicalName" : string
17	"FriendlyName" : string
18	"Position" : int32
19}
20
21Devices:
22DUN_DEVICE_ADDON_TYPE : pointer to DialUpAddon object
23
24Addons that must be deleted:
25DUN_DELETE_ON_QUIT : pointer to DialUpAddon object - this will be deleted when the preflet quits
26		(you should register all your addons here, too)
27
28
29--------------------------------------------------------------------------------------
30Additional data in the BMessage object for add-ons:
31--------------------------------------------------------------------------------------
32DUN_MESSENGER : BMessenger - This messenger can be used to send messages to the preflet
33DUN_TAB_VIEW_RECT : BRect - This rect should be used for tabs
34DUN_DEVICE_VIEW_WIDTH : float - Maximum width a device add-on's view may have
35