Archive for July, 2006

Do NOT attach “target” through script!

Friday, July 28th, 2006

Using target in (X)HTML Strict. If you need to use the target attribute, either stick with Transitional DOCTYPEs, or add the target attributes dynamically using semantic scripting, e.g. based on semantic class names.


NO NO NO NO NO! Your page is just as invalid if you add target in with script as if you put it in your markup.

If you absolutely must open a new window, make it a normal <a href=""> and use and cancel the default action for the link. But if you weren’t providing any size or chrome info (which are impossible with target anyway), then you don’t have any reason to be opening a window in the first place. Just don’t do it.

A good font package approaches…

Thursday, July 27th, 2006

The STIX Fonts have all been made, and just need to be packaged now! Wooo!

emerge chucknorris

Monday, July 17th, 2006
# emerge -Dtau world

These are the packages that would be merged, in reverse order:

Calculating world dependencies... done!
[ebuild  N    ]  games-misc/fortune-mod-chucknorris-0.1

Hard drive archival

Tuesday, July 4th, 2006

To anyone using hard drives as an archival system: Will you have an IDE motherboard in 20 years? In 100?

Perfect Sound

Saturday, July 1st, 2006
  • There is a master sound volume. Only root can change this.
  • There is a per-user sound volume. A user can only change her/his own.
  • There is a per-application sound volume. This is what applications change with their sound control. Applications do not change the per-user volume unless they are specifically for that purpose, like alsamixer. A dedicated volume control program can control application volumes, in case the application doesn’t have a control.
  • If an application wants to provide more detailed control over its sound (e.g. a music track and a sfx track) it ??. Mixes them itself, and only sends one track to the OS? Sends both, but after changing their volume, and with the same application name so the per-application control affects both? Exposes both to the OS entirely, and requests separate volume controls for them (which it then affects using its own in-app controls)?

All values are, of course, multiplied before affecting the sound. Values greater than 100% are allowed.

This does not specify how it interacts with the actual speakers (perhaps volume control on the speakers changes the master volume?).