First Week

In first week, we completed following topics :
  1. Modification in HPCC Platform source code to implement :
    • Function like objects Meta information
    • Inheritance Information
    • Information about whether the object is inherited or overriden.
  2. These Modification were used to identify the necessary information for documentation.
  3. Basic Type System Information was developed (but put on shelf for now).
  4. Meta Tree was linked with source code to identify the attribute signature.
  5. Imports were linked with appropriate file.
  6. Attribute fullnames were appended to find actual source (internal or external).

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

Eighth Week

In eighth week, we achieved following goals: Generate Links to any external Documentation for given ecl source tree. For example , if project A has IMPORT B.B1; stmt in some file and we have included path to B Code in eclcc using -I option, that we can also include path to documentation of B which will be linked correctly to any such import stmts in documentation of A. To generate external documentation, each ecldoc run generates a tree.json file for each folder in given ecl source tree. Tree.json files provides paths to each file starting from the folder the json file is in. If the corresponding source path is included in eclcc, we can determine target path using this json file. Example - If input_root below is included in -I option of eclcc, then any imports of keys in tree (example_8, intest, intest.example_11, intest.inintest, intest.inintest.example_2) will be linked correctly to documentation in output_root in each format. { "input_root": "/media/sart
Read more

Ninth Week

In ninth week, we achieved following goals : Generates Documentation for Users in clienttools documentation format. Code Refactoring : Here we reworked the code, so that all output formats are present in separate directories. This will allow easier extension to other formats in future. The only file needed to be modified to add more formats is Formats/generators.py and it will be added to ecldoc. Templates were moved to separate directory which makes it easier to install using setuptools in python. Code was reworked to generate absolute imports rather than relative imports. This makes it easier to move the destination of imports. Code was documented using docstrings and comments wherever required. Technical Documentation was generated to inform overall working of ecldoc code for future.
Read more