🚀 go-pugleaf

Hi Rob, Ramon:
 
It is always good to hear info. on upcomming "advancements".  I just have a few
comments that may stir up some discussion.
 
>The big problem there is that every app you create carries this Framework
>around as luggage....
>
>...why do we need to have "includes" or "USES" clauses in an OOP environment?
>There should be a big object database behind the scenes -- we just call up
>whatever objects we want, and the extra ones are stripped out at compile time.
>All files could go away......
>
>Furthermore, we should be able to edit and incrementally compile any
>particular part of the program, and test it out right away. This is
>obviously feasible (check out MCL or some if its offspring).
 
From the above comments extracted from Ramon M. Felciano's EMail, it sounds
like Component Workshop by Component Software Corp. is what Ramon wants.  Has
anyone else looked into this alternative, that is available today or at least
sometime in Jan '93, who like to comment?
 
As I understand it, Component Workshop' Extruder suppose to solve the problem
of unwanted luggage.  It "extruds" the combination of standard objects provided
by the Component Workshop frameworks and subclasses that the "programer"
creates, and produce a double-clickable application with only the objects and
methods used.  It also included a AT&T C++ subclasss interpreter that support
incremental builds.
 
>It seems to me that there should be a default application framework that is
>always active and is part of the system software.
 
Pen based systems currently have taken this approach.
 
Just thought I start a discussion to clear the air.
 
Sincerly,
 
:-)
 
Vinko Tsui
Vinko Enterprises
1193 Lindsay Drive
Oakville, Ontario
Canada
L6M 3B8
Tel.: (416) 338-7836
Fax.: (416) 338-7836 (automatic Fax Modem attached)