I don't kinda agree, I totally agree with Peter. Flex is a great tool and if it doesn't have the component you like, you have the option of extending an existing component to get that functionality. Now have at and build us our first PrintableVbox! One condition, when you do please share how you did it ;).
It doesn't hurt to ask for this as an enhancement to adobe but acting like it should be there just because a client wants it is wrong. I'm pleasantly surprised that Alex is willing to look at a sample without sending your client an invoice that will really make em jump out there pants ;). On 12/9/06, Yakov Fain <[EMAIL PROTECTED]> wrote:
I kinda agree with Peter, Flex is just a tool, and if it does not have some features, you should not assume it should have them. Yes, the OP should tell his users that it's doable, but will cost them. The problem is that currently the main theme of Flex sales force is "you can create a fully functional application in Flex in less than one minute". True, if your application just needs to populate a datagrid from an XML source and this is all the user wants. But in the real world, you should deliver a message that clearly states, "Flex is a tool that can substantially speed up your development, but when it comes to customization, it's not faster than any other software tool". Regards, Yakov Fain Farata Systems --- In [email protected] <flexcomponents%40yahoogroups.com>, Peter Bell <[EMAIL PROTECTED]> wrote: > > 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 > >
-- Dominick Accattato, CTO New View Networks www.newviewnetworks.com
