Re: [Traverso-devel] Jmb GUI concept: how to proceed

[Remon Sijrier]

Hi Nicola,

Thanks for sharing this in depth overview with us!

You made some good points I think, and most of them are just what I have in 
mind too, but in fact you're taking it a step further allready.

It's good to have a 'brain stormer' in the team!

The concept of JMB (not sure if this is as good a term as "soft selection, 
though JMB "sounds" better ;-) ) indeed needs a high level of consistency and 
logical grouping of actions.

The action grouping to one type of key action wasn't done before, which wasn't 
to my liking.
However, with the true contextual implementation we have now, this has become 
possible, and allready shows it's validity!

> In my opinion this concept would allow to add much more features without
> running out of hotkeys, and by recycling the well-known keys the work flow
> would be consistent and intuitive. The user will know that pressing <e> on
> an object will open a dialog which allows him to change parameters the
> 'obvious' way.

Exactly!

This way, the user "only" has to learn a couple of actions, and will be able 
to do most stuff in Traverso, without the need to learn "advanced" key 
actions the first day!

> Remon, I think we could implement such a dialog for the fade regions in
> relatively short time, to see how it feels in real life.

A "proof of concept" dialog would be great!

For the future, I think we'll need a solid implementation for this dialog, so 
adding a new feature only requires to extend this dialog, and with minimal 
coding effort get it running!

Just like the un/redo framework has been implemented. Start creating only a 
few un/redoable Command classes, see how it evolves, refine the Command 
class, and once everything seems to be working, start adopting more of the 
edit command to the un/redo framework.

> The subject is open for discussion ;-)

It would be good to analyze some more "advanced" editing actions, not only the 
Fade in/out's and see what they have in common, where they differ, and how to 
handle this.
The end result has to be a set of JMB actions with a GUI which can be used by 
a multitude of advanced editing actions.


> regards

Thanks a lot for your input!

Remon