Julien: do you see an easy(ish) way to update a tree view scene model to support this organisation/display?

Would it help to remove the green arrow and make the thumbnail clickable?

Does this have to be a tree view? We need to identify one of the views as the master view, but there is no functional need for a tree.
When I look at the above, it is a cell in a table containing a nested table. It would be relatively easy to make such a design in a table.

Nicole, you can use a QItemDelegate (see qMRMLNodeItemDelegate for an example), you can customize the look of each cell.
Otherwise, as Ron suggests it, you might not want to display the scene model as a tree, but listen to the model signals(rowAdded, rowRemoved, reset) and populate your own layout.

any update?

I tried the item delegate route and was unable to get it to work. I'll see if I can find some time to consult with Julien on it when he's here for the ctk hackfest.

??

No progress.

ok

I strongly disagree. This is high priority for the last year of NA-MIC.

EDIT (Jc): Updated priority to high

If it can not be done in qt, can it be done in webkit?

I (Steve) thinks this is lower priority than 0001914 where incorrect information is being presented to the user in some circumstances. During the bugfest meeting 2014-03-07 we discussed this in the context of the number of other issues and the time available for release. We want to keep this on the plate but will not prioritize it above circumstances where incorrect information is displayed that may be critical for clinical research.

Look at making a custom widget per scene view node and removing the qMRMLSceneModel (or make a different QtView.

I've done an html version of the Scene Views module using the Qt web view, based on the DataStore module, see attached picture SceneViewsFacelift-1.tiff

From an implementation standpoint, issues are:

• getting the html view to fit inside the module widget (can't currently move the horizontal size slider)
• the scene view thumbnail is being written to disk in a temp dir (exploring if can do it via memory)
• lots of hard coding of the html
• to get the Edit and Restore funtionality I'm capturing the clicks on the links and parsing specially formatted urls (Edit/Restore mrmlNodeID)
• clean up needed to remove the tree view and respond to mrml events, have the name and description also pop up the edit widget

So, it's not pretty under the hood[1], needs a bit more cleaning up, but it seems to work okay. Posting this work in progress to check that it's worth continuing to go down this path.

[1] Initial implementation commit on github:
https://github.com/naucoin/Slicer/commit/655fd3151e3926c8818799e980638b2f687e455c

Under the hood is not my domain, but the tiff looks good.

It actually doesn't look too bad under the hood to me. It doesn't really need to be too flexible, and writing to tmp is allowed. Nice!

Pretty much done:
https://github.com/naucoin/Slicer/commits/1299-facelift-for-sceneviews
The caveate being that the scroll bars don't show up on Mac, but do on linux, and the behaviour matches that of the Data Store which also uses the web view.
To do (Ron said these can be feature requests):

• live links
• move scene view nodes up and down (will require a data structure to track, the old hierarchy had this functionality)
• box around the description text (move to table?)

Squashing it and will commit to svn tomorrow so I can monitor the dashboards.

Squashed commit:
https://github.com/naucoin/Slicer/commit/c751d7519e641a68e149f24782152c2637e79401
svn:
http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=23160