Update notes.

git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@30057 a592a061-630c-0410-9148-cb99ea01b6c8

diff --git a/development/HTML/HTML.notes b/development/HTML/HTML.notes
index 8b7f9e116e917b4c884dbdf50e9468f17fc8afc5..223e1f567cd971bca735977b2d38f20e9b0c2d49 100644 (file)
--- a/development/HTML/HTML.notes
+++ b/development/HTML/HTML.notes
@@ -36,10 +36,10 @@ These insets work but still need work:
                BibTeXInfo::label() method. A similar strategy will work for author-year and
                the like, but calculating labels will be more complex---unless we just parse
                the bbl file, which of course is the only fully general solution.
                BibTeXInfo::label() method. A similar strategy will work for author-year and
                the like, but calculating labels will be more complex---unless we just parse
                the bbl file, which of course is the only fully general solution.

+       InsetFlex: I think this one is OK, but it needs some testing.

 
 These insets do not work but should be completely straightforward:
 
 These insets do not work but should be completely straightforward:

-       Caption, Flex (uses collapsable)
-
+       Caption

 
 May need to make use here of TocWidget::itemInset, which should then be moved
 to TocBackend.
 
 May need to make use here of TocWidget::itemInset, which should then be moved
 to TocBackend.


@@ -68,9 +68,9 @@ These do not yet work and need some attention:
                should we get it? Probably some validation thing again, where labels tell us where 
                they are. Alternatively, we could parse the aux file.
        InsetTabular: This shouldn't be too hard, but will need doing.
                should we get it? Probably some validation thing again, where labels tell us where 
                they are. Alternatively, we could parse the aux file.
        InsetTabular: This shouldn't be too hard, but will need doing.

-       InsetTOC: Here again, validation might do the trick, but I'm not sure. Or perhaps some
-               kind of post-processing? Another option, maybe the best option, would be just to use
-               the information we already have in the TOC.
+       InsetTOC: We should just be able to use what we have in the TOC. To get links to
+               work, though, we'll need to co-ordinate the writing of anchors in the sections,
+               which won't actually happen until later.

        InsetVSpace: This will be easy, once we have the Length::asHTML() method.
        InsetWrap: This should be simple enough, probably a div and some CSS, but I'm not sure
                precisely what this is supposed to do.
        InsetVSpace: This will be easy, once we have the Length::asHTML() method.
        InsetWrap: This should be simple enough, probably a div and some CSS, but I'm not sure
                precisely what this is supposed to do.