[Moose-dev] Re: RTNest should be explicit

Hi! I agree with your analysis. However, RTElement should not have an instance variable “children” or “elements". RTElement simply cannot be a composite, as it is not a composite in other frameworks (e.g., RafaelJS). I’ve spend a couple of hours on working on RTNest. This has become a beast. But I was able to work on it without breaking anything. In Roassal1, I spent too many nights (and days) on working on the nesting. It is much easier for now. If we have a variable “children”, may one may rightfully ask why renderOn: does not iterate over it. Why not adding methods such as #add: and #remove: on RTElement. And no… We will not have this. This is too painful to maintain. I was thinking about adding the list of children as an attribute. Looks like to be the best solution for now. Cheers, Alexandre On Oct 4, 2014, at 1:48 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: I would like to extend the Elements tab of the view with nesting information (essentially, I would like a tree). I cannot build this easily, and this shows me that we have a model problem. This is the side-effect of building custom tools: if the tool costs too much, you might have to think again about the model (it's similar with the relationship between tests and models). level. I would prefer to have in the RTElement links to the nested elements and have the nesting not done via a loose Trachel callback but by an explicit relationship. Alex? -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev