Re: [UOPL-Architect] how design uopl gui applications

[Thomas M. <tm...@bs...>]

Dennis and Richard,

Can you guys take the lead on experimenting with all of this stuff. 

Issues List:

#1)  To make the entire system UNICODE friendly, we will need to probably
start from TObject because we need to update the Exception class, which 
inherits
from TObject.

#2)  Some of the changes we are talking about, like 
TInterfacedPersistent, will that
prevent the IDE's from using our new library.

By the way, couldn't we have both an FOwner and FOwnerInterface?

Richard B Winston wrote:

>That would be an interesting experiment.  TInterfacedPersistent has a
>private field
>
>FOwnerInterface: IInterface;
>
>Its possible that the private field will mess up the typecasting mechanism.
>When you typecast, the compiler may expect FOwner, the first private field
>in TComponent to
>be in the position that is really occupied by FOwnerInterface.
>
>Richard B. Winston
>rb...@us...
>http://water.usgs.gov/nrp/gwsoftware/
>703-648-5988
>on Fridays: 301 474-2762
>
>  
>

-- 
Thomas Miller
Wash DC Delphi SIG Chairperson
Delphi Client/Server Certified Developer
BSS Accounting & Distribution Software
BSS Enterprise Accounting FrameWork

http://www.bss-software.com
http://www.cpcug.org/user/delphi/index.html
https://sourceforge.net/projects/uopl/
http://sourceforge.net/projects/dbexpressplus