On Thu, Jul 20, 2017 at 10:01 AM, Luke Gorrie <luke@snabb.co> wrote:

On 19 July 2017 at 23:58, Andrei Chis <chisvasileandrei@gmail.com> wrote:
Or you can just reuse an inspector:

Great! This is exactly what I was looking for.

Seems like the basic misunderstanding in my example is that there is no browser in there anywhere. The GLMCompositePresentation looks superficially like a pristine Inspector but it's not one: it doesn't have the concept of a selection, it doesn't create million columns, etc. That functionality is all added in the GTInspector subclass (and related places.)

Right?

GLMCompositePresentation is a builder for constructing presentations. It can hold the created presentations and display them using an arrangement. By default it displays them using a tab widget.

Transmissions are added by browsers. For example the tabulator is a browser where the user has to define all transmissions between panes as well as how they are arranged on screen. The inspector is a browser that hardcodes the transmissions between panes and also has a predefined UI.

Each pane can have ports. Transmissions are added between the ports of panes. To populate those ports, panes display presentations. For example, when you select an element in a presentation, the presentation populates the selection port of the pane that displays the presentation. This triggers the transmissions associated with that port.

Hope this makes things a bit more clear :)

If you want to enable refresh in the inspector use GTInspector class>>enableStepRefresh. Then you need to configure your extension using #wantsAutomaticRefresh:. For the moment this will just work for #fastTable and #fastList presentations. I can tell you what you need to add to Glamour if you are using other presentations.

Thanks for these tips. It's text that I want to update. I'll experiment a bit and shout if I get stuck.

_______________________________________________
Moose-dev mailing list
Moose-dev@list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev