(In reply to comment #0)
> Please add more menus (which in effect provides keyboard access and if you make
> sure to dump a gtkrc file it also provides a way for users to setup custom
> keyboard shortcuts).

  What do you mean by "dump a gtkrc file" ?

>  Good menus can often bring out all the existing work
> which has been done and make it more easily discoverable for ordinary users.  

  Couldn't agree more.

> 
> For starters you might want to provide a "Control" menu with items for Play,
> Pause, Back, Forward, etc.  
> Also a view menu with a fullscreen options as well as options to show/hide
> certain user interface, or switch to certian Tabs could also help improve
> keyboard accessibility.   
> 
> I'll provide more detailed suggestions if you like but presumably you are
> borrowing some inspiration from other Video Editors and you already have plenty
> of ideas of your own.
> 

More suggestions are more than welcome.

(In reply to comment #1)

> > sure to dump a gtkrc file it also provides a way for users to setup custom
> > keyboard shortcuts).
> 
>   What do you mean by "dump a gtkrc file" ?

err my bad, terminology error that should have been menurc file, something like this:

  /* dump our applications menurc */
  gtk_item_factory_dump_rc ("~/.gnome2/accels/pitivi-menurc", NULL, TRUE);

> >  Good menus can often bring out all the existing work
> > which has been done and make it more easily discoverable for ordinary users.  
> 
>   Couldn't agree more.

Inkscape is a case in point.  

> > For starters you might want to provide a "Control" menu with items for Play,
> > Pause, Back, Forward, etc.  
> > Also a view menu with a fullscreen options as well as options to show/hide
> > certain user interface, or switch to certian Tabs could also help improve
> > keyboard accessibility.   
> > 
> > I'll provide more detailed suggestions if you like but presumably you are
> > borrowing some inspiration from other Video Editors and you already have plenty
> > of ideas of your own.
> > 
> 
> More suggestions are more than welcome.

The fancy usability term for looking at what others have done is "competative analysis".  My natural inclination is to embrace and extend, but many developers do not realise that most supposed innovations are merely recycled ideas with added polish and cheaper prices (especially in Microsoft case).  Sure it would be nice to do original research but it takes far less resources to "stand on the shoulders of midgets" ;) and it doesn't preclude doing more detailed research later.  

What I was hinting at in my earlier comments was if you were directly inspired by After Effects or some other application like iMovie or something, and if it might be useful to make suggestions on borrowing ideas from that software.  

I look forward to making many more suggestions when I've spent more time using Pitivi and comparing it to alternatives (and I'll try and read any mailing list archives or roadmap you might have because I'd rather not waste either your time or mine suggesting things you wont be interested in).  

Marking this as a blocker of the HIG compliance tracker bug

*** Bug 577390 has been marked as a duplicate of this bug. ***

I merged in support for menus today including:

* new menu layout (some existing items are in new locations now)
* all of the buttons on the toolbars have menu items
* you can now show/hide toolbars, (state is saved into configuration file)
* alternate menu command for adding files to timeline
* appropriate menu shortcuts for most actions

I haven't yet addressed menu shortcut configuration. All of the shortcuts are hard-coded at this point, and in some cases (such as with keyboard navigation), keyboard input is not actually handled through the menu accelerator mechanism, because it doesn't seem to support using unmodified arrow keys.