[scribus-dev] Table/Cell PP sections sketches

[Elvis Stansvik]

Hi Greg,

2011/6/20 Gregory Pittman <gpittman at iglou.com>:
> On 06/20/2011 08:04 AM, Elvis Stansvik wrote:
>>
>> 2011/6/20 Alexandre Prokoudine<alexandre.prokoudine at gmail.com>:
>>>
>>> On Mon, Jun 20, 2011 at 2:09 PM, a.l.e wrote:
>>>
>>>> adding and removing rows, cells or columns should be made as an action
>>>> relative to the current selection...
>>>> in the PP, in the context menu and / or in the main menues...
>>>
>>> Frankly speaking, I don't understand your urge to hide everything in
>>> menus and be happy with that. No, it's OK to have add/remove rows in
>>> main menu and context menu, but a toolbar floating at a small offset
>>> from the table (right on canvas) will make such common operations much
>>> easier to access.
>>
>> That's interesting and worth exploring. Bringing the actions closer to
>> what they act on is a very good idea IMO.
>>
>
> Two things:
>
> Be sure to anticipate the desire for having different line styles for top,
> left, right, bottom borders of each cell, and also around the entire table.
> Not sure all of this makes sense, but it's what people have become
> accustomed to thanks to Wordperfect, Word, etc.

Right, that's what those rectangular things in my sketches and the
corresponding placeholder empty frames in the UI mockup are for;
letting the user select which sides of the table/cell the stroke
properties should apply to. Sorry if it wasn't obvious :)

> You could also consider the functions that might be contained in a context
> menu, which I think is even more intuitive than something on the toolbar --
> the problem with toolbar functions is that you need to create some icon that
> makes some sense as to its function, and we've already got a sea of
> functions there.

Okay. But let's not limit ourselves. We could have both toolbar
(floating or not) and context menu actions.

Elvis