TODO
* Beginning to turn the first part of this into something kind of like an actual TODO list as Org Mode uses it (maybe).
This commit is contained in:
parent
3c3b149996
commit
40da502292
@ -1,6 +1,33 @@
|
|||||||
#+TITLE: Stuff To Do
|
#+TITLE: Stuff To Do
|
||||||
|
|
||||||
* TODO
|
* Project Task List
|
||||||
|
|
||||||
|
** TODO Documentation default format
|
||||||
|
:PROPERTIES:
|
||||||
|
:CUSTOM_ID: todo-docs-default
|
||||||
|
:END:
|
||||||
|
|
||||||
|
Decide on a default file format for documentation. The two main
|
||||||
|
contenders being Org Mode, the default for the GnuPG Project and
|
||||||
|
reStructuredText, the default for Python projects. A third option
|
||||||
|
of DITA XML was considered due to a number of beneficial features
|
||||||
|
it provides.
|
||||||
|
|
||||||
|
The decision was made to use Org Mode in order to fully integrate
|
||||||
|
with the rest of the GPGME and GnuPG documentation. It is possible
|
||||||
|
to produce reST versions via Pandoc and DITA XML can be reached
|
||||||
|
through converting to either Markdown or XHTML first.
|
||||||
|
|
||||||
|
** TODO GUI examples
|
||||||
|
:PROPERTIES:
|
||||||
|
:CUSTOM_ID: todo-gui-examples
|
||||||
|
:END:
|
||||||
|
|
||||||
|
Create some examples of using Python bindings in a GUI application
|
||||||
|
to either match or be similar to the old GTK2 examples available
|
||||||
|
with PyME.
|
||||||
|
|
||||||
|
* Project Task Details
|
||||||
|
|
||||||
** Working examples
|
** Working examples
|
||||||
:PROPERTIES:
|
:PROPERTIES:
|
||||||
@ -27,12 +54,12 @@
|
|||||||
bindings has been removed.
|
bindings has been removed.
|
||||||
|
|
||||||
Current and future documentation will adhere to the GnuPG standard
|
Current and future documentation will adhere to the GnuPG standard
|
||||||
of using Org Mode and not use the reST more commonly associated
|
of using Org Mode and not use the reStructuredText (reST) format
|
||||||
with Python documentation. The reasons for this are that this
|
more commonly associated with Python documentation. The reasons
|
||||||
project is best served as shipping with the rest of GPGME and the
|
for this are that this project is best served as shipping with the
|
||||||
documentation ought to match that. Furthermore, there are aspects
|
rest of GPGME and the documentation ought to match that. There are
|
||||||
of Org Mode's publishing features which are superior to the
|
also aspects of Org Mode's publishing features which are superior
|
||||||
defaults of reST, including the capacity to generate fully
|
to the defaults of reST, including the capacity to generate fully
|
||||||
validating strict XHTML output.
|
validating strict XHTML output.
|
||||||
|
|
||||||
If reST files are required at a later point for future inclusion
|
If reST files are required at a later point for future inclusion
|
||||||
|
Loading…
Reference in New Issue
Block a user