My OperaThe My Opera forums have been replaced with forums.opera.com. Please head over there to discuss Opera's products and features
See the new ForumsYou need to be logged in to post in the forums. If you do not have an account, please sign up first.
Move configuration folder to .config on *nix
Opera stores it's configuration on *nix in $HOME/.opera. With the advent of widgets, we get additional folders $HOME/.opera_widgets and $HOME/.opera_widget_installer, plus at least on one of my computers I get one folder $HOME/.opera-widget-<widget-name> for every widget I have installed, giving me 9 opera configuration folders in my home directory. This is messy and unnecessary.Please move configuration to:
$XDG_CONFIG_HOME/opera (defaults to $HOME/.config/opera)
$XDG_CONFIG_HOME/opera/widgets
$XDG_CONFIG_HOME/opera/widgets/<widget-name>
as per Freedesktop standards. Or, if for some reason widget configuration should not reside in Opera's config folder, at least put everything into $XDG_CONFIG_HOME instead of $HOME.
I shot the serif.
In the .opera folder not only the configuration is stored but also other stuff (eg. email store), and for widgets it's the whole widget (code and all), so "config" would be even more wrong imo.
All my posts only represent my own opinions.
[ Tweedo Monitor - Deluxe Website & Service Monitoring ]
[ Tweedo Monitor - Deluxe Website & Service Monitoring ]
Good point, I forgot about that one, but not a problem, I think.
a) Since Opera's config folder is irregluar anyway, one can go the easy way and just put everything in .config, then at least MOST of the stuff is in the right place, and we cut down on home-clutter.
b) If one invests a bit more work, one can do it properly (see http://standards.freedesktop.org/basedir-spec/basedir-spec-0.6.html ):
configuration in $XDG_CONFIG_HOME/opera ($HOME/.config/opera).
mail and other user data in $XDG_DATA_HOME/opera ($HOME/.local/share/opera).
cache in $XDG_CACHE_HOME/opera (/$HOME/.cache/opera)
There remains the problem of widgets.
Their configuration can be in $XDG_CONFIG_HOME/<widget_name>, their user data in $XDG_DATA_HOME/<widget_name>. That's the easy part.
Their program code (which resides in $HOME/.opera-widgets, if I interpret it's contents correctly), however, should not be there at all, but be installed as a package or to /usr/local or /opt or whatever.
Since that is obviously impractical, I say the best way to do it is treat them as plugins for opera and leave them completely in some sensible subfolder of Opera's folders.
a) Since Opera's config folder is irregluar anyway, one can go the easy way and just put everything in .config, then at least MOST of the stuff is in the right place, and we cut down on home-clutter.
b) If one invests a bit more work, one can do it properly (see http://standards.freedesktop.org/basedir-spec/basedir-spec-0.6.html ):
configuration in $XDG_CONFIG_HOME/opera ($HOME/.config/opera).
mail and other user data in $XDG_DATA_HOME/opera ($HOME/.local/share/opera).
cache in $XDG_CACHE_HOME/opera (/$HOME/.cache/opera)
There remains the problem of widgets.
Their configuration can be in $XDG_CONFIG_HOME/<widget_name>, their user data in $XDG_DATA_HOME/<widget_name>. That's the easy part.
Their program code (which resides in $HOME/.opera-widgets, if I interpret it's contents correctly), however, should not be there at all, but be installed as a package or to /usr/local or /opt or whatever.
Since that is obviously impractical, I say the best way to do it is treat them as plugins for opera and leave them completely in some sensible subfolder of Opera's folders.
I shot the serif.
seems somebody really thought this through All my posts only represent my own opinions.
[ Tweedo Monitor - Deluxe Website & Service Monitoring ]
[ Tweedo Monitor - Deluxe Website & Service Monitoring ]