[rkward-devel] Import preview? (CSV)

[Thomas Friedrichsmeier]

Hi Jan,

On Thu, 17 Dec 2015 20:41:30 +0100
d_jan <d_jan at ymail.com> wrote:
> > Is there an
> > intuitive way, the two could "share" the bottom area of the dialog?
> 
> Ah, funny, I was just thinking, that using a *button* to toggle the
> code area is somewhat not optimal. Along the lines: What if code as
> well as preview go into some accordion-like widget, similar to the
> optionset one? In the case of code, this would make sense for all
> plugins.
> 
> Like this:
> 
> Preview__________________↓__
> Code_____________________↓__

I've been spinning this around in my head the past week or so, and I'm
still not entirely convinced (nor do I have a particularly clever
alternative idea). What bugs me in this approach, is that

1) in this approach we will permanently have two additional lines below
the dialog, when previews are closed (I assume the code-preview will be
closed most of the time; the preview in the CSV-import plugin would be
kept visible most of the time, but keep in mind that once we have this
preview-functionality, we will start adding it in more and more places,
where a preview is _sometimes_ but not always useful). So that's
essentially a bit of a waste of space.

2) A second problem is more subtle: If both previews can be visible at
once, we need some way to adjust their relative sizes. The obvious
solution is a "splitter" (as is used to allow resizing the tool views
in the main window, for example). In this setup, it is not clear to me
(technically and conceptually) how the two would be combined,
meaningfully. Esp. preventing states like preview X is expanded, but
only sized header + 2 px (i.e. barely visible), etc.

Problem 2 would mostly go away, if only one preview can be visible at a
time. That would not be _too_ bad, of course, but still leave problem
1. For problem 1, my thoughts keep returning to a button-like solution,
rather similar to what we have, now (only enhanced a bit with
collapse-expand indicators, and perhaps a different button style).

Your thoughts? Am I just too stubborn, or do you have any further tricks
up your sleeves? (To increase complexity some more: We also have the
concept of "Wizards" (e.g. there is one for Analysis->Means->t-Test).
Rarely used, and perhaps not often useful, but something I would not
want to give up, easily. How would we squeeze in a preview, there?)

Regards
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://mail.kde.org/pipermail/rkward-devel/attachments/20151230/eb9c6014/attachment.sig>