Am Samstag, den 27.03.2010, 11:52 +0200 schrieb Debarshi Ray: > > yes, we have this choice. But it still depend what options will importer > > have. If simple import.. importer can do it all. If import with choice > > then it should be capable to display grouped files > > Right. > > > This will mean we need to have two programms > > doing same: importer wich display without tracker-backend and solang > > with tracker-backend. > > The importer does the actual job of parsing the DCIM layout even if it > does not provide the user with any choices. Solang (or any other > program) just leverages the semantic relationships that have been > inserted into Tracker by the importer. > > The point I am trying to highlight is that the job of deciphering the > DCIM filesystem is not being done by Tracker. > > > Modifikation time. better from exif (for new file names), > > video framerate (quirk for panasonic, may be some other cameras too), > > file size (to be sure we have place to import), > > file and folder names (can actually use urls provided by tracker) > > We might show some of these information to the user if she wants to > choose what is going to be imported. However I would want to keep it > simple and only show relevant bits of meta-data to avoid overwhelming > the user. > > Relying on Tracker just for extracting some meta-data from the files > seems to be an overkill to me, especially because of surrounding > complications and subtleties. For all practical purposes, I would > copy-paste Tracker's code for extracting these bits into the camera > importer. ;-) > > Think of it this way. If Tracker is not being used on the system, the > user can still use the importer although it won't be inserting any > semantic relations anywhere.
Ok, you destroyed all my attempts to create overkiller app :) I'll stay in touch out of tracker list. Regards, Alexey _______________________________________________ tracker-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/tracker-list
