User talk:Raphfrk

From ErfWiki

(Difference between revisions)
Jump to: navigation, search
(Summer Updates)
(The Main Page: new section)
Line 52: Line 52:
Based on the structure of the Summer Updates, it looks like the best framework for them would be a simplified version of the Pager template, with an image, a breadcrumb for forward-back links (with no backward link on Page 1 and no forward link on Page N, for whatever the final value of N turns out to be), and a "Book" link to its own Descriptive Table of Contents page. Am I missing anything? [[User:SteveMB|SteveMB]] 20:34, 4 June 2009 (UTC)
Based on the structure of the Summer Updates, it looks like the best framework for them would be a simplified version of the Pager template, with an image, a breadcrumb for forward-back links (with no backward link on Page 1 and no forward link on Page N, for whatever the final value of N turns out to be), and a "Book" link to its own Descriptive Table of Contents page. Am I missing anything? [[User:SteveMB|SteveMB]] 20:34, 4 June 2009 (UTC)
:I updated the [[Template:Erf|Erf]] template with another new template called [[Template:ArchiveLink|ArchiveLink]] which works just like the [[Template:TBFGK page info|TBFGK page info]] lists.  Each time a new comic archive (like the summer updates) comes out, we just toss in a new alias and the link into the template and Erf will automatically be able to reference it properly.  Words or numbers both work fine.  I've also set it up so that <nowiki>{{erf|TBFGK|2}}</nowiki> or <nowiki>{{erf|1|2}}</nowiki> will both work.  Any questions? --[[User:Ichthus|Ichthus]] ([[User talk:Ichthus|eyeBook]]) 23:34, 6 June 2009 (UTC)
:I updated the [[Template:Erf|Erf]] template with another new template called [[Template:ArchiveLink|ArchiveLink]] which works just like the [[Template:TBFGK page info|TBFGK page info]] lists.  Each time a new comic archive (like the summer updates) comes out, we just toss in a new alias and the link into the template and Erf will automatically be able to reference it properly.  Words or numbers both work fine.  I've also set it up so that <nowiki>{{erf|TBFGK|2}}</nowiki> or <nowiki>{{erf|1|2}}</nowiki> will both work.  Any questions? --[[User:Ichthus|Ichthus]] ([[User talk:Ichthus|eyeBook]]) 23:34, 6 June 2009 (UTC)
 +
 +
== The Main Page ==
 +
 +
<center>{{mainpagecontrol}}</center>
 +
I'm going to revert your changes to the main page where you added edit links the the various sections. There's a reason why I didn't include them in the original main page. It helps keep the page clean and prevents people from editing those sections on a whim. you should use the above template, [[Template:mainpagecontrol|<nowiki>{{mainpagecontrol}}</nowiki>]], to edit the main page.

Revision as of 18:15, 3 November 2009

Contents

Style Guidelines

You are very welcome to take part in discussing and formulating the Style Guidelines for Erfwiki. I believe they would benefit everyone. -- Muzzafar 07:53, 2 May 2009 (UTC)

Crop template

Cool template. I'll take a look at it, it might be a better way to do panel-by-panel than the manual cropping I use. --> ERK!|eyeBook me 13:58, 7 May 2009 (UTC)

Multibrowser is one issue; the other I see might be that it doesn't actually create a smaller image, but only hides the rest of the page. That could be good, though, for p-b-p, because it kinda preloads the next dozen panels so that the viewer can slip through them smoothly. --> ERK!|eyeBook me 14:35, 7 May 2009 (UTC)
I'm not aware of any easy way to test a template, unfortunately. The best you could do is store the template edits at, say, template:crop/test and transclude template:crop/test into User:Raphrk/Sandbox, then just copy and paste the changes to template:crop when you were done. --> ERK!|eyeBook me 15:52, 7 May 2009 (UTC)
Go ahead and change them over. The number of soft-cropped pages now greatly outnumbers the number of hard-cropped, so we may as well get consistency. Cheers! --> ERK!|eyeBook me 13:57, 14 May 2009 (UTC)
Another advantage of soft-cropping is that it allows a click-through on a frame image to the page image, which IMO is a nice intuitive way to go from frame view to page view. SteveMB 22:55, 14 May 2009 (UTC)

Paneler

Regarding Template:Paneler: Good idea, although I wince at having to redo my existing pages. Ah well. It would be wise to make the description/text sections "ifexist"s so that the headers don't appear if the fields are left blank. --> ERK!|eyeBook me 18:44, 7 May 2009 (UTC)

Ah, I see how you're doing it. That's a wicked idea, but rather than the style you're using we should switch it to, for example, TBFGK 1:1/Description to fit the standard wiki format. I'll get on that for my newly uploaded pages, though I'm almost caught up to my backlog. --> ERK!|eyeBook me 18:46, 7 May 2009 (UTC)
Whew, lots to look at. I think my paneler template takes alternate inputs, so you could use that as a base for your lister template. It just defaults to TBFGK. I could be wrong though. You could also look at my old similar template for ideas, though in many ways your lister template is better so far.
I really like what you're doing though. This modular idea is excellent. It will be very useful and flexible. --> ERK!|eyeBook me 19:27, 7 May 2009 (UTC)
PS: Oh yeah, and don't be shy about editing my templates. It's a wiki. Besides, I have backups on ewik.erku.ca --> ERK!|eyeBook me 19:28, 7 May 2009 (UTC)
Dude, you're some kinda hero. Let's do this efficiently: I have up to page 19 in single-panel images. I will upload those soon, so don't worry about doing cropwork on that. If you feel like doing grunt work you could try cropping page 20, and if not don't worry 'bout it. When I have finished cleaning up the work I've done so far I'll get on that. --> ERK!|eyeBook me 21:34, 7 May 2009 (UTC)

