[mythtv] mythtv- code architecture

hendrixski hendrixski at storsint.com
Wed Jun 13 19:20:01 UTC 2007

Good documentation lowers the barrier to entry for new developers who
can make solid contributions.  Making that documentation easily
accessible wouldn't be a bad idea either.

I've been reading the wiki, perusing the lack of documentation on
doxygen, and reading a book on Qt.  I feel like I'm playing Resident
Evil or some other video game where you have to go through a maze
collecting clues and then you have to defeat teh final boss of the
internet before you find what you need to develop something for mythtv.

It's my first attempt at joining an open source project... so I'm gonna
stick it out and learn stuff. I just wanted to say that I sympathize
with Khalid and the long long journey he'll undertake to learn how to
develop stuff for mythtv.

 - hendrixski

P.S. I'd love to see a diagram of the architecture as well.  Something
to help me understand how to code for it.  Just a nice detailed picture
would answer SSSSOOOO many questions for me that I'd probably not have
to pester anyone on the IRC channel for a while.

Stuart Morgan wrote:
>> Also, the most documentation there is for the code is on the wiki, and
>> it's rather light. The best way is to just dive in and read the peices
>> you are interested in.
> There is some incomplete doxygen documentation at
> http://www.cuymedia.net/doxygen-dev-docs/html/
> I don't know when it was last re-sync'd. I suspect that Daniel only does it at 
> each major release.
> It might not be a bad idea to mirror this on the mythtv.org website and maybe 
> include a set for the development version too (updated weekly).

More information about the mythtv-dev mailing list