Source / thg / manual / 2.4-ja / whatsnew.html

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

<html xmlns="">
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <title>3. 最新情報 &mdash; TortoiseHg 2.4.0 documentation</title>
    <link rel="stylesheet" href="_static/default.css" type="text/css" />
    <link rel="stylesheet" href="_static/pygments.css" type="text/css" />
    <script type="text/javascript">
        URL_ROOT:    '',
        VERSION:     '2.4.0',
        COLLAPSE_INDEX: false,
        FILE_SUFFIX: '.html',
        HAS_SOURCE:  true
    <script type="text/javascript" src="_static/jquery.js"></script>
    <script type="text/javascript" src="_static/underscore.js"></script>
    <script type="text/javascript" src="_static/doctools.js"></script>
    <script type="text/javascript" src="_static/translations.js"></script>
    <link rel="top" title="TortoiseHg 2.4.0 documentation" href="index.html" />
    <link rel="next" title="4. TortoiseHg クイックスタート" href="quick.html" />
    <link rel="prev" title="2. 導入" href="intro.html" /> 
    <div class="related">
        <li class="right" style="margin-right: 10px">
          <a href="genindex.html" title="総合索引"
        <li class="right" >
          <a href="py-modindex.html" title="Pythonモジュール索引"
             >モジュール</a> |</li>
        <li class="right" >
          <a href="quick.html" title="4. TortoiseHg クイックスタート"
             accesskey="N">次へ</a> |</li>
        <li class="right" >
          <a href="intro.html" title="2. 導入"
             accesskey="P">前へ</a> |</li>
        <li><a href="index.html">TortoiseHg 2.4.0 documentation</a> &raquo;</li> 

    <div class="document">
      <div class="documentwrapper">
        <div class="bodywrapper">
          <div class="body">
  <div class="section" id="module-whatsnew.dialog">
