Template talk:Screencap

Protecting Templates

:~( -Derik 22:15, 11 May 2009 (EDT)

It had been beaten with the ugly stick, left in the ugly swamp to rot for a few years and then entered into the "Miss Ugly Message Box Template 2009", where it was of such exceeding ugliness that the judges' intestines ripped themselves from their torso and strangled the poor buggers to death, lest they be exposed to the sheer ugliness any more.

And even over and above that, it was hard to read and bore no resemblance to any other template on the wiki. Copyright templates should be clear enough to read from the other side of the room.

[And sandboxing on a live template is HORRENDOUS form.] - SanityOrMadness 22:30, 11 May 2009 (EDT)

Well, yes that is all true... Still! -Derik 23:09, 11 May 2009 (EDT)

If I were to suggest a standard style for copyright templates, I might suggest a box akin to those on the Main Page, but with the colored strip being vertically oriented and on the left side. Said strip would only contain a single character in white text: "©" --Rosicrucian^Talk 22:38, 11 May 2009 (EDT)

Are you suggesting redoing ALL the templates on the wiki in such a form? Right now, the © templates are broadly in line with {{messagebox}} and its' kin.

*notes in horror that {{messagebox}} isn't locked*

You do realise that someone (and you know who I mean) would be able to deface thousands of pages by editing it? And that they'd stand a good chance of crashing the wiki just by editing it? - SanityOrMadness 22:49, 11 May 2009 (EDT)

*Whistles.* --Rosicrucian^Talk 22:52, 11 May 2009 (EDT)

Also {{!}} and {{Offsetep}}.

And I would fully-protect, not semi-protect. There's no reason for these templates to be edited willy-nilly, given the sheer number of pages they're used on - SanityOrMadness 22:59, 11 May 2009 (EDT)

There are non-sysop editors who I still count as very useful template builders.--Rosicrucian^Talk 23:03, 11 May 2009 (EDT)

Such as myself.

(If you were wondering what whatsisname's antics aren't keyword-blocked... this is why. We'd much rather deal with easily-reverted toomfoolery than have that person frustrated and hunting around for other things to break.) -Derik 23:09, 11 May 2009 (EDT)

Build in a sandbox, and get a sysop to move it when it's finalised and agreed though. Anything which could break the wiki shouldn't be freely editable, since malicious intent isn't required for things to go wrong. - SanityOrMadness 23:13, 11 May 2009 (EDT)

That's fine for standard templates, but complicated recursive templates don't just 'move' like that.

...wait, was that directed at me? I broke the wiki once.

Maybe twice. -Derik 23:24, 11 May 2009 (EDT)

Hrm. Is there any way we can create a custom group of "Template Editors" and set the protect privileges to that? (I forget how that all works in wiki terms precisely.) Because I can see Sanity's point. --Jeysie 01:45, 12 May 2009 (EDT)

There is a way, apparently: http://www.mediawiki.org/wiki/Manual:$wgNamespaceProtection --Jeysie 06:33, 12 May 2009 (EDT)

Since we got derailed.

"Are you suggesting redoing ALL the templates on the wiki in such a form? Right now, the © templates are broadly in line with {{messagebox}} and its' kin."

I am at the least suggesting something visually distinct which will point out that all the copyright tags are indeed copyright tags.--Rosicrucian^Talk 23:19, 11 May 2009 (EDT)

This? -Derik 23:42, 11 May 2009 (EDT)

Hmm. I can dig it. I dunno if the copyright symbol needs to repeat, though.--Rosicrucian^Talk 23:44, 11 May 2009 (EDT)

	Image Templates
<charinsert>{{hastak}}</charinsert> <charinsert>{{comicinterior}}</charinsert> <charinsert>{{comiccover}}</charinsert> <charinsert>{{screencap}}</charinsert> <charinsert>{{MarvelUScover}}</charinsert> <charinsert>{{HMcover}}</charinsert> <charinsert>{{MarvelG2cover}}</charinsert>

To include a file in a page, use a link in the form [[File:File.jpg]], [[File:File.png|alt text]] or [[Media:File.ogg]] for directly linking to the file.

	Image Templates
<charinsert>{{hastak}}</charinsert> <charinsert>{{comicinterior}}</charinsert> <charinsert>{{comiccover}}</charinsert> <charinsert>{{screencap}}</charinsert> <charinsert>{{MarvelUScover}}</charinsert> <charinsert>{{HMcover}}</charinsert> <charinsert>{{MarvelG2cover}}</charinsert>

To include a file in a page, use a link in the form [[File:File.jpg]], [[File:File.png|alt text]] or [[Media:File.ogg]] for directly linking to the file.

	Image Templates
<charinsert>{{hastak}}</charinsert> <charinsert>{{comicinterior}}</charinsert> <charinsert>{{comiccover}}</charinsert> <charinsert>{{screencap}}</charinsert> <charinsert>{{MarvelUScover}}</charinsert> <charinsert>{{HMcover}}</charinsert> <charinsert>{{MarvelG2cover}}</charinsert>

To include a file in a page, use a link in the form [[File:File.jpg]], [[File:File.png|alt text]] or [[Media:File.ogg]] for directly linking to the file.

-Derik 00:33, 12 May 2009 (EDT)

Verra nice. Calls attention to it, but is otherwise not too godawful.--Rosicrucian^Talk 00:37, 12 May 2009 (EDT)

You were right about only one ©. Too overpowering otherwise. -Derik 01:06, 12 May 2009 (EDT)

Whadyathink of that bird-dog? -Derik 01:18, 12 May 2009 (EDT)

Even better. I might add an extra space after the colon so it's more visible, but otherwise fab.--Rosicrucian^Talk 01:19, 12 May 2009 (EDT)

And now, pretty much perfect.--Rosicrucian^Talk 01:31, 12 May 2009 (EDT)

That's great! I prefer the blue one, red would seem to be some kind of warning signal. --TX55^TALK 04:47, 12 May 2009 (EDT)

Side note: If we are in fact going to edit the upload page itself, I would add the second paragraph here to that and have this be just the copyright notice. Otherwise, I think it looks spiffilicious. --Jeysie 01:37, 12 May 2009 (EDT)

The nag paragraph there was recently expanded by SanMad. It used to just say to provide the source and owner. In either case, it disappears when source and owner are properly attributed. I jiggered it to do that awhile back.--Rosicrucian^Talk 01:39, 12 May 2009 (EDT)

Ah, OK. I'd just noticed it here and there on the wiki, and it looks... odd when you're coming across it during normal browsing. (I fix them sometimes, but most of the time I have no real clue where the images are from.) --Jeysie 01:45, 12 May 2009 (EDT)

I wish you could preview upload pages for code like this. Unfortunately the software doesn't seem geared for it. (Which kinda makes sense-- you're uploading a file at the same time... you only do that once, unlike page previews. It still irks ms.) -Derik 03:06, 12 May 2009 (EDT)

Not sure if this will work with our version of MediaWiki, but it might be worth investigating (and BTW those copyright notice boxes you have there are excellent!) --abates 03:17, 12 May 2009 (EDT)

Color-coding

For the time being, I've implemented Derik's sandbox, with the color coding being a visual way of showing you used the nice, specific version of the copyright template rather than a generic. All the generics are grey, all the series-specific ones are colored.--Rosicrucian^Talk 14:11, 12 May 2009 (EDT)

Been offline most of the day, and when I have been online, the wiki's been down (it's going up and down right now staying down up again for now, but I'm leaving the timestamp I wrote the post on it/not editing, so I'm going to keep this short). Problems:

1. Too little whitespace at the top between "copyright info" and the actual text. It looks wrong.
2. I would prefer not to use red or red-based colours for stuff done "right"
3. I would also prefer to have a (very light, but) non-white/grey colour for the actual background, like the blue from before.
4. I have a real problem using the AllSpark tattooes on templates about "fair use" - in what way is that required? It sets completely the wrong example.

- SanityOrMadness 23:25 UTC, 12 May 2009

Er, it's reusing a layout element our skin has in the sidebar, as well as being a prominent part of our main page. The source of it isn't even something swiped from official media. It's a fan-created pattern to mimic the cube. The colors used are easily changed. The idea here is to create a "family" of tags that are immediately recognizable as copyright info, and which share a standard form across the board. That's why Derik and I have also been fiddling with the official source tag to match, since it serves the same purpose.--Rosicrucian^Talk 20:45, 12 May 2009 (EDT)