Actually, it already does have the behaviour that I wanted. I have a base type and two extending types, when I display a collection of the base type but which contains instances of the two extending types, Isis is 'casting' the entries to those two different extending types for display.
That is, when I hover over the icons on the left it gives me different titles according to which type and when I navigate to those members its showing them as the specific subtypes with their additional properties. I'll try individual icons for the subtypes and see if it uses them instead of the one for the base-type. Cool On Thu, Nov 19, 2015 at 6:30 PM, Stephen Cameron <[email protected] > wrote: > Its not that important, using the poly module might provide a better > solution when I have time, I will go will go with a viewmodel first off. > > > > On Thu, Nov 19, 2015 at 6:13 PM, Dan Haywood <[email protected] > > wrote: > >> Correct. >> >> I could see it might be doable if we extended the metamodel to specify the >> list of types to be rendered. Raise a ticket if you want it added to the >> backlog. >> >> Thx >> Dan >> >> On 18 November 2015 at 19:39, Stephen Cameron <[email protected] >> > >> wrote: >> >> > Hi, >> > >> > I presume that it is not possible to display an unparented colllection >> of >> > types that all extend a common base type and for the collection to >> display >> > the extending type's icons and properties? Kind of like a UNION view in >> > SQL. >> > >> > Just confirming. >> > >> > Thanks >> > >> > >
