comparison mercurial/ui.py @ 25498:7a5335ed7e1a

progress: move the singleton logic to the ui module

The use of a singleton for all of progress handling is debatable (because
config may vary). However this is how the extension has been doing it so far.
We move that code into the ui module because this is where is should belong when
progress is moved into core.

25497:93b8b0049932

# This software may be used and distributed according to the terms of the
# GNU General Public License version 2 or any later version.

from i18n import _
import errno, getpass, os, socket, sys, tempfile, traceback
import config, scmutil, util, error, formatter
from node import hex

samplehgrcs = {
    'user':
"""# example user config (see "hg help config" for more info)

        ``rawloc`` is the raw location, as defined in the config.
        """
        self.name = name
        # We'll do more intelligent things with rawloc in the future.
        self.loc = rawloc

25498:7a5335ed7e1a

# This software may be used and distributed according to the terms of the
# GNU General Public License version 2 or any later version.

from i18n import _
import errno, getpass, os, socket, sys, tempfile, traceback
import config, scmutil, util, error, formatter, progress
from node import hex

samplehgrcs = {
    'user':
"""# example user config (see "hg help config" for more info)

        ``rawloc`` is the raw location, as defined in the config.
        """
        self.name = name
        # We'll do more intelligent things with rawloc in the future.
        self.loc = rawloc

# we instantiate one globally shared progress bar to avoid
# competing progress bars when multiple UI objects get created
_progresssingleton = None

def getprogbar(ui):
    global _progresssingleton
    if _progresssingleton is None:
        # passing 'ui' object to the singleton is fishy,
        # this is how the extension used to work but feel free to rework it.
        _progresssingleton = progress.progbar(ui)
    return _progresssingleton