Hi Piotr,
Il giorno mar, 28/06/2011 alle 00.26 +0200, Piotr Praczyk ha scritto:
> >Well it represent a document. Could you be more specific about which
> >functions are only related to fulltext?
>
> get_text
> get_text_path
> extract_text
> pdf_a_p
> has_text
Got it. Although this API was to make it extremely easy to script for
text extraction and indexing. If you refactor things to have a hierarchy
of classes, which should think of how to know which class to load for
which type of BibDoc.
Do you know about the pluginutils class? Maybe we can provide BibDoc
classes as plugins that will be automatically instantiated based on the
new column in bibdoc.
Maybe we can have a new column in the bibdoc table to say which class
should be used?
> and in addition, some general flags are vert much BibDoc related
Yes, indeed these flag were introduced to aid certain future workflows
but I guess they will be easily superseded by the extended
functionalities of MoreInfo.
> ... and besides, maybe we should move methods responsable for
> displaying bibdocfiles to something like template ? Currently there are
> functions displaying HTML code inside the BibDoc (and similar) class.
Agree.
Cheers,
Sam
--
Samuele Kaplun
Invenio Developer ** <http://invenio-software.org/>
