Re: [Scrollkeeper-devel] SK mini-roadmap

[Laszlo K. <las...@su...>]

----- Original Message -----
From: "Dan Mueth" <da...@ea...>
To: "ScrollKeeper Devel" <scr...@li...>
Sent: Tuesday, April 17, 2001 5:11 PM
Subject: [Scrollkeeper-devel] SK mini-roadmap


>
> Laszlo,
>
> I'm trying to assemble our plans just a bit.  It looks like we have 4
> developments in the near future:
>
> A) Move SK to libxml2
> B) i18n improvements
> C) Support relocatable packages
> D) indexing/searching
>
> Am I missing anything we need to do in the short term?
No probably not.

> Is this the order we plan to implement things?
The TOC extractor can not be moved to libxml2 as long as the SGML->XML
parser does not work. We might still want to create another XSL based TOC
extractor for DocBook XML docs. That way we would support both DocBook SGML
and DocBook XML (if we want to do this). Another option is to move all of
Scrollkeeper to libxml2 apart from the TOC extractor, this would be really
quick to do. Probably up to one day. And it is possible technically. Then
we'll see what to do with the TOC extractor.

> What is the status on (A).  Is (A) pretty hard or going to take a lot of
> time?
The TOC extractor is the real problem as I said above, the rest can be moved
quickly.

>
> I don't see much point in making a new stable release for (A) since it
> doesn't have user-visible changes.  I'm tempted to make a new release for
> each of the other points unless (C) is easy/fast enough to lump in with
> (B) without delaying it much.  So, I have:
>
>    Release Number         Changes            Est. Release Date
>    --------------         -------            -----------------
>     0.3.x / 0.4         (A) and (B)             late May
>     0.5.x / 0.6             (C)                 late June
>     0.7.x / 0.8             (D)                 mid July

I dont know how much C would take, I think we can decide about a separate
release for it later.

> If we think (A) will take a long time, we may want to do (B) first since
> we get important functionality from (B).  However, if Mary needs (A) to do
> (D), we may have to do (A) before (B).
That develops on the approach, if she develops a new binary then that can be
linked to libxml2 regardless of what the rest of Scrollkeeper is linked to.

Laszlo