I have been thinking for a while about themes.

I love the idea to have a way to modify my CSS within Xoops.

An example of how this can be acomplished is here:

http://www.easterpig.com/demo/easysite/manage/edit.php

A funcionality that could "call" a css, edit some parameters (on a module or a theme).

Then every module should have a standard option to use its own css or use the actual theme or XOOPS default.

Web master could expand capabilities. One theme could have lots of variants, and each module (even each block) could select what to use.

How does it sound?

Macintosh User Guide Interface is a good example of how creating a common set of expected behaviors helped finnal users. A good example is the submit button (I have found modules with different names meaning the same thing).

Basically all this Ideas point to one point. QA must start defining those standards and probably and testing protocols. If this is done right, testing would be a piece of cake.

I agree ,with the language issue.

Ussualy english only coders understimate this fact.

QA should have a way to make translations and language in general consistent.

Is very confusing if you use two different words in separate module for the same purpose.

Something like a Bank of terms shoul be needed

dave_L
can you close this thread, plz !
marco