Hi developers There are plenty of graphics files throughout the codebase. While preparing to give Hugin a face lift using Cristian Marchi's new design, I've looked at cleaning things up and documenting them so that when the next designer comes and want to give Hugin a facelift, things are easier to do than now.
I found that source files and target files are mixed throughout, particularly in ./src/hugin1/huginxrc/data which IMHO is quite a mess. I intend to centralize all source artwork in a new top level folder, ./artwork-src, and I wrote a small primitive script to take it from there, produce the targets and copy them to the right location in the source tree. BUTTONS The buttons are the cleanest part. Bruno redesigned all of them consistently and in SVG. Unless there is a valid reason not to do so, I will move the sources of the buttons (SVG files) into a location in the artwork folder. I have scripted an Inkscape command line to recreate the PNG actually used by the app and copy them into the right location. ICONS We currently have only one icon for Hugin and PTBatcher. This is changing thanks to Cristian's design. PTBatcher is a program in its own right and deserves its own icon. The icons currently in the codebase are the biggest mess. MAC-ICONS The cleanest ones are Mac icons. There are two files, Hugin.icns and HuginFiles.icns in ./src/hugin1/hugin - I will need to regenerate them all and have not yet researched the generation of icns files in Ubuntu. Any help is appreciated. With the new design we'll likely have also PTBatcher.icns, and I will need help to update this on the Mac side. Harry? WINDOWS-ICONS There is a Photoshop file ./src/hugin1/hugin/xrc/data/icon_128x128.psd which is obviously source to a whole bunch of icon_WxH.ico and icon_WxH.png files. I'll move the Photoshop file into some legacy area of the repository. My understanding is that Microsoft's .ico file specification contains multiple resolution images inside a single file, like Apple's .icns I've been able to produce such a .ico file programmatically using Inkscape, ImageMagick, and Cristian's source SVG. Is there a reason to keep all the single-resolution icon_WxH.ico files? For now I'll remove them. It is easy to add a couple of line to the script generating the icons from SVG if during beta testing of 2010.4 we find out that they are needed. See also discussion of bitmap size and bit depth further down under the header WINDOWS INSTALLER LINUX-ICONS For Linux ./src/hugin1/hugin/xrc/data/hugin.png and /home/yuv/src/hugin/hugin.hg/src/hugin1/hugin/gnome-mime-application-x- ptoptimizer-script.png are 48x48. I'll generate a similar one for ptbatcher. I've seen somewhere something about an SVGZ format that uses the gzip compressed SVG file. Anybody knows how to use those? DRUID FILES There are a few ./src/hugin1/hugin/xrc/data/druid.* images that are used in the application. We don't really have sources for them and they are targets. I'll leave them untouched for now. SPLASH & ABOUT SCREEN I'm generating these programmatically from Cristian's SVG file and they fit in as a replacement for the old files, no problems. WINDOWS INSTALLERS There are a number of different size graphics and icons for the three different windows installers. I can generate replacements for those bmp files programmatically. Matthew Petroff has done a great job with the icons of the most recent installer. I'll update his SVG files with the new branding. What I don't understand (Matthew, maybe you can help?) are the xcf (gimp) files. They contains layers of what seems to be rendering of the SVG source file, for the creation of the .ico file? I see layers with: 16x16 4bit 16x16 8bit 16x16 32bit 32x32 4bit 32x32 8bit 32x32 32bit 48x48 4bit 48x48 8bit 48x48 32bit 256x256 32bit I can generate all of this programmatically with Inkscape & ImageMagick, so the xcf file are be redundant? Is there a reason to use 4bit and 32bit images? I read somewhere that only 8bit files are rendered well, and the other icon we have for Hugin is 8bit only if I am not mistaken. Are there standard sizes? I read on the web of 64x64 and of 128x128. Can somebody tell me what resolutions to produce / put inside the .ico file? My intention is to use the same combination of bitmap size and bit depth across the board for all .ico files. What do you Windows expert suggest? This can always be changed very quickly during the beta testing of 2010.4. OTHER IMAGES The images on the website will need an update too. I've listed them and will produce them programmatically / replace them in the website's repository in due time. The new tracker will be activated on Launchpad in a few hours. It allows for branding/customization. I've already uploaded some images there [0]. If you head over and look at it, this is a good time to register for a Launchpad account. If you do register for a Launchpad account, please document your process step by step. I am writing documentation on how to get going with adding bug reports and feature requests, but having had an account for a while now I don't know how to describe the experience of adding an account. thanks Yuv [0] https://launchpad.net/hugin
signature.asc
Description: This is a digitally signed message part.
