HomeNewsSurveyDownloadsDevelopment DocsDevelopment BlogsProject Page

Development Documentation

Table of Contents



Large version

As the diagram above illustrates, the BibWorm project embraces four interlocking applications:


Large Version

All four manifestations share a common code base, termed the core, around which other modules are grouped. The initialization sequence determines the concrete type of application. The sequence for a standalone client, for example, would load and ultimately transfer control to a graphical user interface, whereas for a webservice a SOAP interface is initialized. BibWorm's modularity facilitates customization to suit the needs of individual users and specific environments. The extensive API and the highly flexible plugin system make adding new functionality as easy as dropping a new file into the BibWorm directory. As the first illustration makes clear, one of our primary goals is to let BibWorm applications interact with whatever third-party service (e.g. Wikipedia or Merriam Webster's Online Dictionary), database (e.g. online library catalogues, PubMed, JSTOR, etc.) and locally installed software (e.g. a desktop search application, Mozilla Thunderbird, Microsoft Outlook) users find helpful so as to improve information flow and management and thus boosting productivity.





last updated: 01-10-2006 04:38:24 GMT
Random Screenshot

A screenshot taken from a very early technical demo written in C#.