I was thinking something along the lines of: override def menus = super[MegaMetaProtoUser].menus ::: super[CRUDify].menus
if you need both, but I suppose it's simpler to just remove it. I'll code up the change and send out a breaking changes announcement. Derek On Tue, Nov 24, 2009 at 2:15 AM, Jeppe Nejsum Madsen <[email protected]>wrote: > Derek Chen-Becker <[email protected]> writes: > > > OK, thinking about this a little further, technically it would be a > breaking > > change to remove the menus method from MetaMegaProtoUser. > > Yes, but is that really an issue here? > > > Would it be better to simply introduce a MenuGenerator trait, a la > > > > trait MenuGenerator { > > def menus : List[Menu] > > } > > > > And add that to CRUDify and MetaMegaProtoUser? > > Maybe I'm overlooking something obvious, but how will this solve the > problem? I guess I can override the menus method in my singleton, but I > would still need to get the menus from both CRUDify and > MetaMegaProtoUser so they'll have to be named something different in > order not to clash, no? > > /Jeppe > > -- > > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<liftweb%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/liftweb?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
