[Openberg-devel] Re: Openberg participation

[David T. <dt...@en...>]

Le Mercredi 1 Octobre 2003 16:32, vous avez écrit :
> Hi David,
>
> I will be happy to help, let's see what I can start
> with.
> Do I understand you to mean there is not even a
> requirements document? Oh dear! 

Oh dear, oh dear :)

Well, I must confess there is no such thing. 

> I am certainly willing
> to handle a features list, although I don't know how
> that is managed so if you can either explain the
> mechanisms of doing it or point me to a howto document
> I would be grateful (presuming there is a facility in
> SourceForge to handle this).

I must also confess I have no idea on how to do such a thing. But whenever 
you find out, be sure to tell us :)

> I have a Linux system at home (Red Hat 8) but normally
> use Windows 2000, which would probably be more helpful
> if all programming has been done on Linux so far. Any
> idea what tools and environment are needed to compile
> and run, or is that the first task?

We have not tried even once to compile under Windows.

Best guess :
* wxWindows 2.4.0+ compiled with Unicode
* Mozilla 1.4+
* (soon) Apache Xerces - no version has been specified yet

> I have had a few ideas about features, and could
> certainly also help out writing a test spec. But first
> I need to know what the program is MEANT to do, rather
> than what it does (which I also don't know). 

I'm willing to answer these questions. How many lines of explanation do you 
want ?

> Also I
> haven't seen any Open ebook format books around, so
> what are we going to test against?

Well, the only oebps eBook we have been able to find is
http://www.openebook.org/oebps/oebps1.2/samples/Wuthering%20Heights%20(OEBPS%201.2).zip

For more testing, we will need to develop a compiler, even more so since we 
will definitely need to enrich the oebps standard (for book-to-other-book-, 
book-to-annotation- and annotation-to-book-links, for example)

> When you say specifications are distributed between
> your brain and sourceforge do you mean they have to be
> extracted from code and your brainwaves or is there at
> least a minimal or skeleton document available? I
> don't mind starting from that and building up.

No, our code is definitely not a source for specifications. Only for 
Api documentation.

On the other hand, depending on how you see 
http://openberg.sourceforge.net/documentation.html
we have either some skeletton or no documentation at all.

> regards,
> Philip Kerrigan

Regards,
 David

P.S. : You're at the Ieee ?

-- 
===
 David Teller
  LIP, ENS Lyon : Dav...@en...
   Bureau 306, Poste 87-96 -- http://www.ens-lyon.fr/~dtelle
    Editions Vigdor -- http://www.vigdor.com
     Projet OpenBERG -- http://openberg.sourceforge.net
     
Les Mots appartiennent à ceux qui savent s'en servir.