[daisy] Better desktop integration

[Karel Vervaeke]

Hi

(note: Also check the part of this thread under Marc's feedback, there
are some references to this thread IIRC).

I think most people (including me) will agree that using Daisy as the
central repository for documents is the best solution.  Sure, there is
some overhead if you have to download parts/files every time you want to
make changes, but then again, that is what we are trying to address
right now.

As for Jorg's situation:
- how do you refer to network share documents if people use different
drive mappings? (you could use the UNC path //server/share but that's
not very practical + not every user is aware of UNC paths).
- drag-n-drop (see Marc's feedback) for linking the documents after
adding them to the list + the systray (see Marc...) notification should
give reasonable support).
- If you have suggestions for better integration with your situation
they are welcome, but as you understand, your solutions should not
disturb the 'daisy-as-central-repository' approach since that is the
main use-case we want to support.

On Fri, 2008-05-02 at 23:28 +0200, Jorg Heymans wrote:
> 
> On Fri, May 2, 2008 at 11:10 PM, Parisi, Lou
> <Lou.Parisi at photomask.com> wrote:
>         >Jorg wrote:
>         >It is just so that (for our usecase at least) people often
>         refer to
>         >existing msoffice documents when writing documentation or
>         manuals
>         >in Daisy. These documents are sourced from external document
>         management
>         >systems or well-known protected locations on a network drive.
>         >The documents are accessible (both r/o and r/w) by many other
>         >people that don't even know (or care) about the existence of
>         Daisy.
>         >The original master document location thus cannot be changed.
>         
>         
>         To me it seems like having multiple versions around becomes an
>         information management problem.  Which is the correct version
>         of a
>         document?  If the master is not in Daisy, and some people may
>         be editing
>         the master and not even know about Daisy, then maybe Daisy
>         should just
>         have a link to the master document on the network share
>         instead of a
>         potentially outdated copy attached.
> 
> That would be one way of doing it yes. Unfortunately network share
> links don't translate all that well across our intranet environment.
> Different departments having different mapped drives, a user in dept A
> has no access to a shared drive from dept B, etc etc.  
> 
> 
>         On the other hand, this is really a decision for the actual
>         user so
>         perhaps you are correct in your interpretation of not imposing
>         too many
>         restrictions.  Then it just becomes a development resource
>         question
>         since the two paradigms will have different features.
> 
> Let's see what Karel has to say about it, after all he's the one that
> will be developing this :-P
> 
> Cheers,
> Jorg
> 
> 
> _______________________________________________
> daisy community mailing list
> Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
> mail to: daisy at lists.cocoondev.org
> list information: http://lists.cocoondev.org/mailman/listinfo/daisy