Mailing List Archive: MythTV: Dev

Documentation

Index | Next | Previous | View Threaded

nav.jagpal at gmail

Feb 6, 2005, 10:35 PM

Post #1 of 21 (3284 views)
Permalink

Documentation

Hi,

I have just joined the mythtv-dev mailing list and want to participate
in the Mythtv project.

I want to participate because I feel that it's time to give back to the project.

Is there a need for any type of documentation, manuals, etc?

I do not see a TODO list on the site for new-comers, so if anyone can
throw something my way that a newcomer to the project should be able
to handle, I would greatly appriciate it.

I'm a newcomer to the project, not to the world of coding. However, I
would prefer to work on documentation or light coding projects to
start with.

Thanks in advance
--
Nav

danielk at mrl

Feb 7, 2005, 6:24 AM

Post #2 of 21 (3205 views)
Permalink

Re: Documentation [In reply to]

On Sun, 6 Feb 2005, Nav Jagpal wrote:
]Is there a need for any type of documentation, manuals, etc?

There is a need for developer documentation. Starting with a guide to
theming and a guide to producing a debug build and a backtrace for bug
reporting. But we also need an overview of the classes and how they
interact and something like doxygen for the code itself.

]I do not see a TODO list on the site for new-comers, so if anyone can
]throw something my way that a newcomer to the project should be able
]to handle, I would greatly appriciate it.

Wade through http://www.mythtv.org/bugs/

]I'm a newcomer to the project, not to the world of coding. However, I
]would prefer to work on documentation or light coding projects to
]start with.

That's not a bad idea. People have written architecture overviews and
there is a Wiki at mythtv.info, some of the information in them could be
used to improve the official docs. But there is nothing out there that
tells you how say LiveTV works:

TVPlay on the frontend requests a recorder from the backend via the
RemoteRequestNextFreeRecorder function in remoteutil.cpp. It opens a
socket and sends a "GET_NEXT_FREE_RECORDER" to the master backend. The
recorder number, hostname and port is used to create a RemoteEncoder
class. This RemoteEncoder in turn represents a TVRec on a backend with
which TVPlay communicates. First TVPlay ensures that it is valid and
working, and then changing its internal state to
kState_WatchingLiveTV. When TVPlay enters the kState_WatchingLiveTV
step it tells TVRec to reset its internal state and setup a
ringbuffer, it then sets up its own ringbuffer on the same file. Once
this is done it calls SpawnLiveTV() in TVRec, this simply attempts to
change the TVRec's state to kState_WatchingLiveTV. TVPlay now disables
the screensaver and attempts to start the NuppelVideoPlayer, and if
starting the player is successful waits for the recorder to start.

What TVRec does when it enters WatchingLiveTV could be covered
separately. As could the NuppelVideoPlayer, which actually plays all
video files and not just NuppelVideo files.

I just got this from reading the code just now, but I can see this being
useful to someone getting started with MythTV. I glossed over some
details but basically described what goes on.

-- Daniel

brad+mydev at templetons

Feb 7, 2005, 4:13 PM

Post #3 of 21 (3202 views)
Permalink

Re: Documentation [In reply to]

On Mon, Feb 07, 2005 at 09:24:57AM -0500, Daniel Thor Kristjansson wrote:
> On Sun, 6 Feb 2005, Nav Jagpal wrote:
> ]Is there a need for any type of documentation, manuals, etc?
>
> There is a need for developer documentation. Starting with a guide to
> theming and a guide to producing a debug build and a backtrace for bug
> reporting. But we also need an overview of the classes and how they
> interact and something like doxygen for the code itself.

When I started looking at the code I would have loved to have seen
docs on the scheduler, on the frontend protocol. Also, significant
sections of the code are uncommented beyond having descriptive symbol
names -- so adding comments to variable names and function names would
be an important part of documenting the classes.

As for user docs, one start is reading mythtv-users mailing list and
seeing what things people are asking the most questions about. In some
cases it is undocumented stuff, in other cases it is documented but
they are not finding the documentation. In the latter case, it's
a challenge to reorganize those docs so that even an idiot can find the
answer to their question.

There are also many levels of users, and as Mythtv grows in popularity,
you will see more users who need to be walked through things, folks who
are less linux-familiar etc.

nav.jagpal at gmail

Feb 7, 2005, 6:41 PM

Post #4 of 21 (3211 views)
Permalink

Re: Documentation [In reply to]

Thanks for all of the documentation related advice.

In the next few days I will try to go through existing documentation,
take a look at the users mailing list, and take a look at the source
code (can someone suggest a starting place for the source?... probably
a better for my understanding if I struggle with it anyhow)

Before I sit down and start writing any documentation, I'll send a
quick outline of what I will be attempting to do, so that I can get
some more advice/comments/suggests before starting.

Just wanted to send a note so that the people that have already
responded know that I didn't send an email and run away.

Thanks again
--
Nav

On Mon, 7 Feb 2005 16:13:22 -0800, Brad Templeton
<brad+mydev [at] templetons> wrote:
> On Mon, Feb 07, 2005 at 09:24:57AM -0500, Daniel Thor Kristjansson wrote:
> > On Sun, 6 Feb 2005, Nav Jagpal wrote:
> > ]Is there a need for any type of documentation, manuals, etc?
> >
> > There is a need for developer documentation. Starting with a guide to
> > theming and a guide to producing a debug build and a backtrace for bug
> > reporting. But we also need an overview of the classes and how they
> > interact and something like doxygen for the code itself.
>
> When I started looking at the code I would have loved to have seen
> docs on the scheduler, on the frontend protocol. Also, significant
> sections of the code are uncommented beyond having descriptive symbol
> names -- so adding comments to variable names and function names would
> be an important part of documenting the classes.
>
> As for user docs, one start is reading mythtv-users mailing list and
> seeing what things people are asking the most questions about. In some
> cases it is undocumented stuff, in other cases it is documented but
> they are not finding the documentation. In the latter case, it's
> a challenge to reorganize those docs so that even an idiot can find the
> answer to their question.
>
> There are also many levels of users, and as Mythtv grows in popularity,
> you will see more users who need to be walked through things, folks who
> are less linux-familiar etc.
>

nav.jagpal at gmail

Feb 16, 2005, 2:50 PM

Post #5 of 21 (3184 views)
Permalink

