--===============1177444378==
Content-Type: multipart/signed;
  boundary="nextPart1327096.pQculam2Yg";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1327096.pQculam2Yg
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Thursday 27 November 2008, Andras Mantia wrote:
> Hi,
>
>  the attached patch introduces a config option to show the job progress
> dialogs as separate dialogs. The reason is:
> 1) people are used to the old ones
> 2) the new ones, integrated into the systray notification have  some
> limitation compared to the old ones, like not being visible every time,
> so you don't know if a job stuck, finished, whatever;

not being constantly visible is a bit of a feature, really. but you can jus=
t=20
click on the computer icon to see them. (or drag them out of the extender t=
o=20
some other place).

what would be good, however, is when they stop/die that it pops up=20
automatically so you can see that.

> the information
> given is not that detailed;

all the information is in the dataengine so it's possible to show it in the=
=20
status widgets.

> they disappear after the timeout, etc.

click on the icon =3D)

> I know 2) can be improved over time, but the timeframe to 4.2 is short
> and as no new strings can be introduced, I doubt it is possible now.

it's completely possible; just need someone to do it.

> There is no GUI configuration, again because of the string freeze. The
> option is global, I don't even know if it would be possible to have both
> the separate and the integrated dialogs.

not really.

> The patch doesn't react to config file changes, if requested, I can do
> that part.

no, that's fine.

> There is a question what should be the default. As it is now, I'd think
> showing the separate dialogs should be the default because of 2) and
> because some bugs.=20

if a feature is buggy the solution isn't to hide it away where nobody can s=
ee=20
it so that nobody feels the need to fix it. the solution is to *fix the=20
feature*. we have, what, 6 weeks to do that in? note that the integration o=
f=20
jobs was started, i think, 3 days before the freeze. ;) so it's not like it=
's=20
been sitting there this way for months ...

> Anyway the patch tries to be not intrusive, so I made
> to have the current behavior the default, so people can test in beta
> stage and report bugs. :)

the patch looks ok, though Manager::Private::registerJobProtocol() could ju=
st=20
be rolled right into Manager::Private.

the same should also be done for the notifications, btw.

in 4.3 we can add to the config dialog for these options, but the default=20
should remain as they are since the point of plasma is an integrated=20
experience. it's pretty obvious not everyone will want that, so we need the=
se=20
options (i'm impressed it only took, what, 2 weeks or so for the first patc=
h to=20
show up? =3D) ...=20

feel free to commit.

=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


--nextPart1327096.pQculam2Yg
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)

iEYEABECAAYFAkkvDHUACgkQ1rcusafx20PNPACfdE4x439Qqxjyxd4e0EeRBkpB
LT8AoIjrQp306EwOSdA+9iNlc/yiwu8I
=Pmpd
-----END PGP SIGNATURE-----

--nextPart1327096.pQculam2Yg--

--===============1177444378==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

--===============1177444378==--