re: ScratchList or some such thing

I've been looking for something like this myself to support Apply operations for buffered user interfaces (i.e. present the user a list, allow them to make modifications, but don't make those modifications to the 'live' list pipeline until the user hits Apply or Commit).

 

The behavior sounds suspiciously like a reverse-bahaving TransactionList - but I haven't had time to look to see how hard it would be to invert the logic to achieve the desired results...

 

- K

 

I have an EventList with a bunch of data relative to many files. API
consumers can ask for a pared down list  that contains a list of elements
that only pertain to a particular file on disk. Here's the simple pipeline:

EventList (all data) -> FilterList (data for a given file)

My problem is this:

The consumer of that list wants to render the list contents on screen. They
also want to allow the user to edit the contents of that list without
actually committing the changes upstream yet (so the list would be in a
"dirty" state).

Is there any solution built in to GL for such a problem? Do I need a new
type of list, like a ScratchList that can be used to locally edit and then
push it's changes upstream? Am I thinking about the problem wrong?

Thanks guys!
-Ken
--
View this message in context: h ttp://www.nabble.com/ScratchList-or-some-such-thing-tp23596977p23596977.html
Sent from the GlazedLists - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...