Re: Enterprise objects stored in JSON or byte

2018-12-20 Thread René Bock
Hi Mark, we use a similar (although more generic) data structure in our openforms frameworks. I think I should definitely present our tools at the next WOWWDC, if there will ever such a thing... Am 20.12.2018 um 08:40 schrieb Mark Wardle mailto:m...@wardle.org>>: Thanks Paul. No, not at a

Re: Enterprise objects stored in JSON or byte

2018-12-19 Thread Mark Wardle
Thanks Paul. No, not at all wedded. In fact, I've been stupid in that I did something similar with modelling consent forms and the responses, but for some reason simply couldn't see beyond the end of my own nose on this one! Thanks all, Now to get on and implement... [image: image.png] On Thu,

Re: Enterprise objects stored in JSON or byte

2018-12-19 Thread Mark Wardle
That is a much better idea than my original thoughts, and feels as if I won't be fighting the system - which is always a good indicator that one's design is wrong when building WO applications. Thank you. On Wed, 19 Dec 2018 at 18:37, Samuel Pelletier wrote: > Hi Mark, > > I've done dynamic for

Re: Enterprise objects stored in JSON or byte

2018-12-19 Thread Paul Hoadley
Hi Mark, On 20 Dec 2018, at 07:37, Samuel Pelletier wrote: > 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

Re: Enterprise objects stored in JSON or byte

2018-12-19 Thread Samuel Pelletier
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

Re: Enterprise objects stored in JSON or byte

2018-12-19 Thread Morris, Mark
Hi Mark, This sounds similar to something we do. We create entities on demand that are used for reporting purposes, where data is grouped and rolled up from our “real” persistent entities. I think there are some differences in what you’re looking at, though. Perhaps instead of using NSDictiona

Re: Enterprise objects stored in JSON or byte

2018-12-19 Thread ocs@ocs
Mark, > On 19 Dec 2018, at 4:39 PM, Mark Wardle wrote: > > 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 mecha

Re: Enterprise objects stored in JSON or byte

2018-12-19 Thread Mark Wardle
[forgot to include list in my reply] Good questions! The issue is that I want to build runtime forms that are automatically rendered via D2W. I currently build data collection forms using horizontal inheritance, so I define the model and then D2W and everything else normally "just works". I some

Re: Enterprise objects stored in JSON or byte

2018-12-19 Thread Jesse Tayler
Hi Mark Sounds interesting, I was wondering a while back if an eomodel could work on top of a database like Mongo and store anything without need for migration or table setup - but it sounds like you want the reverse? You sort of want to have arbitrary attributes? Even arbitrary relationships?

Enterprise objects stored in JSON or byte

2018-12-19 Thread Mark Wardle
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