71–80 of 81 posts
I have thought about making video tutorials on how to use Photoshop to create practical design elements. Ie, how to make a button or how to design a header. Something every programmer making their own webapp could use that doesn't really require much Photoshop knowledge. Would there be any interest?
Played around with it for a while, but because I currently don't have a way ($$$) to get Photoshop (nor do I really need it), I use Paint.NET for most of the things I do. For the few things for which Paint.NET is not good enough I use GIMP ;). And of course Inkscape for vector graphics.
I strongly dislike Photoshop for mockups and think that using it is indicative of poor practice. In my experience it leads to premature optimisation of styling over basic design, tends to lock down designs too soon and gives no real insight as to usability. A Photoshop mockup is inherently static and turning it into a clickable prototype generally requires a great deal of duplicated effort. My preferred tool is Keyno…
I use a pen and paper or a tablet for mockups.
I edit images in Pixelmator.
I don't use art editing tools for mockups.
Earlier quoted context omitted.
You might as well have pirated it because you are violating the agreement by installing OEM on a different computer.
What do you mean a different computer? This was a copy that was never installed. I bought it from one of those online OEM shops. It wasn't zipzoomfly.com, but something like that.
Picasa's UI was done entirely using Photoshop files. Layer names=widget names, etc. Our small-company team loved it. But at Google, I found very few engineers who wanted to touch Photoshop, ever. Biggest issue with using Photoshop in your actual production pipeline: "programming in the large" - you can't do code reviews or merges on PSD files, not nearly as easily as .cpp files. So as a team gets big, it is very hard…
So you create the UI elements as PSDs and then export to some image format when building? Or do you actually interpret the PSD files in code itself?
The artwork is saved in largish PSD files and I have a script which generates the required AppleScript to open each one, scale down the images to the required formats (for ex, retina-display and non-retina display), occasionally exporting different layers into different output files.
Not to mention a fraction of the price. There's a free trial, give it a shot.
Picasa's UI was done entirely using Photoshop files. Layer names=widget names, etc. Our small-company team loved it. But at Google, I found very few engineers who wanted to touch Photoshop, ever. Biggest issue with using Photoshop in your actual production pipeline: "programming in the large" - you can't do code reviews or merges on PSD files, not nearly as easily as .cpp files. So as a team gets big, it is very hard…
Thanks for sharing. I've wondered for a long time what UI toolkit was used to make Picasa! So you create the UI elements as PSDs and then export to some image format when building? Or do you actually interpret the PSD files in code itself?