VIEWS - a way to store and recall fixed views of a subset of the db

[ubacher]

The following ideas should be seen as a suggestion (or feature request) for
a future major version of Imatch

VIEWS - a way to store and recall fixed views of a subset of the db.

When we work with existing images we usually do the following:
1. Select the source of images (Folder, Category, Timeline, Collection, Event, People)
2. Filter the images to only show the ones of interest
3. Set the sorting mode
4. Set the thumbnail layout
5. Specify if stacks are expanded or not

A VIEW would be a stored set of these settings.

The views could be shown like a result set - this would make them very easy to switch to.

Note that we already have kind of a VIEW in EVENTS. EVENTS let us specify
the sources and some filtering based on time and file names. It was EVENTS
which inspired me to suggest VIEWS.

We also have RESULT sets which allow us to "freeze" a set of filtered files.
These are, however, static.

To reduce the load on the system one could make VIEWs only update on demand.
All this would require an indicator that the VIEW is not up-to-date and
a button (F5 would actually do) to initiate an update.

[Jingo]

Sounds like this could be accomplished by using Workspaces ... I haven't checked to see exactly what is saved in them beyond the obvious image source and panel display.. but it says over 200 settings are maintained so perhaps some/most of this is already something that can be accomplished via Workspaces and it could be further expanded to include things that are not.?

[ubacher]

I actually would like to also store the work space with a view. Because work space switching is very slow I left this out.