There are 2 xpi files, both based on version 0.9.0.04.
http://downloads.mozdev.org/googlebar/customizerKit-original.xpi
http://downloads.mozdev.org/googlebar/customizerKit-enabled.xpi

The original, is the 0.9.0.04 version. (duh)
The 'enabled' has the changes to get you started.
Please excuse the blatant copy of the mouse icon, to the
file 'sample.png' icon.

You can get to them with a cut and paste in the url bar for now.
The rest is not obsolete per se, but a little different than current.


Have fun,
The Googlebar Team



Here is the unmangled original version by Robert:
*************************************************


Pete,

There is a simple way to make this happen, I do the same thing myself
for having multiple versions of the toolbar at home vs. work. It's all
about overlays, which are such an amazing thing - very useful.

I will attempt to specify all the steps that need to be done to do this,
but it may not come across all that clearly in such a limited amount of
text - but I'll do my best. If you have questions you can always send a
message to the mailing list and I can respond to questions that way.

Since you have already customized the toolbar for yourself, I'm sure
you'll easily be able to do this for yourself. Here is what you need to
do:

1. Take all your images and put them into the skin/ directory.


2. Create the following 4 files (under googlebar):
- skin/extras.css
- locale/en-US/googlebar/googlebarExtras.dtd
- content/googlebarExtrasOverlay.js
- content/googlebarExtrasOverlay.xul


3. Now you add your customizations to those 4 files
- stylesheet (image/layout) changes in extras.css
- button labels / tooltips in googlebarExtras.dtd
- javascript functions in googlebarExtrasOverlay.js
- xul elements (buttons, menuitems, etc.) in googlebarExtrasOverlay.xul

Note for .js file: Be careful when putting functions in the js file. If
you have a function that has the same name as one if the
googlebarOverlay.js file then you will override that function and the
toolbar will probably behave irradically. I would recommend starting all
function names with googlebarExtras, unless of course you WANT to
override the default functionality. Also, because of how this is done
(as you'll soon see) you will have access to all googlebarOverlay.js
functions in the extras file if you need to call them.

Note for .xul file: The overlay works by putting your extras elements on
top of the default googlebar. Where your items go depend on 2 things,
the name of the item and the value of the insertbefore attribute. For
example, to add a button to the toolbar (in front of the special
searches button) and be able to hide it using the context menu, you
would use something like this:

<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE window SYSTEM "chrome://googlebar/locale/googlebarExtras.dtd" >


<overlay xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul">

<popup id="Googlebar-contextmenu">
<menuitem id="myButtonMenuitem"
type="checkbox"
googlebaritem="myButton"
label="My Button"
oncommand="googlebarHideItem(event)"
checked="true"
persist="checked"/>
</popup>

<hbox id="googlebar-buttons">
<toolbarbutton
class="button-all"
id="myButton"
container="true"
tooltiptext="My Button"
persist="hidden"
hidden="false"
insertbefore="Spec-menu"/>
</hbox>

<hbox id="googlebar-buttons-labeled">
<toolbarbutton
class="button-all"
id="myButton-labeled"
container="true"
tooltiptext="My Button"
label="Mine"
persist="hidden"
hidden="false"
insertbefore="Spec-menu-labeled"/>
</hbox>

</overlay>

Notice the inclusion of the .dtd file at the top of this file. This is
where your labels come from for your custom items - the rest of the
files get included elsewhere (next step).


4. Lastly all you have to do is edit the googlebarOverlay.xul file so
that it knows to include your files. The other steps only need to be
done once, this step will need to be done every time because the changes
you make to this file will be overwritten when you install a new version
of the toolbar. However, it's only 3 lines of changes so it's no big
deal.

4a. Change this (towards top of file):

<?xml-stylesheet href="chrome://googlebar/skin/default.css" type="text/css"?>

to this:

<?xml-stylesheet href="chrome://googlebar/skin/default.css" type="text/css"?>
<?xml-stylesheet href="chrome://googlebar/skin/extras.css" type="text/css"?>

4b. Change this (towards top of file):

<?xul-overlay href="chrome://googlebar/content/googlebarPopupOverlay.xul"?>

to this:

<?xul-overlay href="chrome://googlebar/content/googlebarExtrasOverlay.xul"?>
<?xul-overlay href="chrome://googlebar/content/googlebarPopupOverlay.xul"?>

4c. Change this (a little further down into the file):

<script type="application/x-javascript" src="googlebarOverlay.js"/>

to this:

<script type="application/x-javascript" src="googlebarOverlay.js"/>
<script type="application/x-javascript" src="googlebarExtrasOverlay.js"/>


5. That's it, you're done. Start up Mozilla and you should see your
additions to the toolbar.


Bottom line is that once you get your "extras" files created and your
graphics, all you have to do is add those 3 lines (in the correct place)
to the googlebarOverlay.xul file when you update to a new version and
you're ready to have all your changes incorporated into the new version.

I know this was a lot of information, hopefully the feedback engine can
handle it, along with all the xml. If not, I'll put it all in an email
and post it to the mailing list / newsgroup for others to see.

Good luck.

-Robert

[182] Submitted by: Robert Fernandes Wednesday June 11th 2003

Obviously there were a couple of details with that piece of feedback.
First of all you'll have to replace all of the &lt; with the '<' character.
Second, in the example xul file the URL for the xmlns attribute has been
stripped out by the filter. It is the same URL that is used most
everywhere throughout mozilla. I'll put a purposed messed up version
here - put puncuation in the appropriate place or just copy it from
another xul file...

http // www.mozilla.org / keymaster / gatekeeper / there.is.only.xul