Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Managing themes
I was not in touch with themes, just read themes on textbook.
Just an idea, not more not less:
How about to add a table txp_themes to db including all themes with pages, forms and css.
And if a theme is activated, copying all entries belonging to that theme to txp_page, txp_form and txp_css.
The themes themselfe are not included to txp-core, but using txp for the acitive one.
That should match to the requirements in textbook
Offline
Re: Managing themes
If you want to test it without erasing all your hard work, we we’ll need a automated backup system for existing pages-forms-etc.
And in that system, how do we take a small bit from a theme, another bit from another theme, and so on ?
Offline
Re: Managing themes
Are you working on a theme manager or who does?
Offline
Re: Managing themes
Look on the persistent post on this forum, and this thread. We are taking the first steps to describe it fully, so that a dev may code it.
Offline
Re: Managing themes
Opps, next time i first read and the write :)
Offline
#6 2006-02-23 21:56:20
- zem
- Developer Emeritus
- From: Melbourne, Australia
- Registered: 2004-04-08
- Posts: 2,579
Re: Managing themes
we’ll need a automated backup system for existing pages-forms-etc.
Once possibility is that we make every page/form/css belong to a theme. Including user-created stuff, not just those installed via the theme manager. Existing things go in “my site theme” or similar. The user can create a new theme at any time, and copy things from one theme to another.
Perhaps we could also make it possible to refer to things in other themes, e.g. form="othertheme.headline".
Last edited by zem (2006-02-23 21:58:10)
Alex
Offline
Re: Managing themes
Everything belong to a theme, that would work but need some careful UA work not to confuse the beginners.
The idea of refering outside the loaded theme is quite nice however :)
Offline
Re: Managing themes
I like the idea of everything belonging to a theme. And no one seems to have much of problem with that concept in Wordpress if you look at the endless numbers of kubrick sites out there.
I think it could simplify management tremendously specially if one could copy pages/forms/styles between themes or the theme as a whole to start a new variant. Seems much simpler then managing revsions or backups.
Shoving is the answer – pusher robot
Offline
Re: Managing themes
I like the idea of everything belonging to a theme also, that’s what I’ve become accustomed to in Nucleus.
In Nucleus, a skin/template combination is an XML file that is imported via the admin area. Unlike TXP, the CSS is kept on disk along with the images in a seperate /skins/ subdirectory. A skin in Nucleus is like a page in TXP and a template is a form, very similar methods to achieve a unique design.
Last edited by hcgtv (2006-02-23 23:20:12)
We Love TXP . TXP Themes . TXP Tags . TXP Planet . TXP Make
Offline
Re: Managing themes
<blockquote>zem wrote:
Once possibility is that we make every page/form/css belong to a theme. Including user-created stuff, not just those installed via the theme manager. Existing things go in “my site theme” or similar. The user can create a new theme at any time, and copy things from one theme to another.
Perhaps we could also make it possible to refer to things in other themes, e.g. form="othertheme.headline".
</blockquote>
These are both very nice ideas!
But if the sections are separated from this (as you are talking about pages, forms and css) I think it’s going to be confusing for beginners.
Last edited by Skubidu (2006-02-24 08:39:47)
Offline
#11 2006-02-24 16:13:12
- NyteOwl
- Member
- From: Nova Scotia, Canada
- Registered: 2005-09-24
- Posts: 539
Re: Managing themes
I already have a headache ;p
Obsolescence is just a lack of imagination. / 36-bits Forever! / #include <disclaimer.h>;
Offline
#12 2006-02-26 00:37:53
- zem
- Developer Emeritus
- From: Melbourne, Australia
- Registered: 2004-04-08
- Posts: 2,579
Re: Managing themes
But if the sections are separated from this (as you are talking about pages, forms and css) I think it’s going to be confusing for beginners.
Can you elaborate on this? Why is that confusing, exactly? For end users or template designers? What would the alternative be, and how would that be less confusing?
Alex
Offline