After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 352402 - [menu] save/export video button/menu
[menu] save/export video button/menu
Status: RESOLVED DUPLICATE of bug 421652
Product: pitivi
Classification: Other
Component: User interface
Git
Other Linux
: Normal normal
: Git
Assigned To: Pitivi maintainers
Pitivi maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-22 14:33 UTC by Edward Hervey
Modified: 2007-04-23 11:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Add export option to menu. (3.26 KB, patch)
2006-09-24 19:56 UTC, Scott Shawcroft
none Details | Review

Description Edward Hervey 2006-08-22 14:33:29 UTC
From wiki : Feedback_Features

The record button /project video saving

A save video option under File is probabily more logical and easier for new users to understand. As it stands, users need to click on the drop down box, select the Project: [Name] option to even be able to record, which again is rather confusing.
Comment 1 Scott Shawcroft 2006-09-24 19:56:46 UTC
Created attachment 73338 [details] [review]
Add export option to menu.

This adds the export functionality to the menu.  It also raises the issue of where callbacks should be stored because it should access the same callback function as the record function in the viewer.  However, as it is now the viewer is created after the actions are set.
Comment 2 Edward Hervey 2006-11-28 16:36:57 UTC
the callbacks for when a menu item is clicked, or a UI button is clicked, should be in the class where those items belong too.
The issue is that they should call a common method/function.
I'm figuring out where's the best place to store that.

Also, the Export project menu item shouldn't be available if there's no sources in the project.
Comment 3 Edward Hervey 2006-11-28 16:39:46 UTC
In fact.. there should be a widget-agnostic class for the UI, where we could store all those functionnalities. This would:
1/ ease create other widget UIs (think qt, win, ...)
2/ solve the issue of where to store all those common methods
Comment 4 Edward Hervey 2007-04-23 11:32:31 UTC

*** This bug has been marked as a duplicate of 421652 ***