lo

Dear Arikia
  Okay ==> I got it working.
    In this case "I" is me, Dave -- not you, Arikia.
    I'm using your blog, temporarily, to see if it works.
    I'm like a mechanic taking the car for a test drive.
    I want to see if the brakes work.
    Now I'm checking to see if I can edit this on my laptop. If so, that's a pretty good indication that I'll be able to install it on yours.
  If you want to "move in" to your condo, be aware that the pipes are broken and there are live wires exposed in weird places you won't expect them. But if you are brave (you said you are) you will be able to use this to create and edit blog posts.
  User's Manual: Be zen-like. When you spot a problem understand that it is going to be part of the software forever, it will never be fixed. That way if someday by chance it does get fixed you will feel very very very fortunate.
  It's as if you were starting a cross-country trip. Think: The trip is just beginning. Even when you reach the half-way point. It's still just beginning. Even when you're in the last 500 miles. Still a long long way to go.
  That's the way I'm viewing it. In the past I've rushed through development of these things and made bad decisions. It felt like I was going fast, but in fact I was building something that could never be finished. The times I've made good products that won awards, made the users happy and made my investors rich were the ones where I took my time, paced myself and always thought of the journey as just beginning.
  I think the same approach works if you're a user too. This way the users and developers can be on the same page, think about it the same way.
  BTW, I'm going to turn this into a blog post on scripting.com. I've been wanting to say this for quite some time. ";->"