Latest entries tagged in JS

In concordance with the new norm, weeks and weeks have once again passed before I have uttered anything substantial on the intarblag. I had grown used to the infrequency in the presence of internet and all its wonders, but while stuck in the cycle of broadband bureaucracy waiting once again to get that sweet injection, there is too much monotony. My life has been in a constant alternation between coding and trackmania, with only the novelty of new headphones and soundcard to dull the perpetually recurring thoughts. That sounds worse than it is. Coming from the old wreck of a computer in Norway TM actually feels amazing. I’ve got a new chair (Thorbjørn from IKEA) and a desk (black) enabling that deliciously ergonomic south parkian gaming style seen by the antagonist in the WoW episode; leaned back and with outstretched arms. But what mostly has kept my spirits up throughout this ludicrous stone age scenario has been my website project. 300 lines of javascript is a good weekend [linkview.js]. I tell you, if you program, always keep a copy of your API documentation in pdf form - or what you are more likely to find, a copy of the API documentation slightly rewritten by some whack pretending to be original and charges 30 pounds for it - it will save your life.

At any rate, I have been speedrunning TM platform and accumulating a good thousand last.fm stats on Machinae Supremacy whilst doing so. This is what takes its toll. My mind firstly conjured up this elaborate scenario with me in the car, then this even more disturbing serious e-sport scenario where I was the star. That marked the time to stop.

By that time I had 1/3 of all the world records on Platform. Now, weeks later, continuing this interrupted stream of consciousness, I find myself offline again. Presumably only for a few hours this time, but in the presence of Murphy I cannot be certain.

! After another few months, somehow, incomprehensibly, I find this document on my disk. Yes. This post, in some sense, took three months to write. Better break the cycle now.

tldr: virgin sucks and this post summarizing what i am playing in the downtimes would not have existed if they did not suck.

Having written the majority of a website in javascript with a decent framework, one learns how much more efficient it really is than to write in php.

Here is a line from my comment voting system. It basically consists of three arrow links (a.c_up, a.c_dn, a.c_na in css notation) that dont go anywhere but onclick are intercepted by js that fetches out the value of what you clicked (easy), and additionally the value of your old vote if you had voted (hard).

var oldvote = (ele = $('c_'+cid).down('a.voted')) ? {'c_up':1,'c_dn':-1,'c_na':0}[ ele.removeClassName('voted').classNames() ] : 0;

So basically, if there is an a element down from the comment with your comment id that has classname voted, call that element ele, remove its active status (classname voted), find its remaining classname (i.e. figure out which arrow it is) then convert that classname to a number via the json array in curly brackets. If no such element exists, your oldvote is 0.

prototype is awesome, feel free to share yours

There's a yellow color that the google toolbar used to fill in to all your autocompleted text fields. This can be fixed by adding a '!important' to the backgroundcolor property in your css. The problem does carry over to the Chrome browser however, and there the browser's inherent css actually override whatever you put in your css. I have seen scripts for resetting the backgroundcolor manually on loading, but prototype's neutral setStyle feature won't override it.The only thing that will work is actually pressing on the text fields.

With that in mind, this will work for hidden fields - which incidentally is all i need to fix it for my site.

$('loginbox').show();
$$('input').invoke('focus'); 
$('loginbox').hide();

Run that chunk before fading in your loginbox.
Note, this seems to fuck up when combined with scrolling. Or something, in the end I ended up not using it hoping that Chrome would eventually remove this browser css.

Some nifty little thing that was surprisingly easy to whip up in prototype for the purpose of initially hiding the delete and edit controls in the comments section, but making them pop up if the comment <li> is hovered.

$$('li.cmnt b.controls').invoke('hide');
$$('li.cmnt').each(function(e) {
 id = e.readAttribute('id');
 e.writeAttribute("onmouseover","$('"+id+"').down('b.controls').show();");
 e.writeAttribute("onmouseout","$('"+id+"').down('b.controls').hide();");
});

I like the idea of making the user use some of their power to generate the document, even though you shouldn't rely on that I guess. Prototype is an awesome tools for these kinds of manipulations though.