Google Code - Part 1

As I've mentioned earlier, I'm using Google Code to host the apselex project - an Adobe Photoshop Elements Explorer.

It is very easy to get started, and quite easy to use.

But, one thing was eluding me - how to use images in the wiki. I know - the help page has some examples, but as with all these things, the devil is in the details.

• the image needs to be an external link
• as such it needs to be hosted, and available
• a "makes sense" approach is to store images in the wiki directory itself
• and then simply point to the image with a link like this:
  
  [http://apselex.googlecode.com/svn/wiki/ScreenshotExplorer.png]
  

Simple!

Naturally, using Eclipse, it was pretty straight forward to put some images in this directory. The approach I took was:

• create a separate Eclipse project - mine was called ApselWiki
• share this as a Team project (using subversion), and use the wiki as the URL
  
  https://apselex.googlecode.com/svn/wiki
  
  Note, that the wiki directory is outside the /trunk directory. That is, it's in the root of your project.
• You can then simple paste new images into the Eclipse project - and also edit your wiki pages if you really like.
  
• Then simply perform a "Team -> Synchronize"
  

Easy!

Photoshop Elements - Explorer Part 2

Due to overwhelming demand (well, at least 1 person :-)), I've put up my initial code for exploring the Photoshop Elements database. For a small bit of background info, see my previous post.

I thought I'd give google code a try for hosting - as such, the project is located here.

Drop me a line in the comments if you're interested in participating.

Photoshop Elements - Migrating to Version 6

Well, I thought my migration to Adobe Photoshop Elements Version 6 was complete - and I was very happy with the way things had gone.

Until, I needed to print one of my pre-migration dated images.

I was greeted the following, rather unfriendly dialog, and could not print.

Wtf? I was concerned to say the least.

I re-traced some of my steps ...

• newly edited photos would print ok
• new (Version 6) photos were ok
• old (pre-version 6) photos were ok
• old, edited photos were NOT ok

I smelled a rat with the migration process for edited images. The edited images had seemed to be imported as version sets correctly. I did a bit more checking. The following grab shows a typical (albeit) sample image:



Note that the original image in the Version set is selected, and the Size attributes are displayed correctly in the Properties window.

Now, have a look at this next one, with the newer image from the Version set selected:



I've highlighted the problem area - the image width and height are missing. This was pointing to all not being well with the edited image.

I waded through the information on the Adobe support site here, I couldn't find any exact match. I even resorted to the forums, which are extremely painful to use - and still no match.

So, I thought - there's nothing for it but to submit a bug report. This itself was fairly painless, but disappointing:

1. no reference number, or tracking information was returned.
2. no acknowledgment that a bug had even been reported (via email, for example).

However, I was determined not to be beaten by this. I went back to the support documents, and found that a number of suggested fixes finished with the recommendation to use the "Update Thumbnail" command. What the? I didn't think that this would be appropriate for me - since my thumbnails looked fine, thank you very much.

Well, I thought - what could possibly go wrong ?

I'm pleased to report that - it actually fixed the problem!! Woo hoo. I was a little surprised, but relieved to say the least. A few years of editing had not been lost.

I was wondering why I needed to do this though - I used the supported Catalog conversion process. If PSE needed my thumbnails to be updated, I would have preferred them to be done as part of the migration process.

However, this exercise did open my eyes to the strange support mechanisms provided by Adobe. When the product itself sports a gleaming new interface, it's a little sad that the support facilities are somewhat lacking - and in case of those forums, downright primitive.

If any Adobe guys are around - I guess you can close my bug report too :-)