[prev in list] [next in list] [prev in thread] [next in thread]
List: klik-devel
Subject: Re: [klik-devel] klik-devel Digest, Vol 19, Issue 1
From: "Jason Taylor" <killerkiwi2005 () gmail ! com>
Date: 2007-08-03 22:11:59
Message-ID: 94dd8f6f0708031511taadbebdsbfff7dbddc06762e () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Ill put my hand up for the SVN tasks ;), We use svn at work so I have some
experience with it
To be honest I don't know python that well either but I thought I'd make a
start....nothing like just doing it.
Also of interest there is a python port of the xdg tools
http://www.freedesktop.org/wiki/Software/pyxdg
I've been playing around with glade as well just getting the hang of it
heres a screen shot off an initial install screen.
http://img64.imageshack.us/img64/7937/screenshotklikapplicatiuf5.png
See you all at the meeting
KillerKiwi
On 8/3/07, klik-devel-request@kde.org <klik-devel-request@kde.org> wrote:
>
> Send klik-devel mailing list submissions to
> klik-devel@kde.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mail.kde.org/mailman/listinfo/klik-devel
> or, via email, send a message with subject or body 'help' to
> klik-devel-request@kde.org
>
> You can reach the person managing the list at
> klik-devel-owner@kde.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of klik-devel digest..."
>
>
> Today's Topics:
>
> 1. Re: klik-devel Digest, Vol 16, Issue 4 (probono)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 2 Aug 2007 17:33:12 +0200
> From: probono <probono@myrealbox.com>
> Subject: Re: [klik-devel] klik-devel Digest, Vol 16, Issue 4
> To: klik-devel@kde.org
> Message-ID:
> <85d71c370708020833j40af9e1ftae3f1a7c5d11d7b2@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi all,
>
> it's been a while and you might have been wondering what I was
> doing... No, I haven't lost interest in klik at all. I've been
> contemplating various options we could take for "klik2", the next
> major version, and have been waiting until some key technologies for
> "klik2" are ready and are widely available in disttributions.
>
> That time is now. We have FUSE, and we have LSB3 compliance in most
> mainstream distributions. In other words, we can now make serious
> steps toward "klik2".
>
> One key component of "klik2" will be an "application virtualization"
> technology, something that takes the cmg and "blends" it into the /
> filesystem, and that overlays another "layer" for write accesses.
> We've seen quite a number of virtualization options (Discussion on
> http://klik.atekon.de/wiki/index.php/Virtualization_Options). While
> each one has its specific advantages and disadvantages, I would say
> that "UnionFUSE" (as used by Lionel's "klikutils") currently offers
> the approach that fits our requirements best at this time. Especially,
> it works on a great number of distributions, and by now, FUSE is
> present on most general purpose distributions.
>
> Another key component of "klik2" is that it will strive to be as LSB3
> compliant as possible. That also means that we drop the strict
> requirement to use libstdc++5, which allows us to use debian sid,
> Ubuntu, and other binaries. (Let's hope that libstdc++7 won't break
> binary compatibility again.)
>
> What is happening at the moment?
>
> * Lionel is in the finishing touches to make fusecram and fuseiso
> ready to roll.
>
> * Jason has started work on a Python-based klik client. While I don't
> understand much Python (yet), I realize that it's a very powerful
> language. Since itdoesn't need to be compiled, it is ideal for
> cross-distro usage.
>
> What do we need to do next in order to make "klik2" a reality?
>
> * We need discuss and agree on a recipe.xml format. "Old-style"
> recipes have been shell scripts that include the logic for
> downloading, unpacking and creating the cmg. We want to have this
> logic as a generalized part of the client, so that the recipe.xml
> itself will (in the easiest case) consist of little more than the
> package URLs to be used as the ingredients. The question really is
> whether we can use whatever ROX/0install's xml format has or whether
> we need something new. (Discussion on
> http://klik.atekon.de/wiki/index.php/Recipe_Files)
>
> * We need to discuss and agree whether we want to go with Python for
> the client. In addition of Jason's initial code, I had written a
> little GUI app some time ago as well
> (http://klik.atekon.de/wiki/index.php/Updater). With a GUI framework
> that uses native widgets on all desktops, Python might also be the
> answer for our *dialog woes. Also, it can easily parse XML and is well
> extensible using APIs for next to anything.
>
> * We need to "put together" all the great code we have, so that all
> the pieces come together as one. Jason has set up a Subversion
> repository on Google Code
> (http://code.google.com/p/klikclient/source). Personally I don't know
> how to use that yet, but if we agree to move all our development there
> (FUSE, client, thumbnailers,...) it would certainly speed up the
> remaining development process for "klik2". We need to elect a
> Subversion "master". Volunteers, Jason? ;-)
>
> * We should get a issue/wishlist/bugtracker.
>
> * We should agree on a time in the week to hold regular meetings on
> IRC. What about Sundays 9pm CEST?
>
> Greetings,
> probono
>
>
> ------------------------------
>
> _______________________________________________
> klik-devel mailing list
> klik-devel@kde.org
> https://mail.kde.org/mailman/listinfo/klik-devel
>
>
> End of klik-devel Digest, Vol 19, Issue 1
> *****************************************
>
[Attachment #5 (text/html)]
Ill put my hand up for the SVN tasks ;), We use svn at work so I have some \
experience with it<br><br>To be honest I don't know python that well either but I \
thought I'd make a start....nothing like just doing it.<br> <br>Also of interest \
there is a python port of the xdg tools<br><a \
href="http://www.freedesktop.org/wiki/Software/pyxdg">http://www.freedesktop.org/wiki/Software/pyxdg</a><br><br><br>I've \
been playing around with glade as well just getting the hang of it heres a screen \
shot off an initial install screen. <br><br><a \
href="http://img64.imageshack.us/img64/7937/screenshotklikapplicatiuf5.png">http://img64.imageshack.us/img64/7937/screenshotklikapplicatiuf5.png</a><br><br>See \
you all at the meeting<br><br>KillerKiwi<br><br><br> <div><span \
class="gmail_quote">On 8/3/07, <b class="gmail_sendername"><a \
href="mailto:klik-devel-request@kde.org">klik-devel-request@kde.org</a></b> <<a \
href="mailto:klik-devel-request@kde.org">klik-devel-request@kde.org </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;">Send klik-devel mailing \
list submissions to<br> <a \
href="mailto:klik-devel@kde.org"> klik-devel@kde.org</a><br><br>To subscribe or \
unsubscribe via the World Wide Web, \
visit<br> <a \
href="https://mail.kde.org/mailman/listinfo/klik-devel">https://mail.kde.org/mailman/listinfo/klik-devel</a><br>or, \
via email, send a message with subject or body 'help' to \
<br> <a \
href="mailto:klik-devel-request@kde.org">klik-devel-request@kde.org</a><br><br>You \
can reach the person managing the list \
at<br> <a \
href="mailto:klik-devel-owner@kde.org">klik-devel-owner@kde.org</a> <br><br>When \
replying, please edit your Subject line so it is more specific<br>than "Re: \
Contents of klik-devel digest..."<br><br><br>Today's \
Topics:<br><br> 1. Re: klik-devel Digest, Vol 16, Issue 4 (probono) \
<br><br><br>----------------------------------------------------------------------<br><br>Message: \
1<br>Date: Thu, 2 Aug 2007 17:33:12 +0200<br>From: probono <<a \
href="mailto:probono@myrealbox.com">probono@myrealbox.com </a>><br>Subject: Re: \
[klik-devel] klik-devel Digest, Vol 16, Issue 4<br>To: <a \
href="mailto:klik-devel@kde.org">klik-devel@kde.org</a><br>Message-ID:<br> <<a \
href="mailto:85d71c370708020833j40af9e1ftae3f1a7c5d11d7b2@mail.gmail.com"> \
85d71c370708020833j40af9e1ftae3f1a7c5d11d7b2@mail.gmail.com</a>><br>Content-Type: \
text/plain; charset=ISO-8859-1<br><br>Hi all,<br><br>it's been a while and you \
might have been wondering what I was<br>doing... No, I haven't lost interest in \
klik at all. I've been <br>contemplating various options we could take for \
"klik2", the next<br>major version, and have been waiting until some key \
technologies for<br>"klik2" are ready and are widely available in \
disttributions. <br><br>That time is now. We have FUSE, and we have LSB3 compliance \
in most<br>mainstream distributions. In other words, we can now make serious<br>steps \
toward "klik2".<br><br>One key component of "klik2" will be an \
"application virtualization" <br>technology, something that takes the cmg \
and "blends" it into the /<br>filesystem, and that overlays another \
"layer" for write accesses.<br>We've seen quite a number of \
virtualization options (Discussion on <br><a \
href="http://klik.atekon.de/wiki/index.php/Virtualization_Options">http://klik.atekon.de/wiki/index.php/Virtualization_Options</a>). \
While<br>each one has its specific advantages and disadvantages, I would say<br>that \
"UnionFUSE" (as used by Lionel's "klikutils") currently \
offers <br>the approach that fits our requirements best at this time. \
Especially,<br>it works on a great number of distributions, and by now, FUSE \
is<br>present on most general purpose distributions.<br><br>Another key component of \
"klik2" is that it will strive to be as LSB3 <br>compliant as possible. \
That also means that we drop the strict<br>requirement to use libstdc++5, which \
allows us to use debian sid,<br>Ubuntu, and other binaries. (Let's hope that \
libstdc++7 won't break<br>binary compatibility again.) <br><br>What is happening \
at the moment?<br><br>* Lionel is in the finishing touches to make fusecram and \
fuseiso<br>ready to roll.<br><br>* Jason has started work on a Python-based klik \
client. While I don't<br>understand much Python (yet), I realize that it's a \
very powerful <br>language. Since itdoesn't need to be compiled, it is ideal \
for<br>cross-distro usage.<br><br>What do we need to do next in order to make \
"klik2" a reality?<br><br>* We need discuss and agree on a recipe.xml \
format. "Old-style"<br>recipes have been shell scripts that include the \
logic for<br>downloading, unpacking and creating the cmg. We want to have \
this<br>logic as a generalized part of the client, so that the recipe.xml <br>itself \
will (in the easiest case) consist of little more than the<br>package URLs to be used \
as the ingredients. The question really is<br>whether we can use whatever \
ROX/0install's xml format has or whether<br>we need something new. (Discussion on \
<br><a href="http://klik.atekon.de/wiki/index.php/Recipe_Files">http://klik.atekon.de/wiki/index.php/Recipe_Files</a>)<br><br>* \
We need to discuss and agree whether we want to go with Python for<br>the client. In \
addition of Jason's initial code, I had written a <br>little GUI app some time \
ago as well<br>(<a href="http://klik.atekon.de/wiki/index.php/Updater">http://klik.atekon.de/wiki/index.php/Updater</a>). \
With a GUI framework<br>that uses native widgets on all desktops, Python might also \
be the <br>answer for our *dialog woes. Also, it can easily parse XML and is \
well<br>extensible using APIs for next to anything.<br><br>* We need to "put \
together" all the great code we have, so that all<br>the pieces come together as \
one. Jason has set up a Subversion <br>repository on Google Code<br>(<a \
href="http://code.google.com/p/klikclient/source">http://code.google.com/p/klikclient/source</a>). \
Personally I don't know<br>how to use that yet, but if we agree to move all our \
development there <br>(FUSE, client, thumbnailers,...) it would certainly speed up \
the<br>remaining development process for "klik2". We need to elect \
a<br>Subversion "master". Volunteers, Jason? ;-)<br><br>* We should get a \
issue/wishlist/bugtracker. <br><br>* We should agree on a time in the week to hold \
regular meetings on<br>IRC. What about Sundays 9pm \
CEST?<br><br>Greetings,<br>probono<br><br><br>------------------------------<br><br>_______________________________________________
<br>klik-devel mailing list<br><a \
href="mailto:klik-devel@kde.org">klik-devel@kde.org</a><br><a \
href="https://mail.kde.org/mailman/listinfo/klik-devel">https://mail.kde.org/mailman/listinfo/klik-devel</a><br><br><br>End \
of klik-devel Digest, Vol 19, Issue 1 \
<br>*****************************************<br></blockquote></div><br>
_______________________________________________
klik-devel mailing list
klik-devel@kde.org
https://mail.kde.org/mailman/listinfo/klik-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic