QMC2 0.1 beta 11 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News QMC2 0.1 beta 11 (Default branch)
# 1  
Old 12-27-2007
QMC2 0.1 beta 11 (Default branch)

Image M.A.M.E. Catalog / Launcher II (also referred to as QMC2) is the successor of one of the first XMAME GUI frontends available, QMamecat (derived from MAMECAT, which was text-only). QMC2 has been rebuilt from scratch as a Qt 4 project. Parts of the design and code were inspired by its predecessor. The new design was made as flexible as possible to minimize dependencies from frontend- and CLI-related MAME changes, which was a major deficiency of QMamecat. QMC2 uses a template-based MAME configuration scheme, which can easily be enhanced with additional command line options (defined in an XML template file). License: GNU General Public License v2 Changes:
This release includes a lot of bugfixes, some major improvements, and many new and important features. The most important ones are import and export of global and game-specific MAME configurations, PNG game icons, support for BIOS ROMs, a game list cache that gives a tremendous speed-up at reload, support for alternative image sets, and a shortcut and GUI control key remapper.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
ARCHPATH(1)                                                   General Commands Manual                                                  ARCHPATH(1)

NAME
archpath - output arch (tla/Bazaar) archive names, with support for branches SYNOPSIS
archpath archpath branch archpath branch--version DESCRIPTION
archpath is intended to be run in an arch (tla or Bazaar) working copy. In its simplest usage, archpath with no parameters outputs the package name (archive/category--branch--version) associated with the working copy. If a parameter is given, it may either be a branch--version, in which case archpath will output a corresponding package name in the current archive and category, or a plain branch name (without '--"), in which case archpath will output a corresponding package name in the current archive and category and with the same version as the current working copy. This is useful for branching. For example, if you're using Bazaar and you want to create a branch for a new feature, you might use a com- mand like this: baz branch $(archpath) $(archpath new-feature) Or if you want to tag your current code onto a 'releases' branch as version 1.0, you might use a command like this: baz branch $(archpath) $(archpath releases--1.0) That's much easier than using 'baz tree-version' to look up the package name and manually modifying the result. AUTHOR
archpath was written by Colin Watson <cjwatson@debian.org>. Like archpath, this manual page is released under the GNU General Public License, version 2 or later. DEBIAN Debian Utilities ARCHPATH(1)