Skip navigation.

Posts tagged with "configuration"

Kestrel's new shortcuts, why and what

, , , ...

Yippee, Kestrel's finally out. As buggy alpha for now, remember! You are best of testing this in a seperate installation, installing in a new directory does that trick. If you decide to upgrade, you really want to have a backup of mail (and bookmarks, wand, cookies etc if these are important for you).

Among many else, this release aims to become more usable out of the box. That means no surprising non-obvious shortcuts where you need to read the documentation to figure out how to get your normal browser back after pressing the wrong key by accident. Yes, this did happen. Quite a lot. Our Elektrans testers made it very clear that power users will dearly miss some of the one-key shortcuts like 1/2 for tab switching and z/x for navigation. So we've also thought of a way to ship with those power shortcuts in a forward-compatible manner (shipping with an extra 'classic' keyboard setup will bring problems for us later). You can find the new switch to turn these shortcuts on under 'Tools > Preferences > Advanced > Shortcuts'.

Now, what changes did we make, and why? There's a complete official list of changes available (edit: updated the link to point to the beta 2 version). And here's a list of reasons:

  • Several keyboard shortcuts have been changed or added for better cross-browser compatability.
  • All single letter and single number keyboard shortcuts have been removed. These one-key shortcuts are powerful, but also caused serious problems for many users. For most of them alternatives are available. They can also be switched on separately in the Preferences.
  • All Shift+letter and Shift+number keyboard shortcuts have been changed or removed for the same reasons.
  • All Alt+letter keyboard shortcuts have been changed or removed. These keyboard shortcuts are not compatible with many Opera localizations, because Alt+letter is used to access the main menu. Exceptions: Alt+P and the new Alt+D, both available for historical reasons. Preferred alternatives are available for the actions they perform.
  • All Ctrl+Alt+letter keyboard shortcuts have been changed or removed. Windows user interface guidelines reserve these shortcuts for system wide use and as alternative input method for some keyboards.
  • Keyboard shortcuts for seldomly used features have been removed, including two series of shortcuts that didn't show in the normal user interface: Ctrl+Shift+number shortcuts for 'manage' pages and Site Navigation keyboard shortcuts (think <link rel=home ...>)
  • Duplicated keyboard shortcuts that served no purpose anymore have been removed, those that were needed for compliance to operating systems guidelines have been made specific for those operating systems.

9.10 is final - and so is Hugin 2.5

, , , ...

Yippee, 9.10 is final. High time to update the downloadable custom setups I've made. I'll try to get this working with my.opera.com's system later, but for now I'll use my own webspace. First one:

Hugin 2.5
Hugin is a custom setup for a dedicated Mail & Chat client. It makes the power of M2 visible in menus and shortcuts and button - and makes it possible to keep mail and browsing separate processes, which has pros and cons. Normal browser functionality is mostly removed, so create a separate Opera installation for this one. You can open weblinks in a simple web tab. But you can also open them in your normal browser installation, with the link context menu. The toolbar and menu should both the installed for this setup to work!

Edit 2007-04-17: the links point to 9.2-compatible setups now





Mailto-to-webmail

, , , ...

[2008-09-26: updated to better show way to do this in 9.5]

For those of you who've switched to using web-based mail, it might not be intuitive how to use links with "mailto:" URLs. You'll have to change the handling of mailto-links, to pass the address to a webmail service, instead of a mail application on your computer.

In Tools > Preferences > Advanced > Programs, select 'mailto' and press 'Edit'. Enter 'opera' in the 'other application' field. Then use the addresses below to put in the 'Parameter' field:

Note: in Opera 9.2, you put both together in the single field, as in 'opera "http://etc"' (without the single quotes).

GMail
http://mail.google.com/mail/?view=cm&fs=1&to=%t&su=%s&body=%m&cc=%c&bcc=%b


Hotmail
http://hotmail.msn.com/cgi-bin/compose?To=%t&Subject=%s&Body=%m&Cc=%c&mailto=1


