Thanks for the clarification. This all seems to make sense to me.
On Sat, Oct 02, 2004 at 10:34:31PM +0300, Erik Berglund wrote:
> David Everly wrote:
> >Hi Mattias,
> >
> >Thank you for explaining printing in Emilda.
> >
> >As I understand this note, using application/emilda-print-data requires
> >that some special software be installed on the clients. Please correct
> >me if I have misunderstood this.
>
> Emilda-print-data requires the emilda-print program, which is available
> in the emilda-print module on CVS. It simply redirects the data with
> some print commands to the correct port on the computer.
>
> >In my situation, I have little control over the clients that would
> >access Emilda, so for any printing, returning a PDF document to the
> >browser seemed to be a better solution, which I see is already mostly
> >supported within Emilda.
>
> Yes, in parallel to EPD we will support PDF or HTML. Anyone who uses
> Emilda from a "normal" workstation (i.e. not an Emilda terminal) will
> need this type of data, so the majority of requests will require PDF or
> HTML output.
>
> >I hope Emilda will continue to return PDF documents and avoid forcing
> >conversion to application/emilda-print-data exclusively, as it would
> >render Emilda unusable for us.
>
> Emilda will continue to return PDF documents. EPD is only used on
> computers where the software is installed and a printer is used
> directly. The printing software enables prints directly from Emilda
> without user interaction, i.e. barcode labels are printed automatically
> when the book_add page status=success loads. It's a fast, usable and
> fancy feature =)
>
> >Fortunately for us, we don't require receipts. And as far as adding a
> >new item, its more convenient for us to have printed several sheets of
> >labels in advance (30 labels are on each 8.5" x 11" sheet).
>
> Printing labels in advance is another option. Receipts are also printed
> automatically using emilda-print and EPD when certain actions are
> performed. The code that enables this is a simple JavaScript redirect to
> an URL that is catched by the print software.
>
> >But more importantly than our individual needs, I think it would help
> >Emilda to be more widely used if _all_ functionality could be accessible
> >without the need for Emilda-specific software on the client.
>
> The majority of users will never even see Emilda-specific software, the
> beauty of a web-based system is that it doesn't need any client
> installations. Emilda-print is just an add-on; a bonus for hightech
> customers and one of the aspects around the Emilda "product" we provide
> as Realnode Ltd.
>
> >Thanks,
> >Dave.
>
> [snip]
>
> I hope this clarifies some of our intentions around terminals and printing.
>
> Sincerely,
> --
> Erik Berglund
> Partner, Marketing
> Oy Realnode Ab
>
> lastname@xxxxxxxxxxxx
> www.realnode.com
>
>
--
Encrypted Mail Preferred:
Key ID: 8527B9AF
Key Fingerprint: E1B6 40B6 B73F 695E 0D3B 644E 6427 DD74 8527 B9AF
Information: http://www.gnupg.org/
ASCII ribbon campaign:
() against HTML email
/\ against Microsoft attachments
Information: http://www.expita.com/nomime.html
|
