VDR Wiki:Suggestions for improvement: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 4: | Line 4: | ||
:You can construct such a documentation with doxygen or have a look at http://vdr.computer-wiki.de/doxygen/vdrdoxy-1.3.31/ (German) and http://vdr.computer-wiki.de/doxygen/ <br>[[User:Wirbel|Wirbel]] 20:41, 21 Oct 2005 (CEST) |
:You can construct such a documentation with doxygen or have a look at http://vdr.computer-wiki.de/doxygen/vdrdoxy-1.3.31/ (German) and http://vdr.computer-wiki.de/doxygen/ <br>[[User:Wirbel|Wirbel]] 20:41, 21 Oct 2005 (CEST) |
||
doxygen is a really cool tool, but it's not really the same as |
|||
genuine human-written documentation. There are lots of nice tidbits and |
|||
knowledge for VDR developers hidden all over the web, |
|||
but it's quite hard to find and quite incomplete. |
|||
<br>[[User:Dude]] 21:41, 21 Oct 2005 (CEST) |
Latest revision as of 21:56, 21 October 2005
I would love to see a section for VDR developers and hackers. Since the VDR code seems to be mostly devoit of comments, a roadmap to the main classes and hope they interact would be very useful. For example, what is the relationship between EPG scanning (implemented in eitscan and the Set commands use for filtering)?
- You can construct such a documentation with doxygen or have a look at http://vdr.computer-wiki.de/doxygen/vdrdoxy-1.3.31/ (German) and http://vdr.computer-wiki.de/doxygen/
Wirbel 20:41, 21 Oct 2005 (CEST)
doxygen is a really cool tool, but it's not really the same as
genuine human-written documentation. There are lots of nice tidbits and
knowledge for VDR developers hidden all over the web,
but it's quite hard to find and quite incomplete.
User:Dude 21:41, 21 Oct 2005 (CEST)