But with this technique you replace only the stylesheets,
it is not possible in T5 to replace the generated HTML from skin to skin
like in Wordpress because the TML and the Java-class are strongly wired
together, or?
This would be really great ^.^
Greetings, Christian
Onno Scheffers schrieb:
Skinning means you drop in a skin to some folder and everything changes
automatically. With the layout component you have to manually adjust it.
Core support means, that there is a core mechanism to find skins
automatically and be able to change the looks at runtime for example with a
listbox "Skinchanger".
Skinning isn't that hard to do actually.
We have it in our application where each organisation or user can set a
default skin. Each skin has its own sub-folder and you simply change the
path to the css-files based on the user that is logged in. That css-file can
override the default Tapestry styles if needed.
In our solution we have to distribute all available skins along with the
application, but it would be possible to store/retrieve css-files, images
and js-files from a database as well..
I'm currently cleaning up the stylesheets throughout our application and
replacing whatever I can with styles from jQuery UI CSS Framework (
http://jqueryui.com/docs/Theming/API). This means it gets much easier for
non-techies to create custom skins with the ThemeRoller (
http://jqueryui.com/themeroller/).
We do have a need for forum-functionality as well, but it is only on the
agenda for somewhere next year. So if nothing is available by then we may
have to write our own module then.
regards,
Onno
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
