
Source (link to git-repo or to original if based on someone elses unmodified work): Add the source-code for this project on opencode.net
LinuxTalks.org RSS reader
This is a modified version of Slashdot Karamba 0.3 by rodviking. (http://www.kde-look.org/content/show.php?content=12873)
It's modified so it doesn't read the Slashdot.org RSS Feed, but the LinuxTalks.org one.
15 years ago
v0.1.3
Added: URL now opens in default KDE browser
Added: config option "Open URL in new tab"
Added: version number in lower right corner
Changed: default font
v0.1.2
Fixed: limit headline length
Fixed: illegal parsing of some chars
Fixed: size of images
Added: shadow
v0.1.1
Fixed: opening invalid URL for entries in the downloads section
Fixed: opening two URLs with one click (needs more testing)
Added: Last update timestamp
15 years ago
v0.1.3
Added: URL now opens in default KDE browser
Added: config option "Open URL in new tab"
Added: version number in lower right corner
Changed: default font
v0.1.2
Fixed: limit headline length
Fixed: illegal parsing of some chars
Fixed: size of images
Added: shadow
v0.1.1
Fixed: opening invalid URL for entries in the downloads section
Fixed: opening two URLs with one click (needs more testing)
Added: Last update timestamp
Mamonetti
15 years ago
NOTE: maybe a config file could help at this point. opera remote invocation looks like opera -remote openURL(URL,new-tab) but the complete list is here http://www.opera.com/docs/switches. of course an easy way to do it could be something like this at the config file:
OPEN_COMMAND=opera -rem.... %URL,... (so you only have to change the value of %URL when launching a request
and another question: which charset is used by default? i'm a spanish user and things like más (or similar) don't look great.. could the charset be selectable? (at the same way exposed for the first question i think)
regards
Report
NetCopLT
15 years ago
As far as the charset problem you mentioned, LTRSS was made specifically for LinuxTalks.org which is in English only so from that point of view there is no problem. However this in an issue of the parser which I didn't write and having a look at the code makes me think it will take a lot of work to make it suitable for other charsets. At this point I'm not planning to make such changes sorry :-( may be when I have more free time.
Best regards
Report