Re: Documentation [In reply to]

MythTV has been getting more and more popular. Now when I mention the
software to someone, they actually know what I'm talking about pretty
much right away.

That is why I think a step-by-step document for installing, and
perhaps even using, MythTV would be a good to get a larger user
community.

I know that a lot of us out there have our favourite distros, hardware
encoders etc.. And the combinations of different types of hardware is
massive - but what about a document for those non-Linux type people?

Document that outlines: hardware (video card, encoder card, sound
card, distro) setup. ?

For example, I use Debian, and to avoid the whole TV-out hassle, I
just used the onboard video card and a VGA->PC converter from KWorld
(<$100 CDN).

When I went to create my Mythtv box, I had to rumble around the Net
looking for various sources.. I wish I could have found a document
that said "Hey.. if you get this sound card, video card, etc.. , which
will cost you $$ dollars, you can build this box.. And if you have a
sound card and video card that *just works*, you'll be set too".

Comments/suggestions?

On Mon, 7 Feb 2005 18:41:32 -0800, Nav Jagpal <nav.jagpal [at] gmail> wrote:
> Thanks for all of the documentation related advice.
>
> In the next few days I will try to go through existing documentation,
> take a look at the users mailing list, and take a look at the source
> code (can someone suggest a starting place for the source?... probably
> a better for my understanding if I struggle with it anyhow)
>
> Before I sit down and start writing any documentation, I'll send a
> quick outline of what I will be attempting to do, so that I can get
> some more advice/comments/suggests before starting.
>
> Just wanted to send a note so that the people that have already
> responded know that I didn't send an email and run away.
>
> Thanks again
> --
> Nav
>
>
> On Mon, 7 Feb 2005 16:13:22 -0800, Brad Templeton
> <brad+mydev [at] templetons> wrote:
> > On Mon, Feb 07, 2005 at 09:24:57AM -0500, Daniel Thor Kristjansson wrote:
> > > On Sun, 6 Feb 2005, Nav Jagpal wrote:
> > > ]Is there a need for any type of documentation, manuals, etc?
> > >
> > > There is a need for developer documentation. Starting with a guide to
> > > theming and a guide to producing a debug build and a backtrace for bug
> > > reporting. But we also need an overview of the classes and how they
> > > interact and something like doxygen for the code itself.
> >
> > When I started looking at the code I would have loved to have seen
> > docs on the scheduler, on the frontend protocol. Also, significant
> > sections of the code are uncommented beyond having descriptive symbol
> > names -- so adding comments to variable names and function names would
> > be an important part of documenting the classes.
> >
> > As for user docs, one start is reading mythtv-users mailing list and
> > seeing what things people are asking the most questions about. In some
> > cases it is undocumented stuff, in other cases it is documented but
> > they are not finding the documentation. In the latter case, it's
> > a challenge to reorganize those docs so that even an idiot can find the
> > answer to their question.
> >
> > There are also many levels of users, and as Mythtv grows in popularity,
> > you will see more users who need to be walked through things, folks who
> > are less linux-familiar etc.
> >
>

blammo.doh at gmail

Feb 16, 2005, 4:41 PM

Post #6 of 21 (3186 views)
Permalink

Re: Documentation [In reply to]

On Wed, 16 Feb 2005 14:50:08 -0800, Nav Jagpal <nav.jagpal [at] gmail> wrote:
> MythTV has been getting more and more popular. Now when I mention the
> software to someone, they actually know what I'm talking about pretty
> much right away.
>
> That is why I think a step-by-step document for installing, and
> perhaps even using, MythTV would be a good to get a larger user
> community.
>
> I know that a lot of us out there have our favourite distros, hardware
> encoders etc.. And the combinations of different types of hardware is
> massive - but what about a document for those non-Linux type people?
>
> Document that outlines: hardware (video card, encoder card, sound
> card, distro) setup. ?
>
> For example, I use Debian, and to avoid the whole TV-out hassle, I
> just used the onboard video card and a VGA->PC converter from KWorld
> (<$100 CDN).
>
> When I went to create my Mythtv box, I had to rumble around the Net
> looking for various sources.. I wish I could have found a document
> that said "Hey.. if you get this sound card, video card, etc.. , which
> will cost you $$ dollars, you can build this box.. And if you have a
> sound card and video card that *just works*, you'll be set too".
>
> Comments/suggestions?
>
>
> On Mon, 7 Feb 2005 18:41:32 -0800, Nav Jagpal <nav.jagpal [at] gmail> wrote:
> > Thanks for all of the documentation related advice.
> >
> > In the next few days I will try to go through existing documentation,
> > take a look at the users mailing list, and take a look at the source
> > code (can someone suggest a starting place for the source?... probably
> > a better for my understanding if I struggle with it anyhow)
> >
> > Before I sit down and start writing any documentation, I'll send a
> > quick outline of what I will be attempting to do, so that I can get
> > some more advice/comments/suggests before starting.
> >
> > Just wanted to send a note so that the people that have already
> > responded know that I didn't send an email and run away.
> >
> > Thanks again
> > --
> > Nav
> >
> >
> > On Mon, 7 Feb 2005 16:13:22 -0800, Brad Templeton
> > <brad+mydev [at] templetons> wrote:
> > > On Mon, Feb 07, 2005 at 09:24:57AM -0500, Daniel Thor Kristjansson wrote:
> > > > On Sun, 6 Feb 2005, Nav Jagpal wrote:
> > > > ]Is there a need for any type of documentation, manuals, etc?
> > > >
> > > > There is a need for developer documentation. Starting with a guide to
> > > > theming and a guide to producing a debug build and a backtrace for bug
> > > > reporting. But we also need an overview of the classes and how they
> > > > interact and something like doxygen for the code itself.
> > >
> > > When I started looking at the code I would have loved to have seen
> > > docs on the scheduler, on the frontend protocol. Also, significant
> > > sections of the code are uncommented beyond having descriptive symbol
> > > names -- so adding comments to variable names and function names would
> > > be an important part of documenting the classes.
> > >
> > > As for user docs, one start is reading mythtv-users mailing list and
> > > seeing what things people are asking the most questions about. In some
> > > cases it is undocumented stuff, in other cases it is documented but
> > > they are not finding the documentation. In the latter case, it's
> > > a challenge to reorganize those docs so that even an idiot can find the
> > > answer to their question.
> > >
> > > There are also many levels of users, and as Mythtv grows in popularity,
> > > you will see more users who need to be walked through things, folks who
> > > are less linux-familiar etc.
> > >
> >
>
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>
>

