RE: Impression on the new media GUI

 > 2. Can't create the 'sounds' origin if one doesn't already exist.

I added a member to the profile to allow the developer to define the ringer
origins for each phone, look at the 9800 code for an example.

> 5. I REALLY do not like storing the media data in the database.
It isn't. The data is in a directory in the bitpim directory, the files are
named using the md5 hash of the data. The database just has pointers to
these files as per Roger's suggestion.

> 
> My recommendations: keep the new GUI and the existing data structure.  
> The index dicts can be moved into the DB, but there're no real 
> advantages of doing that either.  The index dict can also be improved 
> to support same filename in separate dirs.

Moving the index into the database is tied to the gui changes and other
improvements like storing the file time and the workaround for not being
able to read back media from the 8100 now in the code and the changes
required for supporting the same name in multiple places and I don't want to
port any of this back to the old index as there is no advantage.
However going back to the old style media directories instead of the md5
named files but adding a path for the origin is something that I can do, it
is an isolated change. It will fix the drag and drop, temp filenames and
copy features as well.

How does this sound?

Simon



-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642