2005-12-12, 11:11 PM
Hi
Am contemplating writing a guide plugin for GBPVR. (I may be some time :-) )
Idea is to write a plugin for a TV guide that more properly suits my requirements.
Have looked at the format of the .mdb file from which the existing TV guide gets populated and have some ideas about what I want to do to the data.
Are there rules about what a plugin may do to the .mdb file?
Is a plugin permitted to change the structure of subs .mdb file (e.g. adding tables or columns to the database) or should a new .mdb file be added to the GBPVR directory and then have the plugin gets its data from this? I can easily imagine that messing with sub's database is non preferred.
My scheme is to have the long channel list in the existing TV guide replaced by a number of short channel lists. Similar to the Xguide browser but with an extra level of hierarchy.
Each capture source has its own Guide and the channels on each capture card are divided into shorter guides such as news, sport, music, (or all) etc. (very much like the skybox channel list is subdivided).
The database structure for this is trivial and the existing TV guide viewer might be persuaded to display a filtered list without too much trouble.
Not sure of the practicalities of this but might be an interesting thing to try over Christmas - if I get time.
Kev
Am contemplating writing a guide plugin for GBPVR. (I may be some time :-) )
Idea is to write a plugin for a TV guide that more properly suits my requirements.
Have looked at the format of the .mdb file from which the existing TV guide gets populated and have some ideas about what I want to do to the data.
Are there rules about what a plugin may do to the .mdb file?
Is a plugin permitted to change the structure of subs .mdb file (e.g. adding tables or columns to the database) or should a new .mdb file be added to the GBPVR directory and then have the plugin gets its data from this? I can easily imagine that messing with sub's database is non preferred.
My scheme is to have the long channel list in the existing TV guide replaced by a number of short channel lists. Similar to the Xguide browser but with an extra level of hierarchy.
Each capture source has its own Guide and the channels on each capture card are divided into shorter guides such as news, sport, music, (or all) etc. (very much like the skybox channel list is subdivided).
The database structure for this is trivial and the existing TV guide viewer might be persuaded to display a filtered list without too much trouble.
Not sure of the practicalities of this but might be an interesting thing to try over Christmas - if I get time.
Kev
