You could think of an "all included" row layout that contains an icon, an image, a timestamp, a message, an action button etc - and then some (most) manifestations of that "all included" row layout just don't have some of the elements
To look at the problem another way:
if you were going to build a chat app in almost any GUI toolkit, I guarantee you the way you'd build it isn't to have a scroll cotnainer filled with individual widgets.
Even if that scroll container was annotated with extra API calls to add/remove etc.
There's an internal optimization layer in "detailed-list-esque" widgets that is consistent on almost every platform.
Then Gtk.ListBox has internal optimizations for when all rows are the same widget? Is that correct?
I believe so, yes.
But even if they don't look the same, they can be the same widget. They're just variations of the same widget.
Then I would proceed with the change of Gtk to ListBox and implement the Windows detailedlist. How would I go about expanding the detailedlist language to support arbitrary (yet uniform) widgets?
Well step 1 is to make an API proposal :-)
My suggestion would be to get the "simple" version working first - i.e., the current constant "icon plus primary text plus secondary text" layout.
because the handling of 'customized' layouts will definitely come as an extension of how "simple" layouts are implemented.
I spent some time today looking into the persistent Android layout bug where the app "action bar" prevents Toga from using the full space it has. I don't have a full solution yet, but I have at least characterized the problem.
I also looked into DetailedList some more. I have been playing with the Android Material UI library, and the "Lists" in it are rather lacking. Plus, apparently I now need to better-understand an Android Fragment vs. an Android Activity.
More updates probably within a week, maybe sooner; that's my micro status update.
Sounds like progress, if not yet productive
I emailed an Android-y friend to get more help & advice on the lists thing.
One question I have is... can/should we use a list of Android "Cards" in DetailedList?
The Cards within the Material UI library are quite full-featured, including a swipe to dismiss behavior that feels very native to me.
I'm not overly familiar with Material UI to comment on what a "Card" is... got a link to any details?