On Sun, 21 Sep 2008, Uwe Brauer wrote:
> * Store the .lyx-file in a wiki page as the following "wiki markup":
> (:LyX-file:)
> <LyX file goes here>
> (:LyX-fileend:)
Precisely.
Seeing it, I realize it must actually be more like this:
(:LyX-file <filename> :)
<LyX file goes here>
(:LyX-fileend:)
otherwise you'll end up with random file names.
> * When such a wiki page is rendered by the wiki server, it doesn't
> actually have to show the LyX source. There are several options (not
> exclusive):
On criteria should also be to make it as possible for different users on
different OS with different browsers to use it, with fiddeling some
javascripts or the like.
Since it's a wiki page, they could just edit the wiki page, and within
the page the, the raw .lyx-file. Something more than that is probably
a _lot_ of effort compared to what you'd get.
> ** Insert a [PDF] link for the (:LyX-file:)...(:LyX-fileend:).
> When you click that link you get a PDF version of the LyX document.
> The server can maintain a cached copy of the PDF to speed things up.
That is a solution seems most intuitive to me.
> ** Use a thumbnail image of a page from the LyX document as link text.
> Clicking this image could then e.g. show the PDF.
> ** Insert a [Source] link, clicking it returns the .lyx-file
> ** Insert a special [LyX edit] link, clicking on it launches the process
> described above. You'd probably have to do something with your browser
> to get this to work.
That looks like the second best solution
You could just have several links, e.g.
[PDF] [Source] [LyX edit]
> A lot of this is quite easy to implement, but you will also have a lot
> of disadvantages (external image files, lot's of people may edit it
> etc)
Could you try it on one server? Or is this too much to ask.
I probably could as I don't expect it to take too much time. However,
before doing it I'd insist that we work on describing what it should do
in terms of one or more detailed use cases.
Frankly that looks to me a very GOOD starting point.
<snip>
- up to five collaborates
- a document which is around 50 pages
I really think you'd be better of with a VCS, but it might be worth a try.
Please note that there are things which may prohibit the solution describe
above. For instance, I worry that it will not be safe to compile the
.lyx-file on the server, as the .lyx-file could contain LaTeX code that
compromises the security of the server...
Anyway, as I said above, I'd like to see/discuss some detailed use cases
before actually thinking of implementing anything. If you like, you can
start writing on a use case on this page:
http://wiki.lyx.org/Devel/WikiLyXUseCase
(the page does not exist yet, so just create it)
regards,
Christian
--
Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
