Thanks for the info. This means that you'd have to edit the main CSS file for this, right? This is something I'd rather not do. So, unless it's possible to add CSS code to the module template(s) code, there's no real bonus for this div method for me.

--Anne

OK, CSS classes it is then. I'll look into the Smarty templating system and the default CSS classes to generate my pages.

In retrospect I was kind of expecting some type of custom templateting API. However, this would have only added more processing time.

Thanks for the heads-up.

As ever,

--Anne

The module I'm programming has come to the point where I need to create a number of forms and tables for both the interface used by the end-user and the administrator. From what I can gather from this forum is that there are two main methods to generate tables and forms: Smarty templates and the XOOPS API.

My biggest concern is that when a user changes his or her XOOPS main template, the userinterface(s) of my module pages should change accordingly. If I use Smarty temples the wrong way this could lead to undesireable colour schemes.

What is the prefered method to generate this effect. I'm not too fussy to look into both, but the currently available documentation is scattered and fuzzy at the best of times. If someone could help me get this stuff on track I'd be delighted.

--Anne