(Another) request for a customisable info module

I searched and I found a few requests for a photo info module that could be customised. The response is usually to hack either the info or rwinfo modules. I hope this is possible in my case. I want to present one EXIF field, one IPTC field and tags. But I would have thought that this is such an obvious thing that someone would have taken the idea beyond rwinfo by now, and made it something that you could configure in the admin module.

I know I will be invited to do this myself. I would if I could. I'm not new to basic coding but I am totally new to PHP and other things that G3 is built on (jquery?). It would take a very long time.

U-G

Bharat

Thank you. That's a very generous offer and I would find it hard to say no. The fields I would like are:

Exif Date Original (format 16 December 2010)
Exif Time Original (format 17:15:00)
IPTC Source
Tags for the image

I'm looking for something that would display just for resize pages.

I have experience in Perl5 (years ago now), javascript, visual basic (lots) and C++ (a little). I hope that over time I can contribute, but it will mean self-learning another #$%*$&!! language. Perhaps I can develop whatever you write. I think that something that can be configured via the admin settings would be of general interest.

Thank you again.

U-G

Thank you Bharat. That's very kind and much appreciated. I am travelling for a few days with just my Netbook and a mobile phone. I will take a closer look in a few days when I'm back in front of my desktop.

U-G

After a long string of careless mistakes by a newbie, I have included the IPTC field. I used the following code in about_this_photo_block.php with a corresponding entry in the view:

      // IPTC - copied more or less from iptc.php
      if (module::is_active("iptc")) {
	    $record = ORM::factory("iptc_record")->where("item_id", "=", $theme->item()->id)->find();
   	    if ($record->loaded()) {
          $record = unserialize($record->data);
          $block->content->source = $record["Source"];
  	    }
      }

I also needed to include a test to ensure that this only displayed on photo pages. While it didn't cause major problems without this test on album pages, it did on pages like "contact owner".

I also had a minor problem with formatting in the view. The use of ul/li caused a large indentation of the text. I looked at the IPTC module and it uses the exact same ul/li structure and css and didn't have the indentation. I couldn't for the life of me see why the difference. To remove the indentation I switched to span & br. Why does one module using ul/li have a large indentation and another not?

Thanks again for all your help. I will play with this a little more, but once I've finished, what is the best way to have my changes included in the repository?

U-G

I have struggled with the whole GIT concept. I think I've done it, although my updates were added to the 3.1 branch. Is this normal, or did I do something wrong?

U-G

That information should be in EXIF, and if someone understood the structure of EXIF it could be added to the module fairly readily. Or better, a more EXIF-oriented version created. But I don't see how you will be able to use it to sort.

U-G

My other sandbox

Sorry, I was talking about EXIF. And by sorting I was talking about the tags. When you click on a tag you are sorting by that tag. In my book anyway ;) And this could be in its own block, not mixed with the other tags.