kamion2-devel Mailing List for Kamion
Status: Beta
Brought to you by:
ivan-cukic
You can subscribe to this list here.
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(39) |
Oct
(10) |
Nov
(11) |
Dec
(7) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2008 |
Jan
(5) |
Feb
(12) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Pedro de C. <lei...@gm...> - 2008-02-17 20:31:24
|
Em Domingo 17 Fevereiro 2008, Ljubomir Simin escreveu: > Hi, I missed last Wednesday, but I'll try to be here on the 21. feb, > if we're organizing another meeting. We sure have a lot to discuss. > Like, how many developers are still active on this project? It seems > to have lost some steam, judging from the ml activity, at least. > > PS. Pedro, how's the work on kconfig going? slow'ish. :) there's alot of things i don't quite grasp on the QT/kde. and my c++ is far from decent :D thx for asking. Did anyone tried to run Kamion? I also need help on this :) Regarding the website, where is it hosted? Ivan? Regards, Pedro. |
From: Ljubomir S. <lju...@gm...> - 2008-02-17 20:07:17
|
Hi, I missed last Wednesday, but I'll try to be here on the 21. feb, if we're organizing another meeting. We sure have a lot to discuss. Like, how many developers are still active on this project? It seems to have lost some steam, judging from the ml activity, at least. PS. Pedro, how's the work on kconfig going? -- Ljubomir Simin Registered Linux User #351181 http://counter.li.org |
From: Pedro de C. <lei...@gm...> - 2008-02-11 21:21:17
|
Em Quinta 07 Fevereiro 2008, Ljubomir Simin escreveu: > Hi, > > Tonight we had a first irc meeting on the #kamion channel @ freenode. > There weren't many people on the channel, but hey it's a start! > > I'll try to summarize my personal conclusions from the meeting, as > well as other points that I consider important. > Disclaimer: I didn't understand all the hi-tech stuff, if anybody > disagrees please elaborate. > > 1. In order to attract people to our app we need to have an official > release first. However, we need to take care of a few more steps: > 2. We need a way to read rc files. > 2a. KDE rc files - if we link to KConfig, we loose the portability. > Is parsing the files "by hand" an acceptable solution? my take on this is that if the user has a kde app, well.. we should be able to use the kde features the user has, like the kconfig. we can make it optional at compile time or as Ivan said, at runtime. > 2b. GConf XML files. Do we care? ;) not yet? :D > 3. Small refactorings of the recipe format - replacing <name> with > <file> (or was it the other way around?) and such... > 4. Should we have a user-writable directory (preferably inside ~) for > storing the recipes? well, so keeping in mind that we may have redudant data, this point is agreed to move into $HOME. > 5. Should we support multiple kde/gnome installations? (like .kde and > .kde4 available at the same time) > 6. Should we rely on bash and tar to make our backups, or should we > code it with qt/libtar/whatever? since it's a core thing, i propose use the libs directly. > 7. Repackaging takes some additional space in temp directory. Find a > way to work with FIFO pipelines? later on? > 8. Distro specific packages. After we implement all desired features > for our first release, we should seek for packagers. I could talk with > some Kubuntu ppl, others mentioned Gentoo and SUSE. > 9. Release announcement. I'll try to write some good release > announcement and post in on the dot. > 10. Webpage.Who is gonna maintain it? i don't mind ;) we also could do like the nouveau guys that have a online page with the irclogs of the "TiNDC": The irregular Nouveau Development Companions http://nouveau.freedesktop.org/wiki/ i've installed another bot to do the logging. > 11. Next meeting date. We should definitely organize another one. :) i'm sorry to miss the first one, but i'm all for a weekly one. it helps on being productive. :) > Anyway, just for the record: Kamion from SVN compiles, installs and > works ;). Hurray! > ummm, i must be doing something wrong. > So, let the brainstorm begin! Post your opinions, ideas and suggestions... > > PS. I'm attaching the whole meeting log, if anybody cares so much ;) oh, Ljubomir, stop talking to the bots! :P |
From: Luca B. <lbe...@gm...> - 2008-02-08 06:49:57
|
I am entering in a low availability Internet connection, so I can't attend to IRC meetings and so on. Anyway my coding part in the project is the least relevant, so this is not important for Kamion2 development. I ask you only to take up to date the python test code. It is important we can prove to all of us that Kamion is working after each svn commit. kamion-test.py (that now prints some useless messages too and has some hard coded path, as ~/devel), relies on the command line tool only. bye lb |
From: Ljubomir S. <lju...@gm...> - 2008-02-07 23:53:58
|
Hi, Tonight we had a first irc meeting on the #kamion channel @ freenode. There weren't many people on the channel, but hey it's a start! I'll try to summarize my personal conclusions from the meeting, as well as other points that I consider important. Disclaimer: I didn't understand all the hi-tech stuff, if anybody disagrees please elaborate. 1. In order to attract people to our app we need to have an official release first. However, we need to take care of a few more steps: 2. We need a way to read rc files. 2a. KDE rc files - if we link to KConfig, we loose the portability. Is parsing the files "by hand" an acceptable solution? 2b. GConf XML files. Do we care? ;) 3. Small refactorings of the recipe format - replacing <name> with <file> (or was it the other way around?) and such... 4. Should we have a user-writable directory (preferably inside ~) for storing the recipes? 5. Should we support multiple kde/gnome installations? (like .kde and .kde4 available at the same time) 6. Should we rely on bash and tar to make our backups, or should we code it with qt/libtar/whatever? 7. Repackaging takes some additional space in temp directory. Find a way to work with FIFO pipelines? 8. Distro specific packages. After we implement all desired features for our first release, we should seek for packagers. I could talk with some Kubuntu ppl, others mentioned Gentoo and SUSE. 9. Release announcement. I'll try to write some good release announcement and post in on the dot. 10. Webpage.Who is gonna maintain it? 11. Next meeting date. We should definitely organize another one. :) Anyway, just for the record: Kamion from SVN compiles, installs and works ;). Hurray! So, let the brainstorm begin! Post your opinions, ideas and suggestions... PS. I've attached the whole meeting log, but my mail bounced due to some size restrictions. It'll come through, eventually :) -- Ljubomir Simin Registered Linux User #351181 http://counter.li.org |
From: Ljubomir S. <lju...@gm...> - 2008-02-07 23:35:15
|
Hi, Tonight we had a first irc meeting on the #kamion channel @ freenode. There weren't many people on the channel, but hey it's a start! I'll try to summarize my personal conclusions from the meeting, as well as other points that I consider important. Disclaimer: I didn't understand all the hi-tech stuff, if anybody disagrees please elaborate. 1. In order to attract people to our app we need to have an official release first. However, we need to take care of a few more steps: 2. We need a way to read rc files. 2a. KDE rc files - if we link to KConfig, we loose the portability. Is parsing the files "by hand" an acceptable solution? 2b. GConf XML files. Do we care? ;) 3. Small refactorings of the recipe format - replacing <name> with <file> (or was it the other way around?) and such... 4. Should we have a user-writable directory (preferably inside ~) for storing the recipes? 5. Should we support multiple kde/gnome installations? (like .kde and .kde4 available at the same time) 6. Should we rely on bash and tar to make our backups, or should we code it with qt/libtar/whatever? 7. Repackaging takes some additional space in temp directory. Find a way to work with FIFO pipelines? 8. Distro specific packages. After we implement all desired features for our first release, we should seek for packagers. I could talk with some Kubuntu ppl, others mentioned Gentoo and SUSE. 9. Release announcement. I'll try to write some good release announcement and post in on the dot. 10. Webpage.Who is gonna maintain it? 11. Next meeting date. We should definitely organize another one. :) Anyway, just for the record: Kamion from SVN compiles, installs and works ;). Hurray! So, let the brainstorm begin! Post your opinions, ideas and suggestions... PS. I'm attaching the whole meeting log, if anybody cares so much ;) -- Ljubomir Simin Registered Linux User #351181 http://counter.li.org |
From: Ljubomir S. <lju...@gm...> - 2008-02-07 10:16:49
|
On Feb 7, 2008 7:06 AM, Pedro de Carvalho <lei...@gm...> wrote: > > > Hello all. > > As stated earlier, we have a new home on freenode (irc.freenode.org) called > #kamion. > > So, in the best interest, tomorrow there will be a reunion to get things > moving, questions asked and maybe some anwsers :D > > It was agreed to be at 21:00 gmt (22 CET) > > ------------------------------------ > > Today ( 6 february 2008) rabauke, ljubomir (of AWN fame!! ) and i, spoke and > layed out a plan: > > ** The first step is getting Kamion running. > > ** The second is to have a basic Kamion so we can start building up the > features > > ** Next will be spreading love, gathering some feedback and common > difficulties found by the R,M. (Recipe Manteiners) . > > -------------- > > * One of the things mentioned was moving kamion's files inside $home/ > > Ivan, can you tell us what was the reasoning on why kamion is using /etc > and /var/lib? was there a special reason? > We might not want to kamion be placed inside .kde but we should put all the > things (database, recipies, etc ) in $home/.kamion. > > > * Another thing is to start with supporting kconfig. > > Using kconfig will allow kamion (and the Recipe Manteiners) to have a way to > select a variable inside the rc file. Inside this rc files, there are the > [group] headings and following it there are the entries and their values. > With that in mind, the R.M. would be able to pick up the the entries needed > and let the user decide those entries. > Ex: kmail: > lets imagine the R.M. selected the (pseudo) entries "emails-recieved", > "emails-sent" and "accounts". > > The user then could choose between those and kamion would use kconfig to get > the directories or the value. > > Anyway, show up tomorrow in #kamion! > > Cya. > Pedro. > > PS: i hope i didn't forget some key points that were discused. > I'd like to add that it would be nice if we could manage to keep meetings in a regular (i.e. weekly) fashion. But let's see how things come out today. -- Ljubomir Simin Registered Linux User #351181 http://counter.li.org |
From: Pedro de C. <lei...@gm...> - 2008-02-07 06:05:53
|
Hello all. As stated earlier, we have a new home on freenode (irc.freenode.org) called #kamion. So, in the best interest, tomorrow there will be a reunion to get things moving, questions asked and maybe some anwsers :D It was agreed to be at 21:00 gmt (22 CET) ------------------------------------ Today ( 6 february 2008) rabauke, ljubomir (of AWN fame!! ) and i, spoke and layed out a plan: ** The first step is getting Kamion running. ** The second is to have a basic Kamion so we can start building up the features ** Next will be spreading love, gathering some feedback and common difficulties found by the R,M. (Recipe Manteiners) . -------------- * One of the things mentioned was moving kamion's files inside $home/ Ivan, can you tell us what was the reasoning on why kamion is using /etc and /var/lib? was there a special reason? We might not want to kamion be placed inside .kde but we should put all the things (database, recipies, etc ) in $home/.kamion. * Another thing is to start with supporting kconfig. Using kconfig will allow kamion (and the Recipe Manteiners) to have a way to select a variable inside the rc file. Inside this rc files, there are the [group] headings and following it there are the entries and their values. With that in mind, the R.M. would be able to pick up the the entries needed and let the user decide those entries. Ex: kmail: lets imagine the R.M. selected the (pseudo) entries "emails-recieved", "emails-sent" and "accounts". The user then could choose between those and kamion would use kconfig to get the directories or the value. Anyway, show up tomorrow in #kamion! Cya. Pedro. PS: i hope i didn't forget some key points that were discused. |
From: Pedro de C. <lei...@gm...> - 2008-02-06 09:27:19
|
Em Quarta 06 Fevereiro 2008, escreveu: > On Feb 6, 2008 4:16 AM, Pedro de Carvalho <lei...@gm...> wrote: > > usualy i'm always on the irc. > > #kde, #gentoo, even #plasma. > > > > i'm "oganso" :) > > > > i live on the GMT and, for me, since i'm having some vacations, anytime > > but morning. > > > > BTW, i noticed a typo "...KIO i guess i may not be..." should be "...KIO > > i guess it may be..." > > > > Pedro. > > > > Em Quarta 06 Fevereiro 2008, escreveu: > > > On Feb 6, 2008 12:43 AM, Pedro de Carvalho <lei...@gm...> > > > > wrote: > > > > Hi Andy! > > > > > > > > > > > > one of the things that were spoken back in October was the ability > > > > of following symlinks to pack. if kamion is using KIO i guess i > > > > may not be able to put the gathered data on a remote machine. > > > > > > > > but the article speaks of sync'ing that means that the destination > > > > isn't packed (with tar). (which means we need to had a option to > > > > pack/not pack) > > > > > > > > regarding a way to choose just a part of the config we can do that > > > > using Kconfig. > > > > > > > > I'm still trying to get Kamion working. I can compile it with > > > > errors, launch the gui but it fails mentioning the lack of the core > > > > lib. I still need to get a better grasp at the code before going > > > > further. > > > > > > > > Em Terça 05 Fevereiro 2008, Andy Crouch escreveu: > > > > > Hey > > > > > > > > > > Has anyone else noticed an entry on Jonathans blog about an > > > > > application to save/move user settings between machines. (See > > > > > http://www.kdedevelopers.org/node/3244). > > > > > > > > > > I have left a comment relating to Kamion but perhaps we could > > > > > get some exposure through this avenue?? Might be an aid in > > > > > getting more applications to provide the details we need to > > > > > support their app?? > > > > > > > > > > Andy > > > > > <http://www.kdedevelopers.org/blog/57> > > > > > > Sorry for being OT, but how about organizing an IRC meeting to > > > discuss our development plans? We can't start serious talks with other > > > projects until we come up with the battle plan (at least that's my POV > > > ;)). What do others think? > > > > ------------------------------------------------------------------------ > >- This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > Kamion2-devel mailing list > > Kam...@li... > > https://lists.sourceforge.net/lists/listinfo/kamion2-devel > > Another question is where would we meet? Just for fun i've created a permanent channel called ... #kamion (on freenode). See you ppl there! Pedro. |
From: Pedro de C. <lei...@gm...> - 2008-02-06 03:16:31
|
usualy i'm always on the irc. #kde, #gentoo, even #plasma. i'm "oganso" :) i live on the GMT and, for me, since i'm having some vacations, anytime but morning. BTW, i noticed a typo "...KIO i guess i may not be..." should be "...KIO i guess it may be..." Pedro. Em Quarta 06 Fevereiro 2008, escreveu: > On Feb 6, 2008 12:43 AM, Pedro de Carvalho <lei...@gm...> wrote: > > Hi Andy! > > > > > > one of the things that were spoken back in October was the ability of > > following symlinks to pack. if kamion is using KIO i guess i may not be > > able to put the gathered data on a remote machine. > > > > but the article speaks of sync'ing that means that the destination isn't > > packed (with tar). (which means we need to had a option to pack/not > > pack) > > > > regarding a way to choose just a part of the config we can do that using > > Kconfig. > > > > I'm still trying to get Kamion working. I can compile it with errors, > > launch the gui but it fails mentioning the lack of the core lib. I still > > need to get a better grasp at the code before going further. > > > > Em Terça 05 Fevereiro 2008, Andy Crouch escreveu: > > > Hey > > > > > > Has anyone else noticed an entry on Jonathans blog about an > > > application to save/move user settings between machines. (See > > > http://www.kdedevelopers.org/node/3244). > > > > > > I have left a comment relating to Kamion but perhaps we could get > > > some exposure through this avenue?? Might be an aid in getting more > > > applications to provide the details we need to support their app?? > > > > > > Andy > > > <http://www.kdedevelopers.org/blog/57> > > Sorry for being OT, but how about organizing an IRC meeting to discuss > our development plans? We can't start serious talks with other > projects until we come up with the battle plan (at least that's my POV > ;)). What do others think? |
From: Pedro de C. <lei...@gm...> - 2008-02-05 23:43:06
|
Hi Andy! one of the things that were spoken back in October was the ability of following symlinks to pack. if kamion is using KIO i guess i may not be able to put the gathered data on a remote machine. but the article speaks of sync'ing that means that the destination isn't packed (with tar). (which means we need to had a option to pack/not pack) regarding a way to choose just a part of the config we can do that using Kconfig. I'm still trying to get Kamion working. I can compile it with errors, launch the gui but it fails mentioning the lack of the core lib. I still need to get a better grasp at the code before going further. Em Terça 05 Fevereiro 2008, Andy Crouch escreveu: > Hey > > Has anyone else noticed an entry on Jonathans blog about an application to > save/move user settings between machines. (See > http://www.kdedevelopers.org/node/3244). > > I have left a comment relating to Kamion but perhaps we could get some > exposure through this avenue?? Might be an aid in getting more > applications to provide the details we need to support their app?? > > Andy > <http://www.kdedevelopers.org/blog/57> |
From: Andy C. <and...@gm...> - 2008-02-05 22:02:17
|
Hey Has anyone else noticed an entry on Jonathans blog about an application to save/move user settings between machines. (See http://www.kdedevelopers.org/node/3244). I have left a comment relating to Kamion but perhaps we could get some exposure through this avenue?? Might be an aid in getting more applications to provide the details we need to support their app?? Andy <http://www.kdedevelopers.org/blog/57> |
From: Ivan <iva...@gm...> - 2008-01-12 08:28:36
|
> No problem. Could you point me to a sample xml-file that I could edit to > use it with kamion? http://sourceforge.net/project/showfiles.php?group_id=3D188066 kamion-test-data package contains needed files for testing... Mind that scripting doesn't exist... now, it's only paths and wildcards Cheers, Ivan =2D-=20 The bleeding hearts and artists, Make their stand. -- Pink Floyd |
From: Sven B. <sve...@gm...> - 2008-01-11 23:26:12
|
Hello! On Freitag, 11. Januar 2008, you wrote: > > All other users would have to do is to load them into Kamion or copy them > > into .kde/share/apps > > I haven't understood this part. No problem. Could you point me to a sample xml-file that I could edit to use it with kamion? Sven |
From: Ivan <iva...@gm...> - 2008-01-11 17:27:27
|
Hi, Sorry for the late response, I'm bit in a mess and was hoping that someone= =20 else would answer. > As far as I understood the messages in the archive the key to kamion's > acceptance and usage are the xml-files containing the information on which > files to back-up. That is correct. IMHO, those files could be used in a variety of programs -= =20 automatic access restriction creation for selinux/apparmor and similar, but= =20 that is another story. > I read that scripting would be needed, yet I do not understand why this > would be the best and easiest solution. Hence I would like to suggest a > different way and hope that I did not make any wrong assumptions. > > Kamion should not be the "source" of the xml-files, since if developers of > an application change something kamion does not know about it, unless the > application to be backed-up is the source of the xml-files. That was the intention - applications need to provide the needed metadata=20 (like .desktop files). > Amarok knows which kconfig-settings provide the paths to the data that > needs to be backed up, so it can create a file that contains the neccessa= ry > keys. Kamion can access these keys via KConfig. Further amarok can provide > a list of files or folders to back-up. If the user changes the the paths > for the collection, there is no need to update the xml-file because the > kconfig-keys did not change. Well, that is exactly what scripting should do. The problem is that the Kamion's library is kdelibs-independent [and even=20 almost Qt-independent] software so that KConfig can not be used. (I have ha= d=20 doubts about this lately, but the rest of the guys agreed that this is a go= od=20 thing if we want someone to integrate this system into Gnome and other=20 environments) So, I'm not saying that Amarok guys (or other developers) should write thos= e=20 scripts. For example, Kamion could provide scripts for accessing KConfig an= d=20 GConf (is it called that?) settings and similar, and the scripts would be=20 called from within XML files in a simple manner - for example: <call script=3D"kconfig" file=3D"$KDEHOME" category=3D"Collection" key=3D"W= hatever" /> or even <kconfig file=3D"$KDEHOME" category=3D"Collection" key=3D"Whatever" /> > Kamion could search .kde/share/apps on demand for .xml files and check > whether they contain information and use it to display a list the user can > pick the applications from which he wants to back-up. > > This way, even if the applications did not yet implement a way to > create/change the xml-files it would be quite easy for normal users to set > them up and provide them to others. > > All other users would have to do is to load them into Kamion or copy them > into .kde/share/apps I haven't understood this part. Cheers and thanks for showing interrest. =2D-=20 Those people who think they know everything are a great annoyance to those = of=20 us who do. -- Isaac Asimov |
From: Sven B. <sve...@rw...> - 2008-01-09 23:20:39
|
Hello! As far as I understood the messages in the archive the key to kamion's acceptance and usage are the xml-files containing the information on which files to back-up. Further there seems to be an issue with backing-up data that is not in a fixed position, e.g. amarok's collection, podcasts or playlists or kmails mail-folder. I read that scripting would be needed, yet I do not understand why this would be the best and easiest solution. Hence I would like to suggest a different way and hope that I did not make any wrong assumptions. Kamion should not be the "source" of the xml-files, since if developers of an application change something kamion does not know about it, unless the application to be backed-up is the source of the xml-files. So what I thought about is the following: Amarok knows which kconfig-settings provide the paths to the data that needs to be backed up, so it can create a file that contains the neccessary keys. Kamion can access these keys via KConfig. Further amarok can provide a list of files or folders to back-up. If the user changes the the paths for the collection, there is no need to update the xml-file because the kconfig-keys did not change. So for amarok kamion would for example need to know: [Collection] Collection Folders= and that it has to access it via Kconfig. config/amarokrc that it is a file apps/amarok that it is a folder to be backed up completely Of course one can add some description etc. to it that tells the user what those items stand for. For kmail e.g.: [General] folders= Kamion could search .kde/share/apps on demand for .xml files and check whether they contain information and use it to display a list the user can pick the applications from which he wants to back-up. This way, even if the applications did not yet implement a way to create/change the xml-files it would be quite easy for normal users to set them up and provide them to others. All other users would have to do is to load them into Kamion or copy them into .kde/share/apps Sven |
From: Ivan <iva...@gm...> - 2008-01-04 08:41:38
|
Hi all! Luca's branch is moved to the trunk. So, any development you do from now on= ,=20 do it in the trunk. Cheers! =2D-=20 The bleeding hearts and artists, Make their stand. -- Pink Floyd |
From: Ivan <iva...@gm...> - 2007-12-20 16:38:05
|
> All of us, I think. I don't want to decide for all. Well, I do not think it needs approval at all, but as you wish... =2D-=20 So remember when you're feeling very small and insecure How amazingly unlikely is your birth And pray that there's intelligent life somewhere up in space Because there' bugger all down here on earth. -- Monty Python |
From: Luca B. <lbe...@gm...> - 2007-12-20 13:16:10
|
2007/12/20, Ljubomir Simin <lju...@gm...>: > > pls, use this version, all my work is here, waiting for general approvation: > > http://kamion2.svn.sourceforge.net/viewvc/kamion2/branches/lb-branch/ > > > > I will. BTW. Who decides about it's approval? > All of us, I think. I don't want to decide for all. lb |
From: Ljubomir S. <lju...@gm...> - 2007-12-20 12:28:55
|
T24gRGVjIDIwLCAyMDA3IDEyOjEzIFBNLCBJdmFuIMh1a2nmIDxpdmFuLmN1a2ljK2tkZUBnbWFp bC5jb20+IHdyb3RlOgoKPgo+IEFyZSB5b3UgbWFraW5nIGxvY2FsIHJlbGVhc2UgcGFydGllcz8K PgoKSSdtIGRvbid0IGtub3csIHdpbGwgaGF2ZSB0byBhc2sgTFVHb05TIGd1eXMgOykKCi0tIApM anVib21pciBTaW1pbgpSZWdpc3RlcmVkIExpbnV4IFVzZXIgIzM1MTE4MQpodHRwOi8vY291bnRl ci5saS5vcmcK |
From: Ljubomir S. <lju...@gm...> - 2007-12-20 12:26:11
|
On Dec 20, 2007 12:23 PM, Luca Bellonda <lbe...@gm...> wrote: > > pls, use this version, all my work is here, waiting for general approvation: > http://kamion2.svn.sourceforge.net/viewvc/kamion2/branches/lb-branch/ > I will. BTW. Who decides about it's approval? -- Ljubomir Simin Registered Linux User #351181 http://counter.li.org |
From: Ivan <iva...@gm...> - 2007-12-20 11:13:30
|
> > I have to admit to have been distracted by Android, but in this > > project I am not the only one, I noted someone of us signalling bugs > > in Android list. Yes, I was bugging the list. Well, the main reason [as I've already mention= ed]=20 I looked for new Kamion maintainer was the fact that I got bored with it. I= 'm=20 focused on Plasma and Lancelot now. > > Merry Christmas to all, a wonderful 2008 and, let's hope, a working > > KDE4 on January. > Best of luck, and thank you very much for your work. Yes, we all are going > to enjoy a great KDE in January :) Are you making local release parties? > I'm using this occasion to ask other developers for some instructions on > compiling our app, after having complete qt/kdelibs/kdebase toolchain > installed. I'd like to "eat our own dogfood" for a while. If you have followed the instructions from techbase, then get the sources=20 (SourceForge's SVN) to ~/src/kamion and in that dir invoke cmakekde. Cheers! =2D-=20 So remember when you're feeling very small and insecure How amazingly unlikely is your birth And pray that there's intelligent life somewhere up in space Because there' bugger all down here on earth. -- Monty Python |
From: Ljubomir <lju...@gm...> - 2007-12-20 09:41:49
|
On Wednesday 19 December 2007 21.30:23 Luca Bellonda wrote: > I have to admit to have been distracted by Android, but in this > project I am not the only one, I noted someone of us signalling bugs > in Android list. > > So, after having implemented i18n as promised, completed command line > utility and written some test with pyunit, I stop here for the moment. > > My version is in lb-branch, if someone wants to continue the work. > > Merry Christmas to all, a wonderful 2008 and, let's hope, a working > KDE4 on January. > > lb Best of luck, and thank you very much for your work. Yes, we all are going to enjoy a great KDE in January :) I'm using this occasion to ask other developers for some instructions on compiling our app, after having complete qt/kdelibs/kdebase toolchain installed. I'd like to "eat our own dogfood" for a while. -- Ljubomir Simin Registered Linux User #351181 |
From: Luca B. <lbe...@gm...> - 2007-12-19 20:30:18
|
I have to admit to have been distracted by Android, but in this project I am not the only one, I noted someone of us signalling bugs in Android list. So, after having implemented i18n as promised, completed command line utility and written some test with pyunit, I stop here for the moment. My version is in lb-branch, if someone wants to continue the work. Merry Christmas to all, a wonderful 2008 and, let's hope, a working KDE4 on January. lb |
From: Ljubomir S. <lju...@gm...> - 2007-11-08 12:15:22
|
This mail meant to go to the mailinglist ;) -- Ljubomir Simin Registered Linux User #351181 |