documentation-generation

I'm currently creating a phonegap app that lets you input Data and then creates a PDF with that data. The Input is done, but I can't find anything to make a PDF with Javascript. So far I only found jsPDF, but that doesn't support tables. The App must work offline. Does someone have an Idea? Bytescout PDF Generator SDK for Javascript might come in handy: http://bytescout.com/products/developer/pdfgeneratorsdkjs/index.html Ensure that browser inconsistencies for your targeted devices are taken into account. I wanted to use jsPDF to generate tables so I made a table plugin for it. Check it out!

There are existing tools for auto generating API documentation - most of the weren't designed for REST services. For all of you who have created REST services using ServiceStack - how did you write the docs ? Manual / semi-auto / fully auto-gen ? I'm even considering auto gen a customized WADL and connecting it to something like apigee Console To Go (oh and RESTafaries- please spare the 'REST api should be auto discoverable and self-explained' mantra...I really want nice looking docs for my users). Documenting an API through XHTML might provide better results than formatting DTO's. Look at

By the tutorials that I have seen. I learned how to add text on generating a docx file. but then Every time I add a line of text. I noticed that there is always a space between the first line of text and the second line of text. just like hitting the enter key twice. I know that the main cause is that everytime I add a line of text, I use a paragraph. and a paragraph starts with a space after another paragraph. This is how I add a text ObjectFactory factory; factory = Context.getWmlObjectFactory(); WordprocessingMLPackage wordMLPackage = WordprocessingMLPackage.createPackage(); P spc = factory

I just started using Docfx and set up some basic conceptual documentation. Now I want to make some adjustments to the theme (company logo, perhaps some font changes, etc.) Minor stuff. The official documentation only gives a high-level description of how to create a new template. I've never used a templating language before, so I'd like to avoid that for now if possible. My question is: how can I make small adjustments to the default theme, like some CSS changes and perhaps adding external resources (like font awesome)? Do I have to create an entire template (or a part of it) or can I include

I have a C# project in vs2010 that generates a XML documentation file, where I have set the output path of the generated file to the project output path. My problem is that the file does not update when the path to the document file is the same as project output path, and the file names are the same (except for the file extensions). Does not update XML file: C:\MyProjectFolder\MyProject.dll C:\MyProjectFolder\MyProject.xml (documentation file) But when I change either to another folder or change the documentation file name, the file is generated correctly. Does update XML file: C:

In Sphinx, if I have the following heading declaration: .. _somestuff: ``this is code``, this is not! ============================== It renders, like this: this is code , this is not! Which is good, but, if I use the reference, e.g: Have a look at :ref:`somestuff` It loses the code formatting and renders like: Have a look at this is code, this is not! instead of: Have a look at this is code , this is not! Is it possible to retain the code formatting in the reference? And how would I go about it? If you have a look at :ref: documentation in its official web site about inline markups: :ref: To

How can I convert an RTF file to a PDF one? I have the adobe PDF printer, should I use it? If so, how can I programmatically access it? You can use a PDF printer, but then you still have a few problems to solve. In order to handle text that spans multiple pages, you need this article to create a descendant of RichTextbox that handles the EM_FORMATRANGE Message. There are a lot of (free) PDF printer out there, but I found that only BioPdf will let you control the filename of the output. They also have reasonable rates for licensed versions. I have used this to create complex reports

I have written a epytext to reST markup converter, and now I want to convert all the docstrings in my entire library from epytext to reST format. Is there a smart way to read the all the docstrings in a module and write back the replacements? ps: ast module perhaps? Pyment is a tool that can convert Python docstrings and create missing ones skeletons. It can manage Google , Epydoc (javadoc style), Numpydoc , reStructuredText (reST, Sphinx default) docstring formats. It accepts a single file or a folder (exploring also sub-folders). For each file, it will recognize each docstring format and

Closed. This question is off-topic. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it's on-topic for Stack Overflow. Many questions have been posted and answered about REST / HTTP based APIs, etc, but none seem to have much information on the following question: What tools are available/used to document a HTTP-RPC API? Which tools are the best? A Similar question (specific to ASP.NET) from Jan 2009 can be found here , but with no answers. I am in the process of developing several APIs both professionally and for personal projects (.NET