[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.tools.emf] Re: Best Practice Approach

Balaji,

1. Since the command stack's purpose is to support undo, limiting the size of
the stack will limit the otherwise unlimited undo. Of course, there's no such
thing as unlimited - as you point out, at some point memory will run out.

2. Commit, would be a great point in time to flush the command stack, since as
you say, undo is no longer possible in the backend anyway.

Frank.


Balaji wrote:

> All,
>
> 1. All the EMF commands are stored in a command stack. when should we clear
> the stack? Are there scenarios when the command stack is too huge for the
> application (Eclipse) to handle.
>
> 2. The EMF model data is displayed in my view. The view has a commit and
> retrieve buttons to commit and retrieve information to and from the server.
> Many of you would have handled similar scenario. When a commit is performed,
> would it be advisable to clear the command stack. i.e. users can't  revert
> back (performing an Undo operation) after they have performed a commit
> operation.
>
> Thanks
> Balaji