(selkie link) |
(where's the code?) |
||
Line 72: | Line 72: | ||
* wikipedia runner for KRunner (done :-)) | * wikipedia runner for KRunner (done :-)) | ||
* web identity configuration (central openID config, easy configuration of webservices (think of a button for GMail which then creates an akonadi resource, pulls in email and shows that in Lion Mail on the desktop, or similar, instead of pointing the IMAP config to the GMail server), controls the settings for microblogging, blogging, facebook, google. | * web identity configuration (central openID config, easy configuration of webservices (think of a button for GMail which then creates an akonadi resource, pulls in email and shows that in Lion Mail on the desktop, or similar, instead of pointing the IMAP config to the GMail server), controls the settings for microblogging, blogging, facebook, google. | ||
− | * a flickr browser | + | * a flickr (or rather web-gallery) browser |
+ | * a standalone web video viewer [[http://flavio.tordini.org/minitube||Minitube]] looks interesting (alediaferia is working a dataengine for video) | ||
* microblogging app / applet (done) | * microblogging app / applet (done) | ||
* Plasma dataengines and applets | * Plasma dataengines and applets | ||
Line 96: | Line 97: | ||
== How do we tackle Project Silk == | == How do we tackle Project Silk == | ||
− | The idea is to fly under the radar for some time | + | The idea is to fly under the public radar for some time. |
− | Once we have the first bits in place, we announce it as the next multi-year vision for KDE and try to get everybody on board with a big PR splash. (Flying under the radar for a bit will help -- announcing vapourware wouldn't be cool, if we show that we've already some momentum, it'll work much better. Silk is very much a movement towards deep integration, not a one-off. We have the technologies in place to keep an edge over competitors, and we have the developer community in place to create small plugins to support a wide variety of (even local and niche) services. | + | Once we have the first bits in place, we announce it as the next multi-year vision for KDE and try to get everybody on board with a big PR splash. (Flying under the radar for a bit will help -- announcing vapourware wouldn't be cool, if we show that we've already some momentum, it'll work much better. Silk is very much a movement towards deep integration, not a one-off or a single application. We have the technologies in place to keep an edge over competitors, and we have the developer community in place to create small plugins to support a wide variety of (even local and niche) services. |
+ | |||
+ | == Where's the Code? == | ||
+ | Silk components are hosted in the Project Silk repository on Gitorius. Keep in mind that many applications that make the desktop "silk" are integrated into the applications or Plasma already. This git repo collects the bits that aren't (yet). | ||
+ | * [[http://gitorious.org/project-silk|Project Silk on Gitorious]] | ||
+ | The code is highly experimental, it eats kittens alive. You've been warned. | ||
== How can we get people on board? == | == How can we get people on board? == |
The basic aim of project silk is to deeply integrate online content and communication into the desktop user experience.
The goal of Project Silk is deep coupling of the web with the user experience while overcoming limitations of the browser. "Freeing the Web From the Browser", so to say. Project Silk takes the opposite direction of Google's Chrome OS, instead of making the browser the Operating System, we integrate the content and the communication deeply into the desktop and application
Slogan: "Freeing the Web from the Browser", "A New User Interface (Face) for the Web"
During Akademy, there was much discussion and also already some code to make the webkit kpart ready for prime-time. A fully working, modern and integrated browser is one of the most important pillars of Project Silk. Konqueror will be using webkit, making it fully working with all major websites. Work on this is under way, but it needs to fly under the radar until it has enough momentum. Info about webkit in Konqueror: http://techbase.kde.org/Projects/WebKit
libweb provides the plumbing for applications to easily integrate content from the web by offering a KDE-style API. Think of Solid or Phonon, but for the web. libweb is not so much one library, but a collection of reusable components and sublibraries. It will be a library containing utility classes for integrating online content and services into KDE. Here are some ideas of things it could contain:
The challenge for libweb is to keep it smooth and well-structured. It would be too easy to just dump everything web-related in there, we need to think about how the whole thing should look like for developers.
Backends for the service APIs (public transport, online shopping, ...) we offer in libweb should be written in scripting languages for so far possible, so we can easily distribute and update them through GHNS, much like the comic plasma applet does with its per-site comic scriptlets.
The idea is to fly under the public radar for some time. Once we have the first bits in place, we announce it as the next multi-year vision for KDE and try to get everybody on board with a big PR splash. (Flying under the radar for a bit will help -- announcing vapourware wouldn't be cool, if we show that we've already some momentum, it'll work much better. Silk is very much a movement towards deep integration, not a one-off or a single application. We have the technologies in place to keep an edge over competitors, and we have the developer community in place to create small plugins to support a wide variety of (even local and niche) services.
Silk components are hosted in the Project Silk repository on Gitorius. Keep in mind that many applications that make the desktop "silk" are integrated into the applications or Plasma already. This git repo collects the bits that aren't (yet).
The code is highly experimental, it eats kittens alive. You've been warned.
(Spider)webs are made of it.