guake 3.0.0.0b2

Request Features

Please vote for feature on FeatHub <http://feathub.com/Guake/guake>. Open Issues on GitHub only for bug reports.

Most requested features list for Guake:

Dropped Features from Guake 0.8.x

• --bgimg (this option has been removed from vte)

New Dependencies

• libkeybinder3

Guake 3 Features

• Lightweight

• Simple Easy and Elegant

• Smooth integration of terminal into GUI

• Appears when you call and disappears once you are done by pressing a predefined hotkey (F12 by default)

• Compiz transparency support

• Multi tab

• Plenty of color palettes

• Quick Open in your favorite text editor with a click on a file name (with line number support)

• Customizable hotkeys for tab access, reorganization, background transparency, font size,…

• Extremely configurable

• Configure Guake startup by running a bash script when Guake starts

• Multi-monitor support (open on a specified monitor, open on mouse monitor)

• Save terminal content to file

• Open URL to your browser

Bugs? Information?

Source Code available at: https://github.com/Guake/guake/

Official Homepage: http://guake-project.org

Important note: Do NOT use the domain guake.org, it has been registered by someone outside the team. We cannot be held responsible for the content on that web site.

Note for maintainers

Guake has drastically changed its build system with Guake 3. You may need to adapt all the integration scripts accordingly.

Guake now uses Pipfile to store it Python dependencies (except the system dependencies such as PyGTK3). It is maintained and used by pipenv CLI tool. It is a system more advanced than using requirements.txt, but this file is still generated for backward compatibility (for example: ReadTheDocs only support requirements.txt for the moment), by a tool I’ve developed, named pipenv_to_requirements (makefile target make requirements). It does generate requirements.txt (running dependencies), and requirements-dev.txt (build, checks and test only). From then, Guake is now a classic, canon Python package (with setup.py, building distrubution packages, …).

It however requires system libraries, so cannot work isolated inside a virtualenv. If you look closer to the virtualenv used with make dev ; make run, you will see it is configured to use the system libraries using pew toggleglobalsitepackages.

If for any reason pipenv does not work on your platform, you can still install guake from these requirements file, but the ultimate source of truth for dependency declaration is the Pipfile.

Do not hesitate to contact me at gaetan [at] xeberon.net.

Install System dependencies

Ubuntu

Execute the following command to bootstrap all needed system dependencies:

$ ./bootstrap-debian.sh

Setup development env

Install the dependencies of your system and use the following commands:

$ make dev
$ sudo make install-schemas  # still required even for local execution

Local execution of guake (without system-wide install):

$ make run

$ make setup-githook

$ make style  # fix the style of python files
$ make check  # static code analysis
$ make test   # unit test campaign
$ make dists  # make distribution packages

Update translation

Update all translation files:

$ make update-po

Install the translations files:

$ sudo make install-locale

Then use your favorite po editor, such as poedit.

Update NEWS

Update the NEWS file using the followng command:

make release-note-news

The ChangeLog files is not maintained but instead automatically generated by PBR when building the distribution packages.

Same goes for the ChangeLog file.

Versionning

Versioning is automatically done using git tags. When a semver tag is pushed, a new version is automatically created by PBR.

Travis build

Travis automatically check pull requests are compiling and check for code style.

Status of the master branch: https://travis-ci.org/Guake/guake.png?branch=master