Talk:Zlib

Just getting started, but hopefully this will serve as a good guideline for library pages. --StDoodle (#1059825) 23:18, 28 November 2010 (UTC)

Oh yeah; please chime in with any format requests / criticisms / suggestions. I'd like to nail down a standard format for such pages before adding htmlform's page and any others that may be justified. --StDoodle (#1059825) 23:20, 28 November 2010 (UTC)

Ok, here's the to-do list: 1) finish up the rest of the functions using what's there as a guide. 2) Bring in the external info (such as for eval()). 3) Proof, check format, etc. 4) Come up with a way to link to each function's section via "search"; may need to make redirects (ugh). --StDoodle (#1059825) 00:51, 29 November 2010 (UTC)

4 is really pissing me off... ideally, I'd like table of contents info & search results for each function, without adding extra headings (since they'd either look bad w/o parentheses after function names or require the parentheses in search). Ugh! Halp! --StDoodle (#1059825) 02:46, 29 November 2010 (UTC)

Looks good so far. For concern #4, I want to say redirects are probably the best way to go. Might have to add anchors physically (i.e. via HTML), then have the redirects point to the proper locations on the page. You might want to also add in the function tocs in the same manner -- you can probably use the HTML as a point of reference. --Heeheehee 04:04, 29 November 2010 (UTC)

I found a way to get hidden links working automatically with a single template, but the redirects are still needed. But since everything else is working now, I think I'm going to call that "good enough." Just precede anything you want to have a hidden anchor with the template {{HideLink|param}} where param is the link id (which must substitute underscores for spaces etc. etc.) and you're good to go. --StDoodle (#1059825) 04:20, 29 November 2010 (UTC)