seems that priority has taken over what tier was intended for; easy to add back if necessary / desired, but i think that the idea of chaining really needs more expresivity than that

svn path=/trunk/KDE/kdebase/workspace/libs/plasma/; revision=771458

abstractrunner.cpp

@@ -40,7 +40,6 @@ class AbstractRunner::Private
         bool hasConfig;
         Priority priority;
         Speed speed;
-        int tier;
         RunnerScript* script;
         KPluginInfo runnerDescription;
         AbstractRunner* runner;
@@ -48,7 +47,6 @@ class AbstractRunner::Private
     Private(AbstractRunner* r, KService::Ptr service)
       : priority(NormalPriority),
         speed(NormalSpeed),
-        tier(0),
         script(0),
         runnerDescription(service),
         runner(r)
@@ -163,17 +161,6 @@ void AbstractRunner::setSpeed(Speed speed)
     d->speed = speed;
 }
 
-// For 4.1:
-// int AbstractRunner::tier() const
-// {
-//     return d->tier;
-// }
-//
-// void AbstractRunner::setTier(int tier)
-// {
-//     d->tier = tier;
-// }
-
 AbstractRunner::Priority AbstractRunner::priority() const
 {
     return d->priority;

abstractrunner.h

@@ -157,13 +157,6 @@ class PLASMA_EXPORT AbstractRunner : public QObject
          */
         Speed speed() const;
 
-// For 4.1
-//         /**
-//          * The tier of the runner.
-//          * @see setTier
-//          */
-//         int tier() const;
-
         /**
          * The priority of the runner.
          * @see setPriority