Might not be a bad idea to have a myth-docs email list. That would
facilitate coop development of docs, give you somewhere to post drafts
for review and testing, etc. Some of us get paid to proof other
peoples work, but are terrible at creating our own from scratch.

brad+mydev at templetons

Feb 16, 2005, 5:44 PM

Post #7 of 21 (3186 views)
Permalink

Re: Documentation [In reply to]

On Wed, Feb 16, 2005 at 02:50:08PM -0800, Nav Jagpal wrote:
> That is why I think a step-by-step document for installing, and
> perhaps even using, MythTV would be a good to get a larger user
> community.
>
> Comments/suggestions?

Sounds good, perhaps you can start writing on the mythtv.info wiki
and others will join in? There are of course lots of scattered
docs so a good thing for you to do to start would be to talk to their
authors and see what can be done about consolidating. (Most people don't
want to mirror their own docs because that gets out of sync and they
no longer learn how many are reading them etc.)

eggi-spam at menandmice

Feb 17, 2005, 3:28 AM

Post #8 of 21 (3188 views)
Permalink

Re: Documentation [In reply to]

On 17.2.2005, at 01:44, Brad Templeton wrote:

> On Wed, Feb 16, 2005 at 02:50:08PM -0800, Nav Jagpal wrote:
>> That is why I think a step-by-step document for installing, and
>> perhaps even using, MythTV would be a good to get a larger user
>> community.
>>
>> Comments/suggestions?
>
> Sounds good, perhaps you can start writing on the mythtv.info wiki
> and others will join in? There are of course lots of scattered
> docs so a good thing for you to do to start would be to talk to their
> authors and see what can be done about consolidating. (Most people
> don't
> want to mirror their own docs because that gets out of sync and they
> no longer learn how many are reading them etc.)
>

One thing that I think would be useful (but haven't had the time to add
myself [tm]) is a glossary. A single page listing short definitions of
common terms (OSD, XvMC, nuv, msp3400 etc.) and how the relate to
MythTV, along with links to more detailed info for each. Of course,
all of this info is available to anyone that knows how to use google,
but having it all on one page would help a lot of newbies ploughing
through the docs for the first time.

Eggert

nav.jagpal at gmail

Feb 17, 2005, 8:35 AM

Post #9 of 21 (3162 views)
Permalink

Re: Documentation [In reply to]

I think a myth-docs mailing list is a great idea.

How do I go about requesting such a list?

Thanks in advance

On Wed, 16 Feb 2005 17:41:57 -0700, Blammo <blammo.doh [at] gmail> wrote:
> On Wed, 16 Feb 2005 14:50:08 -0800, Nav Jagpal <nav.jagpal [at] gmail> wrote:
> > MythTV has been getting more and more popular. Now when I mention the
> > software to someone, they actually know what I'm talking about pretty
> > much right away.
> >
> > That is why I think a step-by-step document for installing, and
> > perhaps even using, MythTV would be a good to get a larger user
> > community.
> >
> > I know that a lot of us out there have our favourite distros, hardware
> > encoders etc.. And the combinations of different types of hardware is
> > massive - but what about a document for those non-Linux type people?
> >
> > Document that outlines: hardware (video card, encoder card, sound
> > card, distro) setup. ?
> >
> > For example, I use Debian, and to avoid the whole TV-out hassle, I
> > just used the onboard video card and a VGA->PC converter from KWorld
> > (<$100 CDN).
> >
> > When I went to create my Mythtv box, I had to rumble around the Net
> > looking for various sources.. I wish I could have found a document
> > that said "Hey.. if you get this sound card, video card, etc.. , which
> > will cost you $$ dollars, you can build this box.. And if you have a
> > sound card and video card that *just works*, you'll be set too".
> >
> > Comments/suggestions?
> >
> >
> > On Mon, 7 Feb 2005 18:41:32 -0800, Nav Jagpal <nav.jagpal [at] gmail> wrote:
> > > Thanks for all of the documentation related advice.
> > >
> > > In the next few days I will try to go through existing documentation,
> > > take a look at the users mailing list, and take a look at the source
> > > code (can someone suggest a starting place for the source?... probably
> > > a better for my understanding if I struggle with it anyhow)
> > >
> > > Before I sit down and start writing any documentation, I'll send a
> > > quick outline of what I will be attempting to do, so that I can get
> > > some more advice/comments/suggests before starting.
> > >
> > > Just wanted to send a note so that the people that have already
> > > responded know that I didn't send an email and run away.
> > >
> > > Thanks again
> > > --
> > > Nav
> > >
> > >
> > > On Mon, 7 Feb 2005 16:13:22 -0800, Brad Templeton
> > > <brad+mydev [at] templetons> wrote:
> > > > On Mon, Feb 07, 2005 at 09:24:57AM -0500, Daniel Thor Kristjansson wrote:
> > > > > On Sun, 6 Feb 2005, Nav Jagpal wrote:
> > > > > ]Is there a need for any type of documentation, manuals, etc?
> > > > >
> > > > > There is a need for developer documentation. Starting with a guide to
> > > > > theming and a guide to producing a debug build and a backtrace for bug
> > > > > reporting. But we also need an overview of the classes and how they
> > > > > interact and something like doxygen for the code itself.
> > > >
> > > > When I started looking at the code I would have loved to have seen
> > > > docs on the scheduler, on the frontend protocol. Also, significant
> > > > sections of the code are uncommented beyond having descriptive symbol
> > > > names -- so adding comments to variable names and function names would
> > > > be an important part of documenting the classes.
> > > >
> > > > As for user docs, one start is reading mythtv-users mailing list and
> > > > seeing what things people are asking the most questions about. In some
> > > > cases it is undocumented stuff, in other cases it is documented but
> > > > they are not finding the documentation. In the latter case, it's
> > > > a challenge to reorganize those docs so that even an idiot can find the
> > > > answer to their question.
> > > >
> > > > There are also many levels of users, and as Mythtv grows in popularity,
> > > > you will see more users who need to be walked through things, folks who
> > > > are less linux-familiar etc.
> > > >
> > >
> >
> >
> > _______________________________________________
> > mythtv-dev mailing list
> > mythtv-dev [at] mythtv
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
> >
> >
>
> Might not be a bad idea to have a myth-docs email list. That would
> facilitate coop development of docs, give you somewhere to post drafts
> for review and testing, etc. Some of us get paid to proof other
> peoples work, but are terrible at creating our own from scratch.
>
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>
>
>

