Last years at Gluon
Our mission1) Develop further our OCS server in order to have it usable by every project that needs it. In this phase we'll need to refactor and prepare it to be installable and configurable easily. We'll include install/config scripts with a nice interface. It also will be full Attica/NewStuff compliant.
2) Implement Desktop and web client that will let users download and use content like apps, backgrounds, themes etc. The Desktop client will be written in Qt/QML and the web client will be web based.
We want in the end users to be able to get user created content for Plasma in an easy way from one single common place as well as for creators to upload it. Our secondary target is to unify Gluon and Plasma content server and implement user / login capabilities via KDE Identity in order to have a centralized infrastructure. Our dream is to have a common desktop environment experience also regarding the content distribution system across all distributions
This is a scheme of the future structure:
Technology stackWe have in plan to develop OCS server and client libraries at the same time, creating a full set of classes that are shared between the both libs. This will enhance manteinability and modularity having a php library for both uses that shares most of the model codebase.
Now, having a working server we imagined the Plasma web client to be built on top of the OCS client library (of course), using php/mysql (or generic sql database) and for the client part HTML, CSS, a bit of jQuery and maybe the opensource library famo.us (we still need to do some feasibility studies on this latest).
- Openess of OCS protocol, simple interface in human-readable REST / XML / JSON
- Ownership of KDE project of their content distribution system (we'll have a full working in-house implementation)
- Merge of Gluon games, backgrounds, themes etc... all in a single place, with a single unique login on KDE Identity. This also enhances in users the concept of KDE as a full desktop environment with the same content across various distribution opposed to other semi-proprietary implementations (like Canonical's one)
- Modularity of the server and clients. OCS is a wide protocol and potentials are there. For example I implemented a real-time chat between users in Gluon Player. This could give us some ideas to brainstorm.
- ocs-server at https://projects.kde.org/projects/playground/www/ocs-server, and Gluon Player (includes gluon player libraries that wraps libattica)
written by me, Claudio :)
- "Plasma AppStore" (name is just a placeholder), consisting in Desktop client and Web client, by Francesco Wofford, my guest in this blog post
Have a nice day! And have a cookie! :)