How do you keep your notes/additional instructions together with the original? Now you have two problems, your instructions and the original can be updated independently. What happens when the original is updated, or a new version of the software is released?

Wouldn’t it be great if you could fork the webpage and update it (or even submit a pull request to the maintainer)?

Is there any practical way of working this way – or will I be stuck with a notetaker / blog / bunch of outdated textfiles?

A lot of questions – maybe one of you has the answer.

Turns out that pushing jQuery to the footer is quite easy for the common case. If all we want is a nice $.ready function that we have accessible everywhere we can explicitly define it without jQuery. Then we can pass the functions we capture to jQuery later on after it loads.

The big lesson learned is that we could avoided this whole problem if we started off with my proposed helper.

via Stop paying your jQuery tax.

After working out a few technical kinks and several botched emails, thanks to missing line breaks, we sent out a final test email to ourselves.  Unfortunately, it went out to every user 

fetchworthy notes • What Happens When You Swear At Your Users.

Right after the body tag, put a script tag with this javascript:

jQuery('body').addClass('js');

This gives you a style hook for any elements that will look different in some way when Javascript enabled, and it happens immediately.

via css – Hide jQuery Accordion while loading – Stack Overflow.

Actually, control over CCK fields can be gained using CCK’s own templates.

Consider the situation where your field is called field_test.

Copy content-field.tpl.php to your theme directory and copy it again for the field whose mark-up you wish to alter, naming it content-field-field_test.tpl.php in this case.

Then change the mark-up in the file and it will alter the output of that specific CCK field.

No need to touch node.tpl.php!

Adapted via greg.harvey’s answer at node.tpl.php | Drupal API.

Sign up to WMD, the somewhat unfortunate acronym chosen for Slightly Mad’s World of Mass Development platform, and you’re granted access to regularly released builds of the game, which you’re then free to pick apart in the official forums. That feedback then gets absorbed by Slightly Mad Studios, a simple loop that means that, when the game is eventually released, it’ll be as much a product of the community as it is of the studio.

via Project Cars Preview • Eurogamer.net.

Looks like an interesting development strategy, made famous by Minecraft.

via Asynchronous UIs – the future of web user interfaces.

The first step in compiling WEB code is to run TANGLE to produce unhelpful Pascal source files. Thoughtfully the TeX build system includes a translator to produce compilable C files. Although WEB was hugely influential as the progenitor of modern source code documentation it is now obsolete, and modern extensions to TeX have been written in C. This is compiled alongside the translated WEB code. It is not hard to imagine the effect this has on the readability of the codebase.

Why programming is not yet as advanced as nature in evolution.

Dumping

Exporting from pagefeedbacktool repository the /trunk/public folder and integrating that into the services repository under /trunk/public/pagefeedback:

Dump the repository including only /trunk/public as follows:

E:\Repositories\pagefeedbacktool>svnadmin dump .| svndumpfilter include --drop-empty-revs --renumber-revs trunk/public > ..\services\filtered.dump

Loading

However as pathnames are stored as part of the dump (and replacing the path with a texteditor corrupts the dump), we have to include the full path under a different parent directory:

In VisualSVN create a /trunk/public/pagefeedback/trunk/public folder structure (try without the final public if import fails) then load the dump as follows:

E:\Repositories\services>svnadmin load . --parent-dir "trunk/public/pagefeedback" < filtered.dump

The dump is successful but at the wrong path:

currently: /trunk/public/pagefeedback/trunk/public
should be: /trunk/public/pagefeedback/

Post-correction

Open two Windows Explorer windows with both paths side by side, select all the files that should be moved, then RIGHT click drag them to the destination folder and choose SVN Move versioned files here...

Commit from the repository root.

It is now safe to remove the trunk/public folders under /trunk/public/pagefeedback/

Commit again.

via Useful Coding Tools and JavaScript Libraries For Web Developers