Re: [dws-developer] StaticTables

[Mark <mnm...@co...>]

Andreas Luleich wrote:
[...]
>>I was hoping for some feedback before I did the checkin for the changes 
>>to Tdws2Unit. I just moved the static table related methods back to the 
>>new ancestor class.
>>
>>=================================
>>NEW in Tdws2Unit
>>=================================
>>I've also added a new method called ExposeClassToUnit which uses RTTI to 
>>add a class to a Tdws2Unit at runtime. It will create the class and add 
>>the properties where all the OnEval events tie to the same method that 
>>can sort it all out. This means that TypInfo.pas gets added to the 
>>dws2Comp uses. Is there any problem with this?
>>
> 
> If no one else has a problem with it, I do not have. If we see any other 
 > solutions, we should discuss it as long as we are in beta state.
> 
> ALu

After getting the initial work done and a demo created, I realized that 
it should probably be changed. I plan to remove the "ExposeClassToUnit" 
from Tdws2Unit and create a new unit like dws2UnitDynamicSymbols.pas or 
something. I would like some feedback on the name before I commit it. 
(That means soon! Since I'm leaving for a week on vacation starting this 
Saturday). I can implement the new unit in a few ways. I can have it 
just be some procedures that get a Tdws2Unit passed in or it can be a 
new Tdws2Unit descendent component. Any thoughts? I can also create a 
new component in dws2Comp.pas that decends from Tdws2Unit but introduces 
the new dynamic (runtime) symbol declarations. Thoughts?

I was thinking of creating a new unit because I realized that I can wrap 
more complex property types ONLY if I know that those types are 
available (which may be declared in other units). I can't use the 
"GetClasses" unit call because things like the abstractStaticSymbol unit 
don't support that and may be creating the symbol at runtime only.

Here's the problem ....
If I have a unit that exposes TStrings and TStringList and in my new 
dynamic symbol unit I want to wrap a TMemo at runtime I can't wrap the 
"property Lines: TStrings" because in the dynamic symbol unit I don't 
know if TStrings is declared anywhere. So I don't know if it should be 
redeclared or used or anything.

Solution ...
I can make this work if I have a compiled program (with no script... 
just compiled unit symbols). Then I can see what symbols are already 
available. I can use existing ones if available.

Because the easiest/best solution was to compile an empty script, I 
thought it would probably be best as something separate from Tdws2Unit. 
I think people might be confused if TDelphiWebScriptII events starting 
firing when they called a method on Tdws2Unit before compiling.

Anyway, this is the plan. Let me know if there are any objections or any 
  other ideas. If no feedback is received then I will assume I free 
reign to do whatever sounds fun at the moment. :)

So what /is/ the plan for the release anyway?

-Mark E.

> 
> ______________________________________________________________________________
> UNICEF bittet um Spenden fur die Kinder im Irak! Hier online an
> UNICEF spenden: https://spenden.web.de/unicef/special/?mc=021101
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
> thread debugger on the planet. Designed with thread debugging features
> you've never dreamed of, try TotalView 6 free at www.etnus.com.
> _______________________________________________
> dws-developer mailing list
> dws...@li...
> https://lists.sourceforge.net/lists/listinfo/dws-developer
>