User:Madned
Can you help me out on my page Complex it looks so ugly! thanks in advanced!
has no life...again.
woo 58 already Madned 02:25, 23 June 2010 (UTC)
118, slowing down already :( Madned 22:20, 1 July 2010 (UTC)
693 yay. Madned 21:57, 16 July 2010 (UTC)
anyone else getting intermittent site interruptions? Madned 20:26, 23 September 2010 (CDT)
I just checked the server logs, for some reason the server had a massive load last night. However without massive CPU or memory use, so I think it was the storage network that went a bit crazy. It was fixed by a reboot.
49 page fill-ins til wanted pages are under 500, woohoo! :P Madned 18:03, 4 October 2010 (CDT)
Hmm most wanted pages are sectors. I think we should try to concentrate on completing all the ships first. With their weapons etc. A lot of work but once its done, its really good. After this we can try to concentrate on all the stations and sectors? - rexde500 5 october
stations are a bit tricky, and the templates aren't quite right yet. they also naturally lead into the wares. sectors are straightforward, the general page layout probably needs adjustment, but the infobox looks pretty sound. they lead naturally into the stations of course. Madned 13:16, 5 October 2010 (CDT)
yay! sub 500 wanteds. ok. that was fun. back to the grind. Madned 17:25, 6 October 2010 (CDT)
ha! sub 100 wanteds...temporarily. Madned 22:38, 11 February 2011 (CST)
yay, econ stations all stubbed out. Madned 00:52, 9 March 2011 (CST)
ah x3wiki my old friend. sorry about the neglect, but well, stuff to do now so not so much the time. all in all site looks pretty good, although spam/vandals still seem to be a problem. oh yeah, *little dance* finished stubbing out the split shipyards. Madned 02:22, 13 August 2011 (CDT)
wikimedia spam, funny and a little sad[edit]
spamming is pointless, because external links have the rel=nofollow attribute
from meta.wikimedia.org/wiki/Wiki_spam
examined one of our valid external links and it appears to be true.Madned 15:56, 23 April 2012 (CDT)
Spoiler concept[edit]
spoiler concept
use in the w3c s-chools test beds: (remove dashes)
ww-w.w3s-chools.com/CSS/css_display_visibility.asp
borrows heavily from css drop down menu concepts.
<style>
#spoil2 {visibility:hidden;}
#spoil li:hover #spoil2 {visibility:visible;}
</style
<ul id="spoil">
<li>Percoidei<br />
<span id="nav2">
test2<bR>
test3<bR>
test4
</span>
</li>
</ul><bR>
<ul id="spoil2" style="clear:left;">
<li><a href="#">Percoidei2</a>
<span id="nav2">
test3<bR>
test4<bR>
test5
</span>
</li>
</ul>
primary problem seems to be getting the style definition to operate, don't know how to definite a style block in wikimedia. neat, works without links.
the obvious conclusion of this would be a template which essentially puts the spoiler in the span nav2 tags hidden, and some sort of anchor reveal tag which would reveal it.
<style>
ul {
padding: 0;
margin: 0;
list-style: none;
}
#spoil2 {visibility:hidden;}
#spoil li:hover #spoil2 {visibility:visible;}
</style>
<ul id="spoil" style="clear:left;">
<li>Hover to Reveal Spoiler<br>
<span id="spoil2">
{{{1}}} </span>
</li>
</ul>
option 2 is to switch font and link colors to white and require users to highlight to display. Madned 15:47, 17 February 2011 (CST)
javascript trigger concept: onMouseOver="document.getElementById('spoil2').style.visibility='visible'" limited by wikimedia javascript ban.
alternatively as a class declaration:
<style>
.spoiler li {height:2em;}
.spoiler li div {visibility:hidden;}
.spoiler li:hover div {visibility:visible;}
</style>
<ul class="spoiler" style="padding: 0;margin: 0;list-style: none;clear: left;">
<li><span style="background-color:yellow;color:red;padding:0 1em 0 1em;">Hover to Reveal Spoiler</span><br>
<div>{{{1}}}</div>
</li>
</ul>
class declaration is slightly more useful as it'll work with any arrangement within the spoiler class object so a multiple array could be handled, although it's probably simpler to drop the unordered list in a template and then call repeatedly. it should be noted as defined it will reveal all div tags within the list item. also disp-lay:none/inline/block may be substituted as desired for the visibility. The difference between visibility and display is the display hides the object completely, it does not reserve space, visibility on the other hand will reserve space and merely masks the subject much like a font color, but without being able to see the text when highlighted.
class for example would work with this:
<ul class="spoiler" style="height:1em;padding: 0;margin: 0;list-style: none;clear: left;">
<li><span style="background-color:yellow;color:red;padding:0 1em 0 1em;">Hover to Reveal Spoiler</span><br>
<div>{{{1}}}</div>
<div>{{{1}}}</div>
</li>
<li style="position:relative;left:10em;"><span style="background-color:yellow;color:red;padding:0 1em 0 1em;">Hover to Reveal Spoiler</span><br>
<div>{{{1}}}</div>
</li>
<li style="position:relative;left:20em;">
<div>{{{1}}}</div>
</li>
</ul>
whereas the variant operating on ids would require each element to be appropriately id'd. also the last example
Tabbing experiment[edit]
test portions adapted from http://www.w3.org/Style/Examples/007/target.en.html#tab2
div.tabs > div:not(:target) > div {
position: absolute;
}
target...default (line 96)
div.tabs > div > div {
background: none repeat scroll 0 0 #CCCCCC;
border: 0.1em outset #BBBBBB;
bottom: 0;
left: 0;
overflow: auto;
padding: 0.3em;
right: 0;
top: 1.3em;
z-index: -2;
}
full style.
div.tabs {
min-height: 7em; /* No height: can grow if :target doesn't work */
position: relative; /* Establish a containing block */
line-height: 1; /* Easier to calculate with */
z-index: 0} /* So that we can put other things behind */
div.tabs > div {
display: inline} /* We want the buttons all on one line */
div.tabs > div > a {
color: black; /* Looks more like a button than a link */
background: #CCC; /* Active tabs are light gray */
padding: 0.2em; /* Some breathing space */
border: 0.1em outset #BBB; /* Make it look like a button */
border-bottom: 0.1em solid #CCC} /* Visually connect tab and tab body */
div.tabs > div:not(:target) > a {
border-bottom: none; /* Make the bottom border disappear */
background: #999} /* Inactive tabs are dark gray */
div.tabs > div:target > a, /* Apply to the targeted item or... */
:target #default2 > a { /* ... to the default item */
border-bottom: 0.1em solid #CCC; /* Visually connect tab and tab body */
background: #CCC} /* Active tab is light gray */
div.tabs > div > div {
background: #CCC; /* Light gray */
z-index: -2; /* Behind, because the borders overlap */
left: 0; top: 1.3em; /* The top needs some calculation... */
bottom: 0; right: 0; /* Other sides flush with containing block */
overflow: auto; /* Scroll bar if needed */
padding: 0.3em; /* Looks better */
border: 0.1em outset #BBB} /* 3D look */
div.tabs > div:not(:target) > div { /* Protect CSS1 & CSS2 browsers */
position: absolute } /* All these DIVs overlap */
div.tabs > div:target > div, :target #default2 > div {
position: absolute; /* All these DIVs overlap */
z-index: -1} /* Raise it above the others */
div.tabs :target {
outline: none}
bR>
