From kde-core-devel  Fri Mar 13 18:17:00 2009
From: "Aaron J. Seigo" <aseigo () kde ! org>
Date: Fri, 13 Mar 2009 18:17:00 +0000
To: kde-core-devel
Subject: Re: Fullscreen interfaces
Message-Id: <200903131217.00664.aseigo () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=123696826919051
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart5033189.ViurTb9lVA"

--nextPart5033189.ViurTb9lVA
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Tuesday 10 March 2009, Stefan Majewsky wrote:
> I would like to have a collection of widgets for fullscreen interfaces in

first, on behalf of everyone who hijacked this thread on you to talk about=
=20
other things, i'd like to apologize. it was rude, disrespectful and probabl=
y a=20
bit discouraging.

so... full screen interfaces. let's try this again, shall we? =3D)

one approach would be to create a class, e.g. KFullScreenPresentation or=20
something, that takes a main widget (setCentralWidget(QWidget *)?) and then=
=20
provides access to standardized "chrome" as well do things like set a stand=
ard=20
background colour (black, probably) for wherever the main widget (document)=
 is=20
not painting.

looking around at the various apps, i see that we will likely need:

* an optional progress indicator
	* okular has one for it's slides
	* the video players tend to include this in their control toolboxes

* collapsible toolboxes, arranged in the corners
	* plasma has one
	* looks like pallepeli is getting one as well?
	* right now these are QAction based in the apps using them, perhaps that's=
=20
good enough for these

* control boxes, slide out of screen edges
	* gwenview shows a thumbnail flow
	* video players have stop/start/etc buttons

perhaps we could also offer control boxes that slide out when a corner tool=
box=20
button is pressed?

in any case, adding actions to a toolbox would be a no-brainer. being able =
to=20
add random QWidgets would be similarly required.

so usage might look like:

KFullScreenPresentation *p =3D new KFullScreenPresentation();
p->setCentralWidget(imageView);
p->addToolBoxTool(someAction);
p->addToolBoxTool(someWidget, "some toolbox identifier");
p->show(); // would take over screen, set the proper KPresentationNotificat=
ion=20
settings, etc

i suppose it would need to be able to define multiple toolboxes, where they=
=20
would be on screen ... not sure if xmlgui integration would be of any use=20
here?

this should get one closer to a possible draft api, though. thoughts?

=2D-=20
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Software


--nextPart5033189.ViurTb9lVA
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEABECAAYFAkm6oxwACgkQ1rcusafx20M/qACfVZ4CPKOb16LWYYKc1rsebGM7
XScAn1XBbcLBBx6kW+JKYDPBXX7NuTgv
=x+DS
-----END PGP SIGNATURE-----

--nextPart5033189.ViurTb9lVA--