dan.littlejohn at gmail

Feb 17, 2005, 9:14 AM

Post #10 of 21 (3173 views)
Permalink

Re: Documentation [In reply to]

For developers, what about using a tool like Doxygen to document by
pulling comments out of the source into a html page. That way they
can stay current with the code will minimal effort?

http://www.stack.nl/~dimitri/doxygen/

Dan

On Thu, 17 Feb 2005 08:35:35 -0800, Nav Jagpal <nav.jagpal [at] gmail> wrote:
> I think a myth-docs mailing list is a great idea.
>
> How do I go about requesting such a list?
>
> Thanks in advance
>
>
> On Wed, 16 Feb 2005 17:41:57 -0700, Blammo <blammo.doh [at] gmail> wrote:
> > On Wed, 16 Feb 2005 14:50:08 -0800, Nav Jagpal <nav.jagpal [at] gmail> wrote:
> > > MythTV has been getting more and more popular. Now when I mention the
> > > software to someone, they actually know what I'm talking about pretty
> > > much right away.
> > >
> > > That is why I think a step-by-step document for installing, and
> > > perhaps even using, MythTV would be a good to get a larger user
> > > community.
> > >
> > > I know that a lot of us out there have our favourite distros, hardware
> > > encoders etc.. And the combinations of different types of hardware is
> > > massive - but what about a document for those non-Linux type people?
> > >
> > > Document that outlines: hardware (video card, encoder card, sound
> > > card, distro) setup. ?
> > >
> > > For example, I use Debian, and to avoid the whole TV-out hassle, I
> > > just used the onboard video card and a VGA->PC converter from KWorld
> > > (<$100 CDN).
> > >
> > > When I went to create my Mythtv box, I had to rumble around the Net
> > > looking for various sources.. I wish I could have found a document
> > > that said "Hey.. if you get this sound card, video card, etc.. , which
> > > will cost you $$ dollars, you can build this box.. And if you have a
> > > sound card and video card that *just works*, you'll be set too".
> > >
> > > Comments/suggestions?
> > >
> > >
> > > On Mon, 7 Feb 2005 18:41:32 -0800, Nav Jagpal <nav.jagpal [at] gmail> wrote:
> > > > Thanks for all of the documentation related advice.
> > > >
> > > > In the next few days I will try to go through existing documentation,
> > > > take a look at the users mailing list, and take a look at the source
> > > > code (can someone suggest a starting place for the source?... probably
> > > > a better for my understanding if I struggle with it anyhow)
> > > >
> > > > Before I sit down and start writing any documentation, I'll send a
> > > > quick outline of what I will be attempting to do, so that I can get
> > > > some more advice/comments/suggests before starting.
> > > >
> > > > Just wanted to send a note so that the people that have already
> > > > responded know that I didn't send an email and run away.
> > > >
> > > > Thanks again
> > > > --
> > > > Nav
> > > >
> > > >
> > > > On Mon, 7 Feb 2005 16:13:22 -0800, Brad Templeton
> > > > <brad+mydev [at] templetons> wrote:
> > > > > On Mon, Feb 07, 2005 at 09:24:57AM -0500, Daniel Thor Kristjansson wrote:
> > > > > > On Sun, 6 Feb 2005, Nav Jagpal wrote:
> > > > > > ]Is there a need for any type of documentation, manuals, etc?
> > > > > >
> > > > > > There is a need for developer documentation. Starting with a guide to
> > > > > > theming and a guide to producing a debug build and a backtrace for bug
> > > > > > reporting. But we also need an overview of the classes and how they
> > > > > > interact and something like doxygen for the code itself.
> > > > >
> > > > > When I started looking at the code I would have loved to have seen
> > > > > docs on the scheduler, on the frontend protocol. Also, significant
> > > > > sections of the code are uncommented beyond having descriptive symbol
> > > > > names -- so adding comments to variable names and function names would
> > > > > be an important part of documenting the classes.
> > > > >
> > > > > As for user docs, one start is reading mythtv-users mailing list and
> > > > > seeing what things people are asking the most questions about. In some
> > > > > cases it is undocumented stuff, in other cases it is documented but
> > > > > they are not finding the documentation. In the latter case, it's
> > > > > a challenge to reorganize those docs so that even an idiot can find the
> > > > > answer to their question.
> > > > >
> > > > > There are also many levels of users, and as Mythtv grows in popularity,
> > > > > you will see more users who need to be walked through things, folks who
> > > > > are less linux-familiar etc.
> > > > >
> > > >
> > >
> > >
> > > _______________________________________________
> > > mythtv-dev mailing list
> > > mythtv-dev [at] mythtv
> > > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
> > >
> > >
> >
> > Might not be a bad idea to have a myth-docs email list. That would
> > facilitate coop development of docs, give you somewhere to post drafts
> > for review and testing, etc. Some of us get paid to proof other
> > peoples work, but are terrible at creating our own from scratch.
> >
> >
> > _______________________________________________
> > mythtv-dev mailing list
> > mythtv-dev [at] mythtv
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
> >
> >
> >
>
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>
>
>

tommck at gmail

Feb 17, 2005, 11:35 AM

Post #11 of 21 (3175 views)
Permalink

RE: Documentation [In reply to]

<tongueInCheek>

This would require that there were comments in the code :)

</tongueInCheek>

> Message: 18
> Date: Thu, 17 Feb 2005 11:14:45 -0600
> From: Dan Littlejohn <dan.littlejohn [at] gmail>
> Subject: Re: [mythtv] Documentation
> To: Nav Jagpal <nav.jagpal [at] gmail>, Development of mythtv
> <mythtv-dev [at] mythtv>
> Message-ID: <b1fb43ef0502170914793c43d6 [at] mail>
> Content-Type: text/plain; charset=US-ASCII
>
> For developers, what about using a tool like Doxygen to document by
> pulling comments out of the source into a html page. That way they
> can stay current with the code will minimal effort?
>
> http://www.stack.nl/~dimitri/doxygen/
>
> Dan

