For my next ramble:
As you know, I have a modest website. It has evolved from a simple single page that held my bookmarks (that I could access across all computers at Uni), into a kind of bloated hydra.....lots of pages and facets (a lot of which is mindless info/ramblings.....------I have to put it
somewhere 
).
Anyway, the problem was that the design was also stuck in the past (FIRMLY in the past).
We initially had HTML to play with. That kept updating and then we got given Javascript. With this came a new idea of sort of "fusing" the two functionalities into DHTML (simple way of looking at it I know)....which has evolved into XML and given us an offshoot of CSS.
On top of this, there are now many other ways to code websites, such as Flash (Ugh!), Java, PHP etc etc
...PHEW!, that's a lot of standards.
These standards continually update so you need to keep abreast of them if you want to maintain a "healthy" site.
The problem is, I taught myself HTML, got stuck with JavaScript, and recently started getting to grips with CSS (I don't use programs to do the work for me, I like hardcoding myself using textedit/bbedit). Now we have a whole LOAD of engines to use

.....I can't keep up. So whereas before we had HTML (for structure, view of layout, and with no interactivity), I now use HTML/DHTML (for structure), CSS (for how you view the layout) and JavaScript (for the odd bit of interactivity). I "ignore" the other methods as I can achieve most of what I need with merely those three

.
So there I was, stuck in the past, hardly having ventured past bog standard HTML........and I was ignoring the white elephant in the room.
You see, the structure I have been using in my site is based on an old "stuck-in-the-past" component of HTML called Frameset (or simply Frames). With the advent of all these new ideas for coding, even though HTML is still the gutrock, the single idea of Frames kind of.....well....died. Ages ago. You see, even though frames are supported, they were never a good idea in the first place. Frames break some very basic rules of how the internet should work:
- Frames focus the site on layout as opposed to structure. HTML markup is designed to be a platform-independent way to indicate the meaning of the contents so that each browser can render the document on whatever platform it is running on. Frames violate this principle as everything is designed to accomodate only browsers running on big-screen graphical displays.
- Framesets are not addressable, which means that you can't store a page as you click through. Even though you see something in the main window, the address bar is always pointing to your index.html address. Meaning that you can't isolate and bookmark individual content anymore.
- Frames are incompatible with some browsers....importantly Wii's Opera browser and also many mobile browsers (such as those on mobile phones and pda's).
- They can include content from completely unrelated sites...meaning that the content of what you see is no longer related to where you are. Also, copyright issues may be a problem (eg, if you link to an external site but remain within your own frame/address bar......does the owner of the linked site know/like the idea of it being viewed from within yours? - probably not).
- There is a BIG issue with electronic readers for partially sighted and disabled people. In short, most of them simply don't work with frames.
- They add at least one level of unnecessary complexity, both to the design of the page, and to its navigation.
- They increase apparent load time, and load time is the second most critical consideration in any site design.
I could go on and on, but suffice it to say that there were 2 main issues I didn't like....Point 1 was a problem because I didn't like scroll bars when viewing through lower res:

--->
...and Point 3 was a problem because the site was simply "broken" when viewed from the comfort of my lounge on the wii

.
So I decided to quickly re-arrange a few things during my breaks. I initially wanted to follow a design similar to
this in which the site looks like it's on a "page" with a toolbar at the top.
However, the CSS needed was very complex, so even though it functioned OK, it looked like it was all over the place, with background graphics not working properly.
There are other methods you can use like PHP or Flash, but I'm not well versed in those methods.
THEN I stumbled upon a JavaScript way of doing it. Before I go any further, let me just confess that I'm good at coding HTML, OKish at CSS, but utterly crap at JavaScript (and completely non-existant at the others).
So this code wasn't made by me, it is freely available and has been updated from
EchoEcho.
This is what I've ended up with:

--->
The big advantage of this is that not only have I gotten rid of the dread Frames (
finally - I can now browse the site on my Treo as well as my Wii), but I have optimised everything to display correctly on any screen res from 800x600 all the way up to uber massive Apple Display 2560 x 1600

.
If you also want to use this utility from EchoEcho on your site, remember that the following line in your html document will break the code: <!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
Instead, just use this: <!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN"> (ie, chop out the http://www.w3.org/TR/REC-html40/loose.dtd and you'll be good to go).
I still have things to "sharpen up" a bit which I'll slowly do when I get more time (not now). Firstly, I'd still like to go to the macRabbit style layout as linked above. I like the look of the site appearing to be on a "page" within the window. This would have the benefit of the site actually appearing nigh on identical regardless of screen res (only the outside "grey" area would increase in size with higher res's, whereas at the moment my site "re-sizes'/"re-wraps" dependant on size of browser). It's also a look that more and more sites are migrating to:
MyCheats,
1up,
dejal,
FileJuicer, etc etc.
I also have some code to clean up as is. For instance, rather than repeat the same code over and over identically across all your pages, you can store the code as an external file and then simply call on it to load as the page does. For instance, if you have some JavaScript doing something in odd pages here and there, simply save it in plain text as a whateveritscalled.js file (change the .txt to .js by renaming) in, for example, the root of your directory. Now, if a page needs that script, rather than type it out fully, type this instead:
<script type="text/javascript" language="javascript" src="whateveritscalled.js"></script>
Now the page will simply load the info from the external page.
However, I tried this with both floating toolbar scripts but it didn't work. It would also mean that I could simply alter 2 files and as a result change the appearance of the toolbar in
all of my pages in one fell swoop......but for some reason it won't work (it works with my pop-ups, so I'm confused). Maybe someone with more coding experience could help me here?

Until then, I think I've improved enough for now......
EDIT: Thanx Red Daze (Sorry, I just missed your comment
)......Oh, and with the batteries, it's worth noting that non-rechargeable AA's give 1.5v each, but NiMh ones actually only output 1.2v each. However, they give this slightly lower voltage for longer (a bit like "tortoise and hare" - slightly lower v (and the unit might then require slightly more I to compensate) but more longevity). So your 'motes might quickly go from 4 to 3 lights, but they'll stay at 3 for much longer (the wiimotes are now getting 2.4v rather than 3v, but are also drawing slightly more current to get the same power - and for a longer period).