I'm aware of the existing options, but what I was suggesting is to use these options that are low-level to make printing easier in Flex. For example handling all the scaling and splitting into multiple pages based on user's settings. But more interesting would be to add a way of defining media-type specific skins (just an idea, perhaps there are other better solutions) so that a developer has just to define special skins for printing for his components and make a simple function call like 'Printer.print(myComponent)'.
Haykel On 6 February 2012 21:32, Nicholas Kwiatkowski <nicho...@spoon.as> 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. > > The options to set the DPI, page size, etc. is pretty limited, but it does > exist... > > 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/ > > -Nick > > On Mon, Feb 6, 2012 at 2:40 AM, Haykel BEN JEMIA <hayke...@gmail.com> > wrote: > > > 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 <m...@leichtgewicht.at> 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. > > > > > >
