--===============1356187462==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="XsQoSWH+UP9D9v3l"
Content-Disposition: inline


--XsQoSWH+UP9D9v3l
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Feb 26, 2010 at 06:21:46PM -0500, Evan Kroske wrote:
> Could this be a project for the Google Summer of Code? I'm hoping to work=
 on
> an open-source project this summer through GSoC, and I'd love to make this
> idea into reality. Does anybody else want to replace the aging desktop
> metaphor?

1) Although the general overview of the 10gui window manager consists of
a tiling window manager, a compositing engine and a multi-touch
interface I do not believe it is feasible to modify KWin to behave in
that way as the entire KWin codebase assumes a "traditional" paradigm.
You will be required to either fork KWin entirely and strip is clean of
almost everything before you start or write a new window manager from
scratch; basing sections of code off KWin if you are using Qt (Since
KWin has some nice, properly abstracted libraries that relate to window
management).

2) For 10gui to be useful it depends on hardware that currently doesn't
exist in large numbers (Or in the case of the full implementation:
Doesn't exist at all). This means that it's a waste of time adding
specific support for it inside the primary components that make up the
KDE workspace. There's no problem writing a window manager using KDE
components or libraries but actually adding support throughout multiple
applications for a platform that doesn't actually exist yet isn't a very
good idea.

3) Expanding on #2: Since the hardware doesn't exist in the mainstream
market--the de facto target audience of KDE software--there's really no
point in applying for a GSoC project relating to 10gui from the KDE
organization. There may be other organizations that would like to
sponsor the development of the window manager (And you can happily use
KDE components in the implementation) but I honestly don't see the
sponsor itself being KDE.

--=20

Lucas Murray

PGP/GPG: 0x3D1C34CE; Fingerprint:
  3194 9C1D 4B4C AD7B 3538  551A 87F3 A7A8 3D1C 34CE

--XsQoSWH+UP9D9v3l
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iQEcBAEBAgAGBQJLiypuAAoJEIfzp6g9HDTONaQIALok7on/b6pxCmbrayzz84O/
D1LEUXK9G/SWSclSKGAp1Fslo8bC3H+vu8+aTuxdMnY9WKC5oIK+e1TYVPvLwZ5W
RhNOQNSYzZfoJOo25d8aAwb9uUAZz+RnXc8uGMO8+4m2nXSGLd+TpUqVWul57Tvz
u+ZNJMMncM2inDf40emNZrpD4zJmzf5ngwKtgJUrwMWUPe2/RXFF/07EUDhKCsvV
1w0pd6PNRtxOu80frRHMmdNmoft/CUbAGAOegKNxCMHa7oockEdGAM+aMeyt4ThX
yp9Pxh+gjO51YDRXplwSdy57YVjcNLUpRjL3AR32IrqqqxmSt+ieXvSZdjDLkTk=
=MyJG
-----END PGP SIGNATURE-----

--XsQoSWH+UP9D9v3l--

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

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

--===============1356187462==--