[eluser]BenneX[/eluser]
Hm.. there could be an own Controller in every Module who allows to define which css-classes to use.
I mean:
There should be a Theme with clear Styling-Guidlines to allow the Module-Developer to use the standard-classes for styling his output. So the Modules would work with every Theme which follows these Guidelines. If the Module needs his own classes, they should be stored in a own css-file within the module-folder, for easy installing purposes. And here it should be possible, to assign Style-Changes very easy, over an special Module-Controller, which allow to overwrite the css-styles of the Module over the ACP with a easy to use GUI.
But I think, if the Guidelines of the theme are well thoughted, the module won't need any style-changes, and should work with every Theme which follows the guidelines. If not, the developer of the theme have to solve this problem by his own.
For that Idea, it's only required to seperate the "layouting" and the "theming/coloring" to allow the same layout with other colors and the same colors with an other layout. Then, if the Module-Author uses the given color-classes, the theming issue would be solved ^^
Okay, enough about this topic. Now I come to my main-question.
As I told you some posts above this one, I like pyroCMS very much but doesn't match with all my requirements. But... if I change everything I need to, it would be impossible to update pyroCMS... So I wanted to ask, if I could help you by developing pyroCMS, to make it even better
Well, I'll be glad to help you with this Project, Phil. But there are some little problems. Especially my english isn't as well as it should be, so I hope my posts are understandable. And I don't have much expirience with international team-coding over the www... But maybe you can tell me more about this topic ^^
Hmm, know I'm going to wait for your answer. maybe you don't need my help or haven't enough time to manage it...
