Re: Enterprise objects stored in JSON or byte
Re: Enterprise objects stored in JSON or byte
- Subject: Re: Enterprise objects stored in JSON or byte
- From: Samuel Pelletier <email@hidden>
- Date: Wed, 19 Dec 2018 13:37:37 -0500
Hi Mark,
I've done dynamic forms in the past (in PHP and WO) and never tried to map them
to an ORM entity. I think it is better to model your a Form entity and another
one for answers (FilledForm or CompletedForm). The Form entity is the Meta
model with the questions and the other contains only answers. You end with 2
symmetric hierarchies with one answer class for each question type class
(numeric, text, choice, boolean, image, ...). Each of the Answer class has it's
edit component.
The display form component is build by displaying the proper edit component for
each answer in order. For easy D2W integration, I think you can initialize a
new form with blank answers and simply use the D2W magic to display the
complete form (using an ordered toMany from the CompletedForm entity to it's
answers) .
Regards,
Samuel
> Le 19 déc. 2018 à 10:39, Mark Wardle <email@hidden> a écrit :
>
> I want to define a group enterprise objects at runtime and yet use them in a
> fairly similar way to "normal" enterprise objects.
>
> Essentially, I want a generic object that is backed by a NSDictionary (or
> other persistence mechanism like bytes/protobuf) and has a defined behaviour
> class. I would like to define the model at runtime rather than using
> EOModeler. The definition of the object (list of properties and for each
> property: name, dataType, class, prototype etc.) defined itself at runtime in
> the backing database.
>
> Anyone done something similar, and if so, what is the best approach? I have
> contemplated building a generic EO that delegates its behaviour and data to
> the behaviour class and the backing NSDictionary respectively, and alters the
> implementation of KVC to make it fairly transparent. I'm aware that some of
> the hidden "magic" that comes from defining an object in EOModeler might be
> lost.
>
> Any hints/tips gratefully received!
>
> Best wishes,
>
> Mark
>
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden