Documents and demos can reduce complexity.
 
Gird is very important  for apps such as MIS Application.
 
I think that TcxGrid , which is a production of DevExpress Comp. , is a good exmaple.
 
 
Jesus  Reyes  wrote:
>  It's  a  nice  argument,  however  if  this  grid  continue  to  get  improved  and  more  features  are  added  to  it,  the  descriptive  name  become  misleading.  TMaskEdit  it's  a  good  example  of  a  component  with  a  specific  purpose  not  meant  to  be  improved  but  used  as  it  is.  
>  
>  But  this  is  also  the  topic  of  this  thread,  to  allow  a  component  to  grow  in  features  (in  this  case  a  better,  more  general  name  could  used)  or  let  it  as  it  is  (and  in  this  case  your  argument  fits  very  well).
 
Try  to  prevent  designing  components  that  are  "bloated".  Use  as  much  as  
possible  events  and  component  connections  (aka  plugins),  to  expand  
features,  otherwise  you  get  a  component  no  one  can  use  because  it's  
simply  too  complex.
 
What  kind  of  features  are  you  thinking  to  add,  and  how  ?
 
Just  my  2c,
 
Micha
 
_________________________________________________________________
         To  unsubscribe:  mail  [EMAIL PROTECTED]  with
                               "unsubscribe"  as  the  Subject
 

= = = = = = = = = = = = = = = = = = = = = =

 
              Lee Jingbo
               2006-02-23
 

Reply via email to