|
|
| Line 12: |
Line 12: |
| | | | |
| | | | |
| − | == Further References ==
| |
| | | | |
| − | For an overview of the Bibliographic project's major components and a context diagram see components.html[http://bibliographic.openoffice.org/components.html]. There is information about the current OpenOffice Bibliographic implementation[http://bibliographic.openoffice.org/implementation.html]. There is an example of bibliographic data in a Writer XML save file.[http://bibliographic.openoffice.org/xml_contents.html]
| |
| − |
| |
| − | A start has been made to the Specification for this work (see the Projects Specifications folder[http://bibliographic.openoffice.org/servlets/ProjectDocumentList?folderID=266] on the Documents and Files page). Also see a attempt at an analysis[http://bibliographic.openoffice.org/mindmap/content-analysis.html] of the proposed Bibliographic enhancement components and their relationships.
| |
| − | The best place to start for finding out about development in OpenOffice is the OpenOffice.org For Developers page[http://development.openoffice.org/index.html]. An important resource is the Developer's guide which is part of the SDK (software development kit) or available online[http://api.openoffice.org/DevelopersGuide/DevelopersGuide.html].
| |
| − |
| |
| − | The OOo API is based on UNO (Universal Network Objects)[http://udk.openoffice.org] is the interface-based component model of OpenOffice.org. UNO offers interpretability between different programming languages, different object models, different machine architectures and different processes; either in a local network or even via the Internet. UNO components can be implemented in and accessed from any programming language for which a UNO language binding exists. We currently provide several language bindings for UNO which allows to use the API from Java, C++, OpenOffice.org Basic, Python and Common Language Infrastructure (CLI).
| |
| − | Implementing the new citation element in ''xmloff'' (the XmlOffice module) is a routine task. The Sun developers want to do it together with our programmer, so that he/she can learn how xmloff works. Florian Reuter, from the Sun OOo team, has written in his blog an explanation of how the citation changes could be implemented.[http://blogs.sun.com/roller/page/flo?entry=the_community_and_me_the]
| |
| − |
| |
| − | To modify the Writer save-file read and save modules to support the new the bibliographic data file in the document save package, and to support backwards and forwards compatability logic[http://bibliographic.openoffice.org/backwards.png] to Writer the "''interface XComponentLoader''"[http://api.openoffice.org/docs/common/ref/com/sun/star/frame/XComponentLoader.html], which supports loadComponentFromURL and storeAsURL, needs to be enhanced. See the Development Guide explanation for - 6.1.5 Handling Documents[http://api.openoffice.org/docs/DevelopersGuide/OfficeDev/OfficeDev.xhtml#1_1_5_Handling_Documents].
| |
| − | See other wiki page [[Bibliographic Document XML Format]] [http://wiki.services.openoffice.org/wiki/User_talk:Bibliographic_Document_XML_Format] for a sample Writer save file contents (a .odt file) with the proposed bibliographic enhancements. This is very much a DRAFT effort.
| |
| − |
| |
| − | There is also a demonstration client program for the YAZ toolkit (C & C++). - IRTCL[http://www.indexdata.dk/irtcl/] that can perform the reference searches. (Requires YAZ and Tcl/Tk libraries be installed). It does everything but save or export the results ! However it is good model of how to use the toolkit and could be used as the basis for or model of a prototype internet searching facility. Screen pic[http://bibliographic.openoffice.org/irclient.jpeg], screen pic2[http://bibliographic.openoffice.org/irclient-setup.png].
| |
| − |
| |
| − | A demonstration internet searching facility that writes selected bibliographic records back to the OOo bibliographic database has been written in Python - PyOOBib[http://bibliographic.openoffice.org/files/documents/124/1675/PyOOBib-02.zip], instructions[http://bibliographic.openoffice.org/files/documents/124/2446/file_2446.dat?filename=PyOOBib%20Instructions%2esxw] are available. Various problems with OOo Python have lead to us concluding that YAZ in C++ would be a better foundation than the Python code.
| |
| − |
| |
| − | There is description of the OOo save-file XML Package[http://xml.openoffice.org/package.html], and is a FAQ[http://xml.openoffice.org/faq.html#4] about it.
| |
| − |
| |
| − | For details about GUI interface design please look at our Project Documentation; GUI Design Documents' Folder[http://wiki.services.openoffice.org/wiki/User_talk:Dnw#Graphical_User_Interface_.28GUI.29]
| |
| | | | |
| | == How to get started == | | == How to get started == |
Revision as of 22:05, 7 January 2006
Why is this on the User_talk page instead of being a real content page? --erAck 11:03, 6 January 2006 (CET)
The Bibliographic Project's Developer Page has been moved to a proper 'content' page at Bibliographic Project's Developer Page
How to get started
Access to the source code for this project is available for download via CVS. A child work space has been created for us called "metabib" which contains a copy of the xmloff[1] (OpenOffice.org XML File Format Definition) and sw (the word processor application component and the WYSIWYG HTML editor component) code.
The down load size will be about 1GB(?). And you will need about 2GB of disk space to compile the metabib CWS (Child-Work-Space)[2]. ( Web access to CWS ). If you can not handle that size download then ask us about sending it to you on cdroms.
Administration process - you first need to sign the JCA and then obtain the ssh key. After that we will show you how you can access the 'CWS'. It's basically a CVS branch. The most complicated thing is the setup of your tools, such that you can participate in the OOo development --- but, when you have got the ssh key we will show you.
See OpenOffice.org For Developers[3] for general development information.
Sample Code
- Sample python code that reads and outputs some of the fields of the records in the bibliographic database. biblioacess.py[]
- Sample OpenOffice Basic program to write records to the bibliographic database bibwrite.html[4]
- Henrik Just's LaTeX and BibTeX export filter http://www.hj-gym.dk/~hj/writer2latex/[5]
Applications which interact with Openoffice- Bibus (WxPython) and B3 (Java).
- A Perl module OpenOffice::OODoc[6] provides a simple way to access document elements in the (closed i.e. not interactive with OOo) document save file. An example[7] which retrieves bibliographic details is provided.
Contacts
Question or comments can be put to the Bibliographic Project development list dev@bibliographic.openoffice.org or to the project co-leader David Wilson at dnw@openoffice.org.
