Re: [Announce] GRead : yet another Google Reader application... (PyQt)
 

Ok so there is a problem with theme and QtWebkit. Many options : [LIST][*] the theme is not correct[*] QtWebkit do not take all it's colors from the theme [*] Item specify text color but not background color

I don't know which one is good because i have nothing white in the few themes i tested, but the background of my item view stay white

Perhaps i can force the background to be... white ?

Is this problem appear for all items, with content from GRead or content for original ("view original in GRead") ?

Re: [Announce] GRead : yet another Google Reader application... (PyQt)
 

For my carrier the standard webkit user agent is viewed as a "desktop browser" so it's forbidden (as bad as it is...)
So i put a user agent with these two requirements : "mobile" and "webkit"

I didn't put the MicroB user agent because this one is not "webkit"

Other idea ?

I think i'll add a settings for this (one of my near futur work is to add many things in settings)

Re: [Announce] GRead : yet another Google Reader application... (PyQt)
 

Simple fix that would work for me :)

"View original in GRead" does work fine because it's rendered with white background.

This issue isn't unique to Okuda. The Matrix Theme which uses a black background has the same issue.

TX

Re: [Announce] GRead : yet another Google Reader application... (PyQt)
 

Mozilla/5.0 (X11; U; Linux armv7l; en-GB; rv:1.9.2a1pre) AppleWebKit/528.5+ (KHTML, like Gecko, Mobile Safari/528.5+) RX-51 N900

Frank

Re: [Announce] GRead : yet another Google Reader application... (PyQt)
 

I've just added some settings about the informations banner.

• It can be shown on top or bottom, or never
• When displayed it can be hidden after a (configurable) delay, with sliding, or never

Later, this information banner will have more informations in it, and a shortcut will be available to display it when hidden

Re: [Announce] GRead : yet another Google Reader application... (PyQt)
 

Good idea, thanks. The latest version of Grr-NG has something like that. IMHO it's too big, but something in between should be fine :-)

It does mention the feed name however,which is useful in the "All" list. If you really don't want to put it in the window caption, the banner could be a good place too :-)

Re: [Announce] GRead : yet another Google Reader application... (PyQt)
 

I updated & the first time I ran it my phone rebooted sa soon as I tried to open the first article :( :confused:. I've had this happen a few times before, but hadn't pinned it down to GRead. This time there was nothing else running.

On startup I received an error message that my overclock settings hadn't loaded due to an error. I normally leave it running @ either 850 or 1150 without any problems (until now :eek:).

I find it hard to believe that a news-reader would have anything in it that could cause this, but figured I'd post the info just in case.

TX

Re: [Announce] GRead : yet another Google Reader application... (PyQt)
 

Oops, meant to also say that after the reboot, works really nice :). I especially the ability to keep the tag lines active.

Re: [Announce] GRead : yet another Google Reader application... (PyQt)
 

Huoh..Hmm.

I think it would be good to all overclockers know that cpu overheating is probably not the main problem when overcloking, but unsynced reads&writes between cpu-mainboard-memory. That was the first warnings what power management engineer from Nokia commented here on TMO when people started to oveclock their N900s. (IIRC it was Igor Stoppa). [people who memorize this please correct me if i´m just writing utter bullsh] So do not be surprised on reboots and corrupted filesystem/memory :D

Re: [Announce] GRead : yet another Google Reader application... (PyQt)
 

That's strange. I have also been running the OC'd Titan kernel for quite a while without any problems, and yesterday I had the same thing grog just described. I was probably using GRead too (I always do :-). I thought it was maybe a memory issue and a watchdog kicking in.

Grog, are you also using some of debernardis' "optimizations" scripts ?

One of those says that when a memalloc fails, kill the process that asked for it, not the one that's using the most memory... so if a user process is super greedy, but the failed memalloc happens to come from a system process, maybe that could trigger a reboot ?