All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Uebernickel <larsuebernickel@gmx.de>
To: printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] Coding the Common Printing Dialog	an dits interface - PPD and Foomatic extensions
Date: Fri, 06 Jun 2008 16:45:58 +0200	[thread overview]
Message-ID: <48494DA6.5040502@gmx.de> (raw)
In-Reply-To: <48236D19.9090209@gmx.de>

Lars Uebernickel wrote:
> Glen,
> 
> Great idea - this way, we will have a better overview than browsing 
> through endless threads here on the list.
> 
> I have started a requirements page on the OpenPrinting wiki with the 
> examples you've given:
> 
>    http://www.linux-foundation.org/en/OpenPrinting/Requirements
> 

I have just changed the format of the Requirements page.

Each requirement has its own section now (there was too little room in 
the table). I also suggest to put notes and remarks directly to the 
corresponding requirement (with the colon syntax known from wikipedia 
talk pages).

I have also added some requirements that I came up with while I started 
to specify the API. I will add some more later tonight (CEST).

It would be nice if lots of people could look at them from time to time 
(esp. the 'Pending' ones) and tell me what they think. Also, feel free 
to add more requirements.

I want to finish the API as soon as possible to start implementing it in 
some applications. After that, it will be very hard to change 
fundamental stuff.

Thanks,

     Lars


      reply	other threads:[~2008-06-06 14:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 15:45 [Printing-architecture] Coding the Common Printing Dialog an dits interface - PPD and Foomatic extensions Petrie, Glen
2008-05-08 21:14 ` Lars Uebernickel
2008-06-06 14:45   ` Lars Uebernickel [this message]

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=48494DA6.5040502@gmx.de \
    --to=larsuebernickel@gmx.de \
    --cc=printing-architecture@lists.linux-foundation.org \
    /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.