[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-panel-devel
Subject: [Panel-devel] Plasma GHNS layout bundles
From: Nathan Humbert <nathan.humbert () gmail ! com>
Date: 2005-10-08 20:40:35
Message-ID: 3b9684dc0510081340s2960928ta19304d4daa9540b () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
I have been working on the "Design GHNS ability to download Plasma
preconfigured layout" task for a while.
I think I have figured out the direction I think things should go and
I would like to get some feedback before I
do anything stupid :-)
What I am thinking right now is the "bundle" would basically be a XML
file that would store the basic settings
(Kicker, Kmenu, etc) and a list of dependencies (Applets, background
images, etc). Then the GHNS client framework would
need to be expanded to read through this XML file and retrieve the
dependencies from the appropriate GHNS repository.
The expanded framework should also allow the user to choose which
elements of the "bundle" they wish to get and
allow them to opt for newer versions if available.
One big question I have right now is where this functionality should
be implemented. Should it be generalized
and put into the knewstuff framework or should it be implemented in plasma?
Comments? Suggestions?
Nathan Humbert
[Attachment #5 (text/html)]
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Kate, the KDE Advanced Text Editor">
<pre>I have been working on the "Design GHNS ability to download Plasma \
preconfigured layout" task for a while. I think I have figured out the direction \
I think things should go and I would like to get some feedback before I do anything \
stupid :-)
What I am thinking right now is the "bundle" would basically be a XML file \
that would store the basic settings (Kicker, Kmenu, etc) and a list of dependencies \
(Applets, background images, etc). Then the GHNS client framework would need to be \
expanded to read through this XML file and retrieve the dependencies from the \
appropriate GHNS repository. The expanded framework should also allow the user to \
choose which elements of the "bundle" they wish to get and allow them to \
opt for newer versions if available.
One big question I have right now is where this functionality should be implemented. \
Should it be generalized and put into the knewstuff framework or should it be \
implemented in plasma?
Comments? Suggestions?<br><br>Nathan Humbert<br><br></pre>
_______________________________________________
Panel-devel mailing list
Panel-devel@kde.org
https://mail.kde.org/mailman/listinfo/panel-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic