This document is licensed under the LGPL 2.1.

bzr branch lp:midori

The development trunk (master, tip) is the latest iteration of the next release. Browse it online and look for other branches at http://code.launchpad.net/midori or download a tarball of the latest revision.

The code used to be hosted in git.xfce.org/apps/midori.

Keep your copy updated:

bzr merge --pull

Join #midori on Freenode or use webchat to talk about Midori, discuss bugs and new ideas.

• Go through problem reports and check Unconfirmed bugs or those lacking information and mark any duplicates you spot
• Add a bounty for a feature or bug you'd like to support
• Translate to your own language

./waf configure --prefix=/usr
./waf build
sudo ./waf install

Midori can be run without being installed.

_build/default/midori/midori

You can use a temporary folder for testing without affecting normal settings

_build/default/midori/midori -c /tmp/midoridev

You'll want to unit test the code if you're testing a new version or contributed your own changes:

xvfb-run ./waf check

Automated daily builds in Launchpad (ppa:elementary-os/daily and ppa:midori/midori-dev) run these tests as well.

Testing an installed release may reveal crashers or memory corruption which require investigating from a local build and obtaining a stacktrace (backtrace, crash log).

_build/default/midori/midori -g [OPTIONAL ARGUMENTS]

If the problem is a warning, not a crash GLib has a handy feature

env G_DEBUG=all _build/default/midori/midori -g

For more specific debugging output, depending on the feature in question you may use

env MIDORI_DEBUG=help _build/default/midori/midori

Midori code should in general have:

• 4 space indentation, no tabs
• Between 80 to 120 columns
• Prefer /* */ style comments
• Call variables animal and animal_shelter instead of camelCase
• Keep a space between functions/ keywords and round parentheses

For Vala:

• Prefer new Gtk.Widget () over using Gtk; new Widget ()
• Stick to standard Vala-style curly parentheses on the same line
• Cuddled } else { and } catch (Error error) {

For C:

• Always keep { and } on their own line

Extensions may historically diverge from the standard styling on a case-by-case basis

Tell Bazaar your name if you haven't yet

  bzr whoami "Real Name <email@address>"

See what you did so far

  bzr diff

Get an overview of changed and new files

  bzr status

Add new files, move/ rename or delete

  bzr add FILENAME
  bzr mv OLDFILE NEWFILE
  bzr rm FILENAME

Commit all current changes - Bazaar automatically picks up edited files. If you're used to git, think of an implicit staging area.

  bzr commit -p

If you have one or more related bug reports you should pass them as arguments. Once these commits are merged the bug will automatically be closed and the commit log shows clickable links to the reports.

  bzr commit -p --fixes=lp:1111999

If you've done several commits

  bzr log | less
  bzr log -p | less

In the case you committed something wrong or want to ammend it:

  bzr uncommit

If you end up with unrelated debugging code or other patches in the current changes, it's sometimes handy to temporarily clean up. This may be seen as bzr's version of git stash.

  bzr shelve
  bzr commit -p
  bzr unshelve

Remember to keep your branch updated:

  bzr merge --pull

As a general rule of thumb, bzr help COMMAND gives you an explanation of any command and bzr help commands lists all available commands.

If you're a die-hard git user, checkout git-lp to use git commands with the Bazaar repository.

If you haven't yet, check that Launchpad has your SSH key - you can create an SSH key with Passwords and Keys aka Seahorse or ssh-keygen -t rsa - and use bzr launchpad-login to make youself known to bzr locally.

If you checked out trunk, and added your patch(es), just push it under your username in Launchpad and you can propose it for merging into trunk. This will automatically request a review from other developers who can then comment on it and provide feedback.

bzr push --remember lp:~USERNAME/midori/fix-bug1120383 && bzr lp-propose-merge lp:midori

lp-propose-merge command may not be working on some distributions like Arch or Fedora. In case you get error like bzr: ERROR: Unable to import library “launchpadlib”: No module named launchpadlib just use Launchpad's Web UI to propose a merge.

What happens to all the branches?

Leave the branches alone, approved branches are cleared automatically by Launchpad.

For larger feature branches, use the team in Launchpad to allow other developers to work on the code with you.

bzr push --remember lp:~midori/midori/featuritis && bzr lp-propose-merge lp:midori

What if I want to help out on an existing merge request that I can't push to?

bzr branch ~OTHERPERSON/midori/fix-bug1120383
cd fix-bug1120383
# make commits
bzr push lp:USERNAME~/midori/fix-bug1120383
bzr lp-propose-merge ~OTHERPERSON/midori/fix-bug1120383

Updating a branch that may be out of sync with trunk:

bzr pull
bzr: ERROR: These branches have diverged
bzr merge lp:midori
# Hand-edit conflicting changes
bzr resolve FILENAME
# If any conflicts remain continue fixing
bzr commit -m 'Merge lp:midori'

Save a little bandwidth, branch from an existing local copy that you keep around:

bzr branch lp:midori midori
bzr branch midori midori.fix-bug1120383
cd midori.fix-bug1120383
bzr pull lp:midori

As of Midori 0.5.4 the forumula will be:

• Required dependencies need to be available on the previous stable Fedora and Ubuntu
• For reference OpenBSD
• Windows XP through 8 are to date ABI compatible, all dependencies are included

When built with Granite (–enable-granite) there're a few key differences:

• Preferences uses a Granite.Widgets.StaticNotebook
• URL completion styling is slightly different
• Clear Private Data uses Granite.Widgets.LightWindow
• Edit Bookmark and Security Details use Granite.Widgets.PopOver instead of Gtk.Window
• Browser uses Granite.Widgets.DynamicNotebook instead of Gtk.Notebook

Midori for Windows is compiled on a Linux host and MinGW stack. For the current build Fedora 18 packages are used. Packages needed are listed below:

yum install gcc vala intltool

For a native build

yum install libsoup-devel webkitgtk3-devel sqlite-devel

For cross-compilation

yum install mingw{32,64}-webkitgtk3 mingw{32,64}-glib-networking mingw{32,64}-gdb

Packages needed when assembling the archive

 yum install faenza-icon-theme p7zip mingw32-nsis

Installing those should get you the packages needed to successfully build and develop Midori for Win32.

For 32-bit builds:

mingw32-env
./configure --enable-gtk3 --prefix=/usr/i686-w64-mingw32/sys-root/mingw/
make
sudo make install

For 64-bit builds:

mingw64-env
./configure --enable-gtk3 --prefix=/usr/x86_64-w64-mingw32/sys-root/mingw/
make
sudo make install

Once built and tested you can assemble the Midori archive with a helper script 32-bit build:

env MINGW_PREFIX="/usr/i686-w64-mingw32/sys-root/mingw" ./win32/makedist/makedist.midori

64-bit build:

env MINGW_PREFIX="/usr/x86_64-w64-mingw32/sys-root/mingw/" ./win32/makedist/makedist.midori x64

For testing your changes unfortuantely a real system is needed because Midori and WebKitGTK+ don't work properly under Wine. Even if it works some problems are not visible when using Wine, but are present when running under a real Windows system and vice versa.

One way around it is to virtualize Windows on a Linux host and mount your MinGW directories as a network drive or shared folder.

• freeze: the 4th week of a 4 week release cycle, bug fixes only
• MR: merge request, a branch proposed for review
• ninja: an internal tab, usually empty label, used for taking screenshots
• fortress: user of an ancient release like 0.4.3 as found on Raspberry Pie, Debian, Ubuntu
• katze, sokoke, tabby: API names and coincidentally cat breeds