Re: SEUL: Documentation: info & postscript

[Dave Wreski <dave@nic.com>]

Hi all.  I've been watching the list for about a week or so, and had a few
comments that I thought you might be interested in.

1.  It seems like we are worring about the small little details too early.
Although things like compiling the kernel automatically are important,
don't we need a foundation to start with, before we worry about how the
user will see the interface?

2.  With all the talk about GUI apps, etc, has anyone thought about simply
using a web browser?  Whats wrong with having httpd running on all boxes,
and using this as a backend for all configuration applications?  You could
even use it as a replacement for GNUs 'info', and possibly a replacement
for man pages as well..

3.  How many of us are kernel programmers?  If there aren't that many/any,
should we be so concerned with modifing the auto-detection mechanism of
the kernel, to probe for devices?

In summary, I think we need to look at what we already have to work with,
start simple, and strictly define our goals, before we do any actual
development.  Have we already defined specifically our end goals?

I know this may sound like an obvious question, but I don't think so, if
we are already talking about which GUI builder to use.  I just think which
GUI builder to use would be easy to figure out, once we decide exactly
what we need to build :)

Hope this is clear and helpful..
Dave


----------------------------------------------------------------------------
Simple End User Linux Mailing list
To be removed from this mailing list send a message to majordomo@txcc.net
with the line
unsubscribe seul-project
in the body of the letter.
----------------------------------------------------------------------------