Abdelrazak Younes wrote:
rgheck wrote:
Uwe Brauer wrote:
> No. I suppose it could be done, but it would be a huge amount of
> work.
That I was afraid of. It reminds me of the hen/egg problem. Not very
many people miss such a software, but once it is there...(like with
wikipedia)
No, it's not so much that. I could be wrong, but it seems to me like
doing this would involve writing a whole new program, more or less.
Not entirely. We could extend the lyxserver to do this kind of
synchronisation over the internet. There will always be one LyX
instance acting as a server and that could send func request to other
LyX clients. This is more or less what the Abiword people are doing
with their new version.
I was thinking more in terms of a browser-based frontend communicating
via AJAX with a LyX instance running on a server. But what you're
suggesting makes sense.
I had a different idea, though, too. What if the LyX document itself
were stored on a server somewhere? It wouldn't be that hard to allow
such documents to be opened. (I'm actually kind of surprised I can't
enter "http://frege.brown.edu/font.lyx"; into our file dialog. You can do
that kind of thing in gimp, e.g.) Then you could check for changes to
the existing file and figure out how to integrate them, or pop up some
sort of conflict resolution thingy if that was non-trivial. Of course,
you'd also want to be able to save the file to the remote location. But
if the access method were, say, scp or webdav or something, then this is
do-able. But, as you say, I'm not sure LyX (or, for that matter,
anything) needs this kind of immediate visibility.
rh
