--- In [email protected], "Gordon Smith" <[EMAIL PROTECTED]> wrote:
>
> Bruce, is the problem that you haven't been able to figure out how to do
> this, that you don't think you should have to figure it out, that you're
> not clear on how to subclass, or something else? 

Gordon, let me answer some of the questions you raised (and some that you did 
not raise).

1st.  Everyone who is using flex and does NOT write their entire application in 
1 mxml file 
has learned to subclass.  We are all doing this every time we create a new 
component for 
our applications.  Let me answer your question on why I (and from your 
comments, many 
others) are reluctant to extend a class each time we want new features.  While 
I am older 
than dirt and have been building custom business solutions for about a zillion 
years, keep 
in mind:

•       These are MY opinions
•        I might be wrong!


•       Too many source files.   I use a 24" monitor (and really need the 30" 
one!) so I can 
see many tabs in eclipse @ once, however, having to open up a new file for EACH 
grid that 
I want to customize is less than appealing

•       Too much abstraction and indirection.  One of the reasons that I do not 
use 
Carniform is that  it adds to the complexity of tracing an application flow.   
Each of my 
applications has:
o       My Main Application MXML file (pretty small)
o       What most people call a model locator file (I renamed my GLOBALS) which 
has all of 
the variables (and functions) that are shared between components .
o       A component for each "screen" .  Each component (usually based on a 
panel / canvas 
or other container has the application logic and the UI. 
o       A VO for each of  the "records" that I need to work with
o       A CFC for my Coldfusion Code.

I am a single developer building complex business solutions and I can find my 
way though 
the code months later.  My code reads "procedurally" which works for me.

•       Justify Time ($$) for business solutions.  It is easy for me to tell 
the customer that to 
build a screen to display his orders will take "X" hours.  Telling him that it 
will take "X" 
hours to be able to have code to enhance the UI does not always fly as well.

•       and perhaps most importantly, I want a RAD solution where I can focus 
my time on 
providing a business solution rather than enhancing the tool!   I make my 
living in 
providing "just in time" business solutions.  Just like a Label field where I 
can type:


fontWeight = "{(model.currentBalance == 0) ? `bold' : `normal'; }"
        
I want to be able to do similar with a datagrid.  This is RAD, this is AGILE 
development.  
(There is a strong correlation between the # of lines of code and the # of 
bugs!)


Bruce

 


Reply via email to