Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3F0299FB5 for ; Mon, 6 Feb 2012 07:41:09 +0000 (UTC) Received: (qmail 27293 invoked by uid 500); 6 Feb 2012 07:41:09 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 26056 invoked by uid 500); 6 Feb 2012 07:41:02 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 26030 invoked by uid 99); 6 Feb 2012 07:40:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Feb 2012 07:40:59 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of haykelbj@gmail.com designates 209.85.160.47 as permitted sender) Received: from [209.85.160.47] (HELO mail-pw0-f47.google.com) (209.85.160.47) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Feb 2012 07:40:54 +0000 Received: by pbbb4 with SMTP id b4so4146089pbb.6 for ; Sun, 05 Feb 2012 23:40:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=IogXwRA/7Mj4Gb3Tg1C5vX0Qd7phqa7/6rPBSTxqcak=; b=QSZGa8zw/LTtK3awY5eXxYbIy2P3ImUusyJAGC/3MARBrQ2a8q3nIon9eWW93hLnQv EAwWcoJPu6BJsnE4szcSuDbPkk5emF+KI1wsmttcMmj3QDZQhNEMbGvV7g2GkVKKGgFV +WL3z7gIGz+HGSRUr8ogx4AP6MgbGca90afnw= MIME-Version: 1.0 Received: by 10.68.73.234 with SMTP id o10mr45986344pbv.90.1328514033952; Sun, 05 Feb 2012 23:40:33 -0800 (PST) Received: by 10.68.218.136 with HTTP; Sun, 5 Feb 2012 23:40:33 -0800 (PST) In-Reply-To: <4F2EB68F.7070007@leichtgewicht.at> References: <4F2D5774.1030706@leichtgewicht.at> <4F2EB68F.7070007@leichtgewicht.at> Date: Mon, 6 Feb 2012 08:40:33 +0100 Message-ID: Subject: Re: [Discussion] Printing from Flex From: Haykel BEN JEMIA To: flex-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=f46d04138eb912a8ec04b846c7dc --f46d04138eb912a8ec04b846c7dc Content-Type: text/plain; charset=UTF-8 Flex could also add features for making the native flash printing system easier to use. Some of the functionality I can think of: - Handle scaling based on DPI and page setup options (page size, orientation etc.). - Handle multi-page printing. - Make Flex components printable, e.g. with skins for printing like CSS for different media. For example a DataGrid could have a skin for printing where it does not include scrollbars. Some components could also require more than just a special skin for printing. Haykel On 5 February 2012 18:04, Martin Heidegger wrote: > Hello Omar, > > as far as I can tell we were talking about flex specific printing. Having > problems with the flash player is a reality that needs to be dealt with. > For one: If we encounter bugs during implementation we should document & > report them properly. But also: We need to choose a implementation strategy > based on the things that work. There is a bunch of options to choose from > that I can think of: > > *) A system that prints using a standardized online service > *) A system that uses native extensions > *) A system that generates pdf on the client > *) A system that works within the limitations of flash player printing > > yours > Martin. > --f46d04138eb912a8ec04b846c7dc--