[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: KDE 2.0 Architecture --- please read
From:       Mosfet <mosfet () jorsm ! com>
Date:       1999-11-08 3:10:33
[Download RAW message or body]

Looks cool to me. Should go well with the tutorials I am working on :)

Matthias Ettrich wrote:
> 
> Hi fellow developers,
> 
> may I please draw your attention to the file kde2arch.html
> (In the CVS under develop.kde.org/kde2arch/kde2arch.html)
> 
> Until it shows up on http://developer.kde.org, you can read the current version
> on  http://ettrich.priv.no/kde2arch.html
> 
> ----------------------------------------------
> About this document
> 
> This temporary document is a work in progress. With KDE-2.0 coming nearer, it's \
> time to write some good overview documentation. KDE became a fairly powerful and \
> complex development framework, so powerful that it's getting harder even for core \
> developers to take full advantage of all its possibilites. Therefore I compiled \
> this framework of an architectural overview. It's obviously incomplete and has very \
> likely flaws in the logical structure. But it is a first start.
> 
> The goal is to provide good, structured information. The data produced here will be \
> merged/provided with the informations currently on developer.kde.org, for example \
> here. developer.kde.org does a great job structuring the currently available \
> information, just that the available information is far from being sufficient.
> 
> The goal with the Architecture overview is not to write a pure white paper, but web \
> information. That means that links to the KDE library API documentation on \
> http://developer.kde.org/documentation/library/2.0-api/classref/index.html as well \
> as to the online Qt documentation http://www.troll.no/qt/ are of course possible. \
> The idea is to have a few introductory words for each topic (depending on each \
> topic between a half or one page ) with links where to find more information. Have \
> a look at this page to see how it might be done. 
> I did a very nasty thing: I took myself the freedom to assign each topic to a \
> responsible person. If I made a mistake, may it that I forgot your name, may it \
> that I forgot your topic, may it that I assigned something to you that is not your \
> topic, may it that I assigned to much to you, etc., feel free to change this page \
> in the CVS (module developer.kde.org, kde2arch/ ). If you do not want to \
> participate although your name is in this document, either send me an email, or \
> replace your name with [???] in the file. If you want to participate although your \
> name is not mentioned yet, just do it (or send me an email). Either take some of \
> the unassigned topics (marked with [???]), take over a topic (after contacting the \
> responsible person) or add new topics. Hey, we manage to write first-class software \
> together, we will manage to write at least a good-enough whitepaper :-)
> 
> When you wrote something for a topic, commit the HTML in a file of its own to \
> www.developer.org/kde2arch/ and make the corresponding line in this document a link \
>                 to it.
> ---------------------------------------------------
> 
> There's no definite timeline but most of the paper should be in place before
> the KRASH release. Keep in mind that it's better to have at least some short
> hints about a topic than nothing. It's perfectly fine to commit something now
> and to extend it later.
> 
> I consider these pages as extremely important. Without information like this
> there's almost no point releasing KDE-2.0. It's pure size and the mass of
> technology included will make it hard for developers to take full advantage
> of it. That means: without this documentation we get less applicatons, inferior
> applications and a much higher support load on kde-devel.
> 
> Matthias

-- 
Daniel M. Duley - Unix developer & sys admin.
mosfet@mandrakesoft.com
mosfet@kde.org
mosfet@jorsm.com


[prev in list] [next in list] [prev in thread] [next in thread]