[mythtv] Resurrecting MythBrowser after the switch to Qt4

Paul Harrison mythtv at dsl.pipex.com
Thu Jul 17 12:41:23 UTC 2008


Janne Grunau wrote:
> On Thursday 17 July 2008 12:34:43 Paul Harrison wrote:
>   
>> I'm going to start looking at resurrecting MythBrowser and now that
>> WebKit is part of Qt4.4 thats the approach I was going to take.
>>
>> Would there be any objections to making Qt4.4 the minimum version
>> required for trunk?
>>     
>
> I think it's quite early in the life of Qt 4.4 and we have been 
> conversative with required software. The situation will be better in 
> six months (when all distros are updated with KDE 4.2).
>
>   

I can understand this but I'd like to use MythBrowser now not in six 
months :-(


>> If there is no problem with that then I'd create a generic mythuitype
>> based on QWebPage that can be used on any  screen. That would be the
>> most useful in the long run but requires the most work and would
>> require Qt4.4 as the minimum.
>>
>> The other alternative would be to just require Qt 4.4 for the
>> MythBrowser plugin and use QWebView. That would be by far the easiest
>> approach but would be the least flexible.
>>     
>
> Without knowing MythUI or QtWebKit in detail is it not possible to use 
> the first approach but have the class for now in mythbrowser/mythui and 
> move it mythui when we are comfortable to require Qt 4.4?
>
>   
I don't think this would be possible because libmythui needs to know 
about the new type in order to parse the xml files etc. It would be 
possible to create a class in MythBrowser to do the rendering part but 
why bother when it will only be useful in MythBrowser easier to just to 
use a QWebView. The point of the first option is that the new uitype 
could be used in other parts of Myth like in MythMusic to show the 
wikipedia page for the currently playing artist or could be used to show 
a context sensitive help screen or to replace the current recording info 
screen etc.

Jochen says why not have it conditionally compiled in but again why 
bother if it is only going to be useful in MythBrowser
> Janne
>
>   

I can see what's going to happen here it's going to be another of those 
threads that no one can agree anything and at the end of the day nothing 
really changes :-(

Paul H.



More information about the mythtv-dev mailing list