[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-panel-devel
Subject: Re: [Panel-devel] Plasma GHNS layout bundles
From: Vinay Khaitan <vkhaitan () gmail ! com>
Date: 2005-10-11 11:37:09
Message-ID: 56c534770510110437i3fe4605w () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
I consider xml as bloat sometimes. Although It has advantages of free
parserers being available, and for small tasks, it is okay. But I feel, if
we can do away with binary interfaces instead of xml for lengthy processing
tasks, then it would be much better.
Perhaps that is the reason, why SVG parsers are not as good as Flash.
On 10/10/05, Parker Anderson <baka.rob@gmail.com> wrote:
>
> On 10/10/05, Riccardo Iaconelli <info@ruphy.com> wrote:
> > Nathan Humbert Scrive:
> >
> > > 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
> >
> > Could be better a simple Variable=Value file?
> > Like /etc/make.conf or the file for X configuration...
> > I'm saying something stupid?
> > For implementation in knewstuff or plasma..... I think that's better
> > plasma... it's for desktop.
> >
> It is not a stupid suggestion, to use a "simple" format as opposed to
> XML, but both sides have their own pros and cons. Here is a page
> which lists some common reasons on why XML-based solutions are useful:
>
> http://www.xfront.com/xml/5-minute-intro/sld010.htm
>
> Some disadvantages to XML are outlined in section 8.2.* of the following
> page:
>
> http://www.awprofessional.com/articles/article.asp?p=367637&seqNum=2&rl=1
>
> 8.2.1 and 8.2.2 are talking about the performance and resource usage
> associated with using an XML-based solution, and 8.2.3 also mentions
> that but gives us something else to think about: security
> implications. It's all something to consider, but I guess that's what
> this mailing-list and various forums are for. ;) Has XML already been
> decided on, firmly? Or is the format decision still floating around
> somewhere?
>
> Cheers,
> -Parker
> _______________________________________________
> Panel-devel mailing list
> Panel-devel@kde.org
> https://mail.kde.org/mailman/listinfo/panel-devel
>
[Attachment #5 (text/html)]
I consider xml as bloat sometimes. Although It has advantages of free
parserers being available, and for small tasks, it is okay. But I
feel, if we can do away with binary interfaces instead of xml for
lengthy processing tasks, then it would be much better. <br>
Perhaps that is the reason, why SVG parsers are not as good as \
Flash.<br><br><div><span class="gmail_quote">On 10/10/05, <b \
class="gmail_sendername">Parker Anderson</b> <<a \
href="mailto:baka.rob@gmail.com">baka.rob@gmail.com </a>> wrote:</span><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;">On 10/10/05, Riccardo Iaconelli <<a \
href="mailto:info@ruphy.com">info@ruphy.com </a>> wrote:<br>> Nathan Humbert \
Scrive:<br>><br>> > I have been working on the "Design GHNS ability to \
download Plasma<br>> > preconfigured layout" task for a while.<br>> \
> I think I have figured out the direction I think things should go and <br>> \
> I would like to get some feedback before I<br>> > do anything stupid \
:-)<br>> ><br>> > What I am thinking right now is the "bundle" \
would basically be a XML<br>> > file that would store the basic settings \
<br>> > (Kicker, Kmenu, etc) and a list of dependencies (Applets, \
background<br>> > images, etc). Then the GHNS client framework would<br>> \
> need to be expanded to read through this XML file and retrieve the <br>> > \
dependencies from the appropriate GHNS repository.<br>> > The expanded \
framework should also allow the user to choose which<br>> > elements of the \
"bundle" they wish to get and<br>> > allow them to opt for newer \
versions if available. <br>> ><br>> > One big question I have right now \
is where this functionality should<br>> > be implemented. Should it be \
generalized<br>> > and put into the knewstuff framework or should it be \
implemented in plasma? <br>> ><br>> > Comments? Suggestions?<br>> \
><br>> > Nathan Humbert<br>><br>> Could be better a simple \
Variable=Value file?<br>> Like /etc/make.conf or the file for X \
configuration...<br>> I'm saying something stupid? <br>> For implementation in \
knewstuff or plasma..... I think that's better<br>> plasma... it's for \
desktop.<br>><br>It is not a stupid suggestion, to use a "simple" format \
as opposed to<br>XML, but both sides have their own pros and cons. Here is \
a page <br>which lists some common reasons on why XML-based solutions are \
useful:<br><br><a href="http://www.xfront.com/xml/5-minute-intro/sld010.htm">http://www.xfront.com/xml/5-minute-intro/sld010.htm</a><br><br>Some \
disadvantages to XML are outlined in section 8.2.* of the following page:<br><br><a \
href="http://www.awprofessional.com/articles/article.asp?p=367637&seqNum=2&rl= \
1">http://www.awprofessional.com/articles/article.asp?p=367637&seqNum=2&rl=1</a><br><br>
8.2.1 and 8.2.2 are talking about the performance and resource usage<br>associated \
with using an XML-based solution, and 8.2.3 also mentions<br>that but gives us \
something else to think about: security<br>implications. It's all \
something to consider, but I guess that's what <br>this mailing-list and various \
forums are for. ;) Has XML already been<br>decided on, \
firmly? Or is the format decision still floating \
around<br>somewhere?<br><br>Cheers,<br>-Parker<br>_______________________________________________
<br>Panel-devel mailing list<br><a \
href="mailto:Panel-devel@kde.org">Panel-devel@kde.org</a><br><a \
href="https://mail.kde.org/mailman/listinfo/panel-devel">https://mail.kde.org/mailman/listinfo/panel-devel</a><br></blockquote>
</div><br>
_______________________________________________
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