Yahoo Mail
http://compose.mail.yahoo.com/?To=%t&Subject=%s&Body=%m&Cc=%c


Netscape Mail
http://webmail.netscape.com/compose.adp?mailto=%t&mailcc=%c&mailsubject=%s&mailbody=%m


Mail.com
http://mail01.mail.com/scripts/mail/Outblaze.mail?composeto=%t&subject=%s&body=%m&cc=%c&compose=1


Opera Web Mail
http://mymail.operamail.com/scripts/mail/Outblaze.mail?compose=1&did=1&a=1&to=%t&subject=%s&body=%m&cc=%c


Horde
opera "http://YOUR_HordeURL_HERE.com/horde/imp/compose.php?popup=0&to=%t&cc=%c&msg=%m&subject=%s"


Squirrelmail
http://YOUR_SquirrelURL_HERE.com/src/compose.php?send_to=%t&subject=%s&body=%m&send_to_cc=%c


Generic
http://YOUR_URL_HERE/?To_Field=%t&Subject_Field=%s&Body_Field=%m&Cc_FLield=%c


Test: mailto-link
Button: toggle between M2 and webmail - in theory at least, this makes my Opera 9 crashy...

Tim writes about Site Specific Prefs in Opera 9

, , ,

This is an interesting read for those who want to enjoy Site Specific Prefs in Opera 9. In short, enjoy what we have now in Opera 9 (Tim explains why not all settings can be SSP right now), and look forward to improvements.

Always remember, the developers are not going home after 9.0 gets released, we are not Microsoft. There will be either a 9.1 or a 10.0.

Preview 2

, , ,

