[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-panel-devel
Subject: Re: RFC: plasma2 and configuration
From: Marco Martin <notmart () gmail ! com>
Date: 2013-02-27 12:22:42
Message-ID: 201302271322.42949.notmart () gmail ! com
[Download RAW message or body]
On Wednesday 27 February 2013, Aaron J. Seigo wrote:
> >
> >
> > it still looks a bit clunky, and perhaps a bit error prone as well, but
> > something more refined can come from that...
>
> definitely on the right track, imho ... and perhaps by creating a small set
> of components it can become more succinct and reliable like:
>
> import org.kde.plasma.configuration as PlasmaConfiguration
>
> PlasmaConfiguration.ModuleModel {
> modules: [
> PlasmaConfiguration.Page {
> name: i18n("General")
> icon: "plasma"
> component: MyComponentInAnotherFile
> },
> ....
> ]
> }
.
the really, really simplest declaration could be:
ListModel {
ListElement {
title: i18n("blah")
icon: "foo"
source: "foo.qml"
}
ListElement {
title: i18n("stuff")
icon: "bar"
source: "bar.qml"
}
}
the component could just be there by filename but i think wouldn't be a
serious issue (makes easier to formfactorize, actually)
the actually serious problem is that here scripts aren't supported on the
right hand, so title: i18n("stuff") won't work :/
--
Marco Martin
_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic