Paper size in pixels
I'm doing some work for printed graphic so I was wondering how big is in pixel a paper sheet?
Of course depends on DPI usuallly the standard DPI rate is 300 but also lower resulution are fine for what I'm doing so let's see what happen playing with resolutions.
| paper size | inch | pixel 300dpi | pixel 200dpi |
| A0 | 33.11 × 46.81 | 9933 x 14043 | 6622 x 9362 |
| A1 | 23.39 × 33.11 | 6717 x 9933 | 4478 x 6622 |
| A2 | 16.54 × 23.39 | 4962 x 6717 | 3308 x 4478 |
| A3 | 11.69 × 16.54 | 3507 x 4962 | 2338 x 3308 |
| A4 | 8.27 × 11.69 | 2481 x 3507 | 1654 x 2338 |
| A5 | 5.83 × 8.27 | 1749 x 2481 | 1166 x 1654 |
| A6 | 4.13 × 5.83 | 1239 x 1749 | 826 x 1166 |
HTML Email and CSS on different email-client
I found this interesting table about which CSS attribute is supported by the different email client.
| Style Element | Outlook 2000/03 |
Live Hotmail |
Yahoo! |
Yahoo! Classic |
Outlook 2007/10 |
Apple |
Apple iPhone |
Google Gmail |
Lotus Notes 6/7 |
Lotus Notes 8.5 |
AOL Desk 10 |
| <style> in <head> | |||||||||||
| <style> in <body> | |||||||||||
| Link Element | Outlook 2000/03 |
Live Hotmail |
Yahoo! |
Yahoo! Classic |
Outlook 2007/10 |
Apple |
Apple iPhone |
Google Gmail |
Lotus Notes 6/7 |
Lotus Notes 8.5 |
AOL Desk 10 |
| <link> in <head> | |||||||||||
| <link> in <body> | |||||||||||
| Selectors | Outlook 2000/03 |
Live Hotmail |
Yahoo! |
Yahoo! Classic |
Outlook 2007/10 |
Apple |
Apple iPhone |
Google Gmail |
Lotus Notes 6/7 |
Lotus Notes 8.5 |
AOL Desk 10 |
| e | |||||||||||
| * | |||||||||||
| e.className | |||||||||||
| e#id | |||||||||||
| e:link | |||||||||||
| e:active, e:hover | |||||||||||
| e:first-line | |||||||||||
| e:first-letter | |||||||||||
| e > f | |||||||||||
| e:focus | |||||||||||
| e+f | |||||||||||
| e[foo] | |||||||||||
| Text & Fonts | Outlook 2000/03 |
Live Hotmail |
Yahoo! |
Yahoo! Classic |
Outlook 2007/10 |
Apple |
Apple iPhone |
Google Gmail |
Lotus Notes 6/7 |
Lotus Notes 8.5 |
AOL Desk 10 |
| direction | |||||||||||
| font | |||||||||||
| font-family | |||||||||||
| font-style | |||||||||||
| font-variant | |||||||||||
| font-size | |||||||||||
| font-weight | |||||||||||
| letter-spacing | |||||||||||
| line-height | |||||||||||
| text-align | |||||||||||
| text-decoration | |||||||||||
| text-indent | |||||||||||
| text-overflow CSS3 | ![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
||||
| text-shadow CSS3 | ![]() |
![]() |
![]() |
![]() |
|||||||
| text-transform | |||||||||||
| white-space | |||||||||||
| word-spacing | |||||||||||
| word-wrap CSS3 | ![]() |
![]() |
![]() |
![]() |
|||||||
| vertical-align | |||||||||||
| Color & Background | Outlook 2000/03 |
Live Hotmail |
Yahoo! |
Yahoo! Classic |
Outlook 2007/10 |
Apple |
Apple iPhone |
Google Gmail |
Lotus Notes 6/7 |
Lotus Notes 8.5 |
AOL Desk 10 |
| color | |||||||||||
| background | ![]() |
![]() |
|||||||||
| -moz-background CSS3 | |||||||||||
| -webkit-background CSS3 | |||||||||||
| background-color | |||||||||||
| background-image | |||||||||||
| background-position | |||||||||||
| background-repeat | |||||||||||
| -khtml-background-size CSS3 | |||||||||||
| -moz-background-size CSS3 | |||||||||||
| -o-background-size CSS3 | |||||||||||
| -webkit-background-size CSS3 | |||||||||||
| HSL Colors CSS3 | |||||||||||
| HSLA Colors CSS3 | |||||||||||
| Opacity CSS3 | |||||||||||
| RGBA Colors CSS3 | |||||||||||
| Box Model | Outlook 2000/03 |
Live Hotmail |
Yahoo! |
Yahoo! Classic |
Outlook 2007/10 |
Apple |
Apple iPhone |
Google Gmail |
Lotus Notes 6/7 |
Lotus Notes 8.5 |
AOL Desk 10 |
| border | ![]() |
||||||||||
| -moz-border-color CSS3 | |||||||||||
| -moz-border-image CSS3 | |||||||||||
| -moz-border-radius CSS3 | |||||||||||
| -webkit-border-radius CSS3 | |||||||||||
| -moz-box-shadow CSS3 | |||||||||||
| -moz-box-sizing CSS3 | |||||||||||
| height | |||||||||||
| margin | |||||||||||
| padding | ![]() |
||||||||||
| width | |||||||||||
| Positioning & Display | Outlook 2000/03 |
Live Hotmail |
Yahoo! |
Yahoo! Classic |
Outlook 2007/10 |
Apple |
Apple iPhone |
Google Gmail |
Lotus Notes 6/7 |
Lotus Notes 8.5 |
AOL Desk 10 |
| bottom | |||||||||||
| clear | |||||||||||
| clip | |||||||||||
| cursor | |||||||||||
| display | |||||||||||
| float | |||||||||||
| left | |||||||||||
| opacity | |||||||||||
| outline CSS3 | ![]() |
![]() |
![]() |
||||||||
| overflow | |||||||||||
| position | |||||||||||
| resize CSS3 | |||||||||||
| right | |||||||||||
| top | |||||||||||
| visibility | |||||||||||
| z-index | |||||||||||
| Lists | Outlook 2000/03 |
Live Hotmail |
Yahoo! |
Yahoo! Classic |
Outlook 2007/10 |
Apple |
Apple iPhone |
Google Gmail |
Lotus Notes 6/7 |
Lotus Notes 8.5 |
AOL Desk 10 |
| list-style-image | |||||||||||
| list-style-position | |||||||||||
| list-style-type | |||||||||||
| Tables | Outlook 2000/03 |
Live Hotmail |
Yahoo! |
Yahoo! Classic |
Outlook 2007/10 |
Apple |
Apple iPhone |
Google Gmail |
Lotus Notes 6/7 |
Lotus Notes 8.5 |
AOL Desk 10 |
| border-collapse | |||||||||||
| border-spacing | |||||||||||
| caption-side | |||||||||||
| empty-cells | |||||||||||
| table-layout | |||||||||||
| Total Market Share | 28% | 16% | 14% | 9% | 8% | 7% | 6% | 1% | 1% | ||
from:http://www.campaignmonitor.com/css/
How to convert PSD to JPG using Linux convert from command line
I recently had the need to convert psd images to jpg from command line. I browsed the net a little bit and I found an interesting article about how to do it easily. The right command is "convert" and it works for several images type and among them photoshop psd.
here is how it looks like:
/usr/bin/convert -quality 80 -flatten myimage.psd myimage.jpg
Top 10 Wireframe Tips
1.Start Sketching
Sketch them first with a pencil and paper for a quick sanity check. This should take about 30 seconds and opens up the possibility of getting early feedback. This can save a lot of time and money. The feedback can be gained through peer review or, best of all, from some early and informal user testing (you may need to spend a little more than 30 seconds on the sketches if they’re for user tests).
2.Focus on Communication
The key point of wireframes is to communicate. Don’t forget this. Keep them simple and stop working on them as soon as they communicate their key information.
3.Use Proper Documentation
Since wireframes are meant to communicate something, provide some accompanying notes. Whenever possible, each wireframe should include documentation, i.e. revision date, author, page title, interaction notes, etc.
4.Host the Wireframes
If possible, host the wireframe files yourself, rather than sending them out as email attachments. My preferred method is to export the files as PNGs and then embed them within some simple HTML files. This way they’re easy to share and update.
5.Don’t Forget the Goal Of the Page
Keep the goals of the page in mind when designing a wireframe. Focus on driving action. Organize the information into a hierarchy that serves the goal of the page.
6.Pick Your End Point
Prior to commencement, work out who will be consuming the wireframes, how they’ll consume and what level of fidelity is required. Remember that there’s a relationship between the level of fidelity and type of feedback. Will quick paper sketches suffice or will they need to be fully interactive with accurate dimensions? Keep in mind: the less precise the wireframes are, the more liberty and creativity a designer is going to take with them. On the other hand, if you they look perfect designers may feel inhibited and merely “color in” the wireframes, preventing the design process from really getting going.
7.Loop the Rest of the Team in
Wireframes are not just for clients. All members of the web team should provide feedback on them, buying into the process at an early stage.
8.Consider the Content
If your wireframes aren’t sketches then be realistic about the amount of content that will be added to the page. This holds true also for number (and length) of links in navigation. If practical, use accurate sized fonts, images and consider what will happen when more text than is ideal is added. Nothing on the web should be etched in stone, so ask if the design will flow as required.
9.Use Common Elements
If designing a set of pages, use tools that allow you to make multiple changes to all common page elements at once. Moreover, as you’re creating the wireframes, look out for design patterns that repeat. Leveraging these is key to gaining efficiency and consistency.
10.Get Feedback
Don’t be afraid to test your wireframes in a couple of informal user tests. Grab people from around the office and ask them to find various bits of information or explain what they think the function of certain elements is.
from:http://www.uxbooth.com/blog/wireframing-tips-tools-and-techniques-pt-2/
Less is More: Simplifying your User Experience
Too many options can confuse and weigh down users. Don’t overwhelm them.
Through the rapidly increasing amount of information, messaging, reviews and data online, we know that consumers are presented with more options than ever before. As a result they are becoming more and more savvy and resourceful to research products and services that they’re interested in. Ultimately they’re becoming wiser with how they are making their buying decisions and more demanding to have the information they need, when they need it.
As marketers, it’s important to consider the opportunity we have to lead our consumers from inquiry to purchase by offering them what they need—and only what they need—at every step of the process. No more, no less.
When considering what and when we’re delivering to customers, we need to keep in mind that most consumers are now doing their research through multiple platforms. Whether it’s through their laptop browsers, iPads, Blackberrys or iPhones, the need to develop smart user experiences and intuitive interfaces on every platform is greater than ever.
So how do you ensure you’re providing this to your customers?
Be one step ahead
It’s something that the advertising industry has excelled at for years and something that the digital world can certainly learn from. Who are we communicating with? How do they think and what do we need to say to persuade them towards an action? In our case, what information and options do we need to provide them with to move them to the next step towards their purchase decision?
To fully answer these questions, let’s take a look at the restaurant dining experience. Generally, once someone sits down to eat, you have their full attention and their commitment to spend money with you. For whatever reason, they’ve chosen to engage in a dining experience at your restaurant. In the same way, once someone lands at a website, mobile site, iPhone app, or any user experience that you’ve provided, you have their full attention. Now all you have to do is keep their attention and walk them down the path that you’ve carefully planned and thought through.
How do you carefully plan and think through a user experience?
Start with the end user
Clearly establishing who is going to be using the interface, identifying their wants and desires surrounding your product, and then mapping out their decision making process are things that can’t be overlooked in your planning process. Can you imagine sitting down for dinner at your favorite restaurant and having your waiter ask you what you would like to drink, and then immediately ask what you think you’ll want for dessert later on? You likely have enough trouble trying to figure out what you want for a main course, or if you even want an appetizer.
Stage what you’re presenting your users with in digestible pieces—too much too soon may heighten your drop off rate.
No dessert until you finish your meal
There is a common sense approach to how you are sold at a restaurant. Much like how they stage your dining experience, in web and mobile experiences, our approach needs to be as equally simplistic.
This is where the idea of less is more comes into play. It’s centered around the notion that we don’t want to make our customers think more than they have to. The fewer decisions, the better.
This becomes easier to accomplish when we consider all of our customer touch points throughout the decision making process and specifically what they’ll be looking for at that point. With how connected most people are now, an important part of this is recognizing what platform they’re using and what specific information they’re looking for. An example of this would be someone looking up your website on their way to your store in hopes of finding your address.
Ask yourself the following questions when approaching UX design:
What can we take out of the experience to make it easier for our users to make decisions?
Are we presenting them with a desert option too soon in the process? What options and upgrades would be better suited for another menu at a later time?
How do we keep them engaged through the whole experience?
Less really is more
After identifying what environment or device consumers will be on at any given point along the way, remove all unnecessary options along that path, giving them exactly what they need at each step—no more, no less. The end result will be smaller bounce rates, more sales, customers who feel like you understand their needs, and hopefully as a result, more word of mouth referrals.
from:http://www.uxbooth.com/blog/less-is-more-simplifying-your-user-experience/
