> Do you know about the pluginutils class? Thanks ! I was not aware of this. I will use it.
> 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? Can not this be simply a document type ? Every plugin could provide a boolean function taking type and saying if this type is supported. Besides this, a class or a factory method creating bibdoc could be available. >> 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. Currently they are stored inside MoreInfo. Here I will try to port existing code rather that rewriting the flags subsystem which seems to be independent on the model... just some flags should be probably supported by subclasses of BibDoc (BibObject) >> ... 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. done Besides, this part could be also supported by the same plugins. We might want to provide templates based on type. cheers Piotr
