[eluser]jedd[/eluser]
I was really hoping an OO-guru would have popped in with some advice by now
[quote author="waterloomatt" date="1268503685"]
Ok - so my Model XXYYSurveyModel would have the properties/attibutes (title, active etc) and the methods (CRUD) would manipulate those fields and return them if needed.
[/quote]
Yes, this is pretty much How We Do it. My post (that I linked above) was asking why we don't have many instances of each model - the conclusion (not necessarily from that thread) is that we don't treat models as objects in the full sense of OO.
Whether or not you
can treat them as models in the OO sense .. is not something I can usefully answer - sorry.
Quote:So how do you handle multiplicity, polymorphism etc or are those features useless in CI?
Short pithy response - I don't. And I think others tend to (as a rule) not do, either.
As I say, hopefully some OO experts will have something more useful for you here. Looking through the forums might yield up some good insights, but I haven't seen any in the past 18 months that really stuck in my head (or rather my posts-to-take-note-of file). Perhaps checking out some of the example code and tutorials (see the wiki for links) though I think most of them tend to describe the orthodox approach, rather than explore the finer points of OOP.
