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

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

True, but I think the point that was trying to be made is that these 
private variables often
get surfaced as Public properties.  We could have both Owner and 
OwnerInterface as
a property or function. 

I think the sooner we work some of these little detail out and can start 
the CVS tree,
the better.  I will continue working on website stuff for you.

Dennis Landi wrote:

>>By the way, couldn't we have both an FOwner and FOwnerInterface?
>>
>>    
>>
>
>Private fields shouldn't interfere with the RTTI streaming system at all.  I
>doubt its an issue, but the experiment needs to happen.
>
>Three or four years ago I created my own tInterfacedComponent.  I'll see if
>I can find it.
>
>Dennis Landi
>Allied Data, Inc.
>800 204 2722
>http://www.dennislandi.com
>
>
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real users.
>Discover which products truly live up to the hype. Start reading now. 
>http://productguide.itmanagersjournal.com/
>_______________________________________________
>UOPL-architect mailing list
>UOP...@li...
>https://lists.sourceforge.net/lists/listinfo/uopl-architect
>
>  
>

-- 
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