<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>
</head>
<body>
<p> </p>
<p style="margin: 0px; "></p>
<div style="margin: 5px 0px;">
<br/>
Marco van de Voort <marcov@stack.nl> hat am 28. März 2012 um 16:59 geschrieben:
<br/>
<br/>
> On Wed, Mar 28, 2012 at 09:54:01AM +0200, Mattias Gaertner wrote:
<br/>
> > >
<br/>
> > > 1. One can be offline, the other not.
<br/>
> >
<br/>
> > You can make offline snapshots of the wiki.
<br/>
>
<br/>
> Ah, that is working again? Since when?
</div>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">A db dump is still disabled.</p>
<p style="margin: 0px;">But with a small tool you can download the pages (in wiki format) and images. A chm converter basically works. </p>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;"> </p>
<div style="margin: 5px 0px;">
> > And how do I show it? Probably extracting the contents and
<br/>
> properly relinking and indexing it needs to be redone after each wiki
<br/>
> migration.
</div>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">The tool already does the linking. </p>
<p style="margin: 0px;">I also implemented a simple search, which IMO already is quite useful.</p>
<p style="margin: 0px;"> </p>
<p>The main problem is that currently ipro lacks many html/css features. And many pages have bugs and non portable tags. These need fixing. I guess a full week, which I don't have, because 1.0 bug has higher priority.</p>
<p>If someone wants to help, write me a mail. </p>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;"> </p>
<div style="margin: 5px 0px;">
>
<br/>
> "wiki" is not an abstract format. Even microsoft word would be better, at
<br/>
> least that is COM automatable.
</div>
<p style="margin: 0px;"> </p>
<div style="margin: 5px 0px;">
> > > > 2. One is versioned per lazarus version, one is not.
<br/>
> >
<br/>
> > A release could have snapshots of both.
<br/>
>
<br/>
> That is not the same thing. A zipped copy is not the same as a branch.
</div>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">True.</p>
<p style="margin: 0px;">But it is sufficient for a release. </p>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;"> </p>
<div style="margin: 5px 0px;">
> > > BTW:
<br/>
> > The update problem already exists in the offline version of the LCL.
<br/>
> > There are already outdated links and examples.
<br/>
>
<br/>
> There is a problem yes. But at least in theory, one could merge back doc
<br/>
> fixes from trunk to a fixes branch for the next fixes release.
</div>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">In theory changed wiki pages can be merged back too. It's a simple xml file per page. </p>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;"> </p>
<div style="margin: 5px 0px;">
>
<br/>
> Admitted, neither does FPC, but Lazarus even lacks the theoretical base for
<br/>
> this.
</div>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;"> </p>
<p>Mattias</p>
<p> </p>
</body>
</html>