Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
pitivi
pitivi
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 198
    • Issues 198
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 33
    • Merge Requests 33
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOME
  • pitivipitivi
  • Issues
  • #1303

Closed
Open
Created Feb 07, 2013 by bugzilla-migration@bugzilla-migrationReporter

Kill application.py, port to GTK Application

Submitted by Jeff F.T. @jeff

Assigned to Alex Băluț @aleb

Link to original bug (#3016)

Description

I've been pondering for a while killing Pitivi's menu bar and using Gtk's appmenu. This would allow better integrating with GNOME Shell and other platforms, eliminate redundancy and save screen space (because the application could now be undecorated when maximized, as first suggested in bug #T2954).

Most of our menu items are either duplicates of what we have in toolbars, or could be moved to a GtkApplication menu.

Some items would probably need to be moved elsewhere in the UI:

  • “Revert to saved” could become a full-fledged main toolbar button.

  • "Export as archive" → “Gear” menu

  • Detach/Attach viewer → Make it a button in the viewer’s toolbar

  • Save snapshot of the current image → “Gear” menu

  • Keyframe actions: they should be contextual anyway. Either in the effect properties UI, or appearing temporarily in the timeline toolbar (to avoid visual clutter). Will depend on someone actually implementing the keyframe UI.

  • "Remove layer": kill the menu item, leave the contextual menu, and replace the main interaction by “drag the layer out of the screen or into the media library”? That one is going to depend on our port to a clutter timeline/some other expert than me.

I'm left wondering about the relevance of a "gear" menu (à la Chromium/Epiphany/Nautilus), given that GTK's toolbars will automatically create a "dropdown" arrow if it can't fit all items on the screen...

Imported from https://bugzilla.gnome.org/show_bug.cgi?id=693291

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None