Of course, this introduces some new limitations, but if you are reasonable with your choices, the advantages are much more than the limitations!
example: if you publish the module in a narrow position, it would not be wise to have big images like this:
As you can see, the display gets out of the module position.
Hi,
is there a reason why you do not set the follwing css-option to the sourrunding container:
[code:1]#yourwrapper {
overflow:hidden;
}[/code:1]
The display will be cut off if max width is reached, but it will at least not harm other module positions or template styling.
Tip: Include CBs foundation and you can use CBs code: $_CB_framework, $_CB_database, etc.
Making it cross platform and you won't have to develop 2 side by side.