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 498906 - Save and load settings using a file in ~/.pitivi/
Save and load settings using a file in ~/.pitivi/
Status: RESOLVED DUPLICATE of bug 335547
Product: pitivi
Classification: Other
Component: General
Git
Other Linux
: Normal enhancement
: Git
Assigned To: Brandon Lewis
Pitivi maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-22 05:19 UTC by Tommy
Modified: 2009-02-12 03:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
patch to enable load/save of settings to a file in ~/.pitivi/ (6.55 KB, patch)
2007-11-22 05:21 UTC, Tommy
none Details | Review

Description Tommy 2007-11-22 05:19:47 UTC
I quickly wrote a patch for the settings object which allows it to load settings from a file, and write them back to the file on shutdown.

It uses python's standard ConfigParser module, making a file which is easily modifiable by hand.

I didn't put anything in place to handle plugin settings but it'd be straightforward to do.
Comment 1 Tommy 2007-11-22 05:21:17 UTC
Created attachment 99463 [details] [review]
patch to enable load/save of settings to a file in ~/.pitivi/

filename is currently hardcoded to "pitivi.conf", section name for general settings is "pitivi-main"
Comment 2 Elisée Maurer 2008-10-29 22:32:15 UTC
I think PiTiVi might want to follow xdg base directory specification ( http://standards.freedesktop.org/basedir-spec/basedir-spec-0.6.html ) for storing settings. It's trivial to implement and help users keep a clean home directory.
Comment 3 Jean-François Fortin Tam 2009-01-22 17:18:20 UTC
duplicate of bug #335547 ?
Comment 4 Brandon Lewis 2009-02-03 04:04:52 UTC

*** This bug has been marked as a duplicate of 335547 ***
Comment 5 Brandon Lewis 2009-02-12 03:55:11 UTC
I'm starting a configuration branch based on these changes (but heavily modified at this point).