RSS 2.0
Browse posts:
Unanswered |
Mark all read
RSS 2.0
Browse posts:
Unanswered |
Mark all read
|
|||||
| Author | Message | ||||
|---|---|---|---|---|---|
|
matt_t_hat Nucleus Geek  Joined: 21 Aug 2005 Posts: 1124 Location: UK |
Posted: Mon Jul 18, 2011 2:17 pm Post subject: Skin inspection variables
I really will shut up and go and do something else in a moment but I wanted to put on the table one last idea. It would be truly helpful (I think) if skins could pass information to plugins. I know this sounds odd so let me explain with an example: Let us imagine a new skin called "SuperWebSite 6.2". This skin has optional support for 37 different plugins (just plug them in and the if-installed if blocks do the rest. However there is no way of the skin saying "I support x, y and z". Likewise SuperWebSite supports the new fangled skin concept of named zones which do amazing and sexy things allowing plugin output without skin editing. SuperWebSite 6.2 can not let you know which zones it supports and so the zones plugins have to hit and hope. Let us imagine another skin called "ExtraGeeky". This is the 3rd version of ExtraGeeky but the author didn't want to give each version a new name ExtraGeeky now has no way of saying "This is the 23/09/2010 release; version number 3". Likewise it can not point out that it is CSS3 compliant, HTML5 ready and table free. In all of these cases it would be good if the skin could pass data back for display but also for plugins. I actually have a practical application idea that could use this (the example of zones was not entirely random). I have been thinking about skins and how there are packaged and I have realised that we already have an XML file with all the importable skin parts in it. It should be possible to extend the definition of said file to pass information from skin to plugin etc. Admittedly to start with this is going to be limited to listing plguins supported, version number, release date, author, author site, license, etc. However this "meta" data could and should be available and I think it will stimulate exciting new ideas. Of course this will mostly be down to the skin edit/export/import section allowing the addition of lists and other fields of information to be edited and exported with the skin backup and imported in like manor. I do not see this breaking any current compatibility but enabling new information and features to be listed. How do you feel about this idea? _________________ Host Plugins | Blog | Hundred Quid A Day | My Big Fat Arse |
||||
  
|
|||||
|
ftruscot Nucleus Guru  Joined: 22 Feb 2006 Posts: 7449 Location: Massachusetts |
Posted: Mon Jul 18, 2011 4:29 pm Post subject:
Nice idea. It would be additional static info added to skinbackup.xml that would need to be stored. Would be a nice project for someone with some time. _________________ Is your question not solved yet? Search our FAQ, read the Documentation, or browse the list of available plugins. Check out my plugins |
||||
|
|
|||||
|
ftruscot Nucleus Guru Joined: 22 Feb 2006 Posts: 7449 Location: Massachusetts |
Posted: Mon Jul 18, 2011 4:30 pm Post subject:
While you're around, matt, I would be interested in hearing your experience with NP_SpamSlower on your busier sites. _________________ Is your question not solved yet? Search our FAQ, read the Documentation, or browse the list of available plugins. Check out my plugins |
||||
|
|
|||||
|
matt_t_hat Nucleus Geek Joined: 21 Aug 2005 Posts: 1124 Location: UK |
Posted: Mon Jul 18, 2011 4:39 pm Post subject:
I want it quite badly so I'd be willing to try and find some time soonish... I hope. Don't let that stop someone else getting in there in the mean time
(Also I was sure that Thanet Star had it installed but apparently not, I can't think why though). _________________ Host Plugins | Blog | Hundred Quid A Day | My Big Fat Arse |
||||
|
|
|||||
|
ftruscot Nucleus Guru Joined: 22 Feb 2006 Posts: 7449 Location: Massachusetts |
Posted: Mon Jul 18, 2011 4:44 pm Post subject:
Maybe we can discuss the SpamSlower on its own thread. I'm just really interested in how it performs on a busy site. I'm not running anything that gets a lot of comments but it seems to be useful in low-volume. I think the extra skin data will be all yours whenever you can get to it. _________________ Is your question not solved yet? Search our FAQ, read the Documentation, or browse the list of available plugins. Check out my plugins |
||||
|
|
|||||
|
|
|||||
|
|
|||||
|
All times are GMT + 1 Hour
You cannot post new topics in this forum |
|||||