OpenEuphoria

Re: nix config next steps

• Posted by Matt Lewis <matthewwalkerlewis at gmai?.?om> Dec 22, 2007
• 500 views

Jerry Story wrote:
> 
> Matt Lewis wrote:
> > 
> > Is there anyone interested in starting the man page?  I'd say that we 
> > probably want to make a single page to cover exu/ecu/backendu/bind/shroud.*
> 
> Would there be any problem with using the Euphoria documentation as is?
> For example:
> man exu would get the Euphoria Reference Manual.
> man ecu would get the Euphoria to C Translator Manual.

man files have to be in nroff format.  I'm figuring that we'd explain what
each executable does, give the summary of command line options, and tell
the user where the other documentation is.

There are ways to install the html files into an integrated help system,
which we could do.  Try 'dhelp' on a debian system (assuming you have
dhelp installed).  We might want to create an index page to help navigate
to all the different documents that we have (reference manual, library,
etc.).

> 
> > *  Are names like backendu, bind and shroud too generic?  Assuming that the
> > ultimate goal is to get accepted into Linux distributions, do these conflict
> > with anything already out there?  Should we change them?  If so, to what?
> 
> If you don't change the names now, then after some years there will be more
> resistance to changing the names. Easier now.

I agree.  I'm thinking that we can maybe extend the naming theme we already 
have with exu, ecu, exw, etc.

Matt