> please create more components and charge extra for them. I could give you a list of about 20 that would have a value to most business developers. I'm sure the frameworks team would be interested in seeing your list. Please post it on flexcoders or send it to our product manager Matt Chotin at [EMAIL PROTECTED] - Gordon
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of boy_trike Sent: Tuesday, February 20, 2007 2:20 PM To: [email protected] Subject: [flexcoders] Gordon Smith - Some Answers about the Datagrid --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "Gordon Smith" <[EMAIL PROTECTED]> wrote: > After all, we > can't provide every feature that developers need without bloating our > components, and we've assumed that subclassing will be a commonly used > technique. Gordon: Instead of making components FATTER, create MORE components. Just like there is a vertical and horiz. grid. I used to have a T-shirt that said "he who dies with the most toys wins" Let me paraphrase, "He who has the MOST components wins " (with faster, more focused solutions" Just like the chart components are an extra price option, please create more components and charge extra for them. I could give you a list of about 20 that would have a value to most business developers. (esp. those getting paid a fair amount for their work. > By the way, when you say "for each cell" do you mean that each cell > needs to render differently based on the data it displays? Or every row > might be different, but each column in a row is the same? Or that each > column is different, but every row in a column is the same? > I mean EACH cell, not row or column. while alt. coloring of rows is asthetically pleasing, and coloring columns can make one stand out, I want to solve a business problem (i.e. customers over credit limit have that amount in bold, Orders over 90 days have the due date in RED Bruce
