--nextPart3560640.b0CSfBagiW
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

  Hey everybody,

(re-sent with correct sender address) [Please direct replies to this email =
to the=20
kde-silk list only to avoid too much cross-posting]

This email is interesting for you, if you are

* a developer of an application that could be enhanced by online content
* a developer of an application that is integrating online content or servi=
ces=20
* a developer working on web technologies in KDE

If you didn't say "bingo!" to at least one of those points, skip this email.

During Akademy in Gran Canaria, Richard Moore and I sat down in a bar and d=
reamed up=20
a fully web integrated desktop, what features it would offer to the user an=
d what is=20
needed to get there. Let me outline our departure position first and then t=
alk about=20
the goal we have in mind.

Many users have their data and online identity on the web. Web-based email =
clients=20
are ubiquitous, "googling" has become the new term for finding information,=
 web-logs,=20
social networks, micro-blogging are widely used for all kinds of purposes. =
A large=20
group of users uses a web browser 98% of the time (according to my own made=
=2Dup=20
statistics).=20

Yet, the web experience we deliver in KDE leaves many issues, or rather mis=
sed=20
opportunities. We have built a wonderful desktop, window effects that suppo=
rt running=20
many applications at the same time in a -- for the user -- manageable way. =
We have=20
created a lot of new possibilities for an ergonomic and beautiful desktop, =
and strong=20
applications on top of that. Many developers want to develop KDE applicatio=
ns for=20
non-desktop machine, such as smaller, mobile devices and media centers.

Basically, the two things that set the web apart are content and services.

Content is data, stored on the web (or in the cloud). Think of your emails,=
 movies on=20
youtube, travel information on wikitravel, schedules for the local transpor=
t system,=20
restaurant menus and of course technical documentation on Techbase. The con=
cept of=20
content includes both, private (to the user, to a group of people) and publ=
icly=20
accessible content (for example websites such as wikipedia).

Services make the content data available, structure it, connect it and pres=
ent it.=20
These services offer the content in different ways, for example as (dynamic=
)=20
webpages, some in a more machine-friendly form such as XML REST APIs, RSS f=
eeds.

The client used to access the data through the service nowadays is the web =
browser.=20
The current situation is that the service ships a complete application to t=
he user.=20
Web applications that get their data live from the server and present it in=
 a=20
JavaScript-controlled HTML page are the norm. One problem here is that it's=
 for the=20
service increasingly hard to anticipate what works for the client, a big de=
tailed=20
webpage might not fit on a small, hi-res screen with touch-screen input, sm=
all fonts=20
and mouse-based navigation are both no-gos for a ten-foot interface with a =
remote=20
control. There is also very little consistency in both, appearance and inte=
raction=20
for the user across different web applications.

Project Silk's goal is free the web from these limitations of the browser:

* Content from the web becomes easily accessible to applications and in ext=
ension to=20
  the user
* Web applications become first class citizens on the desktop
* Local clients are enhanced by the web, the web experience is enhanced by =
local=20
  clients' possibilities.

What is Project Silk NOT?

* It's not just a new library, Silk is a coordinated effort to work on rela=
ted topics=20
* It's not an attempt to drag developers away from their projects, Silk is =
a group of=20
  people from different areas in KDE who share the similar goals
* It's not boring.
* A separate project. Silk is a KDE-wide effort, online content can be used=
 in many=20
  parts of KDE, and in fact it is already.

Good Silk examples are the web services framework in Amarok, OpenStreetMap=
=20
integration in Marble, Photo uploads in Digikam, GetHotNewStuff for Plasma=
=20
components. Silk overlaps with many parts of KDE. Konqueror, Nepomuk, Plasm=
a, the=20
Social Desktop, Akonadi and many individual applications.

The Silkiness Scale

The question "How silky is this application?" can be split up into a number=
 of=20
aspects:

* It uses data from the web (1 point)
* It caches data for offline usage (1 point)
* It is a native client to enhance web content (1 point)
* ... for more than one device (1 point)

What's the status?

Project Silk has just started, but not from zero. There are many parts in K=
DE that=20
make applications silky already. Many of the technologies in KDE and Qt mak=
e silky=20
applications very easy to do. There is very little coordination and sharing=
 between=20
those scattered bits and pieces, however.=20
We've also produced some new, silk-driven code. In the Silk Git repo, there=
 is a=20
webpage thumbnailer, and a prototype of a standalone web application done b=
y Rich and=20
me. Some people have started working on Silk projects in other parts of KDE=
, such as=20
Alessandro, who is working on an online video dataengine for Plasma. People=
 such as=20
=46lavio have shown interest to put develop his QtJson library in the Silk =
repo.
The first code has in fact been written the morning after we started thinki=
ng about=20
Silk, it's the wikipedia KRunner.

Where to go from here?

* A write-up of ideas from that bar in Las Palmas:
  http://techbase.kde.org/Projects/Silk
* Some of the code we've been working on:
  http://gitorious.org/project-silk
* Selkie experimental standalone web app:
  http://techbase.kde.org/Projects/Silk/Selkie
* Subscription page for the kde-silk@kde.org mailinglist:
  https://mail.kde.org/mailman/listinfo/kde-silk
* IRC channel: #kde-silk on Freenode

Thanks for listening so far. :)

=2D-=20
sebas

 http://www.kde.org | http://vizZzion.org |  GPG Key ID: 9119 0EF9=20

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

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

iQEcBAABAgAGBQJKs7inAAoJEGdNh9WRGQ754UQH/0wQjmU7U5R+chCf+ybV203m
l2r0jGpKmgzkf8mZf+sAYNyZjE2MKTwScH9WKt2dv9XZBmAor9fectcOZCZ7AgBY
TO8YlDNEwAAOs7mjBDEth+e1T1awRIbDw+TyHGx48T9qgqiT++e+02GgXvpg5Fgw
b1Fd0kWTg67b/6gTdWzydr3VbU2IuaEzNxHYRM9wktXhJ34OJ+ikgYesFLVLgFTy
ZPhDM3hRtyWifX8rWiGenk9ACcBDHjjm5rAjlZEa5f9Vqm7baYwUgcHPLy4nJCpr
VBf9UpaDqMDlx2MrWtUAKzWWfWmC8jNeB+Hj89ktIoe9GGerfS+MSNhZ6LOY7m8=
=+Lc4
-----END PGP SIGNATURE-----

--nextPart3560640.b0CSfBagiW--