Photoshop CS6 and the Liquify tool

To start off with.. I need to mention that I’m an edge-case when it comes to Liquify.  I have spend over a hundred hours using it recently. I know all the keyboard shortcuts and I use the different types of reconstruction brushes as I work. They allow me to stretch the mesh and relaxe parts of it into place, smooth out distortions and sculpt my work. Did I mention I work a LOT in Liquify?

The biggest thing I love about the new liquify is that I can now make actions that load specific meshes and apply them. That allowed me to do some really fancy automation work.

The bad news? They did get rid of all the fancy reconstruction options that allowed a lot of back and forth work. It’s like the difference between sculpting clay and marble. The liquify tool is now more for subtle work.. a nudge here and there. Not working out?  reset and try again. Not many options to relax a mesh locally.

I now need to you 3 Photoshops to get work done. CS5 for making liquify meshes, CS6 for automating them and CS5 x86 for scanning(twain drivers).

MTV.. Why are you arguing with me? – UX fail!

I see some link in the news.. and interesting article on mtv.co.uk and I click on it. Now I have to get past a splash screen that want to take me to the US website. That’s fine. Ok.. but, wait. It doesn’t take me to the article I wanted to read. It’s on the UK site. So.. again., splash screen. Continue to UK site and I get a consistent bar across the top.

“The best experience for US users can always be had at the US website (www.mtv.com).

Not a friendly reminder that there is a US version of the website. It’s.. “Go back, you don’t belong here”. I never got redirected to a closer server with the same content. They are just making me feel unwelcome.
How RUDE!

SCSS workflow

I was playing around with LESS and I started to see some issues I didn’t like with the output of complex selectors. I kept going back to SASS but was put off by the command-line. I like GUI interfaces.. I was not interested at all in Ruby. It’s seemed like a lot of odd things to do to get the CSS files I wanted out of SASS.  I decided to just suck it up and do it anyway. It wasn’t as painful as I feared. I think I may have to write a tutorial for it though.. explaining in artist words what these programmers are doing with the command-line. I feel like the Ruby people are so deep into their own world they don’t know how to talk to lay-people. The instructions are accurate.. just now low-level enough.

Part of the problem is that I’m still on Windows. I say it that way because I listen to podcasts on 5by5.tv and I’m slowly being brainwashed into becoming an Apple fan. It does not help that all the cool dev tools are on the OSX platform.  So that means I had to install Ruby first, then Sass with Compass. I had to figure out ways to get around on the command-line. It haven’t messed much with a terminal since the SGI O2 in college. I played around with some flavor of Linux every year or so.. but I always found it too alien and got in the way of what I wanted to do. Now it looks like I may go Apple and back to the command line.

So.. here is what I have:
Ruby with Compass and Sass
I’m using WAMP server 64bit to host my WordPress installations on an SSD.
I’m telling SASS to watch style.scss:style.less
That’s correct.. I’m telling SASS to generate CSS too a LESS file extension. Why? Because I can tell the less.js in my browser to watch for changes to the style.less file and reload just the CSS. It’s a hack, but it works. I’m probably going to stick with that until LiveReload is more stable on Windows.. or I move to the Apple platform.