[daisy] Better desktop integration

Bruno Dumon bruno at outerthought.org
Mon May 5 10:44:06 CEST 2008


On Wed, 2008-04-30 at 16:56 +0200, Karel Vervaeke wrote:
[snip]
> [0] http://cocoondev.org/wiki/g5/607-cd.html

Hi,

Just some things I thought of while reading through the document:

* As Marc, I think there needs to be more focus on a certain part to be
downloaded. Maybe we need some configuration of which is the default
part type to download for each document type.

* For (local) organisation, allow the creation of folders (= filesystem
directories), instead of just a flat list of documents. Alternatively,
local tagging of the documents could be used, but that seems more
complicated and less robust.

* Foresee some version-handshaking between the tool and the online Daisy
to check if they're compatible.

* Implementation consideration: separate the GUI and functional code so
that creating a CLI or programmatic use is possible.

* For the local filename:
    - there will be a need to determine the extension based on the
mime-type. Probably this is best done by the client (based on OS info
but overrideable by local config)
    - maybe include the document name in the file name, something like
"Document name ~ID~branch~lang~part.pdf" (or other syntax)

* When uploading HTML parts, apply HTML cleaner (server-side).

* As Marc noted, allow more columns in the list view, I'm thinking of:
  - are there local modfications
  - date of last modification
  - is there a lock on the doc
  - what version is downloaded, what is last version on repo
  - data size

-- 
Bruno Dumon                             http://outerthought.org/
Outerthought                            http://www.daisycms.org/
bruno at outerthought.org              http://www.kauriproject.org/



More information about the daisy mailing list