Thread: [aKregator-devel] I want to contribute to Akregator.
Brought to you by:
lippel
From: Nadav V. <nad...@gm...> - 2007-05-14 21:54:37
|
Hello I want to start to programming in Linux and therefore I want to contribute to this project. I don't have good experiment, and I have full job, so I don't have a lot of time, so it take me a lot of time to what ever I do here. I have two Idea that missing for me in Akregator: 1. Export RSS to RSS. There is option for exporting only the channels but not the content. That's allow to move to any other software or RSS service, since they read RSS, so it the best format to export to. 2. Add archive engine which binding to real database like SQL light or other, This allow to use the archive for other purpose. moreover it is open option to future possible use that there is only one archive which any RSS client which support it, could use it, and use for only what it designed to: GUI for RSS. Another thing is how do you except this ideas? to add them to the software when they will finish? What you prefer that I choose? If you already work about something, It's not help if I start. Which version to work on? the one of the CVS or what I have version 1.2.6, of course if it's not matter like base code similar, I prefer to work on what I have, so I not need to have dependencies which may be new to my system. thanks for your help Nadav |
From: Frank O. <fr...@kd...> - 2007-05-16 11:25:51
|
Hi Nadav, On Monday 14 May 2007 23:50:00 Nadav Vinik wrote: > Hello > > I want to start to programming in Linux and therefore I want to > contribute to this project. Great! :) Akregator is mainly a one-man-project now, with the one man=20 having not enough time. So any help is welcome.=20 > I don't have good experiment, and I have full job, so I don't have a > lot of time, so it take me a lot of time to what ever I do here. > > I have two Idea that missing for me in Akregator: > > 1. Export RSS to RSS. There is option for exporting only the channels > but not the content. That's allow to move to any other software or RSS > service, since they read RSS, so it the best format to export to. A very good idea. This is also very useful for backup purposes and archive= =20 migration to later versions of Akregator. > 2. Add archive engine which binding to real database like SQL light or > other, This allow to use the archive for other purpose. > moreover it is open option to future possible use that there is only > one archive which any RSS client which support it, could use it, and > use for only what it designed to: GUI for RSS. An SQLite plugin for KDE3 was started once, which was too slow to be usable= =2E=20 But nobody tried to optimize it I think, it just got forgotten. If you want= =20 to use that as a start, I will have a look if I can find the code. =46or KDE4, we plan to use Akonadi ( http://pim.kde.org/akonadi/ ) for RSS,= =20 provided it becomes stable in time. Also, the storage API in Akregator will= =20 change a lot in that process (from synchronous to asynchronous, from the=20 current FeedStorage API to something libakonadi-like). So longterm, the=20 sqlite plugin will most probably become obsolete. On the other hand, people= =20 will still use KDE3 for quite some time so having an alternative to metakit= =20 would be very useful nevertheless and worth the effort. > Another thing is how do you except this ideas? to add them to the > software when they will finish? Both ideas a very good, as they add very useful and wanted features. They are also very suited for newcomers, as they are self-contained and do = not=20 need deep knowledge of the Akregator codebase or KDE libraries. AFAIK there will be no KDE3 release after 3.5.7 anymore - but it should be= =20 possible to implement both features as plugins (the sqlite feature for sure= -=20 that even must be done as plugin) so we can offer them for download on the= =20 Akregator website.=20 > Which version to work on? the one of the CVS or what I have version > 1.2.6, of course if it's not matter like base code similar, I prefer > to work on what I have, so I not need to have dependencies which may > be new to my system. =46or these features, I would suggest to work with the Akregator version fr= om=20 branches/KDE/3.5/kdepim, which is the current 3.5 branch. You can also work with trunk (KDE4), but that needs more time to set up and= is=20 not really usable yet. Using the 3.5 branch will give a version you can=20 easily test and use right now (which is very motivating). Both features should be easy to port to KDE4 later on (if not obsolete then= =20 b/c of Akonadi). If you need help, contact me, especially when it's about getting a plugin u= p=20 and running. I thought we have a plugin template somewhere, but I can't fin= d=20 it at the moment. =2D-=20 =46rank Osterfeld -- fr...@kd... Klar=E4lvdalens Datakonsult AB, Platform-independent software solutions |
From: Nadav V. <nad...@gm...> - 2007-06-23 16:17:31
|
Hello Unfortunately, I can't do what I asked. I don't have many time, and I stop using in RSS redears (except Google) since they take me big part from my time, so I don't have the enthusiasm and motivate to do it more. Sorry for that Nadav On 5/16/07, Frank Osterfeld <fr...@kd...> wrote: > Hi Nadav, > > On Monday 14 May 2007 23:50:00 Nadav Vinik wrote: > > Hello > > > > I want to start to programming in Linux and therefore I want to > > contribute to this project. > > Great! :) Akregator is mainly a one-man-project now, with the one man > having not enough time. So any help is welcome. > > > I don't have good experiment, and I have full job, so I don't have a > > lot of time, so it take me a lot of time to what ever I do here. > > > > I have two Idea that missing for me in Akregator: > > > > 1. Export RSS to RSS. There is option for exporting only the channels > > but not the content. That's allow to move to any other software or RSS > > service, since they read RSS, so it the best format to export to. > > A very good idea. This is also very useful for backup purposes and archiv= e > migration to later versions of Akregator. > > > 2. Add archive engine which binding to real database like SQL light or > > other, This allow to use the archive for other purpose. > > moreover it is open option to future possible use that there is only > > one archive which any RSS client which support it, could use it, and > > use for only what it designed to: GUI for RSS. > > An SQLite plugin for KDE3 was started once, which was too slow to be usab= le. > But nobody tried to optimize it I think, it just got forgotten. If you wa= nt > to use that as a start, I will have a look if I can find the code. > For KDE4, we plan to use Akonadi ( http://pim.kde.org/akonadi/ ) for RSS, > provided it becomes stable in time. Also, the storage API in Akregator wi= ll > change a lot in that process (from synchronous to asynchronous, from the > current FeedStorage API to something libakonadi-like). So longterm, the > sqlite plugin will most probably become obsolete. On the other hand, peop= le > will still use KDE3 for quite some time so having an alternative to metak= it > would be very useful nevertheless and worth the effort. > > > Another thing is how do you except this ideas? to add them to the > > software when they will finish? > > Both ideas a very good, as they add very useful and wanted features. > They are also very suited for newcomers, as they are self-contained and d= o not > need deep knowledge of the Akregator codebase or KDE libraries. > AFAIK there will be no KDE3 release after 3.5.7 anymore - but it should b= e > possible to implement both features as plugins (the sqlite feature for su= re - > that even must be done as plugin) so we can offer them for download on th= e > Akregator website. > > > Which version to work on? the one of the CVS or what I have version > > 1.2.6, of course if it's not matter like base code similar, I prefer > > to work on what I have, so I not need to have dependencies which may > > be new to my system. > > For these features, I would suggest to work with the Akregator version fr= om > branches/KDE/3.5/kdepim, which is the current 3.5 branch. > You can also work with trunk (KDE4), but that needs more time to set up a= nd is > not really usable yet. Using the 3.5 branch will give a version you can > easily test and use right now (which is very motivating). > Both features should be easy to port to KDE4 later on (if not obsolete th= en > b/c of Akonadi). > > If you need help, contact me, especially when it's about getting a plugin= up > and running. I thought we have a plugin template somewhere, but I can't f= ind > it at the moment. > > -- > Frank Osterfeld -- fr...@kd... > Klar=E4lvdalens Datakonsult AB, Platform-independent software solutions > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > aKregator-devel mailing list > aKr...@li... > https://lists.sourceforge.net/lists/listinfo/akregator-devel > |
From: Nadav V. <nad...@gm...> - 2009-04-01 20:56:06
|
Hello Can I propose to make those ideas as part og google summer of code? thanks Nadav On Wed, May 16, 2007 at 4:40 AM, Frank Osterfeld <fr...@kd...> wrote: > Hi Nadav, > > On Monday 14 May 2007 23:50:00 Nadav Vinik wrote: >> Hello >> >> I want to start to programming in Linux and therefore I want to >> contribute to this project. > > Great! :) Akregator is mainly a one-man-project now, with the one man > having not enough time. So any help is welcome. > >> I don't have good experiment, and I have full job, so I don't have a >> lot of time, so it take me a lot of time to what ever I do here. >> >> I have two Idea that missing for me in Akregator: >> >> 1. Export RSS to RSS. There is option for exporting only the channels >> but not the content. That's allow to move to any other software or RSS >> service, since they read RSS, so it the best format to export to. > > A very good idea. This is also very useful for backup purposes and archive > migration to later versions of Akregator. > >> 2. Add archive engine which binding to real database like SQL light or >> other, This allow to use the archive for other purpose. >> moreover it is open option to future possible use that there is only >> one archive which any RSS client which support it, could use it, and >> use for only what it designed to: GUI for RSS. > > An SQLite plugin for KDE3 was started once, which was too slow to be usable. > But nobody tried to optimize it I think, it just got forgotten. If you want > to use that as a start, I will have a look if I can find the code. > For KDE4, we plan to use Akonadi ( http://pim.kde.org/akonadi/ ) for RSS, > provided it becomes stable in time. Also, the storage API in Akregator will > change a lot in that process (from synchronous to asynchronous, from the > current FeedStorage API to something libakonadi-like). So longterm, the > sqlite plugin will most probably become obsolete. On the other hand, people > will still use KDE3 for quite some time so having an alternative to metakit > would be very useful nevertheless and worth the effort. > >> Another thing is how do you except this ideas? to add them to the >> software when they will finish? > > Both ideas a very good, as they add very useful and wanted features. > They are also very suited for newcomers, as they are self-contained and do not > need deep knowledge of the Akregator codebase or KDE libraries. > AFAIK there will be no KDE3 release after 3.5.7 anymore - but it should be > possible to implement both features as plugins (the sqlite feature for sure - > that even must be done as plugin) so we can offer them for download on the > Akregator website. > >> Which version to work on? the one of the CVS or what I have version >> 1.2.6, of course if it's not matter like base code similar, I prefer >> to work on what I have, so I not need to have dependencies which may >> be new to my system. > > For these features, I would suggest to work with the Akregator version from > branches/KDE/3.5/kdepim, which is the current 3.5 branch. > You can also work with trunk (KDE4), but that needs more time to set up and is > not really usable yet. Using the 3.5 branch will give a version you can > easily test and use right now (which is very motivating). > Both features should be easy to port to KDE4 later on (if not obsolete then > b/c of Akonadi). > > If you need help, contact me, especially when it's about getting a plugin up > and running. I thought we have a plugin template somewhere, but I can't find > it at the moment. > > -- > Frank Osterfeld -- fr...@kd... > Klarälvdalens Datakonsult AB, Platform-independent software solutions > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > aKregator-devel mailing list > aKr...@li... > https://lists.sourceforge.net/lists/listinfo/akregator-devel > -- הבלוג שלי: http://nadavvin.com |
From: Frank O. <fr...@kd...> - 2009-04-02 18:41:01
|
Hi Nadav, On Wednesday 01 April 2009 22:56:02 Nadav Vinik wrote: > Hello > > Can I propose to make those ideas as part og google summer of code? I fear they are obsolete now, see below. > >> I don't have good experiment, and I have full job, so I don't have a > >> lot of time, so it take me a lot of time to what ever I do here. > >> > >> I have two Idea that missing for me in Akregator: > >> > >> 1. Export RSS to RSS. There is option for exporting only the channels > >> but not the content. That's allow to move to any other software or RSS > >> service, since they read RSS, so it the best format to export to. > > > > A very good idea. This is also very useful for backup purposes and > > archive migration to later versions of Akregator. That is done in trunk (to be part of 4.3), there is a tool "akregatorstorageexporter" writing out the feed in atom format. > > An SQLite plugin for KDE3 was started once, which was too slow to be > > usable. But nobody tried to optimize it I think, it just got forgotten. > > If you want to use that as a start, I will have a look if I can find the > > code. For KDE4, we plan to use Akonadi ( http://pim.kde.org/akonadi/ ) > > for RSS, provided it becomes stable in time. Also, the storage API in > > Akregator will change a lot in that process (from synchronous to > > asynchronous, from the current FeedStorage API to something > > libakonadi-like). So longterm, the sqlite plugin will most probably > > become obsolete. On the other hand, people will still use KDE3 for quite > > some time so having an alternative to metakit would be very useful > > nevertheless and worth the effort. That's soon obsolete when using krss/Akonadi. Noting that I wrote the same thing nearly two years ago is astonishing, but since last year (to the last GSoC to be exact), there is actually progress on that. -- Frank Osterfeld -- fr...@kd... Klarälvdalens Datakonsult AB, Platform-independent software solutions |