Hi Ricardo I doubt it adds anything and probably complicates matters. Both the Joomla templates and WordPress themes contain .php elements. My point was to make people aware that trying to become compatible so as to be able to use WP Themes in Xwiki was likely not such a good solution. I would think a Xwiki skin/theme/template would consist of images, html, JavaScript and possibly Groovy and Velocity in the this, but that stuff needs to only be there for the display of items in your Xwiki and be able to be removed without affecting the core operation of the Xwiki. Hope this helps towards building a great solution Cheers Peter Quoting "[Ricardo Rodriguez] eBioTIC." <[email protected]>:
Hi!
Peter McLarty wrote:
Hi As someone with a level of experience there may not be such a stretch to getting to such a place. I think it isn't so much as getting the WP compatibility in the sense of them being the same. I think it is more about moving to a model whereby the content that defines the look and feel in the way a Theme in WP or a Template in Joomla are able to be a separate product from the core code. This leans that certain elements that relate to how things are displayed are done with a set of elements that are completely independent of the core. The main component of a WP them is images and css, but it can and does contain php elements. Does Xwiki want to incorporate php into its product mix for display?
Please, what does PHP add to the landscape considering XWiki is built in Java and supports Velocity Template Language and Groovy? Thanks!
I build for other projects themes for WP and templates for Joomla using a tool called Artisteer. It is a good product albeit with a share of bugs, but it allows the ability to create a single look and feel in Joomla and WP if being used within a single site. Can we get a tool like Artisteer to support the Xwiki community, possibly if it is possible to build a skin that provides the sort of model that it needs to build to when creating the skin theme. Understanding what this tool is doing might help those to understand what is going to be required for a skin to support a similar them model to WP or Joomla and allow people to make a simple mod to elements that allow the product to support Xwiki.
I would be more than happy to throw out somewhere a copy of the Artisteer output for a WP or Joomla site as a starting point of what they contain to help people understand what they need to work towards. So in this vein I think the first step is moving to a complete separation of CSS, JavaScript, images, HTML markup and anything else. that defines look and feel from the main code tree into a template/theme directory. Both WP and Joomla rely on only selecting a directory within the themes/templates location to define the look and feel. It is also possible in both cases to define individual parts of a site to use different look and feel.
HTH
Cheers
Peter
Quoting Andreas Hahn <[email protected]>:
From the xwikis operators point of view it would be a huge "selling" point if it where possible that exisiting wordpress designs could be used in a certain (may be new) xwiki skin.
The reason for this is that xwiki operators aren't necessarily good and experienced designers but there is a large crowd of designers spcialized in wordpress theme design. And its possible to start design contest e.g. 99designs.com where you can buy individual designs for small money meaining you have an individual and professional looking design at small cost.
You might say Xwiki is a wiki and wordpress is a blog but for sure there is a not so small group of usage scenarios where it is justifiable to use one or the other product. And people are tempted to go with the product with the better design options. This is even more true as if you plan a new plattform that should be individual and professional looking and you can't do a professional design yourself you have to hire a designer but with using wordpress you can pick up a design out of the many options and modify it - which is much easier than doing it along yourself.
I have no idea how complex it might be to realize such a 'design compatibility layer' though ...
Andreas
-- View this message in context: http://xwiki.475771.n2.nabble.com/VOTE-Stop-supporting-the-Albatross-skin-tp... Sent from the XWiki- Dev mailing list archive at Nabble.com. _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ricardo RodrÃguez CTO eBioTIC. Life Sciences, Data Modeling and Information Management Systems
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Peter McLarty Senior Consultant, Pacific DBMS Pty Ltd [email protected] 15 Barron Road Margate, QLD 4019 Australia work: 61 7 3883 1086 mobile: 61 4 0209 4238 fax: 61 7 3883 1016 IM: pameacs.cto (Skype) http://au.linkedin.com/in/pameacs Database Consultants across Asia Pacific ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.