Undocking (plot) preview

[jan]

I like the idea from the technical point of view, but I assume it is not
easy to grasp for the user. It is most likely that users would see the
preview not as some "view" (in the MVC-meaning of view) of the data but
as "the one preview" – just because most people are used to that.

So I would recommend that you can easily dock/undock the preview, but –
if that makes still sense – to provide the duplicate in the menu.

One important thing: I would strongly advice to find another name
instead of "device" – like "visualization", "graphic", or even "display"
or "view".

Jan



Am 03.02.2016 um 21:37 schrieb Thomas Friedrichsmeier:
> Hi,
>
> not the most important question about docked previews, IMO, but to
> get back to "undocking":
>
> Essentially you can already do this (in the work/preview_with_menu
> branch), by using Device->Duplicate, i.e. first option in the menu.
> This is not strictly undocking, but it can be used to turn a preview
> into an independent plot window. And I tend to think it does so in a
> rather useful way: logically promoting it from a preview to a regular
> plot, so that it will neither be updated by changes in the dialog, nor
> closed with the dialog.
>
> As we also have print, copy to output, export in the preview's menu, do
> we need a more prominent - or different - "undock" action at all?
>
> Regards
> Thomas
>
> On Sat, 30 Jan 2016 16:44:25 +0100
> d_jan <d_jan at ymail.com> wrote:
>>> while we're still at brainstorming, I'll toss in a further thought
>>> in this category: Turn the "Preview"-checkbox itself into a
>>> tri-state control, e.g. a drop-down menu "Preview disabled",
>>> "Docked Preview", "Separate window".[…]
>> What I know as a sort of standard from dockable windows in
>> applications is having the preview on/off button on the "main"
>> window, and the attached/detached button on the dockable (sub) window.
>>
>> E.g. Developer Tools in the browser: Open them via the menu or
>> shortcut; dock/undock them via a button at the dev tool window.
>>
>> Or see this mockup: http://codepen.io/anon/pen/obyGpv (wording
>> dock/sockable etc. needs to be discussed, but I think it is clear
>> enough to get what it does)
>>
>> Does this make sense?
>>
>> Jan
>>