--------------------------------------------------------------------------------------
Notes for add-on developers:
--------------------------------------------------------------------------------------
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...

--------------------------------------------------------------------------------------
Add-on registration:
--------------------------------------------------------------------------------------
Tabs and Protocols (protocols are tabs):
DUN_TAB_ADDON_TYPE : pointer to DialUpAddon object

Authenticators:
DUN_AUTHENTICATOR_ADDON_TYPE : BMessage with the following entries:
{
	"KernelModule" : string
	"TechnicalName" : string
	"FriendlyName" : string
	"Position" : int32
}

Devices:
DUN_DEVICE_ADDON_TYPE : pointer to DialUpAddon object

Addons that must be deleted:
DUN_DELETE_ON_QUIT : pointer to DialUpAddon object - this will be deleted when the preflet quits
		(you should register all your addons here, too)


--------------------------------------------------------------------------------------
Additional data in the BMessage object for add-ons:
--------------------------------------------------------------------------------------
DUN_MESSENGER : BMessenger - This messenger can be used to send messages to the preflet
DUN_TAB_VIEW_RECT : BRect - This rect should be used for tabs
DUN_DEVICE_VIEW_WIDTH : float - Maximum width a device add-on's view may have