Instructions For Enabling The Global Skin Plugins In A Skin
===========================================================

in trillian.xml, put this at the beginning (after the <trillian>)
	&pluginXML; <!-- <trillian>-level plugin code -->
and put this at the end (before the </trillian>)
	&plugin_default_XML; <!-- default code so the skin doesn't crash -->


look for <prefs> and </prefs>  (may be in trillian.xml, may be 
elsewhere)
Put this at the beginning
	&pluginprefs; <!-- <prefs>-level plugin code -->
and this at the end
	&plugin_default_prefs; <!-- default code so the skin doesn't crash -->


Finally, look for the .dtd file (usually trillian.dtd) Put this towards the 
beginning...  (replacing the names with where the skinplugins directory is
installed)  These are important as they establish to the skin where the plugins 
are related with respect to the skin.  If you have a config utility, it would be 
nice to allow the user to select what directory is put here so they can place 
the global plugins where they want.  Also, globalplugin_dtd sets up all the 
entities used in the skin, i.e. %plugin_default_dtd;, etc.  (Configurator
users, can skip this step if they have their main settings and globalplugins
enabled.  TC will insert it into the config file for you.)

<!ENTITY % PluginDir "..\SkinPlugins\" >
<!ENTITY PluginDir "..\SkinPlugins\" >
<!ENTITY % globalplugin_dtd SYSTEM "..\SkinPlugins\config_(default).dtd" > 
%globalplugin_dtd;

then put this at the end of the .dtd file (TC users still need to do this)
	%plugin_default_dtd;

Note: if you're going to allow your user to have personalized profiles, you'll 
need to make it so they can change the globalplugin_dtd filename ... i.e. in a 
config utility or something.  If you don't want them to personalize it, just use 
the (default) one.


That will enable the core code...  For things like system icons and sounds, 
this is all you need.

For other deeper hooks, you need to put in the hooks where you want 
them.  (look in the SkinPlugins\default\main.dtd file to see what hooks are 
available.... although since this isn't a completed standard yet, some things 
may be added/removed...)

i.e. for the emoticons control put:

   <control name="emoticons" type="emoticons">
      &emoticons; <!-- Main emoticons should all use this -->
      &emoticons2; <!-- personalized/non-standard emotes -->
      &emoticons3; <!-- personalized/non-standard emotes -->
      &publicEmotAvatars; <!-- Avatars -->
      &jones; <!-- Jones Soda avatars ... long story -->
   </control>


Or, for the contact list (buddy status) icons, put:

   <control name="YourContactListName" type="list">
      &PLUGstatusIcons; <!-- the icons themselves -->
      <!-- your fonts/color code here -->
      &PLUGstatus;  <!-- places to add additional code -->
      &PLUGstatus2; <!-- for when Cerulean studios makes -->
      &PLUGstatus3; <!-- future updates. 
      <!-- or for instance, contact list 'background' plugins for Pro. -->
   </control>


I may try my hand at an XML parser later to automatically put in the code, but 
I'd rather leave it to the skinners so they can choose what they put and 
where...