Re: [vdr] VDR form packages
On 20.03.2013 00:01, Tobi wrote: Can you point me to the upstream sources? Is there an official version of the VNSI plugin for Frodo? Based on http://forum.xbmc.org/showthread.php?tid=139675 here it is: https://github.com/opdenkamp/xbmc-pvr-addons/tree/master/addons/pvr.vdr.vnsi There is somewhere repo of developer, FernetMenta, but I think those source should perfectly fit XBMC plugin -noepg - plugin is simple so easy to package and it would be nice to have it in repo. I use it, maybe others too? Just updated it to the latest version: http://anonscm.debian.org/gitweb/?p=pkg-vdr-dvb/vdr-plugin-noepg.git;a=summary Thank you :) Marx ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR form packages
On Wednesday, 20 March 2013, Marx wrote: On 20.03.2013 00:01, Tobi wrote: Can you point me to the upstream sources? Is there an official version of the VNSI plugin for Frodo? Based on http://forum.xbmc.org/**showthread.php?tid=139675http://forum.xbmc.org/showthread.php?tid=139675 here it is: https://github.com/opdenkamp/**xbmc-pvr-addons/tree/master/** addons/pvr.vdr.vnsihttps://github.com/opdenkamp/xbmc-pvr-addons/tree/master/addons/pvr.vdr.vnsi There is somewhere repo of developer, FernetMenta, but I think those source should perfectly fit XBMC plugin Here is correct link for stable frodo version, VDR plugin subdir https://github.com/opdenkamp/xbmc-pvr-addons/tree/frodo/addons/pvr.vdr.vnsi/vdr-plugin-vnsiserver there is already a Debian packaging branch too with Debian/ structure. https://github.com/opdenkamp/xbmc-pvr-addons/tree/packaging/debian ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Makefile variable names LCLBLD and PLGCFG
Carsten Koch wrote: But if they really cannot have readable names, at least I would not provide a default, but let the makefile issue a message that they must be set (as I suggested in the other thread). They don't have to be set, so why should the Makefile issue a message? Yours Manuel ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Makefile variable names LCLBLD and PLGCFG
Am Sonntag, den 17.03.2013, 18:06 +0100 schrieb Klaus Schmidinger: On 17.03.2013 18:00, Carsten Koch wrote: On 03/17/13 13:00, Klaus Schmidinger wrote: On 17.03.2013 12:46, Ville Skyttä wrote: Hello, Should probably have spoken earlier, but is there any particular reason for the ugly and hard to read Makefile variable names LCLBLD and PLGCFG? I suppose they're short for LOCALBUILD and PLUGINCONFIG, but why do they have to be short for anything, it's not like we're running out of space for their names anywhere, is it? Besides, I don't think LCLBLD describes what its effects are very well, INPLACE would sounds better to me. The ship may already have sailed for plgcfg in vdr.pc as it's being used by many plugin Makefiles already, but I believe the attached patches should be safe for 2.0.0. I'm afraid it's too late for that. I do not understand why it should be too late. 2.0 is not out yet. But we're in the final testing phase. Besides, Ville's patch also touched the Makefiles of plugins - and plugin authors and distribution managers react very intense when they have to modify their files ;-). If I am not mistaken, Ville’s issue was that the names were not clear. Could a comment be added to the Makefile what the meaning is then. That should not break anything. […] Thanks, Paul signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Makefile variable names LCLBLD and PLGCFG
On 20.03.2013 18:02, Paul Menzel wrote: Am Sonntag, den 17.03.2013, 18:06 +0100 schrieb Klaus Schmidinger: On 17.03.2013 18:00, Carsten Koch wrote: On 03/17/13 13:00, Klaus Schmidinger wrote: On 17.03.2013 12:46, Ville Skyttä wrote: Hello, Should probably have spoken earlier, but is there any particular reason for the ugly and hard to read Makefile variable names LCLBLD and PLGCFG? I suppose they're short for LOCALBUILD and PLUGINCONFIG, but why do they have to be short for anything, it's not like we're running out of space for their names anywhere, is it? Besides, I don't think LCLBLD describes what its effects are very well, INPLACE would sounds better to me. The ship may already have sailed for plgcfg in vdr.pc as it's being used by many plugin Makefiles already, but I believe the attached patches should be safe for 2.0.0. I'm afraid it's too late for that. I do not understand why it should be too late. 2.0 is not out yet. But we're in the final testing phase. Besides, Ville's patch also touched the Makefiles of plugins - and plugin authors and distribution managers react very intense when they have to modify their files ;-). If I am not mistaken, Ville’s issue was that the names were not clear. Could a comment be added to the Makefile what the meaning is then. That should not break anything. Something like this? # Use 'make LCLBLD=1' to build locale and plugin files under the source directory: ifdef LCLBLD ... # Use this if you want to have a central place where you configure compile time # parameters for plugins: #PLGCFG = $(CONFDIR)/plugins.mk Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] 0.1.0
Hi Louis, I tried the plugin on vdr 1.7.41, but i don't get the OSD working (osd is blank). I run my vdr on Ubuntu, and I use xineliboutput. Could it be some libraries that i'm missing? Regards, René On 13.03.2013 16:52 , Stefan Braun wrote: Hi, One additional technical remark: the skin uses intensively the eMenuCategory enumeration introduced in VDR 1.7.34 to determinate which menu has to be displayed and if this menu should be displayed narrowly or in default style. So plugins like epgsearch or extrecmenu which replace VDR menus also have to set correct MenuCategories to be displayed correctly by the skin. In the newest versions of these plugins this is already implemented, so you should use always the latest git version of these plugins. One remaining issue with older plugins which are not already adapted to this new behaviour is the following: in plugins with dedicated setup menus which inherit from cMenuSetupPage the menu category mcSetup is set by the constructor of VDRs cMenuSetupPage, but this category should only be used by the main setup menu from VDR (which is diplayed narrow by default in the skin). To solve this, in the constructors of these plugin menus a different menu category (for instance mcSetupPlugins) has to be set via a call to SetMenuCategory: SetMenuCategory(mcSetupPlugins); Cheers Louis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- René Hertell Mäntytie 19 00270 Helsinki Finland TEL: +358 (0)9 135 1477 GSM: +358 (0)50 64 447 Fax: +358 (0)9 135 4001 VOIP: r...@voip.hertell.com ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