nav.jagpal at gmail

Feb 17, 2005, 12:14 PM

Post #12 of 21 (3179 views)
Permalink

Re: RE: Documentation [In reply to]

The practice of writing development documentation would definitely
improve one's understanding of the code.

However, I would like to start with user documentation. I'm sure there
is someone out there that would like to join the development process,
and what is a better way then documenting what is currently there.

On Thu, 17 Feb 2005 14:35:22 -0500, Tom McKearney <tommck [at] gmail> wrote:
> <tongueInCheek>
>
> This would require that there were comments in the code :)
>
> </tongueInCheek>
>
> > Message: 18
> > Date: Thu, 17 Feb 2005 11:14:45 -0600
> > From: Dan Littlejohn <dan.littlejohn [at] gmail>
> > Subject: Re: [mythtv] Documentation
> > To: Nav Jagpal <nav.jagpal [at] gmail>, Development of mythtv
> > <mythtv-dev [at] mythtv>
> > Message-ID: <b1fb43ef0502170914793c43d6 [at] mail>
> > Content-Type: text/plain; charset=US-ASCII
> >
> > For developers, what about using a tool like Doxygen to document by
> > pulling comments out of the source into a html page. That way they
> > can stay current with the code will minimal effort?
> >
> > http://www.stack.nl/~dimitri/doxygen/
> >
> > Dan
>
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>
>
>

alandgonzalez at gmail

Feb 17, 2005, 1:48 PM

Post #13 of 21 (3162 views)
Permalink

Re: Documentation [In reply to]

You mean like:

http://www.gonzalezfamily.org/devel/mfddocs/html
http://www.gonzalezfamily.org/devel/mfedocs/html
http://www.gonzalezfamily.org/devel/mythtvdocs/html

Though this is just there so that I can look through mfd more quickly.

Alan

On Thu, 17 Feb 2005 11:14:45 -0600, Dan Littlejohn
<dan.littlejohn [at] gmail> wrote:
> For developers, what about using a tool like Doxygen to document by
> pulling comments out of the source into a html page. That way they
> can stay current with the code will minimal effort?
>
> http://www.stack.nl/~dimitri/doxygen/
>
> Dan
>
>
> On Thu, 17 Feb 2005 08:35:35 -0800, Nav Jagpal <nav.jagpal [at] gmail> wrote:
> > I think a myth-docs mailing list is a great idea.
> >
> > How do I go about requesting such a list?
> >
> > Thanks in advance
> >
> >
> > On Wed, 16 Feb 2005 17:41:57 -0700, Blammo <blammo.doh [at] gmail> wrote:
> > > On Wed, 16 Feb 2005 14:50:08 -0800, Nav Jagpal <nav.jagpal [at] gmail> wrote:
> > > > MythTV has been getting more and more popular. Now when I mention the
> > > > software to someone, they actually know what I'm talking about pretty
> > > > much right away.
> > > >
> > > > That is why I think a step-by-step document for installing, and
> > > > perhaps even using, MythTV would be a good to get a larger user
> > > > community.
> > > >
> > > > I know that a lot of us out there have our favourite distros, hardware
> > > > encoders etc.. And the combinations of different types of hardware is
> > > > massive - but what about a document for those non-Linux type people?
> > > >
> > > > Document that outlines: hardware (video card, encoder card, sound
> > > > card, distro) setup. ?
> > > >
> > > > For example, I use Debian, and to avoid the whole TV-out hassle, I
> > > > just used the onboard video card and a VGA->PC converter from KWorld
> > > > (<$100 CDN).
> > > >
> > > > When I went to create my Mythtv box, I had to rumble around the Net
> > > > looking for various sources.. I wish I could have found a document
> > > > that said "Hey.. if you get this sound card, video card, etc.. , which
> > > > will cost you $$ dollars, you can build this box.. And if you have a
> > > > sound card and video card that *just works*, you'll be set too".
> > > >
> > > > Comments/suggestions?
> > > >
> > > >
> > > > On Mon, 7 Feb 2005 18:41:32 -0800, Nav Jagpal <nav.jagpal [at] gmail> wrote:
> > > > > Thanks for all of the documentation related advice.
> > > > >
> > > > > In the next few days I will try to go through existing documentation,
> > > > > take a look at the users mailing list, and take a look at the source
> > > > > code (can someone suggest a starting place for the source?... probably
> > > > > a better for my understanding if I struggle with it anyhow)
> > > > >
> > > > > Before I sit down and start writing any documentation, I'll send a
> > > > > quick outline of what I will be attempting to do, so that I can get
> > > > > some more advice/comments/suggests before starting.
> > > > >
> > > > > Just wanted to send a note so that the people that have already
> > > > > responded know that I didn't send an email and run away.
> > > > >
> > > > > Thanks again
> > > > > --
> > > > > Nav
> > > > >
> > > > >
> > > > > On Mon, 7 Feb 2005 16:13:22 -0800, Brad Templeton
> > > > > <brad+mydev [at] templetons> wrote:
> > > > > > On Mon, Feb 07, 2005 at 09:24:57AM -0500, Daniel Thor Kristjansson wrote:
> > > > > > > On Sun, 6 Feb 2005, Nav Jagpal wrote:
> > > > > > > ]Is there a need for any type of documentation, manuals, etc?
> > > > > > >
> > > > > > > There is a need for developer documentation. Starting with a guide to
> > > > > > > theming and a guide to producing a debug build and a backtrace for bug
> > > > > > > reporting. But we also need an overview of the classes and how they
> > > > > > > interact and something like doxygen for the code itself.
> > > > > >
> > > > > > When I started looking at the code I would have loved to have seen
> > > > > > docs on the scheduler, on the frontend protocol. Also, significant
> > > > > > sections of the code are uncommented beyond having descriptive symbol
> > > > > > names -- so adding comments to variable names and function names would
> > > > > > be an important part of documenting the classes.
> > > > > >
> > > > > > As for user docs, one start is reading mythtv-users mailing list and
> > > > > > seeing what things people are asking the most questions about. In some
> > > > > > cases it is undocumented stuff, in other cases it is documented but
> > > > > > they are not finding the documentation. In the latter case, it's
> > > > > > a challenge to reorganize those docs so that even an idiot can find the
> > > > > > answer to their question.
> > > > > >
> > > > > > There are also many levels of users, and as Mythtv grows in popularity,
> > > > > > you will see more users who need to be walked through things, folks who
> > > > > > are less linux-familiar etc.
> > > > > >
> > > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > mythtv-dev mailing list
> > > > mythtv-dev [at] mythtv
> > > > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
> > > >
> > > >
> > >
> > > Might not be a bad idea to have a myth-docs email list. That would
> > > facilitate coop development of docs, give you somewhere to post drafts
> > > for review and testing, etc. Some of us get paid to proof other
> > > peoples work, but are terrible at creating our own from scratch.
> > >
> > >
> > > _______________________________________________
> > > mythtv-dev mailing list
> > > mythtv-dev [at] mythtv
> > > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
> > >
> > >
> > >
> >
> >
> > _______________________________________________
> > mythtv-dev mailing list
> > mythtv-dev [at] mythtv
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
> >
> >
> >
>
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>
>
>

