As mentioned in an earlier post, we want to implement a new module to 
show some pieces of information about all users, and from all of the 
users calendars. We made a new button for this in the top panel by 
manually adding it to the top.htm template, and now we have some 
architectural questions again. We see at least these two scenarios:

1. We create our own servlet that utilize the OX API-classes and any 
other classes we might need (altough I'm not yet sure what that might 
be). I'm not quite sure how to best integrate the html output with the 
rest of OX, but at least we should include the CSS-files.

2. We create a subclass of the Management class, and add it in 
/path/to/openxchange/etc/groupware/classfiles. Then we write a template 
for our module and make a folder for it in 
/path/to/openxchange/share/groupware/data/templates/EN/. We found this 
way of doing it outlined in a couple of postings on the mailing list: 
http://www.open-xchange.org/pipermail/devel/2006-March/010793.html and 
http://www.open-xchange.org/pipermail/devel/2005-October/010557.html

And then for the questions:

As we would like to be able to contribute this module back to the 
community if it turns out to work well, we want it to be easy to install 
and to fit in nicely with the rest of OX and other modules both in 
looks, deployment method, ease of upgrades, and architecture.

a) Which is the preferred, or "right" way of doing this?

b) Is there any other way which would make it cleaner and deployment 
even easier?

c) What is the criteria for something to be an "OXtender"? Is it pretty 
much anything that in any way tries to integrate with and extend OX' 
functionality, or are there any other criteria that needs to be filled?

Regards,
Roger