| |||||||||||||
|
| |||||||||||||
KDE's Project SilkKDE's Project SilkPosted Sep 22, 2009 15:10 UTC (Tue) by rahulsundaram (subscriber, #21946)In reply to: KDE's Project Silk by hunger Parent article: KDE's Project Silk
The website that hosts it would indicate the intentions of the project. FDO is the place to host specifications and code that would not be desktop environment specific.
The suggestion isn't merely to push KDE specific code to FDO. That would not make sense. Instead work with other desktop environments on things that can be shared. If code cannot be shared, specifications can be.
(Log in to post comments)
KDE's Project Silk Posted Sep 22, 2009 20:49 UTC (Tue) by aseigo (guest, #18394) [Link]
When we do work on specifications, we do take them to freedesktop.org. After all, it's an organization KDE helped create and one which we continue to help improve. Recent additions include the Open Collaboration APIs for Free software online services (which does relate to Silk topically) and the Notification Items specification. The recent work on the Notification specification to finally bring that one together is another nice example, though not a brand new spec.
Silk, by contrast, is not about specifications, it's about very specific integration points (source code) between existing and future KDE applications and online content. So Silk is not something that would make any sense on freedestop.org, though others who are involved with freedesktop.org may wish to work on similar integration points in their software.
HTH clear things up a bit. :)
KDE's Project Silk Posted Sep 24, 2009 2:59 UTC (Thu) by pabs (subscriber, #43278) [Link]
I was mainly thinking refactoring the code to split it into toolkit/desktop agnostic C libraries and the per-desktop code linking against Qt/GTK etc. The desktop-agnostic code could then live at FDO. A really good example of this is the Telepathy project.
|
|
||||||||||||