From kde-core-devel  Thu Nov 16 19:47:56 2006
From: Thomas Zander <zander () kde ! org>
Date: Thu, 16 Nov 2006 19:47:56 +0000
To: kde-core-devel
Subject: Re: Okular moving
Message-Id: <200611162048.02653.zander () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=116370653015067
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart12250599.RQcujfDY96"

--nextPart12250599.RQcujfDY96
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Tuesday 14 November 2006 10:16, Stefan Kebekus wrote:
> as far as I see, there are substantial differences in Ligature and oKular
> when it comes to DVI and PDF files. I feel that these are quite important
> for a number of people.

In KDE4 the concept of user-comes-first should be the first and foremost=20
design goal.
This means that choosing who you create the software for and the usecases t=
hat=20
those users will meet is where I see the biggest value of finding out if th=
e=20
functionalities of the apps overlap.
Afterall, just looking at a feature list is shortsighted and does not descr=
ibe=20
an application very well.
Looking at the goals of an application and the core user that is targetted =
by=20
the application instead, will tell you that.

A huge portion of the features you listed in your email seem out of place f=
or=20
either app. As Tobias also pointed out.

I suggest that the app-maintainers sketch a profile (personas + goals) of=20
their app and see where the two apps overlap.

With the friendly suggestion that the maintainers should work hard to make=
=20
those overlapping areas share code to the max.

The TWG can then decide which application is most mature (not just codewise=
)=20
and is most in line with the userbase of KDE as a whole.
=2D-=20
Thomas Zander

--nextPart12250599.RQcujfDY96
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQBFXMByCojCW6H2z/QRArk8AKCBRmwPTfO2WQ4FzwXJvW5I1l0C5ACcCtFH
gT5QLCeaq5LDsybsFCt32l8=
=iQbp
-----END PGP SIGNATURE-----

--nextPart12250599.RQcujfDY96--