Re: First time Glom usage + database question.
- From: "Arq. Maximiliano" Meilán <meilan adinet com uy>
- To: Murray Cumming <murrayc murrayc com>
- Cc: glom-devel-list gnome org
- Subject: Re: First time Glom usage + database question.
- Date: Sat, 20 Jun 2009 08:50:35 -0300
Agree with Murray, remember I asked the same question, but after work a
little with Glom, I find automatic save is a good choise. (undo is the
only thing I miss)
What about an automatic backup of the entire session?
El mié, 10-06-2009 a las 12:09 +0200, Murray Cumming escribió:
On Wed, 2009-06-10 at 11:57 +0200, Michael Hasselmann wrote:
Regarding the use case of saving data:
That's what confused me as well when I started to work with Glom. You
somehow expect the edit/undo/save/load paradigm (is there a better name
for that?). Well, since undo and save are missing perhaps one could wrap
everything into (database) transactions that get applied when you change
windows (or when you click "apply changes"). That would allow undos and
perhaps be more fitting to what the user expects?
Another possibility could be a flag for each row (in list view)
indicating whether the data in that row is still in a dirty state or
whether it was already made persistent. Or use a signal color (yellow,
red, ...) for the cell background while editing in the details view,
hinting at how the data is only made persistent after finishing editing
a cell. The color semantics (for a cell) could then be:
* white or blue background: persistent data
* red or yellow background: dirty data
This all seems too much like confronting the user with technical stuff
that he doesn't care about. There's also the risk that data would be
lost, or not visible to other users yet, if the user does not do the
step to actually save the data, though a timeout could help slightly.
There's also the problem that various features would not work if the
data is not really there - such as lookups and related records and
related fields. Avoiding problems with that would add more UI
complication and points of failure.
I am fairly happy about the instant saving because it's exactly what
FileMaker does.
--
____________________________________
Estudio MEILÁN
(arquitectura y construcción)
Avda. Artigas y Zabala - Piriápolis
Tel.(043) 27431 - www.meilan.com.uy
____________________________________
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]