scott parsons
Wed, 09 Jun 2004 09:11:11 -0700
Rimantas Liubertas wrote:
Well ok...Can you name some industries?
HA! you joke but I've had to do that before... Often the actual end client is a half dozen or more layers away from my team and everyone in between has different agendas and different understandings of what is going on.
Why not to export entire page from photoshop as GIF, JPEG, or PNG and put
it on the website? That's the only way I know to get pixel percision.
How do you and your clients imagine pixel precision in screen readers, mobile phones
and PDAs? How do they know is this layout pixel presice or not?
For me talks about pixel prescion is an indicator that nobody really cares what and whom this website is for.
>Patrick Lauke wrote:
Or it might be time to educate your client with regards to "the web is not print". What's next: discussions about exact colour matching, across all browsers?
Well I have tried this from time to time... whenever possible with examples of where web beats print... but usually I never get to even see the client, and account handlers are not interested in techno babble...
Another point to note is that when the stuff you are making is ephemeral in nature there is less of a requirement to make it perfect... if it is 6:45 on a friday and this microsite needs an adjustment you can do in 6 seconds with a hack, and the site is only gonna be there for 2 weeks...
I'm not saying all hacks are good or anything, just that there is a time and place for everything. Take the @import 'hack', a valid way of hiding complex CSS from a browser that will choke on it, which allows me to actually use css because if I can't hide my css from certain browsers then I have to limit my css to what they understand or else my documents might not be usable
s