jra at baylink

Feb 17, 2005, 2:17 PM

Post #14 of 21 (3169 views)
Permalink

Re: RE: Documentation [In reply to]

On Thu, Feb 17, 2005 at 12:14:00PM -0800, Nav Jagpal wrote:
> However, I would like to start with user documentation. I'm sure there
> is someone out there that would like to join the development process,
> and what is a better way then documenting what is currently there.

You bet.

http://www.mythtv.info/moin.cgi/UserManual

Cheers,
-- jr 'we're moving it soon, but don't let that stop you' a
--
Jay R. Ashworth jra [at] baylink
Designer Baylink RFC 2100
Ashworth & Associates The Things I Think '87 e24
St Petersburg FL USA http://baylink.pitas.com +1 727 647 1274

If you can read this... thank a system adminstrator. Or two. --me

nav.jagpal at gmail

Feb 17, 2005, 2:57 PM

Post #15 of 21 (3178 views)
Permalink

Re: RE: Documentation [In reply to]

Let me apologize if attaching files to emails on this list is inappropriate.

The last few months, part of my job has been to document the building,
configuring, maintenance of Windows 2003 servers - the documentation
that I had to write was almost step-by-step. It was intended for
people somewhat familiar with the Windows environment.

My intended audience for the MythTV user manual is the same audience -
people familiar with Windows. I assume these people can use web
browsers and CD writers etc. But I do not assume that they are
familiar with bash commands etc.

The document that I have attached is obviously only a sample of the
writing style for the document. I used XMLMind to create the DocBook
XML file. This way the look & feel can be changed for various purposes
(web, print outs, etc).

There is a ton of documentation on mythtv.info that I want to re-use
in this document. I believe that the documentation already available
on mythtv.org and mythtv.info is fairly comprehensive - but the
problem is that it tries to cover all situations/setups. I think we
are missing out on the audience that thinks "I just want a PVR. Tell
me how to make it! I'll find the parts you tell me to get, and install
the OS that you want me to install... "

Please send me comments/feedback. If someone can give me a reason why
such a document should not exist, please do not hesitate to let me
know. I'm not trying to make busy-work for myself - I just want to
give back to the community for such a great product.

If I have no objections, I will start to document the Debian
installation instructions in fairly great detail. I will have a box
beside me, and document the step-by-step installation.

Thanks in advance
--
Nav

On Thu, 17 Feb 2005 17:17:58 -0500, Jay R. Ashworth <jra [at] baylink> wrote:
> On Thu, Feb 17, 2005 at 12:14:00PM -0800, Nav Jagpal wrote:
> > However, I would like to start with user documentation. I'm sure there
> > is someone out there that would like to join the development process,
> > and what is a better way then documenting what is currently there.
>
> You bet.
>
> http://www.mythtv.info/moin.cgi/UserManual
>
> Cheers,
> -- jr 'we're moving it soon, but don't let that stop you' a
> --
> Jay R. Ashworth jra [at] baylink
> Designer Baylink RFC 2100
> Ashworth & Associates The Things I Think '87 e24
> St Petersburg FL USA http://baylink.pitas.com +1 727 647 1274
>
> If you can read this... thank a system adminstrator. Or two. --me
>

Attachments:

MythTV User Manual.xml (4.26 KB)

nav.jagpal at gmail

Feb 22, 2005, 3:22 PM

Post #16 of 21 (3138 views)
Permalink

Re: RE: Documentation [In reply to]

I've been researching various operating systems.

I think for beginners, a Live-CD installation like Ubuntu or Knoppix
might be easiest. Since they are both Debian based, we can use the
Debian packages to install MythTV.

I'm leaning towards Knoppix because it has the 2.4 kernel which is
supported by MythTV... Not sure if 2.6 works (out of box) yet.

Comments/Suggestions before I get too far in the docs?

On Thu, 17 Feb 2005 14:57:40 -0800, Nav Jagpal <nav.jagpal [at] gmail> wrote:
> Let me apologize if attaching files to emails on this list is inappropriate.
>
> The last few months, part of my job has been to document the building,
> configuring, maintenance of Windows 2003 servers - the documentation
> that I had to write was almost step-by-step. It was intended for
> people somewhat familiar with the Windows environment.
>
> My intended audience for the MythTV user manual is the same audience -
> people familiar with Windows. I assume these people can use web
> browsers and CD writers etc. But I do not assume that they are
> familiar with bash commands etc.
>
> The document that I have attached is obviously only a sample of the
> writing style for the document. I used XMLMind to create the DocBook
> XML file. This way the look & feel can be changed for various purposes
> (web, print outs, etc).
>
> There is a ton of documentation on mythtv.info that I want to re-use
> in this document. I believe that the documentation already available
> on mythtv.org and mythtv.info is fairly comprehensive - but the
> problem is that it tries to cover all situations/setups. I think we
> are missing out on the audience that thinks "I just want a PVR. Tell
> me how to make it! I'll find the parts you tell me to get, and install
> the OS that you want me to install... "
>
> Please send me comments/feedback. If someone can give me a reason why
> such a document should not exist, please do not hesitate to let me
> know. I'm not trying to make busy-work for myself - I just want to
> give back to the community for such a great product.
>
> If I have no objections, I will start to document the Debian
> installation instructions in fairly great detail. I will have a box
> beside me, and document the step-by-step installation.
>
> Thanks in advance
> --
> Nav
>
> On Thu, 17 Feb 2005 17:17:58 -0500, Jay R. Ashworth <jra [at] baylink> wrote:
> > On Thu, Feb 17, 2005 at 12:14:00PM -0800, Nav Jagpal wrote:
> > > However, I would like to start with user documentation. I'm sure there
> > > is someone out there that would like to join the development process,
> > > and what is a better way then documenting what is currently there.
> >
> > You bet.
> >
> > http://www.mythtv.info/moin.cgi/UserManual
> >
> > Cheers,
> > -- jr 'we're moving it soon, but don't let that stop you' a
> > --
> > Jay R. Ashworth jra [at] baylink
> > Designer Baylink RFC 2100
> > Ashworth & Associates The Things I Think '87 e24
> > St Petersburg FL USA http://baylink.pitas.com +1 727 647 1274
> >
> > If you can read this... thank a system adminstrator. Or two. --me
> >
>
>
>

