Theming for the future

registered · Posted: Sat Feb 07, 2009 10:27 am

There are translations for German, Italian, Russian, Spanish and Turkish as far as I know. The downloads for the languages are on the site there.

http://www.spidean.com/index.php?name=Downloads&req=viewsdownload&sid=35

Posted: Sat Feb 07, 2009 10:36 am

Thanks ! There is indeed a German file from 2004.

Site Admin/Owner Joined: Aug 27, 2002 Posts: 17088

Mars wrote:

The author Shawn also just patched it to support RN 2.3 as well.

I was not aware of this! Shawn and I had embarked down that path at the end of 2007 and I was sending him code alterations as I found it. But truthfully, I don't remember why it all stopped. Probably too busy or my health. In any event, I will d/l the latest and start testing it again as soon as we get v2.30.01 released. Somehow I think you (Mars) might have yielded a bit of influence with him Wink

. Regardless, this is really good news!

Posted: Sat Feb 07, 2009 7:51 pm

I do what I can. Wink

I also promote RN and recommend it every chance I get. Smile

Theme Guru Joined: Jan 11, 2006 Posts: 170

Raven Wrote: papamike: This is an open forum and anyone can throw in their opinion

I don't have alot of experience with forums and I don't want to post in the wrong areas. But, I do believe Raven invited me to add my opinion in a PM. I'll try to hang in with the conversation. I am a Network Engineer (retired) and never used a forum until I retired, and then it seems I have a bad habit of making people upset with me. Smile

Posted: Sat Feb 07, 2009 9:38 pm

PapaMike wrote:

... and then it seems I have a bad habit of making people upset with me. Smile

Welcome to the club!!

Posted: Sun Feb 08, 2009 6:18 am

Yep, I'm in the exclusive Club too Smile

registered · Posted: Sun Feb 08, 2009 10:34 am

Wish I could retire. I hate you all. Laughing

Anyways, excellent discussion. Couldn't read it all in detail, but just wanted to throw my 2-cents worth in.

When I was on the development team, one of the things I always struggled with is how to leverage the great wealth of add-ons, themes, hacks, etc. while at the same time move RN to where Raven wants to take it... break away from the *nuke core. Although I don't have any answers, it seems that blocks, modules and themes are the key add-ons where maintaining compatibility, adds value to RN (IMO).

So, what I was pondering over time if is there was a way to write a "compatibility layer" between old *nuke and the future RN? It should be a separate download and would have to be GPL2. If "future RN" were to adopt a different license (as has been mentioned from time-to-time over the years), this could even help enable that.

What I was thinking is that as a key core component, such as theme management, is undertaken, as the final new design takes shape, ALL core RN provided modules, blocks, etc. should be retrofitted to use the NEW core design. But, hooks be in place to also allow a compatibility plug-in to be, well, um, "plugged in", to the core and many of the older stuff still work.

Not sure how to do that because I haven't given it much thought, but it sure would keep RN "relevant" even from a *nuke standpoint and give it just that much more of a boost as it evolves. Another issue with it, is that it could, IMO, require that the overall end-state design be decided up front so that each core component could have a clear migration path. But, that takes a ton of work up-front.

Don't know. Just thoughts off the top of my head.

registered · Site Admin Joined: Jun 04, 2004 Posts: 6437

Thanks, Rob. I was having montego-withdrawal!

Posted: Sun Feb 08, 2009 7:39 pm

The opening still reads hiatus Wink

registered · Posted: Sat Mar 21, 2009 8:07 am

I wonder if the fckeditor could be used to edit the css of the themes? There is a plugin to add css editor to fckeditor. Hmmmmm?

Posted: Sun Jul 19, 2009 3:53 am

Here's my 2 cents that i think should solve the implementing of a new template system or for recoded modules design.

And the good part is... it is already builded in.
What to do:

Lets take the module Downloads .. make it tableless and let it use it's own css , so not code the css for it inside style.css but make it downloads.css .
to give other users compability , let them take theire OLD downloads module and simple let them copy it to the themes/ directory.
Voila

Code:

 $ThemeSel = get_theme();


         if(file_exists('themes/'.$ThemeSel.'/modules/'.$name.'/'.$file.'.php')) {


            $modpath = 'themes/'.$ThemeSel.'/';


         } else {


            $modpath = '';


         }


         $modpath .= 'modules/'.$name.'/'.$file.'.php';

This is already done for the forums and i think this is forgotten by everyone in this dicussion.

Another thing is flexebility for positioning blocks and blocks per module control.
Personaly i think (php-nuke)raven's cms should be able to use a block just for a particular module.
For that it excist blocks manager.

I'm proud that i was able to create a theme that has the flexebility for blocks i just described.By do a little code adding to:
-mainfile.php
-admin/modules/blocks.php
-header.php
-footer.php

+ it has old theme compability.
when i was running nukecss site , i announced i would go make such theme controller.NOT A THEME CREATOR as pappa mike made(if i readed correctly) or autotheme does.

However the final conclusion for me is that inside the core code and it's modules is that these shouldnt have any design aspects in it.