The {{lister}} template is cool, but it needs someway of editing the individual panels from the main comic annotation page. Also docs for it and paneller.--Doran 23:46, 7 May 2009 (UTC)

I haven't decided what to do about Klogs either. I guess just have the paneler template link straight to the Klog page as a whole... it really doesn't need a panel breakdown, unless we decide to separate the header but that seems frivolous. I can take a look at the template if you like, I remember the structure and can probably manage the klog thing without much trouble. There are some other things I need to work on anyway: presently the paneler template will break after page 40, and I have to go fix that old stopgap very soon. The two are related. --> ERK!|eyeBook me 02:53, 9 May 2009 (UTC)

Expandable Template

Is it possible to make an expandable template, rather like the spoiler boxes on the Giantitp forms? I was thinking pf uploading the full comics and hiding them behind these on the annotation pages. --Doran 23:37, 7 May 2009 (UTC)

I just tried stealing the code directly off of the Giantitp website and it won't work on the wiki. The wiki cancels out any <input> tags which means you can't get the buttons on there. There might be a way to javascript a link or something, but it's a bit above my head. Code from Giantitp is as follows:
<div class="pre-spoiler">
  <span style="float: left; padding-top: 2px;">Spoiler</span> <input value="Show" style="margin: 0px; padding: 0px; width: 80px; font-size: 10px;" onclick="if (this.parentNode.parentNode.getElementsByTagName('div')[1].getElementsByTagName('div')[0].style.display != '') { this.parentNode.parentNode.getElementsByTagName('div')[1].getElementsByTagName('div')[0].style.display = '';this.innerText = ''; this.value = 'Hide'; } else { this.parentNode.parentNode.getElementsByTagName('div')[1].getElementsByTagName('div')[0].style.display = 'none'; this.value = 'Show';}" type="button">
</div>
<div>
  <div class="spoiler" style="display: none;">{{{1}}}</div>
</div>

I put the {{{1}}} myself as that is where the spoiler text is supposed to be put. --Ichthus 10:45, 16 May 2009 (UTC)

Page Annotation

Please do not replace text in the page annotation articles with a broken template. People spent their time writing that text and keep working on this project. I am reverting the changes that you made to those pages. -- Muzzafar 20:46, 8 May 2009 (UTC)

Created a section for discussing how to integrate this stuff --Doran 21:34, 8 May 2009 (UTC)

Cookie

Oh my goodness. A cookie!. --> ERK!|eyeBook me 17:25, 9 May 2009 (UTC)

Booker

Uhm... what is the Booker template for? Just wondering. --Ichthus 08:40, 16 May 2009 (UTC)

Subpage

"Ichthus created a subpage template. It adds a link back to the panel from the /text and /description pages, but doesn't include it in the actual panel page. It would be worth adding to any new panel by panels that you create. See TBFGK_27:1/Text as an example."

Thanks for the tip; I'll include that from now on and add it into the existing subpages in my copious free time. SteveMB 17:14, 17 May 2009 (UTC)

Summer Updates

Based on the structure of the Summer Updates, it looks like the best framework for them would be a simplified version of the Pager template, with an image, a breadcrumb for forward-back links (with no backward link on Page 1 and no forward link on Page N, for whatever the final value of N turns out to be), and a "Book" link to its own Descriptive Table of Contents page. Am I missing anything? SteveMB 20:34, 4 June 2009 (UTC)

I updated the Erf template with another new template called ArchiveLink which works just like the TBFGK page info lists. Each time a new comic archive (like the summer updates) comes out, we just toss in a new alias and the link into the template and Erf will automatically be able to reference it properly. Words or numbers both work fine. I've also set it up so that {{erf|TBFGK|2}} or {{erf|1|2}} will both work. Any questions? --Ichthus (eyeBook) 23:34, 6 June 2009 (UTC)

The Main Page

ErfWiki Main Page Control Panel
{{topbox}}
This is the very top section of the main page
{{rulesbox}}
This is info for new users
{{contentbox}}
The featured content is displayed in here
{{featured article}}
This used to be the featured article, but has since
been re-purposed to be just a list of tasks.
{{Latest Update}}
Change this to reflect the latest update
{{Latest Update/page}} controls the image.
{{improvementdrive}}
Change this to change the Improvement Drive
{{Didyouknow}}
Change this to change the Did You Know section

I'm going to revert your changes to the main page where you added edit links the the various sections. There's a reason why I didn't include them in the original main page. It helps keep the page clean and prevents people from editing those sections on a whim. you should use the above template, {{mainpagecontrol}}, to edit the main page.

Go To:
Personal tools