Tasks that need to be addressed

[Morten Omholt Alver]

I have given some thought to what tasks need to be done, and this is what I came up with:

* GUI tasks:

  - Editing of @preamble, @string and @comment fields.
   
  - Editing of fields that do not appear either in 'Required' or 'Optional' categories (according to the LaTeX Companion).

  - Customizable listing of database contents in the BaseFrame.

  - Polishing of ItemFrame. Among other things, the focus handling doesn't work correctly under Linux (on my own computer, at least).

  - Online help. Not too extensive; the program should be easy enough to use without consulting help frequently.

  - Validation of database entries. How should the user be notified if required fields are not filled in?

* Auto-creation algorithms for BibTeX-keys. The user will have a strong opinion on how the keys should look, and how long they should be. Are there standard rules that should be implemented?

* Sorting algorithm to reorder the database listing according to any of the fields (author, year, title, etc.).

* Searching

  - Search function that creates a listing based on search (and sort) criteria.

  - Probably a light-weight, incremental search function would be a nice addition.

* Export functions (I'm not sure exactly what is needed. Saving to BibTeX format is already implemented in toString(). Maybe other formats would be appropriate, too)

* Web page; there isn't one yet, but we really should have a good web page.

To those of you who are interested in joining the team, please tell me which of these tasks sound interesting.

[Morten Omholt Alver]

Some of these tasks might be wise to postpone until after the initial release, since we'll want to release as soon as we have a functional program, and add features in later releases.