Projects tagged ‘rst’

WCV uses a very extendable handler mechanism to display content managed in directory structures with come version control system or from some other sources (CMS, ...) Using a user extendable ... [More] handler mechanism the directories, files, content and meta data may be handled and fetched separately and displayed with different display decorators for different output, like HTML, txt or the original binary. Mainly used for static cached content, also dynamic user interaction is possible when the content classes are implementing the corresponding interfaces. [Less]

A tool to convert lightly marked plain text (Restructured Text) directly into PDFs, supporting font embedding, custom paper sizes, arbitrary paragraph and character styles, and much more.

WinRST incorporates existing command line tools into user friendly package that makes converting ReStructured Text to PDF and HTML easier under MS Windows.

The goal is to be able to convert Open Document produced with Open Office (.odt files) into reStructuredText file (.rst files). In particular to convert back the .odt files produced by rst2odt into ... [More] .rst files. To let people review and modify .rst file using OpenOffice. [Less]

This project is a pastebin for formatted displaying of restructered text.

Trestle is a nose plugin that enables you to write testable documentation for web apps (or shell commands, but more on that later). To use trestle, write a reStructured Text document using a set of ... [More] special directives to indicate the fixtures to be used for testing (including the http or mock http client), each request to be sent via the client, and the expected response from the application under test. A simple trestle test document might look like this:: Frog: A web service for doing things with frogs ----------------------------------------------- .. fixtures :: frog_fixtures Frog is a web service for doing things with frogs. You can list the available frogs. .. request :: List available frogs GET /frogs .. The response is in a plain-text format. .. response :: bullfrog poison dart treefrog ... .. You can find out if something is a frog. .. request :: Get bullfrog details GET /frogs/bullfrog .. If the requested term is a frog, details about the frog will be returned. .. response :: Bullfrogs are really big frogs. .. Otherwise, a 404 response is returned. .. request :: Get details for a non-frog GET /frogs/toad .. .. response :: 404 ... ... "toad" is not a frog. .. You can create frogs. .. request :: Create a frog POST /frogs/pouched+frog A pouched frog camouflages itself to look like dead leaves. .. .. response :: 201 Created ... ... ..Trestle directives ^^^^^^ Fixtures for a trestle test file are set like so: .. fixtures:: aboutA fixtures directive is required in every document to be tested. The directive must name a python module. The module must include the following attribute: client A client application to be called with methods .get(), .post(), .put(), etc. Each method must accept at least the arguments url and data, and may accept others but may not require them. paste.fixtures.TestApp is such a client, though it natively supports only .get() and .post(). And may include the following functions: setup_all(cls) Setup fixture run before the first request. teardown_all(cls) Teardown fixture run after the last request. setup_each(inst) Setup fixture run before each request. teardown_each(inst) Teardown fixture run after each request. Tests in a trestle document consist of a `.. request` directive, followed by one or more `.. response directives. The .. request` directive defines the request to be sent to the web app under test, using the client defined in the fixtures module. A simple request directive looks like this: .. request:: A simple get GET /foo/bar ..If the request is a POST or PUT that includes data to be sent, include that data in the body of the request, after the request line:: .. request:: A post POST /foo/bar a=1&b=2 ..The response expected to be returned to the client is defined using a response block:: .. response:: Ponies!!1! ..The testing process is simple: each request is executed using the client defined in the fixtures module, and each expected response following that request in the text is compared against the actual response. If all responses match, the test passes. Otherwise, it fails. Passing examples are given a pleasing green background, failures a sinister red. Details of the failed match are included following the failed example. Fixture commandsAt times it may be necessary to execute a unique fixture before executing a request. While it's usually better to make the test depend only on public apis and not internal details or externalities, sometimes (e.g. when testing time-dependent operations) that isn't possible or reasonable. For those times, use the :setup: argument to the request. The body of the exec argument will be evaluated in the context of the fixture module before running the request. Naturally, there is also a :teardown: argument, which will be executed after the request is run and the response processed. Here's an example: .. request:: Get something special :setup: client.set_special(true) :teardown: client.set_special(false) GET /special .. Shell examplesTrestle also supports shell examples. When a shell example is executed, the shell command given is executed, and the stdout produced by the command is compared to the body of the `..shell` example using the normal doctest output checker. A simple shell example looks like this: .. shell :: echo "Hello" Hello ..Trestle is most useful in writing testable documentation for ReST services. [Less]

rstsuite wraps docutils' rst2html converter and adds tools like for instance an index-generator.

English Translation reStructuredText を HTML として表示するためのビューアーです。 実行には python, docutils, wxpython が必要です。 .exe ... [More] ファイルはソースに含まれていませんが、ビルドスクリプトを実行すれば .exe を作成できます。ビルドを行うには bbfreeze が必要です。 current source: http://restructuredtext-viewer.googlecode.com/svn/trunk/rst_viewer.py [Less]

Convert a collection of restructured text files into a Qt Help file and (optional) a Qt Help Project file. Just so you get an idea what the output and the input look like:

A blogging application built on Eclipse. For anyone whose ever thought: man, I wish I could keep my blog under version control seriously, I should write this stuff using rst.