Skip to main content

Photo organizer for Mac III

Ok, I'm gonna write my own.
  1. GUI will be done in C++/QT -
    I'm familiar with coding GUIs using this combination
    C++ should give the necessary snappy response such an app needs for comfort
  2. The database will be sqlite (the database will mirror the metadata for speedy searching and organizing)
  3. The core will be built around
    libiptcdata OR
    exiv2
    Both libraries are self contained, but I'm leaning towards exiv2 because libiptcdata can not read/write Exiv info
Project road map:
  1. Put down on paper what the program will do and what its interface will look like
  2. Download, compile and install QT
  3. Figure out API for exiv2
  4. Write a baby program to read and write metadata using exiv2. The baby program should use a text based interface but have all the functionality of the final product
  5. Implement the full design
UPDATE:

My new direction, instead of messing around with exiv2's C code, is to go back to the idea of building an interface around exiftool.

To start with I'll do batch operations to speed things up:
  1. The application (Chhobi) will import the picture library (batch read relevant metadata into its sqlite database)
  2. Accessing pictures will pull the data from the sqlite database
  3. Editing metadata will modify the sqlite database and set modified flags
  4. On command (or in the background, periodically) the modified metadata will be batch written to the actual images.
UPDATE:
Now alive and kicking on github Moving this to sourceforge (chhobi.sf.net) ...
Labels:

Comments

Post a Comment

Popular posts from this blog

A note on Python's __exit__() and errors

Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or...
Post a Comment
Read more

Store numpy arrays in sqlite

Use numpy.getbuffer (or sqlite3.Binary ) in combination with numpy.frombuffer to lug numpy data in and out of the sqlite3 database: import sqlite3, numpy r1d = numpy.random.randn(10) con = sqlite3.connect(':memory:') con.execute("CREATE TABLE eye(id INTEGER PRIMARY KEY, desc TEXT, data BLOB)") con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", sqlite3.Binary(r1d))) con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", numpy.getbuffer(r1d))) res = con.execute("SELECT * FROM eye").fetchall() con.close() #res -> #[(1, u'1d', <read-write buffer ptr 0x10371b220, size 80 at 0x10371b1e0>), # (2, u'1d', <read-write buffer ptr 0x10371b190, size 80 at 0x10371b150>)] print r1d - numpy.frombuffer(res[0][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] print r1d - numpy.frombuffer(res[1][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] Note that for work where data ty...
Post a Comment
Read more