<span id="id1"></span><h1>3. 最新情報<a class="headerlink" href="#module-whatsnew.dialog" title="このヘッドラインへのパーマリンク"></a></h1>
<div class="section" id="tortoisehg-2-0">
<h2>3.1. TortoiseHg 2.0<a class="headerlink" href="#tortoisehg-2-0" title="このヘッドラインへのパーマリンク"></a></h2>
<div class="section" id="id2">
<h3>3.1.1. 方針<a class="headerlink" href="#id2" title="このヘッドラインへのパーマリンク"></a></h3>
<p>以下の方針転換が TortoiseHg 1.0 と TortoiseHg 2.0 の間に行われました。</p>
<div class="section" id="id3">
<h4> ワークベンチ<a class="headerlink" href="#id3" title="このヘッドラインへのパーマリンク"></a></h4>
<p>We wanted a single &#8216;TortoiseHg&#8217; application which can access nearly all
TortoiseHg (and Mercurial) functionality and that could be launched by a
desktop or start menu shortcut.  So we developed the Workbench
<p>The Workbench can support multiple repositories open at a time via &#8220;Repo
Tabs&#8221; across the top of the main window.</p>
<p>Each repository tab supports multiple &#8220;Task Tabs&#8221; beneath its graph
splitter.  These task tabs are switchable via icons on the side of
the Workbench or via application menus.  Available task tabs include a
changeset browser, a commit tool, a manifest browser, a history search
widget, and a sync widget.</p>
<p>Also available are two dockable widgets - a <em>Repository Registry</em> which
lists all known repositories on your local machine and an <em>Output Log
Window</em> which displays running command lines and their output and can
also function as a minimal shell.</p>
<div class="section" id="mercurial">
<h4> Mercurial コマンドラインの表示<a class="headerlink" href="#mercurial" title="このヘッドラインへのパーマリンク"></a></h4>
<p>In an effort to educate users on Mercurial&#8217;s command interface, nearly
all commands are executed in the log window, displaying the full command
line and Mercurial&#8217;s output (progress indication is provided by progress
bars inside the Workbench status bar).  The few tools that do not use a
command log window will generally display the command line they execute.</p>
<div class="section" id="resolve-tool-deliberate-merges">
<h4> Resolve tool, deliberate merges<a class="headerlink" href="#resolve-tool-deliberate-merges" title="このヘッドラインへのパーマリンク"></a></h4>
<p>TortoiseHg 2.0 introduces a resolve dialog for resolving conflicted
file merges.  It shows the users all the files that require resolution
and those files that have been resolved, allowing merges to be verified.</p>
<p>As supported by Mercurial&#8217;s resolve command, individual file merges may
be restarted as many times as necessary to get the merge correctly
<p>By default, TortoiseHg will use the resolve dialog to resolve all
conflicts, including trivial conflicts.  It instructs Mercurial to never
merge files automatically, deferring their resolution until the resolve
dialog can be launched.  This is true for merges, update commands that
require content merges, rebases, and backouts.</p>
<div class="section" id="shelve-improved">
<h4> Shelve Improved<a class="headerlink" href="#shelve-improved" title="このヘッドラインへのパーマリンク"></a></h4>
<p>TortoiseHg 2.0 includes a new shelve tool which is capable of moving
changes between your working directory, a shelf file, or an unapplied MQ
<div class="section" id="revision-sets">
<h4> Revision Sets<a class="headerlink" href="#revision-sets" title="このヘッドラインへのパーマリンク"></a></h4>
<p>We have replaced the filter bar of the Repository Explorer with a
revision set bar in the Workbench.  Revision sets were introduced in
Mercurial 1.6 and have been integrated with an increasing number of
commands in each subsequent release.  They are a powerful query language
for finding and specifying revisions in your repository.</p>
<p>The Workbench also includes a revision set editor which both teaches the
user the available keywords and their arguments, and offers brace
matching, auto-completions, and other editing amenities.</p>
<p>In TortoiseHg 2.0, incoming and outgoing changesets are visualized as
revision sets.  In previous versions they were represented by graph
<div class="section" id="technology">
<h3>3.1.2. Technology<a class="headerlink" href="#technology" title="このヘッドラインへのパーマリンク"></a></h3>
<div class="section" id="qt-and-pyqt">
<h4> Qt and PyQt<a class="headerlink" href="#qt-and-pyqt" title="このヘッドラインへのパーマリンク"></a></h4>
<p>TortoiseHg 2.0 has been a near rewrite of all of the tools and dialogs
taking advantage of Nokia&#8217;s excellent <a class="reference external" href="">Qt</a>
UI framework and Riverbank Computing&#8217;s fine
<a class="reference external" href="">PyQt</a> Python
<div class="section" id="qscintilla2">
<h4> QScintilla2<a class="headerlink" href="#qscintilla2" title="このヘッドラインへのパーマリンク"></a></h4>
<p>TortoiseHg uses the <a class="reference external" href="">QScintilla2</a>
editing component extensively to:</p>
<ul class="simple">
<li>display file contents and diffs with syntax highlighting</li>
<li>display annotations with syntax highlighting</li>
<li>edit commit messages with auto-completion of filenames and source symbols</li>
<li>edit revision set strings with brace matching and auto-completion</li>
<p>One can configure the QScintilla2 tab stop parameter using the settings
tool, while white space visibility and wrap are controlled by context
<div class="section" id="polling-of-repository-state-and-config">
<h4> Polling of repository state and config<a class="headerlink" href="#polling-of-repository-state-and-config" title="このヘッドラインへのパーマリンク"></a></h4>
<p>The Workbench and other applications like the commit tool will poll
repositories on your local machine to detect changes made to either the
repository or their configuration files, and automatically update
running applications as necessary.  Nearly all configuration changes are
effective immediately, with the notable exception of enabling or
disabling Mercurial extensions.  Changes to extension configuration
generally require application restarts before they take effect.</p>
<div class="section" id="immediate-bug-report-dialogs">
<h4> Immediate bug report dialogs<a class="headerlink" href="#immediate-bug-report-dialogs" title="このヘッドラインへのパーマリンク"></a></h4>
<p>Prior to TortoiseHg 2.0, bug reports were written to stderr as they
occured and stderr was captured and scanned at exit to report those
errors to the user.  While we gained many valuable bug reports via this
mechanism, there was rarely any context on what operations caused these
<p>In TortoiseHg 2.0, we have created a generic exception handler that
catches all Python exceptions that are otherwise unhandled by
application code.  This allows us to display exception tracebacks almost
immediately after they occur (after a short timeout to collect
consecutive exceptions together).  The hope is that future bug reports
will contain better reproduction instructions, or at least context for
the tracebacks.</p>
<div class="section" id="demand-loaded-graph">
<h4> Demand loaded graph<a class="headerlink" href="#demand-loaded-graph" title="このヘッドラインへのパーマリンク"></a></h4>
<p>To keep refreshes as efficient as possible, the graphing algorithm will
only load a couple hundred revisions initially during a refresh, and
then load further revisions only when those revisions are required to be
displayed.  You will notice scrolling through the graph is jerky, these
are bulk loads of revisions into the graph.  To avoid this jerkiness you
can force TortoiseHg to load all revisions in the graph via the
<em class="guilabel">Load all revisions</em> option from the <em class="guilabel">View</em> menu.</p>

      <div class="sphinxsidebar">
        <div class="sphinxsidebarwrapper">
            <p class="logo"><a href="index.html">
              <img class="logo" src="_static/thg_logo_92x50.png" alt="Logo"/>
  <h3><a href="index.html">目次</a></h3>
