kevin.krammer at gmx.at
Sun Jun 26 12:49:49 CEST 2005
On Sunday 26 June 2005 12:26, Carsten Niehaus wrote:
> What do we need from kdelibs API-wise? Tobias, Elian and I had a discussion
> and pretty much agreed on this API:
> * validate if an article exists
> -- bool articleExists( const QString& articlename )
> * return an article (wiketext, xml or html) which I request
> * @param articlename the name of the article
> * @param type defines if this returned string is in XML,
> Wikitext or html
> -- QString getArticle( const QString& articlename, DocumentType type )
Maybe a method to ask which DocumentTypes are available for a given existing
I can imagine that there are situation where one would prefer one type but
could also extract at least a subset of the information form others.
> * return the users who modified an article. This is needed because the
> GNU-FDL requires that you name all contributors of an article. I suggest
> that we don't display them in a text but have "Author"-Buttons.
> -- QString articleAuthors( const QString& articlename )
Maybe using QValueList<KAboutPerson> as the return value type?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kde-edu/attachments/20050626/83738422/attachment.pgp
More information about the kde-edu