Re: Other UI Issues

On Thu, 2005-10-06 at 11:37 -0400, Richard Heck wrote:

> Actually, it should probably be harder, overall, to lose one's work than
> it now is. Adding one further confirmation dialog---"Are you
> sure?"---would be a good idea, I think. And it wouldn't be a terrible
> idea for temporary files to be written to /tmp/pyblio_procid/ every time
> a change is made, so that, I don't know, a crash of some sort wouldn't
> have to cause lost work. (Perhaps such files are already written
> somewhere.) Those could be cleaned up whenever the database was formally
> saved, and the program could check for old files each time it was started.

Also, I think the opened files should be watched for changes. I have set
up mozilla (via a simple script) to append new items to my main .bib
file. If pybliographer is open (which it often is) then these new items
are lost next time I save. It needn't do anything fancy like try and
merge the changes automatically, just warn me that the file has changed.
A revert to file menu item would be useful too, because currently I have
to close and reopen.

The other issue is that you can't minimise/windowshade the main window,
but keep an edit window visible - this is something I frequently try and
do if I'm copying stuff from an open webpage/pdf doc/whatever into a new
entry.

-- 
Robert Hart <enxrah-QabDm/[email protected]>
University of Nottingham


This message has been checked for viruses but the contents of an attachment
may still contain software viruses, which could damage your computer system:
you are advised to perform your own checks. Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl