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 219D59200 for ; Mon, 6 Feb 2012 22:59:48 +0000 (UTC) Received: (qmail 26492 invoked by uid 500); 6 Feb 2012 22:59:47 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 26464 invoked by uid 500); 6 Feb 2012 22:59:47 -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 26456 invoked by uid 99); 6 Feb 2012 22:59:46 -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 22:59:46 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jackringg@gmail.com designates 209.85.161.175 as permitted sender) Received: from [209.85.161.175] (HELO mail-gx0-f175.google.com) (209.85.161.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Feb 2012 22:59:41 +0000 Received: by ggeq1 with SMTP id q1so3210505gge.6 for ; Mon, 06 Feb 2012 14:59:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:references:from:content-type:x-mailer:in-reply-to :message-id:date:to:content-transfer-encoding:mime-version; bh=kv0HZk05XhHq9QcbFzou+P3ZjGZzLflTCYtv81uF5jw=; b=deoDrAXU479QjO+pjOeXP4PnemPk9jVUIicSpi3gCa8PSBTlnFVJqv1iIblQa0Lipd D+UHMs/sK6kK7Vnv8iWUsOaTGb2yjnsYnb1Di7URasc3rVd1V1eGYlDEiqAonXrYENuy oi6lYts7laRV3jRu9J7tJc5wCLa2VnrfoIIck= Received: by 10.50.76.130 with SMTP id k2mr23726356igw.22.1328569160620; Mon, 06 Feb 2012 14:59:20 -0800 (PST) Received: from [10.64.135.78] (mobile-166-147-098-177.mycingular.net. [166.147.98.177]) by mx.google.com with ESMTPS id uy10sm21670961igc.1.2012.02.06.14.59.19 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 06 Feb 2012 14:59:20 -0800 (PST) Subject: Re: [Discussion] Printing from Flex References: <4F2D5774.1030706@leichtgewicht.at> <4F2EB68F.7070007@leichtgewicht.at> From: Jack Ring Content-Type: text/plain; charset=us-ascii X-Mailer: iPhone Mail (9A405) In-Reply-To: Message-Id: <506C3EDB-B761-473B-8355-5046C759DD38@gmail.com> Date: Mon, 6 Feb 2012 17:59:13 -0500 To: "flex-dev@incubator.apache.org" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Thanks Nick. I found myself setting up ColdFusion ReportBuilder to do what I want. ( a po= tentially worse solution) See my original quote in this subject=20 Jack Ring On Feb 6, 2012, at 3:32 PM, Nicholas Kwiatkowski wrote: > While not a GREAT component, we do have the PrintDataGrid, which actually > handles the last two items you requested. Multi-page printing is handled > by queuing multiple pages into the print queue. >=20 > The options to set the DPI, page size, etc. is pretty limited, but it does= > exist... >=20 > I have a blog post on it from 2006, but it is still accurate for the most > part : http://quetwo.com/2006/10/01/printing-in-flex-part-1/ >=20 > -Nick >=20 > On Mon, Feb 6, 2012 at 2:40 AM, Haykel BEN JEMIA wrot= e: >=20 >> Flex could also add features for making the native flash printing system >> easier to use. Some of the functionality I can think of: >>=20 >> - 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. >>=20 >>=20 >> Haykel >>=20 >>=20 >>=20 >> On 5 February 2012 18:04, Martin Heidegger wrote: >>=20 >>> Hello Omar, >>>=20 >>> as far as I can tell we were talking about flex specific printing. Havin= g >>> 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 fro= m >>> that I can think of: >>>=20 >>> *) 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 >>>=20 >>> yours >>> Martin. >>>=20 >>=20