feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

"Build Issues" was renamed to "Issues"

Browse Source 
Change-Id: If514e2497a52456bfd16aaebf2a7c83def4621f7
Reviewed-by: Eike Ziller <eike.ziller@nokia.com>
This commit is contained in:
Robert Loehning
2011-10-21 16:39:14 +02:00
committed by Robert Löhning
parent e4a7b0642b
commit 998281c5c9
11 changed files with 13 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/api/qtcreator-dev.qdoc
View File

@@ -215,11 +215,11 @@
file, which is then opened within Qt Creator. You provide
an editor (probably read-only) for handling this file.
For lists of issues, consider creating task list files which are shown in
the \gui {Build Issues} output
the \gui {Issues} output
pane.
\list
\o \l{http://doc.qt.nokia.com/qtcreator/creator-task-lists.html}
{Showing Task List Files in the Build Issues Pane}
{Showing Task List Files in the Issues Pane}
\o \l{Creating Plugins}
\o \l{Qt Creator Coding Rules}
\o \l{Menus and Menu Items}

2
src/plugins/analyzerbase/analyzerplugin.cpp
View File

@@ -82,7 +82,7 @@ bool AnalyzerPlugin::initialize(const QStringList &arguments, QString *errorStri
// Task integration.
ExtensionSystem::PluginManager *pm = ExtensionSystem::PluginManager::instance();
ProjectExplorer::TaskHub *hub = pm->getObject<ProjectExplorer::TaskHub>();
//: Category under which Analyzer tasks are listed in build issues view
//: Category under which Analyzer tasks are listed in Issues view
hub->addCategory(QLatin1String(Constants::ANALYZERTASK_ID), tr("Analyzer"));
return true;

4
src/plugins/projectexplorer/buildmanager.cpp
View File

@@ -157,9 +157,9 @@ BuildManager::BuildManager(ProjectExplorerPlugin *parent)
void BuildManager::extensionsInitialized()
{
d->m_taskHub->addCategory(Constants::TASK_CATEGORY_COMPILE,
tr("Compile", "Category for compiler isses listened under 'Build Issues'"));
tr("Compile", "Category for compiler isses listed under 'Issues'"));
d->m_taskHub->addCategory(Constants::TASK_CATEGORY_BUILDSYSTEM,
tr("Build System", "Category for build system isses listened under 'Build Issues'"));
tr("Build System", "Category for build system isses listed under 'Issues'"));
}
BuildManager::~BuildManager()

2
src/plugins/projectexplorer/ioutputparser.cpp
View File

@@ -38,7 +38,7 @@
/*!
\class ProjectExplorer::IOutputParser
\brief Interface for an output parser that emit build issues (tasks).
\brief Interface for an output parser that emit issues (tasks).
\sa ProjectExplorer::Task
*/

2
src/plugins/projectexplorer/taskwindow.h
View File

@@ -48,7 +48,7 @@ class Task;
namespace Internal {
class TaskWindowPrivate;
// Show build issues (warnings or errors) and open the editor on click.
// Show issues (warnings or errors) and open the editor on click.
class TaskWindow : public Core::IOutputPane
{
Q_OBJECT

2
src/plugins/qt4projectmanager/makestep.cpp
View File

@@ -243,7 +243,7 @@ void MakeStep::run(QFutureInterface<bool> & fi)
canContinue = false;
}
if (!canContinue) {
emit addOutput(tr("Configuration is faulty. Check the Build Issues view for details."), BuildStep::MessageOutput);
emit addOutput(tr("Configuration is faulty. Check the Issues view for details."), BuildStep::MessageOutput);
fi.reportResult(false);
return;
}

2
src/plugins/qt4projectmanager/qmakestep.cpp
View File

@@ -309,7 +309,7 @@ void QMakeStep::run(QFutureInterface<bool> &fi)
canContinue = false;
}
if (!canContinue) {
emit addOutput(tr("Configuration is faulty, please check the Build Issues view for details."), BuildStep::MessageOutput);
emit addOutput(tr("Configuration is faulty, please check the Issues view for details."), BuildStep::MessageOutput);
fi.reportResult(false);
return;
}

2
src/plugins/qt4projectmanager/qt-s60/s60createpackagestep.cpp
View File

@@ -266,7 +266,7 @@ void S60CreatePackageStep::handleWarnAboutPatching()
const QString text =
tr("%1<p><em>These changes were not part of your build system</em> but are required to "
"make sure the <em>self-signed</em> package can be installed successfully on a device.</p>"
"<p>Check the Build Issues pane for more details on the modifications made.</p>"
"<p>Check the Issues pane for more details on the modifications made.</p>"
"<p>Please see the <a href=\"%2\">documentation</a> for other signing options which "
"remove the need for this patching.</p>").arg(changedText, url);
m_patchWarningDialog->setWindowTitle(title);

2
src/plugins/tasklist/TaskList.pluginspec.in
View File

@@ -10,7 +10,7 @@ GNU Lesser General Public License Usage
Alternatively, this plugin may be used under the terms of the GNU Lesser General Public License version 2.1 as published by the Free Software Foundation. Please review the following information to ensure the GNU Lesser General Public License version 2.1 requirements will be met: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html.
</license>
<description>Use .tasks-files to populate the build issues view.</description>
<description>Use .tasks-files to populate the Issues view.</description>
<url>http://qt.nokia.com</url>
<dependencyList>
<dependency name=\"Core\" version=\"$$QTCREATOR_VERSION\"/>

2
src/plugins/tasklist/tasklistplugin.cpp
View File

@@ -198,7 +198,7 @@ bool TaskListPlugin::initialize(const QStringList &arguments, QString *errorMess
ExtensionSystem::PluginManager *pm = ExtensionSystem::PluginManager::instance();
d->hub = pm->getObject<ProjectExplorer::TaskHub>();
//: Category under which tasklist tasks are listed in build issues view
//: Category under which tasklist tasks are listed in Issues view
d->hub->addCategory(QLatin1String(Constants::TASKLISTTASK_ID), tr("My Tasks"));
Core::ICore *core = Core::ICore::instance();

2
src/plugins/valgrind/memcheckerrorview.cpp
View File

@@ -361,7 +361,7 @@ void MemcheckErrorDelegate::paint(QPainter *painter, const QStyleOptionViewItem
}
}
// Separator lines (like build issues pane)
// Separator lines (like Issues pane)
painter->setPen(QColor::fromRgb(150,150,150));
painter->drawLine(0, opt.rect.bottom(), opt.rect.right(), opt.rect.bottom());