With respect, I would tell them that Flex can do exactly what they want. It has a built in tool PrintDataGrid that supports their requirements (with any limitations there might be for your use case) and if that doesn¹t work for them for a substantially higher fee you could code a custom component to meet their specific needs. I don¹t think that support for multi-page print pagination support on all controls is the kind of feature you would expect by default and I¹m actually glad to hear that Flex even supports that in the PrintDataGrid component.
I don¹t see what the beef is. They bought a development tool that has a built in control to solve the class of problem and that has the capacity to be extended using custom controls if the standard controls don¹t meet their needs. Was there a label on the box saying ³all controls support multi-page pagination²? Did someone from Adobe call you up and say ³buy Flex because the multi-page pagination support on our Vbox is cool²? What if I purchased VS.NET and found (because I hadn¹t checked in advance) that one of the controls didn¹t do something I¹d just assumed that it should? Maybe Microsoft should reschedule their production release because I¹m in a bind? It is perfectly appropriate to ask respectfully for feature enhancements and I¹m guessing they¹ll get evaluated by the product team and may be added to the production schedule based upon whatever criteria they have for evaluating such requests. If you think a missing feature makes a product unusable, select a different alternative. Flex is amazing but I can¹t believe it solves every single problem for every single use case. But what is with the attitude? It seems to me like the only mistake that was made was that a consultant assumed a feature would exist, made a recommendation based on that assumption and is now in a bind. I¹ve been there too none of us are perfect, but that wasn¹t Adobes fault. FYI, I am completely unaffiliated with Adobe, and I don¹t know Alex at all. But to be honest, the tone of your post just pissed me off. Sorry you¹re having a bad day, but it isn¹t Alex or Adobe¹s fault. Best Wishes, Peter On 12/8/06 4:47 PM, "dmiramontesval" <[EMAIL PROTECTED]> wrote: > > > > > Well i do understand all that, but my client wants a report with an > specific format, i could use PrintDataGrid but i need to convince > them, after all the client is who pays my bills. > > Besides they already purchased Flex so what should i say to them? That > the report they want can't be done with that format because the > product they purchased only allows DataGrid controls to be printed > properly? Don't think so man. > > Do we need to submit any kind of petition in order to get this > printing support in a future release? After all they already paid for > this product. > > I think you should consider this, because it is very frustating that > Flex has such a limitation of what you can print, people won't be > printing datagridsd forever man. > > I understand it is difficult to do this, i'll try to figure out a way > to handle this multipage thing with a VBox, if i succeed i'll let you know > > If you have any general ideas on how to handle this, where i could > start, let me know > > Thanks, hope you don't get the feeling i am taking it on you > > --- In [email protected] > <mailto:flexcomponents%40yahoogroups.com> , "Alex Harui" <[EMAIL PROTECTED]> > wrote: >> > >> > I'm sorry you think it is lame. The reason there is a PrintDataGrid is >> > because we know what the content will look like well enough to know how >> > to paginate it. A VBox is much more general, and we haven't had the >> > time to figure out what the right API would be to allow you to control >> > page breaks. Once you get this working, you may be able to help provide >> > some feedback as to what kinds of pagination control you and others >> > might need, or you will end up with a reusable component that others can >> > take advantage of. >> > >> > The basic principle in the PrintDataGrid is to hide its scrollbars, >> > figure out how much it should display on the current page, fire off a >> > printed page, scroll some more data in and repeat until done. You might >> > do something similar to your VBox, it would depend on what components >> > are in the VBox and how you want them to look. >> > >> > One of the reasons I believe we haven't heard many requests for this is >> > that often, folks design their UI to have multiple screens using one of >> > our navigators like Accordion or TabNavigator which can often provide an >> > easier way for the user to view the report on-screen instead of having >> > to scroll through many pages. Then printing is a matter of printing >> > each of those screens. >> > >> > If your report has many lines of data, it would seem like you could >> > still use a PrintDataGrid. Simply make an array of each line of data, >> > put it in the PDG with one column, hide the header and print it. >> > >> > -Alex >> > >> > ________________________________ >> > >> > From: [email protected] >> <mailto:flexcomponents%40yahoogroups.com> >> > [mailto:[email protected] >> <mailto:flexcomponents%40yahoogroups.com> ] On Behalf Of dmiramontesval >> > Sent: Friday, December 08, 2006 1:15 PM >> > To: [email protected] >> <mailto:flexcomponents%40yahoogroups.com> >> > Subject: [flexcomponents] Re: Printig multipage output >> > >> > >> > >> > I am printing a VBox which is a report, it contains information >> > concerning an accounting report. >> > >> > I need to print this in multiple pages but there's no way to do it, >> > any ideas? any custom component which could handle multiple page format? >> > >> > It is pretty lame that i can only print DataGrid in multiple pages >> > >> > --- In [email protected] >> <mailto:flexcomponents%40yahoogroups.com> >> > <mailto:flexcomponents%40yahoogroups.com> , "Alex Harui" <aharui@> >> > wrote: >>> > > >>> > > Sorry, there is no other multipage print components available. What >> > are >>> > > you printing? Pages of text should be relatively easy. >>> > > >>> > > ________________________________ >>> > > >>> > > From: [email protected] >>> <mailto:flexcomponents%40yahoogroups.com> >> > <mailto:flexcomponents%40yahoogroups.com> >>> > > [mailto:[email protected] >>> <mailto:flexcomponents%40yahoogroups.com> >> > <mailto:flexcomponents%40yahoogroups.com> ] On Behalf Of dmiramontesval >>> > > Sent: Friday, December 08, 2006 12:07 PM >>> > > To: [email protected] >>> <mailto:flexcomponents%40yahoogroups.com> >> > <mailto:flexcomponents%40yahoogroups.com> >>> > > Subject: [flexcomponents] Printig multipage output >>> > > >>> > > >>> > > >>> > > I need to print a component which has a lot of information and which >>> > > doesn't fit on a single page, so i need multiple pages to print it. >>> > > Unfortunately Flex doesn't provide any support for this UNLESS you use >>> > > PrintDataGrid, which is useless to me because the application i am >>> > > trying to print doesn't have ANY PrintDataGrid control. >>> > > >>> > > So the big question is how to handle multipage when printing something >>> > > that IS NOT a PrintDataGrid. >>> > > >>> > > Any ideas? any custom components that implement this functionality? >>> > > any solution? >>> > > >>> > > Thanks >>> > > >> > > > >
