I was going to email you about skin support a few days ago but I forgot it :p (because of G.I. Joe!!)

I think similar to the plugin support.

• Separate tab for skin checking

• Screenshot of the skin (using the skinshot.jpg / skinshot.png will suffice)

• Reading of skininfo.html will be good too

• Support for official website

• Support for linking/redirecting to the official download link - only problem is if the official download link changes like for example if its located on Google Code (personally, I prefer to keep one download area instead of sending updates to b2evo.com; to this site; to that site - altho I don't mind sending quick updates to update the direct download URL)

[/list:u]

I still don't see why info about updated skins would be needed. Can someone explain using something other than "it should be"? I mean, how often do skins ever *need* updating?

Skins often get updated when the core changes, but that's by the by.

One of the other reasons why BOPIT is so cool, apart from the fact that it was coded by buxom dwarfs that had been force fed psychedelic omelettes for 7 days before being allowed near a keyboard ... anyway, apart from that, it has an annoying habit of showing you new/available plugins that you don't have installed.

¥

sometimes skins were updated. Sometimes

Yeah true on both points. But when a generational change happens that causes skins to be upgraded it is something the user will care about when they do a core upgrade. The occasional skin that is so buggy it needs support (like my totally crappy "purple beauty" thing that Afwas kept propping up) doesn't, to my mind, validate a need for this feature.

No worries though. Life is good when you get info you don't need instead of not getting info you might need.

EdB wrote:

Life is good when you get info you don't need instead of not getting info you might need.

That reminds me, I need to add some form of filters to bopit so that it can hide info that my life *really* doesn't need ... you know, shit like "there's been an update to EdB's core" ;)

Can't please all off the people all of the time ... you can dev > null your complaints process though :D ... doesn't always go down well with the end user :P

¥

EdB wrote:

I still don't see why info about updated skins would be needed. Can someone explain using something other than "it should be"? I mean, how often do skins ever *need* updating?

Actually the skins *needs* to be updated frequently.. none of the initial releases are ever perfect for a start.. and you cant create a skin that will fit all the widgets / plugins / new features ..

Also, personman seems to be kinda busy, or maybe he just forgets to update the screenshots, and in addition, no notice or version info for the skin is given in the skin directory...So, it would be the best both for personman and the authors if they could update their skins.. I would love to have it in BOPIT, and i have pretty good ideas for 3.x, really good ones this time.

Ideally it could be sth like this

| Title | Demo | Features (desc.) | Cur. Version | Updates | Last updated on|

Screenshot

How many skins get customized by end users? Dunno, but looking at the number of questions about customizing a skin I'd say a heck of a lot.

How many plugins get customized by end users? Dunno, but looking at the number of questions about customizing a plugin I'd say very few.

So *again* what is the point of saying "I just changed the skin you probably changed to suit your tastes"?

And let's be honest: if you can't make a skin that works properly in a default installation the first time go back to the drawing board!

But hey have fun with it. If checking skins isn't an option in the next gen BOPIT then I'll either make it so or not upgrade mine. Simple yah?

EdB wrote:

How many plugins get customized by end users? Dunno, but looking at the number of questions about customizing a plugin I'd say very few

¥åßßå wrote:

... anyway, apart from that, it has an annoying habit of showing you new/available plugins that you don't have installed.

EdB wrote:

But hey have fun with it. If checking skins isn't an option in the next gen BOPIT then I'll either make it so or not upgrade mine. Simple yah?

Pretty damn sure most people don't hit the tools tab to see new plugins so adding skins isn't gonna tax cpu/bandwidth, but if you'd like an "I want to follow skins/plugins/next_bloat_idea" settings it's not a problem ;) ( obviously the default for all new settings would be true ( we need to blow the minds of the minority that visit by default ), but you'd be able to switch it off permanently ;) )

EdB wrote:

How many skins get customized by end users? Dunno, but looking at the number of questions about customizing a skin I'd say a heck of a lot.

I hear yah ;) but it's not like any bugger will visit the tools tab to see a glorious list of red-x's cos I screwed up the <img> tag to the skinshot :P

¥

I was thinking today BOPIT won't be BOPIT with skin support cuz it'll be either BOPSIT or BOSPIT. BOPSIT is both alphabetical and reflects chronological development, although you have to ignore the fact that plugin gets two letters and pretend the I is somehow something different. Like maybe it was Back Office Plugin Interface Template?

BOSPIT sounds cool unless you think it sounds like BO SPIT which probably isn't cool.

And after hack support is implemented? Back Office Plugin, Skin & Hack Interface Template?

Blame the displaced yank for the name ....

yabs > pick a great name stk
stk > BOPIT
yabs > shit, we're never gonna live that one down

¥

http://waffleson.co.uk/pastel-palace/call_plugin.php?plugin_ID=98&method=download&am_plug=am_bopit

Techno Babble II
++?????++ Out of Cheese Error. Redo From Start

Argh, I'm not able to download bopit :-(

YABBA !!! I need help ;-)

Ohhh Slamp sorry I emailed you the wrong link ... you can grab last version from http://innervisions.org.uk/media/blogs/babbles/plugins/

thanks for letting me know about the screwed links, I'll fix them soon as

¥

Thanks a lot. I installed it and upgraded 2 plugins in 2 clicks ;-)