Tim:
I was some research on property expressions and am wondering if they shall be part of EWB's OP in the future?


For example, writing:
   property Detail: string read (lblDet.Caption) write (lblDet.Caption);

is an incredible time and code saver, over:

type
 TToDoList=class(Tfrm1)
 private
   function GetDetail: string;
   function GetTask: string;
   procedure SetDetail(value: string);
   procedure SetTask(value: string);
 public
   property Task: string read GetTask write SetTask;
   property Detail: string read GetDetail write SetDetail;
 end;

<, I was some research on property expressions and am wondering if they shall be part of EWB's OP in the future? >>

Which OP implementation has those ?

Tim Young
Elevate Software
www.elevatesoft.com

<< Which OP implementation has those ? >>

Tim:
Here it is: http://bit.ly/2ehZOJd

<< Here it is: http://bit.ly/2ehZOJd >>

Interesting.  I considered something like that for EWB, but the problem is that it can result in a *larger* emitted JS application, and that isn't good for EWB.  It's preferential with JS applications to keep any complexity hidden within functions because that arrangement compresses a lot better than in-lining code.

Tim Young
Elevate Software
www.elevatesoft.com