Steve Alexander wrote:
> In the ScinScript, you need to determine what data to use based on
> Here's the SkinScript I use for a similar function; I'm
> creating "virtual" instances of one ZClass, based on instances of a
> different ZClass from another Specialist. In this case, the other
> specialist is "Responses".
> WITH Responses.get_data_for_code( COMPUTE
>    subject_name,
>    rater_name,
>    relationship_name,
>    response_code,
>    process_step


Is it possible to have a Specialist that is entirely
'virtual'? Can a Specialist be set up to use a generic
DataSkin that stores attributes persistently, without having
to define a ZClass at all?

If so, can you describe a procedure for accomplishing this?


Michael Bernstein

Zope-Dev maillist  -  [EMAIL PROTECTED]
**  No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to