<li><a class="reference internal" href="#">3. 最新情報</a><ul>
<li><a class="reference internal" href="#tortoisehg-2-0">3.1. TortoiseHg 2.0</a><ul>
<li><a class="reference internal" href="#id2">3.1.1. 方針</a><ul>
<li><a class="reference internal" href="#id3"> ワークベンチ</a></li>
<li><a class="reference internal" href="#mercurial"> Mercurial コマンドラインの表示</a></li>
<li><a class="reference internal" href="#resolve-tool-deliberate-merges"> Resolve tool, deliberate merges</a></li>
<li><a class="reference internal" href="#shelve-improved"> Shelve Improved</a></li>
<li><a class="reference internal" href="#revision-sets"> Revision Sets</a></li>
<li><a class="reference internal" href="#technology">3.1.2. Technology</a><ul>
<li><a class="reference internal" href="#qt-and-pyqt"> Qt and PyQt</a></li>
<li><a class="reference internal" href="#qscintilla2"> QScintilla2</a></li>
<li><a class="reference internal" href="#polling-of-repository-state-and-config"> Polling of repository state and config</a></li>
<li><a class="reference internal" href="#immediate-bug-report-dialogs"> Immediate bug report dialogs</a></li>
<li><a class="reference internal" href="#demand-loaded-graph"> Demand loaded graph</a></li>

  <p class="topless"><a href="intro.html"
                        title="前の章へ">2. 導入</a></p>
  <p class="topless"><a href="quick.html"
                        title="次の章へ">4. TortoiseHg クイックスタート</a></p>
  <ul class="this-page-menu">
    <li><a href="_sources/whatsnew.txt"
<div id="searchbox" style="display: none">
    <form class="search" action="search.html" method="get">
      <input type="text" name="q" />
      <input type="submit" value="検索" />
      <input type="hidden" name="check_keywords" value="yes" />
      <input type="hidden" name="area" value="default" />
    <p class="searchtip" style="font-size: 90%">
<script type="text/javascript">$('#searchbox').show(0);</script>
      <div class="clearer"></div>
    <div class="related">
        <li class="right" style="margin-right: 10px">
          <a href="genindex.html" title="総合索引"
        <li class="right" >
          <a href="py-modindex.html" title="Pythonモジュール索引"
             >モジュール</a> |</li>
        <li class="right" >
          <a href="quick.html" title="4. TortoiseHg クイックスタート"
             >次へ</a> |</li>
        <li class="right" >
          <a href="intro.html" title="2. 導入"
             >前へ</a> |</li>
        <li><a href="index.html">TortoiseHg 2.4.0 documentation</a> &raquo;</li> 
    <div class="footer">
        &copy; Copyright 2010, Steve Borho、他.
      このドキュメントは <a href="">Sphinx</a> 1.1.3 で生成しました。