Sixth Week

In sixth week, we achieved following goals :


  1. PDF Documentation was generated.
  2. To generate PDF Doc, we generate LATEX files for each source and then run pdflatex on them.
  3. XML Doc was read to get appropriate information for PDF Doc.
  4. Jinja2 library was used to generate template for latex files.
  5. New jinja2 environment was created as default environment clashes with latex syntax.
  6. New jinja2 filter was added to escape special chars present in latex.
  7. The Definition can not be indented in pdf, so used breadcrumbs bar in each definition to show its ancestors in definition tree.
  8. Each folder was also given a pkg.toc.tex file to create a table of contents. It contained bundle info, if any and links to individual source file along with first line of the that source.
  9. PDF Documentation was generated from tex files by combining them using \input in latex. Using this, we create an overall documentation (for complete source tree) and individual folder documentation (for all files in one folder - no subfolders).

Comments

Post a Comment

Popular posts from this blog

Fifth Week

In fifth week, we achieved following goals : Text Documentation was generated. XML Doc was read to get appropriate information for Text Documentation. Jinja2 library was used to generate Template. For Text Documentation, we limited all information display to 150 chars per line. The Definition was indented on basis of their level in the tree. We use textwrap library to heuristically break long sentences along word boundaries. Each folder was also given a pkg.toc.txt file, which contained bundle information and links to all files in that folder. Heuristic signature breaking was designed. The signature for definition was read and broken into return type, name and parameter string. The breaking occured along heuristic : break at first incidence of name in the sign that it not enclosed by brackets and ends in whitespace or '('. Then break at end of the name.
Read more

Tenth Week

In tenth week, we achieved following : Ecldoc installation was determined. We used setup.py from setuptools to generate installation information for the project as python package. Requirements for projects was determined as jinja2 and lxml. All data files in Templates folder was added to setup.py as data files. A single script was added to bin directory to act as entry point for the ecldoc utility. We use pip to perform actual installation (for easy uninstall). We generated a Makefile with 2 targets - install and uninstall. Each target can be run with root permissions to install for all users and local permissions to install for given user only. Documentation was updated with installation info.
Read more