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

List:       kde-devel
Subject:    Re: KFile plugins
From:       Kevin Krammer <kevin.krammer () gmx ! at>
Date:       2005-10-14 17:02:42
Message-ID: 200510141902.42845.kevin.krammer () gmx ! at
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Friday 14 October 2005 14:29, Thomas Kadauke wrote:
> Am Friday 14 October 2005 14:22 schrieb Adriaan de Groot:
> > On Friday 14 October 2005 14:15, Thomas Kadauke wrote:
> > > Am Friday 14 October 2005 10:14 schrieb Brad Hards:
> > > > Feel free to use any of my tutorial material for this purpose. I'd
> > > > suggest moving the examples to compilable code (eg in an examples/
> > > > sub-directory under the actual kfile code) and then using doxygen to
> > > > include them. We can then just turn the location on developer.kde.org
> > > > into a link back to the API docs.
> > >
> > > Thanks. So should I update the dox for 3.5 branch or for trunk?
> >
> > Branch. Please mark apidox commits with the first line starting with DOX:
> > so that my commit filter catches them -- I batch-forward-port to trunk
> > when the fancy strikes me. Watch the generated apidox on
> > www.englishbreakfastnetwork.org to see the effects of your work
> > (developer.kde.org apidox don't update well right now).
>
> Ok. But I don't have an SVN account. Can I just send a patch to this list
> when I'm done?

You can send them to me, I am also working on KDE3.5 API dox improvements.

Cheers,
Kevin

-- 
Kevin Krammer <kevin.krammer@gmx.at>
Qt/KDE Developer, Debian User
Moderator: www.mrunix.de (German), www.qtforum.org

[Attachment #5 (application/pgp-signature)]

 =

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscrib=
e <<


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