Tigers and Monkeys Took Over My Room
Tigers and monkeys took over my room, Just when mommy had given me the broom, To clean up the mess all over my floor, That got so deep, she couldn’t open my door.
Elephants and giraffes got in my way, And stopped me from cleaning so I could play, I tried to say no but what could I do, When into my room marched the whole zoo.
Iguanas and eagles fought at my feet, I had work to do but they wanted to eat, So I said, “Enough, enough! Get out of my room!” “My mother will kill me if I don’t clean up soon!”
Bears and big horns knocked me flat on my butt, With all this commotion, my mom said, “What’s up!” I must be in trouble, I am certainly doomed, For the whole day has passed, and I haven’t cleaned my room.
RapidWeaver tip: How to make a sub page
It might sound like the most basic task but I get many many questions regarding this very issue; how do I make a sub page in RapidWeaver? It’s actually quite easy and logical. Sub pages in web design are often referred to as nested pages. In RapidWeaver that is exactly what you’ll do; just grab a page in the RapidWeaver sidebar and drop it onto another page. Click the image below.
Finder actions buried
Just when you had high hopes of things becoming more streamlined, Apple throws a wrench into the gears of productivity. This might sound like such a minor thing to you all but it’s a REALLY big deal to me. In my quest to blaze through my operations on a mac with blistering speed I hit a big speed bump in Leopard when it came to the contextual menu in finder. The Automator actions are now buried 2 deep so getting to my actions requires skimming through 3 levels of contextual menus.
Like I said, it may sound like a small thing butt it’s a pretty big deal to me.
[tags]Leopard, OS X 10.5, Finder, contextual menu[/tags]
The long road is getting shorter
You ever get to the end of a project and just let out a sigh of relief? I just finished one of those. It was the kind where there were variables that would go one way, but then needed to come back to another. I shopping cart was required, but it had to be easy to use, but then it had to be expandable for the future. One choice broke one aspect, another choice would break something else. Tax calculations, shipping calculations, inventory calculations… You see, I am a digital download guy and exempt from all those bothers. But on this project I had build a store for tangible goods in a state that doesn’t take tax lightly.
Anyhow, this job is complete with the exception of a few tweaks here and there. I’ll let you know when you can see it.
I shall not follow the heard
I can’t begin to describe my frustration! Once single javascript library is throwing a monkey wrench into my entire process! The venerable MooTools, who I have no use for, but many services I use do, is not a team player it seems when it comes to rounding corners in javascript. They don’t believe rounding corners is the job of unobtrusive javascript and instead think that bags full of poor markup, redundant, empty tags, place holders and css should be our only method of rounding a corner in a layout….
So WCAG says we ought not use tables for layouts if we can avoid it…“Tables should be used to mark up truly tabular information (“data tables”).” So by that guideline one can only assume that using <b> tags (which is for bolding or adding strength to type) for layout would be equally offensive. I have now tried every javascript library and snippet I can get my hands on to round corners and not a single one will work with MooTools and a Lightbox window. Arghhhh!
Sorry, I just had to vent.