wendy at seltzer

Feb 22, 2005, 3:41 PM

Post #17 of 21 (3148 views)
Permalink

Re: RE: Documentation [In reply to]

At 3:22 PM -0800 2/22/05, Nav Jagpal wrote:
>I've been researching various operating systems.
>
>I think for beginners, a Live-CD installation like Ubuntu or Knoppix
>might be easiest. Since they are both Debian based, we can use the
>Debian packages to install MythTV.
>
>I'm leaning towards Knoppix because it has the 2.4 kernel which is
>supported by MythTV... Not sure if 2.6 works (out of box) yet.

If you want to build on the work EFF has done, we just released a
"Cookbook" describing step-by-step setup of MythTV for U.S. HDTV,
with KnoppMyth and the pcHDTV HD-3000 card.
<http://www.eff.org/broadcastflag/cookbook/>

We're encouraging people to build HDTV PVRs before the broadcast flag
outlaws manufacture of the tuners, and found that KnoppMyth offered
an easy and full-featured way to get there.

We'd be happy to see this document expanded to cover more of the
surrounding features of MythTV.

--Wendy
--
--
Wendy Seltzer -- wendy [at] seltzer || wendy [at] eff
Electronic Frontier Foundation
Berkman Center for Internet & Society at Harvard Law School
http://cyber.law.harvard.edu/seltzer.html

simon at koala

Feb 23, 2005, 1:12 AM

Post #18 of 21 (3137 views)
Permalink

Re: RE: Documentation [In reply to]

On Tuesday 22 February 2005 23:41, Wendy Seltzer wrote:
> At 3:22 PM -0800 2/22/05, Nav Jagpal wrote:
> >I've been researching various operating systems.
> >
> >I think for beginners, a Live-CD installation like Ubuntu or Knoppix
> >might be easiest. Since they are both Debian based, we can use the
> >Debian packages to install MythTV.
> >
> >I'm leaning towards Knoppix because it has the 2.4 kernel which is
> >supported by MythTV... Not sure if 2.6 works (out of box) yet.
>
> If you want to build on the work EFF has done, we just released a
> "Cookbook" describing step-by-step setup of MythTV for U.S. HDTV,
> with KnoppMyth and the pcHDTV HD-3000 card.
> <http://www.eff.org/broadcastflag/cookbook/>
>
> We're encouraging people to build HDTV PVRs before the broadcast flag
> outlaws manufacture of the tuners, and found that KnoppMyth offered
> an easy and full-featured way to get there.
>
> We'd be happy to see this document expanded to cover more of the
> surrounding features of MythTV.
>
> --Wendy
no practical use (in its current form) to me (Europe) but very nice indeed

please continue to update and expand it to cover more features of myth

you don't have to go into mythweb to get the channel information (well
certainly for DVB you don't). it is available in the setup program in the
channel editor.

regards
--
simon
_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

nav.jagpal at gmail

Feb 27, 2005, 3:27 PM

Post #19 of 21 (3110 views)
Permalink

Re: Documentation [In reply to]

I have spent the weekend trying to document a MythTV install from
start to finish.

If you have time, please take a look at
http://silver.cs.uvic.ca/~nav/mythtv/index.html

The document is DocBook XML, so the appearance can be (and should be!)
changed fairly easily by using different style sheets.

Ideally, I would like to put this document somewhere so that other
people can help complete it -- any ideas? For example, it would be
nice to get installation procedures for other video cards etc.

Oh, and I know I haven't put an "Acknowledgements" section in yet, but I will.

Two big sources:
http://ivtv.writeme.ch/tiki-index.php?page=Debian-MultiCard-Howto
and
http://www.wilson-stowe.com/mythtv/installguide

Thanks in advance.
--
Nav Jagpal

On Mon, 7 Feb 2005 09:24:57 -0500 (EST), Daniel Thor Kristjansson
<danielk [at] mrl> wrote:
> On Sun, 6 Feb 2005, Nav Jagpal wrote:
> ]Is there a need for any type of documentation, manuals, etc?
>
> There is a need for developer documentation. Starting with a guide to
> theming and a guide to producing a debug build and a backtrace for bug
> reporting. But we also need an overview of the classes and how they
> interact and something like doxygen for the code itself.
>
> ]I do not see a TODO list on the site for new-comers, so if anyone can
> ]throw something my way that a newcomer to the project should be able
> ]to handle, I would greatly appriciate it.
>
> Wade through http://www.mythtv.org/bugs/
>
> ]I'm a newcomer to the project, not to the world of coding. However, I
> ]would prefer to work on documentation or light coding projects to
> ]start with.
>
> That's not a bad idea. People have written architecture overviews and
> there is a Wiki at mythtv.info, some of the information in them could be
> used to improve the official docs. But there is nothing out there that
> tells you how say LiveTV works:
>
> TVPlay on the frontend requests a recorder from the backend via the
> RemoteRequestNextFreeRecorder function in remoteutil.cpp. It opens a
> socket and sends a "GET_NEXT_FREE_RECORDER" to the master backend. The
> recorder number, hostname and port is used to create a RemoteEncoder
> class. This RemoteEncoder in turn represents a TVRec on a backend with
> which TVPlay communicates. First TVPlay ensures that it is valid and
> working, and then changing its internal state to
> kState_WatchingLiveTV. When TVPlay enters the kState_WatchingLiveTV
> step it tells TVRec to reset its internal state and setup a
> ringbuffer, it then sets up its own ringbuffer on the same file. Once
> this is done it calls SpawnLiveTV() in TVRec, this simply attempts to
> change the TVRec's state to kState_WatchingLiveTV. TVPlay now disables
> the screensaver and attempts to start the NuppelVideoPlayer, and if
> starting the player is successful waits for the recorder to start.
>
> What TVRec does when it enters WatchingLiveTV could be covered
> separately. As could the NuppelVideoPlayer, which actually plays all
> video files and not just NuppelVideo files.
>
> I just got this from reading the code just now, but I can see this being
> useful to someone getting started with MythTV. I glossed over some
> details but basically described what goes on.
>
> -- Daniel
>

