All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Shirkey <pshirkey@boosthardware.com>
To: Andy Wingo <wingo@pobox.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: new alsa docs.
Date: Tue, 06 Aug 2002 18:25:22 +0900	[thread overview]
Message-ID: <3D4F9602.7030804@boosthardware.com> (raw)
In-Reply-To: 20020805232519.H683@cebreiro.nc.rr.com

Andy Wingo wrote:
> On Tue, 06 Aug 2002, Patrick Shirkey wrote:
> 
> 
>>I'm have soreted out all the final bugs I had with the new docs setup. 
>>Added the midi stuff and I feel that the site is ready for prime time.
>>
>>You can see it here:
>>
>>http://www.alsa-project.org/alsa-doc/
> 
> 
> Rad!
> 
> I hadn't been keeping up with the status of your work, Patrick, but it
> looks great. Nice job.
> 

Thanks.

> A few suggestions, quibbles, etc, meant to be constructive feedback:
> 
> * It wasn't obvious to me that the "plus" down at the bottom is a link
> to add information. Perhaps if it were a link or a button that said
> something like "Add comment to this card's page..." or something it
> would be more clear.
> 

Ok. I stole it from the php site. I am trying to think of a new design 
that is funky. Probably a spin on the ALSA logo with ADD instead of ALSA.

> * I know you've got it templated, but I suppose that all of the common
> stuff on the card pages could maybe go on one separate page.
> 

We discussed this a while ago and the general consensus was that we 
wanted the page to be complete. I have tried to make a compromise 
between having the high level stuff easily accesible and not making it 
too scary for new users. The aim of the new setup is to provide a style 
of documentation which is similar to the way M$ does it. The sad truth 
is that is what the majority are used to so we want to make the 
transition easier for them.

I am open to other ways of presenting the material on the page.

> * Are there any programs that don't work with ~/.asoundrc files? I don't
> have one, personally. I just use the "default" device, as it suits my
> needs fine. I think that templated asoundrc isn't all that useful, but
> maybe that's just me.
> 

The .asoundrc is very simple for the main reason that we don't have 
working user docs for the .asoundrc file yet. I am working on it as are 
others. Watch this space. However the one in the template does work with 
  f.i ardour so that is useful for a lot of people.

> * It would be nice if the link to the driver docs were a link instead of
> a button. A table full of buttons is rather imposing, at least to me. I
> think it takes longer to render, too.
> 

I know but I haven't yet figured out how to make use a link as a submit 
button for a form which is the basis of the current design. Everything 
is posted around. I know there are better ways to do this but I don't 
know how to do them. So it will be form based until I or someone else 
can write a better version. Emphasis on write :)

> Anyway, what you have looks good, keep up the good work. These are just
> suggestions, take them or leave them as you will.
> 

I appreciate your feedback because it shows me which parts I need to 
work on.



-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2002-08-06  9:25 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-05 15:51 new alsa docs Patrick Shirkey
2002-08-05 20:01 ` Dan Hollis
2002-08-06  9:13   ` Patrick Shirkey
2002-08-06 12:48     ` Joerg Mayer
2002-08-07  7:24       ` Use less number of BDs in i810 Shaju Abraham
2002-08-07  9:54         ` Takashi Iwai
2002-08-06  3:25 ` new alsa docs Andy Wingo
2002-08-06  9:25   ` Patrick Shirkey [this message]
2002-08-06  9:47     ` James Tappin
2002-08-06 11:12       ` Patrick Shirkey
2002-08-07 12:32         ` Takashi Iwai
2002-08-09 19:50         ` Karsten Wiese
2002-08-06 16:24       ` Andy Wingo
2002-08-07 12:27         ` Takashi Iwai
2002-08-07 17:11 ` Niklas Werner
2002-08-08 23:49   ` Scott MacKenzie
2002-08-09  7:19     ` Patrick Shirkey
     [not found] <Pine.LNX.4.44.0208061855490.23759-100000@yme.mo.himolde.no>
2002-08-08 15:56 ` Patrick Shirkey
2002-08-09  6:25   ` Antti Boman
2002-08-09  6:52     ` Patrick Shirkey
2002-08-09  7:31       ` Patrick Shirkey
2002-08-10 18:51         ` Frans Ketelaars
2002-08-09 15:27       ` Patrick Shirkey
2002-08-13 14:40         ` Clemens Ladisch
2002-08-13 15:01           ` Patrick Shirkey
2002-08-14 16:01             ` Pedro Lopez-Cabanillas
2002-08-15  8:56               ` Patrick Shirkey
2002-08-15 14:22                 ` Pedro Lopez-Cabanillas
2002-08-15 10:19               ` Patrick Shirkey
2002-08-14 16:40             ` Clemens Ladisch
2002-08-15  9:03               ` Patrick Shirkey
2002-08-15 12:25                 ` Clemens Ladisch
2002-08-15 12:42                   ` Patrick Shirkey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D4F9602.7030804@boosthardware.com \
    --to=pshirkey@boosthardware.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=wingo@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.