[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    Re: User Resources
From:       Zak Jensen <coolguyzak () gmail ! com>
Date:       2005-08-23 15:24:13
Message-ID: 21bb44f305082308241e79c8fd () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


It was just an example. I was trying to communicate the complication that 
could arise in the configuration files... and how much of a pain it could be 
to implement it. :)
 But, if you want to develop the XML schema to actually make it work, by all 
means, go ahead :D

 On 8/23/05, Johan De Messemaeker <johan.demessemaeker@telenet.be> wrote: 
> 
> On Monday 22 August 2005 22:29, Aaron J. Seigo wrote:
> > > <backup>
> > > <title>Chat Logs</title>
> > > <path>.local/chat_logs/</path>
> > > <category>chat logs</category>
> > > <meta>more info</meta>
> > > </backup>
> >
> > that's really about all you need. we'd probably have items to denote the
> > pathing system. for instance in KDE that would be KDEDIRS... so it might
> > be:
> >
> > <path system="kdedirs" local="true">kopete/logs</path>
> 
> Would it be a good idea to store some more information in this (like 
> nfs://,
> ftp://, http:// ...) ? kioslaves is really powerfull and it would be great 
> to
> be able to use that kind of functionallity. It is then still the
> responsibility of the client program to deal with this.
> 
> kioslaves is great for this, I know :P
> 
> Regards, Johan
> _______________________________________________
> kde-usability mailing list
> kde-usability@kde.org
> https://mail.kde.org/mailman/listinfo/kde-usability
>

[Attachment #5 (text/html)]

<div>It was just an example. I was trying to communicate the complication that could \
arise in the configuration files... and how much of a pain it could be to implement \
it. :)</div> <div>&nbsp;</div>
<div>But, if you want to develop the XML schema to actually make it work, by all \
means, go ahead :D<br><br>&nbsp;</div> <div><span class="gmail_quote">On 8/23/05, <b \
class="gmail_sendername">Johan De Messemaeker</b> &lt;<a \
href="mailto:johan.demessemaeker@telenet.be">johan.demessemaeker@telenet.be</a>&gt; \
wrote:</span> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px \
0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Monday 22 August 2005 22:29, Aaron J. \
Seigo wrote:<br>&gt; &gt; &lt;backup&gt;<br>&gt; &gt;&nbsp;&nbsp; &lt;title&gt;Chat \
Logs&lt;/title&gt; <br>&gt; &gt;&nbsp;&nbsp; \
&lt;path&gt;.local/chat_logs/&lt;/path&gt;<br>&gt; &gt;&nbsp;&nbsp; \
&lt;category&gt;chat logs&lt;/category&gt;<br>&gt; &gt;&nbsp;&nbsp; &lt;meta&gt;more \
info&lt;/meta&gt;<br>&gt; &gt; &lt;/backup&gt;<br>&gt;<br>&gt; that's really about \
all you need. we'd probably have items to denote the <br>&gt; pathing system. for \
instance in KDE that would be KDEDIRS... so it might<br>&gt; be:<br>&gt;<br>&gt; \
&lt;path system=&quot;kdedirs&quot; \
local=&quot;true&quot;&gt;kopete/logs&lt;/path&gt;<br><br>Would it be a good idea to \
store some more information in this (like nfs://, <br>ftp://, http:// ...) ? \
kioslaves is really powerfull and it would be great to<br>be able to use that kind of \
functionallity. It is then still the<br>responsibility of the client program to deal \
with this.<br><br>kioslaves is great for this, I know :P <br><br>Regards, \
Johan<br>_______________________________________________<br>kde-usability mailing \
list<br><a href="mailto:kde-usability@kde.org">kde-usability@kde.org</a><br><a \
href="https://mail.kde.org/mailman/listinfo/kde-usability"> \
https://mail.kde.org/mailman/listinfo/kde-usability</a><br></blockquote></div><br>



_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability


[prev in list] [next in list] [prev in thread] [next in thread]