nav.jagpal at gmail

Feb 28, 2005, 11:55 AM

Post #20 of 21 (3087 views)
Permalink

Re: Documentation [In reply to]

Oops..

URL is actually http://silver.cs.uvic.ca/~nav/mythtv/index.xhtml

(Notice the .xhtml)

Also, this is still a big work in progress. I'm just looking for
anyone that wants to help!

--
Nav
On Sun, 27 Feb 2005 15:27:10 -0800, Nav Jagpal <nav.jagpal [at] gmail> wrote:
> I have spent the weekend trying to document a MythTV install from
> start to finish.
>
> If you have time, please take a look at
> http://silver.cs.uvic.ca/~nav/mythtv/index.html
>
> The document is DocBook XML, so the appearance can be (and should be!)
> changed fairly easily by using different style sheets.
>
> Ideally, I would like to put this document somewhere so that other
> people can help complete it -- any ideas? For example, it would be
> nice to get installation procedures for other video cards etc.
>
> Oh, and I know I haven't put an "Acknowledgements" section in yet, but I will.
>
> Two big sources:
> http://ivtv.writeme.ch/tiki-index.php?page=Debian-MultiCard-Howto
> and
> http://www.wilson-stowe.com/mythtv/installguide
>
> Thanks in advance.
> --
> Nav Jagpal
>
> On Mon, 7 Feb 2005 09:24:57 -0500 (EST), Daniel Thor Kristjansson
> <danielk [at] mrl> wrote:
> > On Sun, 6 Feb 2005, Nav Jagpal wrote:
> > ]Is there a need for any type of documentation, manuals, etc?
> >
> > There is a need for developer documentation. Starting with a guide to
> > theming and a guide to producing a debug build and a backtrace for bug
> > reporting. But we also need an overview of the classes and how they
> > interact and something like doxygen for the code itself.
> >
> > ]I do not see a TODO list on the site for new-comers, so if anyone can
> > ]throw something my way that a newcomer to the project should be able
> > ]to handle, I would greatly appriciate it.
> >
> > Wade through http://www.mythtv.org/bugs/
> >
> > ]I'm a newcomer to the project, not to the world of coding. However, I
> > ]would prefer to work on documentation or light coding projects to
> > ]start with.
> >
> > That's not a bad idea. People have written architecture overviews and
> > there is a Wiki at mythtv.info, some of the information in them could be
> > used to improve the official docs. But there is nothing out there that
> > tells you how say LiveTV works:
> >
> > TVPlay on the frontend requests a recorder from the backend via the
> > RemoteRequestNextFreeRecorder function in remoteutil.cpp. It opens a
> > socket and sends a "GET_NEXT_FREE_RECORDER" to the master backend. The
> > recorder number, hostname and port is used to create a RemoteEncoder
> > class. This RemoteEncoder in turn represents a TVRec on a backend with
> > which TVPlay communicates. First TVPlay ensures that it is valid and
> > working, and then changing its internal state to
> > kState_WatchingLiveTV. When TVPlay enters the kState_WatchingLiveTV
> > step it tells TVRec to reset its internal state and setup a
> > ringbuffer, it then sets up its own ringbuffer on the same file. Once
> > this is done it calls SpawnLiveTV() in TVRec, this simply attempts to
> > change the TVRec's state to kState_WatchingLiveTV. TVPlay now disables
> > the screensaver and attempts to start the NuppelVideoPlayer, and if
> > starting the player is successful waits for the recorder to start.
> >
> > What TVRec does when it enters WatchingLiveTV could be covered
> > separately. As could the NuppelVideoPlayer, which actually plays all
> > video files and not just NuppelVideo files.
> >
> > I just got this from reading the code just now, but I can see this being
> > useful to someone getting started with MythTV. I glossed over some
> > details but basically described what goes on.
> >
> > -- Daniel
> >
>

jam at tigger

Nov 7, 2009, 4:50 AM

Post #21 of 21 (1617 views)
Permalink

Re: documentation [In reply to]

On Sat, 2009-11-07 at 12:00 +0000, mythtv-dev-request [at] mythtv wrote:
> every now and again i think that i should write a book on myth. after
> all, i spend some much time faffing about with it. another motivation
> is
> that my better half gets terribly fed up as she doesn't understand how
> to use the software.
>
> so with that said, i was thinking about aggregating the words in the
> documentation, stuff from the wiki, and anything else i can lay my
> hands
> on. i have the various mailing lists archived back into the mists of
> time. but certainly there is useful stuff in -dev going over the last
> 12
> months.
>
> my proposal would be to take all this and produce a "book" for want of
> a
> better term. it would be released under a compatible licence (not
> investigated what would be best - for some value of best).
>
> i really, really, really do not like Microsoft. with a passion, you
> might say. having said that, i use ms word for about 4-5 hours a day
> for
> my job of work. for this reason, the current tool that i'm using to
> work
> on the text is word. it can be converted to whatever format is deemed
> acceptable at some point in the future.

I find that there is a gulf between the wiki and TheCurrentRelease.
TheCurrentRelease is what the developers *know*.

IMHO an introduction (Jarrad Wilson's stuff dates from when myth was
really esoteric and hard to setup) would cover basic setup then the meat
of the work would cover a reference for non trivial users.

EGs /tmp is used for snapshots that are taken by <read the source>
My slave backend says 'Tuner asleep'. What's that mean ?
How to enable the cut list in archive? (C) but that is hard to
discover

and a plethora of detail that is not revealed.

That MS is utterly evil does not prevent them from making good software,
so appologise not for using MSWord. Interesting to observe my wife, as a
total neophite, make much better progress with crossover/MSword than
OOffice!

James

_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads