[vdr] [ANNOUNCE] LIVE plugin version 0.3.0
Hello After the release of VDR 2.0 I'm happy to announce a new 'stable' version of the LIVE plugin. Stable is written in quotes because it just declares the current stage of the development in the LIVE Git-tree as stable. Since the last stable release of LIVE several contributions have been added by the community. I myself have only a very limited amount of time to do own development at the moment, so every good contribution was and is appreciated a lot. I thank all contributors to this version. You will find their names in the GIT history of this new version. This version of LIVE still supports VDR versions before 1.7.36. Thus it still uses the old Makefile layout. Since a lot of VDR users still use older versions of VDR I wanted to make the current state of LIVE available for those who don't plan to upgrade their VDR with the VDR 2.0 release. Later versions of LIVE will offer only support for VDR 2.0. More details about this release can be found on the LIVE plugin homepage: http://live.vdr-developer.org/ The LIVE 0.3.0 stable version is available for download from: http://live.vdr-developer.org/downloads/vdr-live-0.3.0.tar.gz The GIT-tree of LIVE (with all previous versions and the development version) is available from: http://projects.vdr-developer.org/git/vdr-plugin-live.git/ Enjoy tadi (Dieter) -- Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de live plugin developer http://live.vdr-developer.org ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] range-select in live plugin
Hi Am Sonntag, 13. Januar 2013 schrieb Torgeir Veimo: I was getting carpal tunnel symptoms trying to select multiple recordings for deletion in the live plugin, so I made a patch to add range selection using the Quickboxes mootools plugin. It works by allowing you to click and hold the mouse, while moving over subsequent selection checkboxes of recordings. Is the live plugin still being maintained? It seems most activity halted about four years ago. It is in apply external submission phase only. I do not add new functionality currently and doubt that I will be able to do so in the next future. Of course I keep the plugin compilable against the development in VDR. I currently wait until the disturbance through the development on the Makefile in VDR 1.7.34 and following versions have settled. This patch is a bit rough, so some testing in different browsers might be required. The Quickboxes plugins i MIT licensed, so can safely be included if accepted. Yes it could be accepted. I tried to apply the supplied patch with patch -p1 live.patch but it reported errors and rejected some hunks. Could you please revise your patch against the current 'master' branch of the version in the git [1]? While still beeing marked as unstable the 'master' version in the git can be used in productive environments. Kind regards Dieter [1] http://projects.vdr-developer.org/git/vdr-plugin-live.git/ -- Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de live plugin developer http://live.vdr-developer.org ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.28
Hello Am Montag, 4. Juni 2012 schrieb Ville Skyttä: On 2012-06-04 17:58, Klaus Schmidinger wrote: On 04.06.2012 16:51, Ville Skyttä wrote: On 2012-06-03 13:44, Klaus Schmidinger wrote: - Renamed the function cString::sprintf(const char *fmt, va_listap) to vsprintf(), Hm, I don't see this change actually implemented in the source...? Are you sure you're looking at the right files? I was, and I wasn't :) http://git.gekrumbel.de/vdr.git?p=vdr.git;a=commitdiff;h=c80ddbc27b8c7b2a7b 6ed822330da069d5cd3b68 Looks like the gekrumbel.de git tree (which is what I _was_ looking at) is missing at least this change. It was my fault. Please apologize :) I corrected the wrong commit into that (and the other) git tree. It was late yesterday evening after I came back home and apparently I've been to tired to do it right :) You get a forced update with the next pull. Kind regards Dieter -- Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de live plugin developer http://live.vdr-developer.org 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] shouldn't a vdr recording pause during status 3 flag?
Hi Lou Am Freitag, 13. Januar 2012 schrieb Lou: Where can I find tarballs for vdr 1.4.x? Your webspace only ships version patches (diff) You can clone a git repository of all released versions of VDR: $ git clone git://projects.vdr-developer.org/vdr.git There used to be a Web-Access to that repository too, but currently it doesn't seem to work any more. I have an own mirror of that which is accessible via Git-Web on http://git.gekrumbel.de/vdr.git Regards Dieter -- Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de live plugin developer http://live.vdr-developer.org 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] Can VDR Live name recordings according to title?
Hi Am Dienstag, 11. Oktober 2011 schrieb John Klimek: Is it possible to have VDR Live name it's recordings according to the title of the show? For example, I'd love to see recordings named like this: Show Name - Episode Name.ts (ie. The King of Queens - Name of Episode.ts) If you name your recordings accordingly (i.e. with timers created by epgsearch), then LIVE will list the recordings like you named them :) Best regards Dieter -- Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de live plugin developer http://live.vdr-developer.org 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] [ANNOUNCE] VDRAdmin-AM v3.6.8
Hi Am Freitag, 3. Juni 2011 schrieb John Klimek: Looks nice! What's the main difference between this and VDR-Live? VDR-Live extends the VDR with a http-server. It accesses the VDR data structures like any other VDR-plugin directly. It has thus some speed benefits. VDRAdmin-AM uses the SVDRP interface provided by VDR. Every action needs to be encoded as command and the commands output needs to be parsed and brought into a form suitable for the web frontend. Surely exist some feature differences between these two web frontends for VDR. Regards Tadi -- Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de live plugin developer http://live.vdr-developer.org 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] Can VDR record only new episodes of shows?
Hi Am Freitag, 3. Juni 2011 schrieb Henning Pingel: Am Freitag, den 03.06.2011, 15:01 +0200 schrieb Carsten Koch carstenkochelsd...@web.de: On Fri, 2011-06-03 at 08:28 -0400, John Klimek wrote: ... For example, I don't want to record every single episode of a certain show, but instead I just want the new episodes. That's one of the things VDRAdmin-AM can do for you. Where new is defined as one that you have not recorded yet. Aren't VDRadmin-AM and vdr-plugin-live both just using a feature that epgsearch provides for avoiding the recording of repeated shows? Yes, it is a basic feature of epgsearch and timers created from it. It is no 'special' feature of vdr-plugin-live. And AFAIK also no special feature of VDRAdmin-AM. Both web-frontends can be used to configure epgsearch accordingly. But it should also work from within the VDR menu, when epgsearch is installed. Regards Tadi -- Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de live plugin developer http://live.vdr-developer.org 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] [ANNOUNCE] dynamite plugin
Hi Am Donnerstag, 24. März 2011 schrieb Holger Schvestka: Am Donnerstag, den 24.03.2011, 11:38 +0200 schrieb Mika Laitio: [...] Maybe just adding a patch branch to http://projects.vdr-developer.org/git/?p=vdr.git;a=summary ? It could also contain some other known patches for 17.7, like the vdr-1.7.17-updatemarks-2.diff or vdr-1.7.17-updatemarks-3.diff... maybe kls adopts all this patches in vdr-1.7.18 ? Even if kls does not adopt this patch that fast, I will not add it to the above git repository. That GIT is maintained by me and it will contain only releases provided by kls. That is and will remain its intended purpose. Of course one of the intentions of that GIT is it to be cloned :) Host the clone on http://projects.vdr-developer.org and and apply the patch you mentioned yourself. The site projects.vdr-developer.org is open for everybody who want's to host a vdr related project ;) Regards Tadi -- Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de live plugin developer http://live.vdr-developer.org 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] RfC: add encryption and compression to VDR
Hi Am Samstag, 13. November 2010 schrieb Christian Tramnitz: Am 13.11.2010 11:23, schrieb Klaus Schmidinger: However, my suggestion would be to implement authentication, encryption and compression as an externel layer. Much like a proxy, which offers [...] I tend to agree with Dieter (and a few comments in vdrportal)... what the live-plugin currently does is about the fastest method of data transfer we could possibly have, so why not build on this? @Dieter: I haven't looked at the live internals in too much detail, for what part is tntnet being used and would we need to reuse this for the xml-http/JSON idea? tntnet and boost are not really common or light-weight, is there a simpler solution for that? The functions LIVE is using from boost are header only and are AFAIK meanwhile implemented by GCC in the TR1 C++ standard library extension. Thus boost should not be considered heavy weight. With tntnet it is a bit different. Tntnet does the complete http protocol handling incl. parsing the requests and providing the html c++ integration (in some way comparable how you merge html and php, but at compile time). It is based on an additional library (cxxtools) from the same developer Tommi Mäkitalo. I just checked the web-page[1] and found out that one of the newest features of cxxtools is now native support for xmlrpc (without the need for tntnet). It will also implement the complete http server needed. Tommi was very responsive during 'main' LIVE development and I know that he continues to be as I traditionally still join the #tntnet channel on freenode. And he lives in Germany and not how one would guess from his name in Finland. I just had a conversation with him on #tntnet and he would be glad if cxxtools (which by the way I just learned also supports JSON) could be used. Well at least if this project will make it beyond the 'being an idea' phase. Regards Tadi [1] http://www.tntnet.org/ -- Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de live plugin developer http://live.vdr-developer.org 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] RfC: add encryption and compression to VDR
Hi Am Samstag, 13. November 2010 schrieb Steffen Barszus: On Fri, 12 Nov 2010 23:10:23 +0100 Dieter Hametner dh+...@gekrumbel.de wrote: The live-plugin has support (contributed by third party developer) for SSL connections to its internal web-server. See the README file in LIVE for more details. The concept how LIVE works as plugin could be generalized to provide a 'generic' (SVDRP like) access via xml-http(s)-requests or via JSON etc. I like this idea a lot - additional advantage is that the access that way should be easier for the accessing applications. The general disadvantage of such an approach is, that it creates an 'officially unsupported' way to control VDR remotely. I mean it does not get 'standardized' by Klaus :) As long as more than one project is using this, it should be fine. Well the LIVE plugin could make use of this new infrastructure :) That could be number one but it is not a promise :) Tadi -- Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de live plugin developer http://live.vdr-developer.org 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] RfC: add encryption and compression to VDR
Hi Am Freitag, 12. November 2010 schrieb Christian Tramnitz: Right now when the needs of a vdr extension goes beyond core SVDRP capabilities a different approach is being used by the each extensions. Prominent examples are: - vdradmin (using native SVDRP and suffering from its performance, optional use of direct file access to epg data) - live-plugin (integrating into vdr as plugin) - vdr iphone remote (using native SVDRP and due the bad performance and encryption capabilities an optional web-based interface) (and I'm sure there are more) [...] Now I would like to start a few discussions related to this topic, the ones that come to my mind mind first are: - Should this be implemented as plugin or in core vdr as svdrp extension? - Would Klaus accept patches if this will be native SVDRP? - Are developers/maintainers of current or feature plugins/extensions interested in such a solution? - What technical implementation would make most sense? - Who would be willing to contribute to such a project? The live-plugin has support (contributed by third party developer) for SSL connections to its internal web-server. See the README file in LIVE for more details. The concept how LIVE works as plugin could be generalized to provide a 'generic' (SVDRP like) access via xml-http(s)-requests or via JSON etc. The general disadvantage of such an approach is, that it creates an 'officially unsupported' way to control VDR remotely. I mean it does not get 'standardized' by Klaus :) Regards Tadi -- Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de live plugin developer http://live.vdr-developer.org 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] LIVE: Missing streams for recordings
Hello Am Donnerstag, 27. August 2009 schrieb RalfGesellensetter: Am Mittwoch 26 August 2009 schrieb Christian Wieninger: please try the current cvs or git version: git clone git://projects.vdr-developer.org/vdr-plugin-live.git live Hi there, thanks for the hint, but: I miss precise instructions on how to proceed. I got the most recent version into /tmp. Further on, I tried make - resulting in: [ ... removed error codes ] You need the package 'vdr-dev' to build vdr plugins outside of VDR sources. I use the following small script to build LIVE outside of VDR sources (cd into the to level 'live' directory and execute): - snip - #!/bin/sh # make-live: call make in the vdr live plugin sources with correct settings. [ -d live ] || exit 0 mkdir -p .libs VDRDIR=/usr/include/vdr LIBDIR=.libs make $* snip - If you try a manual installation of the live-plugin into VDR you should carefully read the README file in the LIVE distribution. And you need to be aware, that different Linux distributions have VDR setups which differ from what is documented in VDR or LIVE. In your case I suggest to check also the LIVE-Threads on the german www.vdr- portal.de: Version 0.2.0 announce: http://www.vdr-portal.de/board/thread.php?threadid=76629 Version 0.1.0 announce: http://www.vdr-portal.de/board/thread.php?threadid=64821 There are also hints on how to build a Debian package from the LIVE sources in CVS/Git. Regards Dieter -- Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de live plugin developer http://live.vdr-developer.org ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] weekly or daily timers
Hello Am Dienstag, 21. April 2009 schrieb VDR User: I've been using epgsearch and vdradmind-am for years and I can't imagine not using them! Not to forget the LIVE plugin, which has a very good integration with epgsearch too. After all most of the LIVE timer functionality was provied by the epgsearch author himself. Kind regards Dieter P.S. I know it a little bit of advertising :) but its open source too -- Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de live plugin developer http://live.vdr-developer.org ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR-Live plugin
Hello Am Dienstag, 24. März 2009 schrieb Rob Davis: [...] I have it working. However, for the next version, is there a way to select two different streamdev profiles quickly. When I am home I would like to select streamdev TS, but when away extern? Sorry, that is currently not possible. Unfortunately there is only one 'user' accessing the LIVE plugin - as you can set only one password. There exist thoughts/proposals on implementing a multi-user feature in LIVE. This would enable the addition of individual settings for each user. Kind regards Dieter -- Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de live plugin developer http://live.vdr-developer.org ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] 1.7.2 xine plugin FIXMEs
Hello Am Donnerstag, 1. Januar 2009 schrieb Goga777: [...] Also is there a cvs/hg repository for vdr, no any cvs/hg repo for vdr Right. But there is a Git tree of VDR. Look at: http://git.gekrumbel.de/vdr.git and a clone of it on: http://projects.vdr-developer.org/git/?p=vdr.git Regards Dieter -- Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de live plugin developer http://live.vdr-developer.org ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.2
Hello Am Sonntag, 14. Dezember 2008 schrieb Klaus Schmidinger: VDR developer version 1.7.2 is now available at I just updated the VDR readonly sources Git tree hosted at http://projects.vdr-developer.org/projects/show/vdr The two public gitweb-access sites are in sync and can be found under these urls: http://git.gekrumbel.de/vdr.git http://projects.vdr-developer.org/git/?p=vdr.git Regards Dieter -- Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de live plugin developer http://live.vdr-developer.org ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] projects.vdr-developer.org launched
Hello Am Freitag, 12. Dezember 2008 schrieb Tobi: Hello! projects.vdr-developer.org is a place for community maintained VDR projects. The idea for this was born out of a survey conducted among VDR users, where it turned out, that even some VDR plug-ins that haven't been updated for years are still very popular. [...] Read more about this here: http://projects.vdr-developer.org http://projects.vdr-developer.org/wiki/project-management/Start Great to see this announced! Since I support Tobis initiative I decided to host the following two projects on projects.vdr-developer.org too. 1. The vdr-sources git tree (Maintained by skiller2k1 and me) 2. The LIVE plugin git tree (Maintained by Christian Wieninger and me) (*) I think it was a good decision to use git as the central SCM system for this because it supports a patch driven development modell very well. Regards Dieter (Tadi on vdr-portal.de) (*) The old LIVE plugin CVS is still alive, will be updated regularly and will remain at its current hosting. -- Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de live plugin developer http://live.vdr-developer.org ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Help with: vdr-1.7.1 + s2api + h264
Hello Am Freitag, 21. November 2008 schrieb [EMAIL PROTECTED]: There's a git repository for vdr at http://git.gekrumbel.de/?p=vdr.git Wouldn't it be appropriate to use it to maintain a working vdr+s2+h264 source tree ? I'm maintaining that aforementioned git repository. I didn't want to host different versions of VDR in this git repository (except the 'original sources' git). Ok, sorry I should have asked you first. I did setup this git as a kind of seed. It contains the development history (in terms of the official releases) of VDR since its beginning. I have the hope that the community picks it up and creates something usefull out of it. BTW is it used by a lot of people ? Unfortunately I don't think so. Nobody ever informed me about that he cloned it, added some patches and published them somewhere else. I know only of some experiments Tobias Grimm did with it. Look at git homepage http://git.or.cz/ for a list of public git hosting providers. ok. I'm not a h264 or s2api user yet, it would be very nice if some people could maintain such a repository. It's seem messy to get these patches working and questions about them are very recurrent. I'm no h264 and s2api user either. But helping to reduce this kind of mess was one of my motivations to setup the VDR git. Regards Dieter -- Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de live plugin developer http://live.vdr-developer.org ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Help with: vdr-1.7.1 + s2api + h264
Hello Am Donnerstag, 20. November 2008 schrieb [EMAIL PROTECTED]: Goga777 [EMAIL PROTECTED] writes: Hi I couldn't run properly vdr 171 + s2api + extension patch + s2api patch + h.264patch that's why I keep vdr 170 + s2api patch + h.264patch There's a git repository for vdr at http://git.gekrumbel.de/?p=vdr.git Wouldn't it be appropriate to use it to maintain a working vdr+s2+h264 source tree ? I'm maintaining that aforementioned git repository. I didn't want to host different versions of VDR in this git repository (except the 'original sources' git). This repository is intended to be used as a source for cloning own git repositories and pulling upcoming development changes provided by Klaus Schmidinger. If you clone it to a public git hoster (or publish it on some own server) and add the various patches (s2api, h.264 etc.), it will be easy for others to retrieve already patched versions of VDR to their local computers. If I get informed of such a repository I will be happy to add a link on my VDR git hosting site, to inform others about the patched VDR git existence. Look at git homepage http://git.or.cz/ for a list of public git hosting providers. Kind regards Dieter -- Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de live plugin developer http://live.vdr-developer.org ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Build plugin with different headers then in VDR distribution
Hello On Monday, 8. September 2008 Michael Stepanov wrote: Thanks a lot, Clemens, for your reply. This is my mistake that I didn't explain clearly what actually I need. I use LinuxMCE (http://linuxmce.com) with integrated VDR 1.6.0. I have just VDR headers and binary. So, I can easily build any plugins which have debian patch using dpkg-buildpackage. In that case the plugins work fine. But for those which don't have that there is an only one way to build them using common way - make plugins from the VDR source directory. So, I think I can make a symlink to patched headers in the $VDR_SORUCE/include/vdr and theoretically it should work. I started my contribution to the development of the LIVE plugin without installed vdr sources. I installed the vdr-dev package from e-tobi debian repository and used the following script to build the binary of the plugin. 'libvdr-live.so.1.6.0' is created in the .libs subdirectory then. Of course the binary had to be copied into the right installation path afterwards. #!/bin/sh # check if this are live sources # (there is an extra live subdir in the sources) [ -d live ] || exit 0 mkdir -p .libs VDRDIR=/usr/include/vdr LIBDIR=.libs make $* Kind regards Dieter Hametner -- Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de live plugin developer http://live.vdr-developer.org ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Build plugin with different headers then in VDR distribution
Hi Michael On Monday, 8. September 2008 Michael Stepanov wrote: Thanks a lot, Dieter, for your solution. It seems very useful. Especially when VDR installed from the package and not from the sources. But I don't understand clearly how to run your script? What parameters should be passed there? Just keyword plugins? And where in should be run? From the building pluguns directory? I just have somewhere in my $HOME the live sources directory. I just cd into it and execute 'make-live' (the name of the previously posted script in my ~/bin). That will create the 'default' target of the live plugins Makefile which is the binary. You can execute 'make-live clean' to clean the sources from build artefacts. What you pass to the script is what you would pass to the normal make call. That way I build only the live plugin. The sources of the live plugin are *not* in the PLUGINS/src/live subdirectory like it would be with 'normal' VDR plugin development. A side note: the same Makefile (inside the live sources, without any modifications) is also suitable to build the LIVE plugin inside the VDRs PLUGIN directory. Hope this helps :) Kind regards Dieter Hametner -- Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de live plugin developer http://live.vdr-developer.org ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR git tree (was: Re: VDR Development)
Hello This is an spin off from the VDR Development thread. On Sunday, 7. September 2008 Clemens Kirchgatterer wrote: Georg Acher [EMAIL PROTECTED] wrote: I also don't think that a vdr-repository would help in the development speed. Either the whole development procedure needs to be changed (more maintainer with KLS's approval) or it has no advantage compared to the .tgz-distribution. maybe using git, where you can pull into your own repository for privat vdr hacking and let other people check it out may be worth a thought. I've had this idea since the beginning of this year. But now I thought I give it a try. I present a VDR git at http://vdr.gekrumbel.de/git/?p=vdr.git First of all: This is not meant to be a fork of VDR development. Please read my explanation why it can't be: Git is a distributed source code management system. That means every git working tree contains the full history of the whole project plus the history added by the owner of a tree. The tree I present here is *read* *only* for the whole world. That means Michael Brückner or I will update it some time after Klaus releases a new VDR version or patch to the stable sources. Only code from Klaus will be committed into this tree. That means it is a exact copy of Klaus sources and the history of official VDR development. And it never will be more! Other developers will benefit from this work by having a base from where they can clone their own trees, add their contributions and publish their work as git trees too. They are strongly encouraged to make clear what distinguishes their trees from the original vanilla VDR. Whenever Klaus releases new code, they can merge the changes by pulling from this VDR tree. When we learn about such clones we will add them into a list of contribution work. Please let me (us) know when such a tree comes alive. Eventually somebody will take all the distributed contributions and merge them into one big all contributions tree. I am convinced that this approach gives Klaus the freedom to add features to VDR in the way he thinks is most appropriate for the overall stability and quality of his code. On the other side, using the distributed and collaborative approach, which is well supported by using git, gives the community the possibility to add enhancements to VDR and have a chance to make these changes trackable (no longer the need for everybody interested to go through the patch search hell). In essence this is an approach on better manageing the various patch sets floating around. This can only be successful if the most active VDR contributors adopt this approach and start working towards this goal. And it will need a lot of discipline of everybody involved. To contact Michael and myself you should use the email address: [EMAIL PROTECTED] Kind regards Dieter Hametner -- Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de live plugin developer http://live.vdr-developer.org ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] a simple locale question
Hello Am Dienstag, 4. September 2007 schrieb [EMAIL PROTECTED]: Hello, In writing a plugin that displays a date, it occurred to me that date in a locale-friendly way might be a good idea. What is the current 'blessed' way to make vdr display a date? I suppose it could be a setup option, but that just seems kindda drab. In the live plugin - http://live.vdr-developer.org/ - we use a two fold approach. Dates are formatted with strftime(3) which obeys for some of the format specifiers the current locale of the VDR. Additionally we 'translate' the format strings with the standard i18n support of VDR (e.g tr() macro). This allows the localization people to tailor to their special needs. Best regards Dieter -- Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de live plugin developer http://live.vdr-developer.org ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] po2i18n - converter for plugin backwards compatibility
Hi Udo Am Samstag, 18. August 2007 wrote Udo Richter: Hi list, I've uploaded a little perl script and instructions to convert from the new gettext based po i18n files to the old i18n.c system of VDR 1.5.6 and earlier. By using this script its easy to use the new po based i18n system for translations, and still compile the plugins with full i18n support all the way back to VDR 1.2.0. The script can either be used manually to generate the i18n.c file from the po files and a template, or automatically as part of the build process. Get it here: http://www.udo-richter.de/vdr/scripts.html#po2i18n http://www.udo-richter.de/vdr/scripts.en.html#po2i18n I kind of enhanced your script to use the CPAN module Locale::PO for reading the .po/.pot files. Your implementation did not handle multi line msgids and msgstrs well. My change adds all strings in the plugins .pot file to the resulting i18n.c file, even when no translation exists for the string and it does not sort the msgids. I called it pot2i18n.pl to take into account that it reads the .pot file too. Usage is analogous to po2i18n.pl. You must specifiy the plugins .pot file as first argument. Feel free to use my changes for your next version if you like. Regards Dieter -- Dieter Hametnermailto: [EMAIL PROTECTED] live plugin developer http://live.vdr-developer.org pot2i18n.pl.bz2 Description: BZip2 compressed data ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] po2i18n - converter for plugi n backwards compatibility
Hi
Am Sonntag, 19. August 2007 schrieb Udo Richter:
Dieter Hametner wrote:
I kind of enhanced your script to use the CPAN module Locale::PO for
reading the .po/.pot files. Your implementation did not handle multi line
msgids and msgstrs well.
Hmmm, ok, I don't have multi-line strings that need translation, but
this is probably worth a fix.
But I don't really want to depend on Locale::PO, as it is not very
likely to be installed on systems out there.
I'm aware of that. Debian sid has also an outdated package for it
('liblocale-po-perl' version 0.15 where as in CPAN it is version 0.17).
Still I think building on others work is one of the spirits of open source :)
My change adds all strings in the plugins .pot file to the resulting
i18n.c file, even when no translation exists for the string and it does
not sort the msgids.
Since all po files get updated too all the time, reading the pot file is
not really necessary.
With the Locale::PO package I needed a file where I would know of, that all
possible strings appear because the single .po files don't get merged
together.
Regards
Dieter
--
Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de
live plugin developer http://live.vdr-developer.org
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
