Like any unimplemented feature, there've been a lot of open design issues which we've hoped that a good fields implementation would help address. For the sake of completeness, I'm listing them below. However, I don't plan to address any of these issues until we've got a concrete fields design on the table to look at. The following is a summary of design issues which probably ARE related to what we plan on doing with fields. AutoNum and Fields ------------------ http://www.abisource.com/mailinglists/abiword-dev/00/January/0186.html AutoNum and Fields -- what CSS does ----------------------------------- http://www.abisource.com/mailinglists/abiword-dev/00/January/0187.html Luke: fields and lists, late summer ------------------------------------ http://www.abisource.com/mailinglists/abiword-dev/00/March/0229.html Martin: updated lists patch, waiting on fields ----------------------------------------------- http://www.abisource.com/mailinglists/abiword-dev/00/April/0334.html DocBook mapping to specific fields ---------------------------------- http://www.abisource.com/mailinglists/abiword-dev/00/April/0101.html Fr�d�ric: not using fields (yet) for biblio stuff -------------------------------------------------- http://www.abisource.com/mailinglists/abiword-dev/00/May/0490.html The following design issues may be related to fields, but I'm not currently sure: Calculated sections ------------------- http://www.abisource.com/mailinglists/abiword-dev/00/February/0511.html Martin: groups also useful for lists, tables? ---------------------------------------------- http://www.abisource.com/mailinglists/abiword-dev/00/April/0062.html The following are probably *NOT* related to the fields work, although at first glance they seemed to be. Embedded math ------------- http://www.abisource.com/mailinglists/abiword-dev/00/February/0625.html Previews for embedded objects ----------------------------- http://www.abisource.com/mailinglists/abiword-dev/00/March/0297.html Paul
