comments on current cvs gui
Ianiv Schweber
burundo@telus.net
Sun, 5 May 2002 11:16:38 -0700
> 1. Building
>
> I can't get configure to work without creating a bunch of symlinks
> in the admin/ directory:
I probably screwed up when I put everything in CVS, I'll take a look
at it.
> 2. Index numbers
>
> The image-IDs in the gui are currently numbered 1,2,3, rather than
> 0,1,2,
>
> Personally I prefer 0,1,2 numbering - This is never going to be a
> non-technical application.
I don't care either way. I thought about what it should be and then
decided 1,2,3 because I didn't have to figure out how to change the
headers in the table widget :)
>
> 3. Status bar
>
> There is a lot of information that needs to be displayed (like the
> stderr output from optimising). Maybe this should be a resizable
> text window with a scrollable history?
I agree. The status bar in the current program was there by default
and it is used to put descriptions of menu items, etc.
Maybe we should use the status bar for messages that can be displayed
for a couple of seconds and then it doesn't matter if they are
replaced. We can have a separate output scrollable area with error
info, etc.
What do you think?
> 4. Loading images
>
> Are all the input images loaded into memory? ..or are they fetched
> from disk every time they are shown full-size?
My idea is to use an image memory cache with user defined size. Right
now it is used only for the thumbnails so they don't have to be
created avery time (expensive).
If we put the original images in the cache then the working set of
images will always be in there and we will only have to load them from
disk when the user focuses its attention on other images.
Ianiv