gnokii-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: API docs


From: Pedro Côrte-Real
Subject: Re: API docs
Date: Thu, 02 Sep 2004 15:09:16 +0100

On Wed, 2004-09-01 at 21:04 +0200, Pawel Kot wrote:
> On Wed, 1 Sep 2004, Pedro [ISO-8859-1] Côrte-Real wrote:
> 
> > On Wed, 2004-09-01 at 17:55 +0200, Pawel Kot wrote:
> > > On Wed, 1 Sep 2004, Pedro [ISO-8859-1] CĂ´rte-Real wrote:
> > >
> > > > Where can I get API documentation from libgnokii/libsms?
> > >
> > > How detailed documentation do you need?
> >
> > Detailed enough to be able to use it. :)
> 
> There's some description in Docs/* files. See also include/gnokii.h and
> include/gnokii/*.h to see what you can use. Also comments in common/*.c
> may be usable.
> 
> > I've started by ripping code from gnokii.c. I've just succeeded in
> > making an sms.c that is capable of fetching and sms message from the
> > phone. Basically I've made getsms() a standalone program. I'm doing this
> > so I can make this program spit out XML to be parsed by other programs.
> > Unix-style so to speak.
> >
> > Wouldn't it be better to split gnokii into smaller programs for
> > SMS/Calendar/Logos/Etc?
> 
> What would be a benefit?

Well I've pretty much done that already for retrieving sms's from the
phone. The code is much more readable now because I've split it into
smaller functions. I've also added that XML support I was talking about.
It was pretty easy.

Doing the same for everything would simplify the command line handling
immensely and it would be easier to use. Now, every time I want to do
anything I have to see gnokii's manpage. If they were all separate
programs I could use tab completion to find the right program check it's
options with a --help and be done with it.

If you want me to send you what I've done just say so.

Pedro.

Attachment: signature.asc
Description: This is a digitally signed message part


reply via email to

[Prev in Thread] Current Thread [Next in Thread]