On 04 Mar 2015, at 06:20, Ben Coman <btc@openInWorld.com> wrote:
Could someone explain why the "ToOne" and "ToMany" are the preferred semantics for the class names versus OneRelatedTo or RelatedToOne ? To me, "ToOne" feels like its describing the #directedMovies part. I guess it makes sense if you are looking in towards #director. cheers -ben
Right now I care more about fixing all bugs to make the examples actually loadable⦠there are so many details⦠e.g. integrating the examples broke the build as the code that generates the #initialize method asked for initialsâ¦
On Fri, Feb 27, 2015 at 7:51 PM, Marcus Denker <marcus.denker@inria.fr <mailto:marcus.denker@inria.fr>> wrote:
On 27 Feb 2015, at 11:46, Jan van de Sandt <jvdsandt@gmail.com <mailto:jvdsandt@gmail.com>> wrote:
Hello,
Thanks for your suggestions. I have improved the naming and definition to this:
Object subclass: #SlotExampleMovie slots: { #name. #year. #director => ToOneRelationSlot inverse: #directedMovies inClass: #SlotExamplePerson. #actors => ToManyRelationSlot inverse: #actedInMovies inClass: #SlotExamplePerson } classVariables: { } category: 'SlotAssociations-Tests-Example'
Because it is for now just an example I haven't renamed the Slot classes yet.
Thanks! I will add the associations as examples to Pharo4 (today I think)
Marcus