Lots of Opera folk writing about preview 2. Moose has a list of them. Especially nice (because he's a desktop developer!) is the new blog of Petter Nilsen (aka Mitchman), explaining how the new 'block content' feature works, among else.

Update:
Peter K about the changes in preferences settings: overrides.ini and override_downloaded.ini.

Battling Feature Anaemia

, , , ...

One of the core goals of Opera has always been to provide you, to our best approximation, with the browser that makes the web available to everyone, and to give anyone the most comfortable way to surf the web. The way we handle features and configuration follows the following approximate formula:

  • Normal browsing features: included, on by default
  • Comfort features: included, can be disabled from the UI
  • Features to make the web more accessible: feature included, UI to make use of feature might be second tier if it gets in the way for the majority that doesn't need it
  • Finetuning features: configurable via Advanced prefs (if a significant minority might find it useful) or by editing text-based ini files
  • Features to keep old users happy: feature included, disabled by default, configurable via UI or by editing text-based ini files


Note that "features to make the web more accessible" are not "bloat" or a "distraction for developers". Such features are very much needed for our mobile browsers, and it makes little sense to not make them available or try them out in the desktop version of Opera. Hence things like "Fit to window width" and "Voice". And from old times: disable image loading, plugins, javascript etc. In Opera 9 you will get site-specific preferences, to make it easier to use the accessiblity options when necessary, and use the web as the authors intended by default. Or the other way around! To keep a sane and understandable interface, not all preferences can be made site-specific in 9.0. Experience and feedback will tell how the UI will need to improve or make more or less prefs available in this context.

"Editing text-based ini files" can be somewhat hard to explain to potential power users. Opera 9 will include a built-in editor for opera6.ini to make this easier. Of course we can have long discussions about what the default settings should be, and which settings should be delegated to opera.ini. The built-in editor is not meant as a alternative interface for the Preferences, so the latter should contain all the things a 'normal' user might want to change once in a while.

This posting is inspired by Firefox developer Ben's latest post Battling Firefox Bloat. The problem I have with the Firefox philosophy: almost everyone is a member of a minority, and usually member of a few minorities. So with Firefox, everyone has to manage a set of extensions for necessary (for them) features or nice-to-have comfort features like "Mouse gestures" and "Paste and Go".

And it has become clear that you can not trust the extension developers to stay passionately involved over many years, so it can be days or months after installing a new Firefox version before it is working again as it used to do. Opera's text-based ini files can be a bit more clunky to work with, and less powerful, but the advantage is that anyone with a text editor can find out how to do it. To write an Firefox extension, you need to know a fair bit of JavaScript at least, if not XUL.

Update: also read David Baron's concerns about Firefox maybe relying too much on extensions.

Merlin: shortcuts and buttons for all settings

, , ,

In Merlin, you can use opera:config to directly change all available settings. But it is still a chore if you want to do this regularly, for example to toggle User JavaScript on and off. So Merlin also introduces an action for shortcuts and buttons, that makes a direct change in your settings. This means you don't have to wait for Opera's developers to add specific actions.
Moose gives a nice example of this new feature in Opera 9 (Merlin):
Set preference, "User Prefs|User JavaScript=1" | Set preference, "User Prefs|User JavaScript=0"

  • Action name: Set Preference
  • First parameter: "Section|Prefs parameter" (as they appear in opera6.ini)
  • Second parameter: not used

This can be used in custom keyboard shortcuts, mouse gestures, voice commands, buttons, and in custom menu setups.

Note: this is a new action that has not been thoroughly tested yet (apart from the one example here :smile: ). So your feedback is welcome

Try the 'Opera Tools' apps

, , , ...

MyOpera regular Diplo today released his Opera Tools. These tools, combined with a tweaked menu setup, give a proper GUI to two features of Opera 8, that normally require editing of ini files: URL filtering and server-specific UA spoofing.

The readme file in the package tells all you need to know. For those that want to incorporate the tool in their already customized setup, it is accessed using this menu item:

Item, "Add to Block List" = Copy image address & Execute program,"C:\Program Files\OperaTools\OperaAdBlock.exe", "C:\Documents and Settings\USERNAME\Application Data\Opera\Opera8\profile\filter.ini"

and
Item, "Identify As..." = Copy document address & Execute program, "C:\Program Files\OperaTools\OperaUAEditor.exe", "C:\Documents and Settings\USERNAME\Application Data\Opera\Opera8\profile\ua.ini"


This obviously needs editing to get the paths right.

All the files used by Opera 8.01 explained

, , ,

Finally: an update for the Files Used by Opera document. This was created for Opera 6, and is now updated to reflect the Profile system, M2 files, etc. Comments are welcome.

After this and the updated opera.ini documentation, what other documentation are tweakers waiting for?

Tweakers delight: opera6.ini

, , ,

Finally! The opera6.ini documentation has been updated for Opera 8. As the old docs where valid for Opera 5 only, this is great news. No more searching in a gazillion changelogs to find newly added entries, etc. Thanks to Jorunn and Nafmo!

As a bonus, there is also an updated and improved sysadmin handbook (with for example info on 'fixed' ini settings) and command line switches for Opera for Linux and Opera for Windows.

Migration guide

, ,

Opera's Knowledge base now has a nice article about the changes you'll encounter when upgrading from Opera 7.x to Opera 8. Recommended reading for all power users that didn't closely follow the preview/beta developments. So read the Migration Guide.

Search.ini update

, ,

Opera offers several search options and related resources like translations and dictionary lookups. Some of the searches will provide Opera ASA with a little money. As URLs can change, and contracts can expire, Opera needs to be able update the searches and search URLs. It is of no use if you have an Ebay search on your Personal bar, and Ebay changes it's URL or contract with Opera so the search doesn't work anymore.

Opera uses a separate file to store the necessary information: search.ini. This file is copied to Profile directories, because different profile users can choose different searches to show on the personal bar. This file has a version number, so when you install a new version of Opera the installer can see if you are using a version that is up to date. Opera 8 will have some updates, and the version number of search.ini will incremented to 5. Existing search.ini files will be backed up (renamed search.bak) and replaced with the newer version.

Tweakers have of course found out that you can manually edit search.ini and so add searches. Nontroppo's wiki has a whole section dedicated to it. Everyone who tweaked search.ini and installs new versions should consider these options:

  • manually compare the new search.ini and their old search.bak, and edit the new search.ini to incorparate the tweaks again
  • change the version number of their search.ini before upgrading, thereby preventing the replacement with the newer search.ini, and manually check to see whether the URLs in their tweaked search.ini that came from the official search.ini still work


To help with this, here are the changes since version 4:

  • new entry 'Opera web search'
  • new URL for Ebay search
  • redirector URLs are now used for encyclopedia and dictionary and many translations, to prevent the URLs from going stale

About user scripts in beta 3

, , , ...

NOTE: I've made a webpage now to present the user.js framework script. See <http://people.opera.com/rijk/opera/userjs.html>

Hallvord introduced Opera's latest surprise for tweakers in his Journal.

What is a user script

Basically it is a script from a local file that gets executed before any other scripts (or event handlers) on the page, once in every document.

I've collected some more or less interesting scripts that I'd like to run on all pages, and on specific sites, in this user script: <http://people.opera.com/rijk/opera/scripts/user.js>. I'm not yet using any versioning there BTW, it can be a different script tomorrow, or in an hour. The script is set up to easily add extra functions, and enable/disable them for all or for specific sites when you want. Don't expect me to explain specific functions, because I'm not a proficient JavaScripter myself. I'd say: experiment, share, and file bug reports if necessary.

Enabling user script in Opera 8 beta 3

[User Prefs]
User Javascript=1
User Javascript File=C:Program FilesOperauserjs.js

Security

The script has exactly the same restrictions as a script on the page, except that it can access some User JS specific functionality (we'll get back to you on that) and that it can read the text property on any script element (normal scripts can't read the text property of external scripts loaded from other servers than the document.)

The additional privileges are available when the User JS file is initially executed and when a User JS event is being handled. Global functions defined by User JS but called from a script in the page have no special privileges.

Voice and Sounds enabled. And Nicklas.

, ,

Some people expressed their surprise when they learned that Opera 8 beta needs to have 'Sounds in webpages' enabled for the new 'Voice' functionality to work. But they should realise that the Voice implementation in Opera is interactive. I've now added a Voice intro to my webpage to show that it can be annoying:
http://people.opera.com/rijk/opera/

Something else: one of my esteemed Swedish collegues, Nicklas Larsson, has started some serious blogging this year. Nine posts so far, one for each day!
http://my.opera.com/Kilsmo/journal

How to change the place where Opera stores your data

,

edited October 20 2007 to be more complete
edited June 30 2008 to add 9.5 changes

To move from a multi-user to a single-user setup
  1. take note of the current locations shown in 'Help > About Opera' [1]
  2. close Opera
  3. open 'OperaDef6.ini' from the main Opera folder (where opera.exe can be found) in a plain text editor like Notepad
  4. change the line 'Multi-user=1' to 'Multi-user=0'
  5. save and close 'OperaDef6.ini'
  6. copy the Profile and Mail folder from the 'Documents and settings' folder to the main Opera folder
  7. 9.5: copy the contents of both Profile folders [1] to the profile folder you create under the main Opera folder
  8. 9.5: doublecheck whether your mail data was stored under '\Local settings\Application data' (the new default location) or '\Application data' (the old default location)
  9. open 'opera6.ini' from the newly created Profile folder in a plain text editor
  10. update all the file paths you find there to match the new location
  11. save and close 'opera6.ini'
  12. done


To move from a single-user to a multi-user setup
  1. take note of the current locations shown in 'Help > About Opera'
  2. close Opera
  3. open 'OperaDef6.ini' from the main Opera folder in a plain text editor
  4. change the line 'Multi-user=0' to 'Multi-user=1'
  5. save and close 'OperaDef6.ini'
  6. start Opera, this should give you clean new profile folders under the 'Application data' folders for the current user
  7. take note of the current locations shown in 'Help > About Opera' [1]
  8. close Opera
  9. copy the Profile and Mail folders from the main Opera folder to the noted new directories, replacing the newly created profile files (these can be overwritten)
  10. 9.5: note that the profile subfolders 'bt_metadata', 'cache4', 'images', 'opcache', 'voicelib', 'vps' will go to the profile folder under '\Local settings\Application data'
  11. 9.5: note that the Mail folder will also go under '\Local settings\Application data'
  12. open 'opera6.ini' from the new Profile folder in a plain text editor
  13. update all the file paths you find there to match the new locations
  14. save and close 'opera6.ini'
  15. done


To move to a setup with the profile data saved in a random location
  1. take note of the current locations shown in 'Help > About Opera'
  2. close Opera
  3. copy the Profile and Mail folders from the 'Documents and settings' folder to your chosen locations
  4. open 'opera6.ini' from the Profile folder in a plain text editor
  5. update all the file paths you find there
  6. save and close 'opera.ini'
  7. create a shortcut with this commandline:
    "C:\Program files\Opera\opera.exe" /settings "{path to profile folder}\opera6.ini"
    ... of course, using you chosen locations.
  8. done


[1] Default folder locations for multi-user installations when using Windows XP
  • main (installation) folder is likely 'C:\Program files\Opera\'
  • profile folders can likely be found at 'C:\Documents and settings\username\Application data\Opera\Opera\profile\' and 'C:\Documents and settings\username\Local Settings\Application data\Opera\Opera\profile\' (the latter are used by 9.5 installations for data not suited for inclusion in a roaming profile)
  • mail directory is likely either 'C:\Documents and settings\username\Application data\Opera\Opera\mail\' or 'C:\Documents and settings\username\Local Settings\Application data\Opera\Opera\mail\' depending on whether you started with 9.5 or an earlier Opera version.


Using 'browser.css' and 'user.css' in Opera 7.5 for non-geeks

, , , ...

Quick tutorial on using 'browser.css' and 'user.css' in Opera 7.5. This is meant as an introduction for people not well versed in CSS.

  • A file stored as 'browser.css' in the directory \Profile\styles will be used to override browser default styling (and also author styling if you add '!important' to a rule); it will always be applied. Changes in browser.css need a restart before becoming effective.
  • You can also create a 'user.css' file. You can control when to apply it with the settings under 'Tools > Preferences > Page Style > Configure modes' and Ctrl+G (Shift+G in Opera 8 and higher).
  • See 'Help > About Opera' to locate you Profile directory.
  • CSS files are rulesets stored as plain text files, easily created with, for example, Notepad.
  • CSS rules consists of 'selectors', which select a piece of the HTML document to work on, and 'declarations' that say how to style that piece. Declarations consist of one or more 'property:value' pairs.
  • * is the universal selector.


Here are some examples of a css rules to put in either browser.css or user.css files. You just put them after each other in the css file.

Rule to fix the font face

 * {font-family: "Trebuchet MS", Arial !important;}
 pre, code, tt, kbd {font-family: "Andale Mono", "Courier New" !important;}


Or leveraging your settings for 'Generic CSS font families':

 * {font-family: sans-serif !important;}
 pre, code, tt, kbd {font-family: monospace !important;}


Rules that fix font size
With some inflexible pages, this can lead to uglier display as text overflows too narrow boxes.

 * {font-size: 16px !important;}
 big {font-size: 18px !important;}
 small {font-size: 14px !important;}
 h1 {font-size: 26px !important;}
 h2 {font-size: 22px !important;}
 h3 {font-size: 20px !important;}
 h4 {font-size: 18px !important;}
 h5, h6 {font-size: 16px !important;}


Rules that fix colors

 * {color: black !important; background: white !important;}
 a:link {color: blue !important; background: white !important;}
 a:visited {color: purple !important; background: white !important;}
 a:active, a:hover {color: red !important; background: white !important;}


More info can be found at <http://nontroppo.org/wiki/OperaUserCSS>
November 2009
S M T W T F S
October 2009December 2009
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30