scrollkeeper-devel

[Scrollkeeper-devel] API to get the count of newly added omf files

[Rajkumar S. <raj...@wi...>]

Hi,

This is further in continuation of my earlier mail about "Indication of
newly added omf file". On further analysis I wrote a small API say
scrollkeeper_get_omffile_count() in update.c which will return the count
of omf files that needs to be registered/unregistered with
scrollkeeper_docs.

With the help of this API any help browser would know if there are any
newly installed omf files that needs to be registered and if so it can
prompt a message to the user asking him to run 'scrollkeeper_update' to
register them.


Issue in implementing the API:
-----------------------------

I find that scrollkeeper doesn't have any API yet and hence there are no
scrollkeeper .h files to export the API's, so for implementing this
scrollkeeper_get_omffile_count() we would need to have a scrollkeeper .h
file installed in standard path (like /usr/include/scrollkeeper/*).

Pls. let me know if we could move forward in implementing this API.


Note: Am not sure if my previous mail sent on '25th Apr 2003' was
delivered to this list as I couldn't see it in the archives list
"http://sourceforge.net/mailarchive/forum.php?thread_id=2014500&forum_id=4112",
hence am attaching my previous mail with it.


Thanks & Regards,
Raj.

Re: [Scrollkeeper-devel] API to get the count of newly added omf files

[Dan M. <mu...@al...>]

Hi Raj,

These sound like good additions.  I would hope that not many packages
forget to run updatedb.  Especially since many users don't have root
access on their machines.  (It might make sense to have a crontab entry
installed to run updatedb daily, although I'm not sure how uniform cron is
handled across distributions and different flavors of Unix.)  However, I
think this utility is a good thing to have.

Further, we have had intentions to export an API for some time.  In fact,
many of the things which are now scripts should be put into a library.  
Your present work could be the start of the exported API and then we can
expand it from there.

Thanks for the contributions :)

Cheers,

Dan

On Wed, 30 Apr 2003, Rajkumar Sivasamy wrote:

> Hi,
> 
> This is further in continuation of my earlier mail about "Indication of
> newly added omf file". On further analysis I wrote a small API say
> scrollkeeper_get_omffile_count() in update.c which will return the count
> of omf files that needs to be registered/unregistered with
> scrollkeeper_docs.
> 
> With the help of this API any help browser would know if there are any
> newly installed omf files that needs to be registered and if so it can
> prompt a message to the user asking him to run 'scrollkeeper_update' to
> register them.
> 
> 
> Issue in implementing the API:
> -----------------------------
> 
> I find that scrollkeeper doesn't have any API yet and hence there are no
> scrollkeeper .h files to export the API's, so for implementing this
> scrollkeeper_get_omffile_count() we would need to have a scrollkeeper .h
> file installed in standard path (like /usr/include/scrollkeeper/*).
> 
> Pls. let me know if we could move forward in implementing this API.
> 
> 
> Note: Am not sure if my previous mail sent on '25th Apr 2003' was
> delivered to this list as I couldn't see it in the archives list
> "http://sourceforge.net/mailarchive/forum.php?thread_id=2014500&forum_id=4112",
> hence am attaching my previous mail with it.
> 
> 
> Thanks & Regards,
> Raj.

Re: [Scrollkeeper-devel] API to get the count of newly added omffiles

[Rajkumar S. <raj...@wi...>]

Hi Dan,

Thanks for your comments and motivation.


> These sound like good additions.  I would hope that not many packages
> forget to run updatedb.  Especially since many users don't have root
> access on their machines.  (It might make sense to have a crontab entry
> installed to run updatedb daily, although I'm not sure how uniform cron is
> handled across distributions and different flavors of Unix.)  However, I
> think this utility is a good thing to have.

- Yes, I do agree that packages should run updatedb by default, but
there are some odd cases where it fails to run it, in those cases the
help browser can make use of this API to know if there are any
unregistered omf files, if there are any it could popup a message
saying:

"Newly installed app. detected, pls. ask your admin to run
scrollkeeper_update to view the help doc's for the app".

 
> Further, we have had intentions to export an API for some time.  In fact,
> many of the things which are now scripts should be put into a library.
> Your present work could be the start of the exported API and then we can
> expand it from there.
> 
> Thanks for the contributions :)

- Sure :) Once I finish with the API I'll post in the list for
review/approval.


Thanks & Regards,
Raj.