Notices

Wow!! A great effort has been done since the first version! Good work!!!!

great job

i am using linguines default web browser its ok responsive but theres no zoom fit to screen option and disable image option nor some way to select text or save images
another problem is the linguine browser takes time to open the first time and starts with a white screen its better to have some kind of indication that its loading also i dont seem to get any feedback if or not the news article got clicked
try clicking a news article and when linguine browser opens cancel it i got an error banner with something like premature end of file while loading and after that no article opens on linguine browser also when multiple items get clicked mistakenly as linguine browser hasent opend yet linguine crashes

can the background be changed to a diff colour ?

most awsome is the audio news it works flawlessly in 2.5g and actually now i hear news multiple times a day also is very convenient the funny thing is when first time the linguine audio player opend i was staring at the screen thinking lirycs or some images would come up i got fooled
make some use of that vast blank space please

Yeah, I'm really just using a raw QWebView for that, I haven't really added any user interface options. (At least not yet.) You should be able to suppress images now, though -- there's an option in the Preferences page for that. (Unfortunately, you need to go all the way back to the main window to get to the drop-down menu so that you can reach the preferences page. I'll have to work on that...)

Yes! QWebView does provide feedback when it is loading, I just haven't gotten around to making that feedback visible. Another item I need to get up and running...

Yes, error handling needs to be improved as well.

Hmm. I've been trying to have Linguine match the default color scheme used by your current Maemo theme. Let me see how much effort it would take to provide some color options. (At the very least, I could offer a handful of simple options, the way that most e-book readers seem to do...)

My apologies, there is supposed to be a graphic in that empty space. That's bug I introduced in the 0.3.0 release. I fixed it right afterwards, but got caught up playing around with delegates and QPainter, and forgot about it...

So, let me go ahead and push up another update. Version 0.3.1 is now making its way up to extras-devel. I've finally taken the advice of Pichlo and Marxian, and set up a custom item delegate for the list of newsfeeds. Playing with QPainter was not as hard as I'd thought; so, I now have newsfeed names and timestamps as well as the title of the latest news entry being displayed in the list:



This is going to need additional tweaking. Also, now that I can show the name of the newsfeed, I've gone ahead and sorted the list by those names. Hopefully there will be other sorting options in the future. I'm also still working on implementing the rest of The Old Reader's API, so hopefully there will soon be improvements in that area as well...

had time to give the app a test today and on the whole i'm impressed. layout is a huge improvement over stock rss client and despite added features the app is still responsive/quick.

in my opinion, the only real feature lacking is support for managing the feeds. some of them have less relevance to some of us, be it foreign languages or politics etc. how it ships at present, with a predefined set of defaults, should not change though as its a good way to show of features.

There just needs an option for adding and removing feeds along with specifying their category. category could be a list of predefined options with the choice of adding custom options. tab bar would need a little adjusting so that any categories with no entries are not dispayed. i don't know if it'd be easier to manage if feeds were stored in a database instead.

Yes! I really need to get a graphical user interface set up for subscribing & tagging newsfeeds, and managing collections. (I should note, although it's a pain, you can already control both subscriptions and collections via an XML file.)

Well, I'm already using the QSettings mechanism to store feed information; it's really easy to add, remove, or modify the feeds. My problem is really that I'm not a UI guy, so it takes me longer to create new GUIs...

Hi folks, I've finally gotten around to doing a little cleanup on Linguine, so version 0.4.0 is now making its way up to the extras-devel repository. Aside from a few RSS fixes and the addition of Deutsche Welle to the list of text news rss feeds, the most interesting addition this time is a rudimentary Linguine desktop widget:



For now, only audio or video sources are supported; click on the image to start loading the source in the default media player. A long-press will bring up the wrench icon, which when clicked will allow you to select a new newsfeed. For now, the widget checks for updates once every half hour. A warning: this isn't the most efficient of widgets yet, and for me is taking up about 10% of ram when I run it (or more, if I've been loading lots of different newsfeeds into it)...

In any case, it's something to play with. I'll try to work on it more as I get time...

Thank you for your efforts!
One problem: while without internet connection, the widget triggers the dialog "choose internet connection" generating then an error for the contents not available.

Yes, I can confirm this one.

Yes, I really should put at least a minimal amount of error-checking into the app, I suppose. (I've been concentrating on other stuff, but I really should give some more attention to this app...)

A small Linguine update is on its way up to the extras-devel repository. This one cleans up the widget UI a bit, and fixes a problem with the NPR newsfeeds.

I'm still trying to figure out what would be the best approach to dealing with a lack of network connectivity when Linguine is running. As Linguine is just a front-end to services running on the net, it is basically useless if the net is not available; so, if it cannot reach the net, I suppose it should just quit (after presenting an appropriate error message). There isn't much more it could do...