A challenge to the Nuke Leadership.

Posted on Thursday, April 06, 2006 @ 04:38:00 UTC in Community
by Raven

spottedhog writes:  
I think it is time to move Nuke to the next level. The tremendous work of the Nuke Patch Team and security addon creators have given Nuke a stable foundation. However, I believe the foundation is not yet complete. I firmly believe the foundation needs to be complete so Nuke can distance itself from the other CMS's and move to the next level.

To that end I propose a new forum board to be created at the various Nuke Leadership websites for the purpose of setting up minimal standards and requirements for the Nuke code in themes, modules, addons, and blocks. For example, compliance to W3C HTML Transitional standards at the very least.

If/when these standards and requirements are agreed upon, then I suggest only those themes, modules, addons, and blocks that meet the proposed standards be allowed to be listed as news articles in the future or for downloading to the general public.

Please Read More....... to see my explanation and arguements.
Discussion Starting Points:

Make all code HTML Transitional compliant. nuff said...

style.css File

I think standardizing the minimal requirements or listings is needed. Each theme's style.css should have at least certain listed classes. To that end I suggest removing $bgcolor from all themes and modules and making them classes called in the style.css file. For example:

--Suggested Addition to all style.css files (colors listed for demo purposes only)

.bgc1 {background:gray} /*replaces $bgcolor1*/

.bgc2 {background:navy} /*replaces $bgcolor2*/

.bgc3 {background:red} /*replaces $bgcolor3*/

.bgc4 {background:fuschia} /*replaces $bgcolor4*/

.txtclr1 {background:black} /*replaces $textcolor1*/

.txtclr2 {background:white} /*replaces $textcolor2*/


theme.php File
Put properties in the style.css file and use the theme.php file for structure only. I have recently been thru over 300 different themes and I think each and every one fully violates this. For example: All the themes list the BODY properties in the style.css file, then in the theme.php file they list---body margin= background= cellpadding= etc. thus replacing each and every property listed in the BODY class in the style.css file. Another frequent violation is with the class="title". .title properties are listed in the style.css file, then in the themeblock area, I will see: font class="title" and then change colors, or make it bold, etc.

Modules
Let the theme determine how the data is presented/decorated. Remove the $bgcolor and let the style.css class properties take over. A common error in nearly all the modules I have recently looked at is again, with the .title property. A module will have: font class=title then they will make it bold.... Let the style.css in each theme take care of decoration.

I realize change will not come quick and easy, but if nuke is to move to the next level, a firm foundation must be in place. The Patch Team and security addon creators have poured a lot of the quality foundation. I think it is time to finish the foundation so true improvements can begin.

Let the stone throwing begin..... :-))))Note:
Note from Raven: We just did this a few months ago and it really ended up nowhere. There's too much diversity and distros and new versions, etc. The idea is good but reality makes it virtually impossible.
 
 
click Related        click Share
 
 

Re: A challenge to the Nuke Leadership. (Score: 1)
by spottedhog on Thursday, April 06, 2006 @ 11:33:04 UTC
  
(User Info | Send a Message) http://www.smf-nuke.com

Sorry to hear it did not go anywhere in the past. I expected that, but thought I would throw out for discussion what needs to be out there. This may be cold to say, but it would be nice if others would see the elephant standing in the room. oh well......

Life goes on..... ;-)

 
 

Re: A challenge to the Nuke Leadership. (Score: 1)
by CodyG on Friday, April 07, 2006 @ 13:09:29 UTC

(User Info | Send a Message)

I'm on a borrowed pc, so must keep this brief...

I totally agree with the idea of standards. Even a clear discussion of nuke standards would be great practice for all of us.

Theory will infiltrate, our conciousness will be raised and so will the education of everyone who loves their nuke. The outcome will likely be better code for everyone because of enhanced developer passion.

in my humble opinion ... Unless it's close to the perfect nuke, for everyone, a fork does not help with anything. It is a distraction from the theory, the discovery, usually the same old phpnuke problems, with a new banner.

However, I'm the first to admit that with the nuke forks I've played with in the past four years I found creativity blossoming... but until RavenNuke, of the soon to be future, all are lacking the basics.

My basics might be different than your basics and that is where everything nuke, re: community, gets even more complex. Nuke users are a diverse crowd with diverse needs ... families of nukers, like gamers, shoppers, coders bloggers, friends and whatever.

Anyways... when it comes to nuking ... looking for some enlightenment and some plan is always a fine way to start the day. Even if it doesn't happen today, nudging things forward is all good.

:)

 
 

Re: A challenge to the Nuke Leadership. (Score: 1)
by nukeevangelist on Friday, April 07, 2006 @ 15:56:56 UTC
  
(User Info | Send a Message)

hi there

great work - great project. keep on hammering like this and plz., keep usinformed

thanks
ne

 
News ©

Site Info

Last SeenLast Seen
  • NellBui955
  • nextgen
Server TrafficServer Traffic
  • Total: 481,399,029
  • Today: 3,941
Server InfoServer Info
  • Mar 19, 2024
  • 06:07 am UTC