Notes update.

[lyx.git] / development / HTML / HTML.notes

diff --git a/development/HTML/HTML.notes b/development/HTML/HTML.notes
index e5139650601e935a8df7e6bfb7a9ecf809c65d24..02d08a12d1fbd21451014178ea2cb02ae5da8535 100644 (file)
--- a/development/HTML/HTML.notes
+++ b/development/HTML/HTML.notes
@@ -33,6 +33,7 @@ These insets work but still need work:
                the bbl file, which of course is the only fully general solution.
        InsetFlex: I think this one is OK, but it needs some testing.
        InsetFloat: This seems to work OK, but it will need testing and tweaking.
+       InsetFloatList: Seems to work well, but may need testing.
        InsetGraphics: This works in a pretty primitive way, in that it outputs the graphic
          and appropriate img tag. But we don't yet do any sort of scaling, rotating, and
                so forth. That won't be hard, since we can just call ImageMagick to do this for 
@@ -43,23 +44,17 @@ These insets work but still need work:
        InsetTabular: Works reasonably well, but we don't do anything with any of the 
                arguments provided for longtable. There are probably other limitations, too,
                since I'm very much not an expert with tables.
-       InsetTOC: This now works pretty well, but only for the table of contents, not for
-               any other TOC-like lists. Getting those to work shouldn't be too bad, as we can
-               do almost exactly the same thing. That said, though, we might want to do things
-               slightly differently, and have the links target actual *insets*, rather than just
-               target paragraphs. That'd mean doing a bit of work on TocBackend, etc.
-       InsetXYMatrix: So far as I can tell, using this in LyX effectively involves using a
-               lot of ERT, within the matrix, to get the arrow effects. At present, it just prints
-               as an InsetMathGrid, from which it inherits, and so as a simple table. I don't know
-               how much more we can do.
+
 
 Math
   We have a fair bit of math now working via MathML output, but there are still some 
   isues, and not all the insets work. Here are the ones I know still need work:
-       - Array
+       - Array: Should be able to use alignment information via appropriate attributes, for
+               mtable, mrow, and mtd.
        - Box: There is a general issue here with text mode nesting. See the FIXME attached
                to the SetMode class.
-       - Lefteqn
+       - Lefteqn: For this, and numbering in general, probably need mlabeledtr, which may
+               mean we always need to output <mtable>.
        - Par?
        - Phantom: There is some support for this in MathML....
        - Ref: Needs to be deferred.
@@ -73,6 +68,18 @@ Math
        - Tabular: This is more or less a text-like table in math. Probably output it
                as a table, but set the font.
 
+Other math notes:
+       - Hull:
+               -       Need to handle the equation hull type by outputting a counter. But that will 
+                       have to wait for the counter patch. The counter probably goes with mlabeledtr, 
+                       which may mean we always need to output <mtable>.
+               - Similar issues about eqnarray.
+               - It's not clear if we need to do much about the other hull types.
+       - XYMatrix: So far as I can tell, using this in LyX effectively involves using a
+               lot of ERT, within the matrix, to get the arrow effects. At present, it just prints
+               as an InsetMathGrid, from which it inherits, and so as a simple table. I don't know
+               how much more we can do.
+
 
 These insets do not work and are not yet scheduled to work:
        InsetExternal: It may be that this won't be too hard, but I don't understand 
@@ -84,8 +91,3 @@ These insets do not work and are not yet scheduled to work:
 
 May need to make use here of TocWidget::itemInset, which should then be moved
 to TocBackend.
-
-MATH
-       Regarding math, the view seems to be that we should in the first instance just use what
-       we get from instant preview and copy those over to the output directory, and then try
-       to make MathML work.