On Sun, Aug 16, 2015 at 7:59 PM, Sean P. DeNigris <sean@clipperadams.com> wrote:

Sean P. DeNigris wrote
> Also...

While we're on the API. I'm assuming that #when: blocks are the
implementation of the "activation predicates" mentioned in the paper. Is
that right?

Yes, it's a more fancy name for the #when: block.

Two feature requests have been brewing as I've used GT intensively. They
both have to do with crystalizing a workflow found in the Inspector:
- Lock Panes - say I have a list of e.g. Morphs in pane 1, which propagates
to the Morph presentation in pane 2, and the Raw presentation in pane 3. It
would be great if one could indicate that changing the selection in pane 1
should not remove all panes to the right but preserve the current layout;
bonus points if it realized that pane 2 and 3 were showing the same object
and updated them jointly
- Create Glamour Browser from Inspector Session - a more permanent version
of the above. Take the current session and reify it into a dedicated tool.

This is something that we really want but, more or less, due to Glamour we didn't

really got to implementing it. A general solution for saving the navigation in a glamour

browser is a bit tricky. Now the long term plan is to rewrite the inspector on top of Bric.

This should make saving the navigation workflow easier. Or at least we'll incorporate

this feature from the start.

Now if you want to dig into Glamour and see if we can't get at least some of these feature

to work I can help. Though we do not really want to invest too much effort now into Glamour :)

This is fun :)

Cheers,

Andrei

-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Presentation-Context-Update-tp4843171p4843341.html

Sent from the Moose mailing list archive at Nabble.com.
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev