XHTML theme Dream City ported to Serendipity
-
- Regular
- Posts: 1331
- Joined: Sun Dec 04, 2005 5:43 pm
- Location: Andalucia, Spain
- Contact:
XHTML theme Dream City ported to Serendipity
Dream City is an XHTML template from Open Designs that has now been ported to Serendipity. You can download the zipfile from my Dream City post.
-
- Regular
- Posts: 196
- Joined: Sun May 11, 2008 2:53 am
- Contact:
Wow, that was quick. I will have a look at this tonight when i get back from the office.
Thanks, Steve
Thanks, Steve
Steve is occasionally blogging here
-
- Regular
- Posts: 1331
- Joined: Sun Dec 04, 2005 5:43 pm
- Location: Andalucia, Spain
- Contact:
It doesn't take long to port a basic template, this particular theme took a little longer because it has some odd little things in it that needed to be thought about. I'm sure people who use this template will have many things they'll want to change, but I'll wait for comments before I do any more on it.
-
- Regular
- Posts: 1331
- Joined: Sun Dec 04, 2005 5:43 pm
- Location: Andalucia, Spain
- Contact:
It's all thanks to Garvin and that nifty code that lets you create extra navbars. I just named each of the three parts differently so users can still drag sidebar items to whichever part they want to use.
But now you've got me all nervous, I forgot to see what would happen if a user doesn't have any sidebars.
But now you've got me all nervous, I forgot to see what would happen if a user doesn't have any sidebars.
-
- Core Developer
- Posts: 30022
- Joined: Tue Sep 16, 2003 9:45 pm
- Location: Cologne, Germany
- Contact:
Hi!
Yay, love that theme. It looks very unique. I'm really stumbed to see you so active again, Carl. I don't even dare to thank you because I don't want to scare you off !;-)
We have long not added new themes ported by YellowLED or you to Spartacus. Might it be worth the effort to check which themes should be incoroporated there, if Carl, YellowLED and the possible other contributers agree to add their work there?
Best regards,
Garvin
Yay, love that theme. It looks very unique. I'm really stumbed to see you so active again, Carl. I don't even dare to thank you because I don't want to scare you off !;-)
We have long not added new themes ported by YellowLED or you to Spartacus. Might it be worth the effort to check which themes should be incoroporated there, if Carl, YellowLED and the possible other contributers agree to add their work there?
Best regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
-
- Regular
- Posts: 1331
- Joined: Sun Dec 04, 2005 5:43 pm
- Location: Andalucia, Spain
- Contact:
Garvin I'm working on another theme right now, Nautica05, which is also an XHTML theme. I hope to release it next week.
Spartacus really needs to be updated, after all it is where most of the users will hope to find templates. If you think any template I do is worth adding to Spartacus then please do, no need to ask.
Themes have a lot of different of options now so making a test site that let's people see the different themes working is not easy, but I wonder if we could somehow standardize some items like the navbar? At the moment if a user switches from one theme to another they lose any navbar links they've put in, and most themes only have the link and the anchor text, so it should be possible to preserve these from theme to theme. What do you think, could this be implemented somehow?
Spartacus really needs to be updated, after all it is where most of the users will hope to find templates. If you think any template I do is worth adding to Spartacus then please do, no need to ask.
Themes have a lot of different of options now so making a test site that let's people see the different themes working is not easy, but I wonder if we could somehow standardize some items like the navbar? At the moment if a user switches from one theme to another they lose any navbar links they've put in, and most themes only have the link and the anchor text, so it should be possible to preserve these from theme to theme. What do you think, could this be implemented somehow?
-
- Regular
- Posts: 196
- Joined: Sun May 11, 2008 2:53 am
- Contact:
I think making the navlinks a common property across all templates would be a killer feature. Although I tend not to switch themes regularly it is a pain to copy them to notepad, and then paste them into each new template.carl_galloway wrote:Themes have a lot of different of options now so making a test site that let's people see the different themes working is not easy, but I wonder if we could somehow standardize some items like the navbar? At the moment if a user switches from one theme to another they lose any navbar links they've put in, and most themes only have the link and the anchor text, so it should be possible to preserve these from theme to theme. What do you think, could this be implemented somehow?
Would there be any impact on the older themes ?
Steve is occasionally blogging here
I agree, and I'd be happy to have some of my ports put on Spartacus. But I also see a need to clean it out a little.carl_galloway wrote:Spartacus really needs to be updated, after all it is where most of the users will hope to find templates. If you think any template I do is worth adding to Spartacus then please do, no need to ask.
I realize there's a need to keep old templates available, but there's also a need to keep the themes section in Spartacus tidy. Maybe we should have something like a "themes vault" or something to store all s9y templates and just keep the up-to-date ones in Spartacus ...
YL
-
- Core Developer
- Posts: 30022
- Joined: Tue Sep 16, 2003 9:45 pm
- Location: Cologne, Germany
- Contact:
Hi!
Making the options available in other templates is really hazardous.
The reason is that the options are saved in the database, associated with the name of the template they apply to. If that were changed, a template would never be able to figure out if a template option applies to itself, or to another template. Also, switching templates would maybe overwrite the options of the old template.
Plus, having different template options for different categories would no longer be possible.
Technically, a template itself could first fetch its own template options, and later query for all template options, but that would put a lot of PHP code stress to a template. Sooo...even though it's very nice from a user's standpoint, technically this is really dangerous, because it could also screw up any template that accidentaly declared the same template option name but handles values differently...
Maybe a different approach could be better, like a menu item "Import template settings from Category [XXX]", so that a user could simply import it. Technically that's just a INSERT INTO options (...) SELECT (...) FROM options where template = 'OLD'. But creating the interface to that is more work, it could be done, maybe this is a cool thing for the Judebert+Don-Supercombo?
Regards,
Garvin
Making the options available in other templates is really hazardous.
The reason is that the options are saved in the database, associated with the name of the template they apply to. If that were changed, a template would never be able to figure out if a template option applies to itself, or to another template. Also, switching templates would maybe overwrite the options of the old template.
Plus, having different template options for different categories would no longer be possible.
Technically, a template itself could first fetch its own template options, and later query for all template options, but that would put a lot of PHP code stress to a template. Sooo...even though it's very nice from a user's standpoint, technically this is really dangerous, because it could also screw up any template that accidentaly declared the same template option name but handles values differently...
Maybe a different approach could be better, like a menu item "Import template settings from Category [XXX]", so that a user could simply import it. Technically that's just a INSERT INTO options (...) SELECT (...) FROM options where template = 'OLD'. But creating the interface to that is more work, it could be done, maybe this is a cool thing for the Judebert+Don-Supercombo?
Maybe some people could volunteer and create a list of cool templates and which ones to sort out? I could commit all the necessary files, but I don't have the time nor knowledge to sort out good templates and bad ones. I like most of themI agree, and I'd be happy to have some of my ports put on Spartacus. But I also see a need to clean it out a little.
Regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
-
- Regular
- Posts: 1331
- Joined: Sun Dec 04, 2005 5:43 pm
- Location: Andalucia, Spain
- Contact:
I've always been a big fan of taking the legacy templates, updating them to work with the new config screen, and merging colorsets into a single theme. My last few themes have removed backwards compatibility and I know this is an issue for Garvin, but even so it would tidy up the older themes and remove some of the clutter.
Speaking of backwards compatibility, do we know how many users are still running versions of Serendipity pre1.1?
Speaking of backwards compatibility, do we know how many users are still running versions of Serendipity pre1.1?
-
- Regular
- Posts: 3652
- Joined: Mon Feb 13, 2006 2:40 am
- Location: Chicago, IL, USA
- Contact:
A long time ago, I proposed the idea of making navlinks a template-independent concept... since that time, however, I have come to realize that it may not be all that desireable... for a lot of reasons. Importing sounds like a nifty idea, but I would be concerned about that trying to be an apples to oranges proposition - ie, there is no guarantee that one template handles navigation the same as another.
=Don=