1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
|
This is a compilation of things left to do on imgSeek. You can help by discussing any of these topics on the mailing lists or directly with the author.
Generic
-------
- add images to database automatically as they are viewed on a thumbnail browser. Since at this time, a cached thumbnail for it already exists.
- poll users (on the homepage ? on the ML ?) for the reasons why they use or why they stopped using imgSeek. Also survey future features, where development should head, etc.
- a way to search for text on all metadata fields, and not just specific ones
- rating system for images, similar to whats done for songs on cymbaline and imms (xmms plugin). Integrated to slideshow viewer and preview pane. Shortcuts for changing image score, and automatic increase on each view. Possibly increasing a value proportional to the time spent viewing it. (Make that an option).
Slideshow would then favor high scored images when picking the next random one. (also an option)
- new option on the HTML album wizard: "Preserve image filename", which when enabled would not generate random unique filenames. (To avoid name collisions, i might append random words on the filename) Not sure how useful this can be. Someone please enlighten me.
- unify all error msgs output. Right now every error will use "print". Redirect this to a wrapper, which could later be fed to a log or something; In other words, use python's "logging" module. It's available on python2.3. Not sure how much requiring python2.3 or a standalone install of "logging" would piss people off.
- write a plugin for other iptc/exif apps. See http://johnst.org/sw/exiftags/
- add iptc/exif writeback support
- remove distributed distutils module as more people start to support python > 2.2
- allow big (256x256), normal (the currently used: proportionally constrained to 128x128), small (64x64) thumbnail sizes. -- shouldn't be too difficult. I could/should still only keep cache for 128x128, as it is already generated anyway when added to content-based db.
- make thumbnail cache an option
- extend distutils with support for uninstalling. (unlikely. Many have already tried, none succeeded afaik. A distutils rewrite is probably already under work)
- forward and backward navigation buttons on html generated pages
- Clean callback system and implement event notification better. -- sigh
- Visit link:http://www.tasi.ac.uk/advice/delivering/metadata.html#mt9[this page] for more metadata features
- Write documentation for XML tags used on the exported files -- does anyone out there even use it ???
- code speed up on imgdb.cpp and haar.cpp -- the best way to speed it up right now is a better integration to the underlying image opener api (aka QT or ImageMagick). ImageMagick has some progressive-aware jpeg opener that could be useful when retrieving a thumbnailed low resolution version of the image. Also, imgdb.cpp should work fine with low resolution thumbnails.
- transform image before querying (rotate, etc). (a popup somewhere on the import image tab)
- more transforms (watermarking, frames, etc) on the Transform dialog (see Transforms class on imgSeekLib/TransformWnd.py) -- bloat. People actually use it ?
- ignore images that have too few coefficients. That will avoid web banners, table and html backgrounds, etc.
- better debugging, assertion and error msgs on C++ modules
- customizable slideshow shortcuts and commands
- move files when browsing by System Dirs
- Improve performance and usability for huge databases.
- Everything else on the "Planned features" section of the site
- stuff on http://imgseek.sf.net/todo-code.html
- investigate: Good evening, if I start ImgSeek (imgSeek 0.8.2 on KDE 3.2.1 on SuSE 8,2), then the program takes itself more than 90 % of the physical memory, without irgedn something makes. If I implement now actions on the imgSeek data base, then still approx. 70 MT Swap memory is added. With this memory situation naturally no pleasant working more if possible is, can one understand. Which I can do, so that imgSeek becomes faster, except: more memory, whereby I assume that it will not also help, because it seems with imgSeek something to be, but which.
Windows
-------
- make sure the lite package (the one without python included?) follow this install file naming convention: "imgseek-0.8.3.win32-py2.3.exe"
- crash on abort (when adding files), metadata dialog doesn't appear.
- make main window smaller (add progress bar is getting on the way)
- finish port
Testing
-------
As usual, testing and bug reporting is needed. Please send complete and descriptive bug reports to imgseek-users|at|lists.sourceforge.net.
Translation
-----------
If you are interested in translating imgSeek to another language,
please link:nieder|at|mail.ru[contact me].
I don't have much experience on adding internationalization support to apps, but I suppose using Python's gettext module is recommended. If you have experience translating or adding translation support to PyQt programs, please share with me.
I've tried using Qt's translation classes (.ts files generated with lupdate and translated with QT Linguist), but all I could get was a "Segmentation Fault".
I'll try using python's gettext and .pot files later.
Documentation
-------------
imgSeek documentation is poor, so any help is really appreciated.
Some documentation (imgSeekCmd) was written in a pure text and then procesed with link:http://www.methods.co.nz/asciidoc/[AsciiDoc]. Other documentation, specially for the GUI could be done in DocBook or LaTeX format, so it can be easily exported to simple html (used on the site or inside imgSeek), plain text, pdf, etc.
It should be complete (which the current attempt of documentation isn't) and focus on the non intuitive parts of the user interface (work batches, groups, etc).
|
