Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Merge fixes from the 3.21.0 release branch. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA3-256: |
411a4d6ddee985e441ce1ff796476320 |
User & Date: | drh 2017-11-04 15:02:01.565 |
Context
2017-11-04
| ||
17:08 | Begin adding the "WAL-mode File Format" document. Much work left to be done. (check-in: 3f66c70302 user: drh tags: trunk) | |
15:02 | Merge fixes from the 3.21.0 release branch. (check-in: 411a4d6dde user: drh tags: trunk) | |
2017-11-03
| ||
02:37 | Fix typo reported on the mailing list. (check-in: d26d101c74 user: mistachkin tags: trunk) | |
2017-11-02
| ||
20:07 | Fix a typo ("quote" instead of "quota") in the VFS document. (check-in: 877f14d569 user: drh tags: branch-3.21) | |
Changes
Changes to pages/affcase1.in.
1 2 3 4 5 6 7 8 9 10 11 | <tcl>hd_keywords {What If OpenOffice Used SQLite} \ {OpenOffice case study}</tcl> <title>What If OpenDocument Used SQLite?</title> <h1 align="center"> What If OpenDocument Used SQLite?</h1> <h2>Introduction</h2> <p>Suppose the [http://en.wikipedia.org/wiki/OpenDocument|OpenDocument] file format, | | | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 | <tcl>hd_keywords {What If OpenOffice Used SQLite} \ {OpenOffice case study}</tcl> <title>What If OpenDocument Used SQLite?</title> <h1 align="center"> What If OpenDocument Used SQLite?</h1> <h2>Introduction</h2> <p>Suppose the [http://en.wikipedia.org/wiki/OpenDocument|OpenDocument] file format, and specifically the "ODP" OpenDocument Presentation format, were built around SQLite. Benefits would include: <ul> <li>Smaller documents <li>Faster File/Save times <li>Faster startup times <li>Less memory used <li>Document versioning |
︙ | ︙ | |||
463 464 465 466 467 468 469 | and constraints to enforce consistency of content even in the face of programming errors. Further enhancement ideas include: <ul> <li> Store an [automated undo/redo stack] in a database table so that Undo could go back into prior edit sessions. <li> Add [FTS4|full text search] capabilities to the slide deck, or across multiple slide decks. | | | 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 | and constraints to enforce consistency of content even in the face of programming errors. Further enhancement ideas include: <ul> <li> Store an [automated undo/redo stack] in a database table so that Undo could go back into prior edit sessions. <li> Add [FTS4|full text search] capabilities to the slide deck, or across multiple slide decks. <li> Decompose the "settings.xml" file into an SQL table that is more easily viewed and edited by separate applications. <li> Break out the "Presentor Notes" from each slide into a separate table, for easier access from third-party applications and/or scripts. <li> Enhance the presentation concept beyond the simple linear sequence of slides to allow for side-tracks and excursions to be taken depending on how the audience is responding. </ul> |
︙ | ︙ |