DWD HIG Draft

[Ken Vermette]

Update;

After feedback we made some moderately heavy changes to teh DWD
requirements, namely removing/changing 'priority groups' in favour of
'layouts'.

Instead of the application firing off widgets with a "spray & pray" manner
via priority groups, we're using layouts. With layouts the application sets
a primary layout, and can switch to contextual layouts later. The primary
layout has to be accepted as-is otherwise DWDs will be disabled for that
window.

Layouts can specify the order and size policies of widgets, but only for
the area inside the canvas - an application can't try to scramble
user-defined buttons. Applications can swap layouts if there's a contextual
need, but the DWD can reject them if there's an issue, telling the app to
provide traditional controls.

We will specify how things should be laid out by applications in HIGs later
(basically, it's what the required layout was before), but this will let
applications use discretion if something would be awkward. More information
on this can be found under 'Widget Placement" in the doc.

Document link:
https://docs.google.com/document/d/1mYzHjcuDitWmk99syjC0xzQPPmyUrpL_29_s3-2Yl_g/edit?usp=sharing

This upcoming weekend is a long weekend here, so I'll have time to put this
on the wiki and make a blog post. If anyone wants me to hold off for more
feedback please let me know.

Cheers;
 - Ken

On Tue, May 17, 2016 at 10:49 AM, Ken Vermette <vermette at gmail.com> wrote:

> Howdy!
>
> We have our first serious formal proposal for the DWD HIGs and the
> functionality we are looking for; here's a link to the publicly editable
> Google doc:
>
>
> https://docs.google.com/document/d/1mYzHjcuDitWmk99syjC0xzQPPmyUrpL_29_s3-2Yl_g/edit?usp=sharing
>
> I'd like to invite anyone with a stake in this to make edits/suggestions.
> Once we have any rapid-fire editing done I'll pretty it up and put it on
> the wiki; if editing wrecks the formatting in the doc that's fine. It
> contains a general overview of functionality, the first four widgets we're
> looking to implement, and a list of widgets which I'll be writing out once
> we're satisfied with the current documentation and direction.
>
> It may also be good to fill in technical or implementation details in the
> doc so anyone reading the wiki can be on the same page. If anyone has any
> concerns about anything please bring them up so we can hammer it out.
>
>  - Ken
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20160518/75842bae/attachment.html>