Split project structure

[stevensultana]

Calling back #22.

I'd rather call this a proof of concept for a restructuring of the project, than anything else. There are 2 main parts to the PR:

• split the tests into: test_jinja.py, test_master.py, test_page.py, test_shape.py, test_visiofile.py
• split the main file into:
  • __init__.py, containing the namespace definitions
  • connectors.oy, containing the Connect class
  • media.py, containing the Media class
  • pages.py, containing the Page class and PagePosition
  • shapes.py, containing Shape, Cell, DataProperty classes
  • vsdxfile.py, containing VisioFile class and helper functions

There are questions like:

• should each class have its own file, or shall we combine tightly-coupled classes in a single file (eg. Cell, DataProperty and Shape as they are right now)?
• How should tests be split up? For example, should tests related to connectors be in their file? (currently, tests are grouped according to the class to which the tested method belongs)
• Maybe most importantly, how do we break the circular imports, if at all possible? (I guess this ties back to the original scope of the issue of reviewing the API)
  • Currently, the Connect.create() method imports Media to break a circular import situation, and so does Page.set_name() (imports file_to_xml())

Let me know your thoughts, maybe you have a different vision of how things should look like, again this was more of a POC than any definitive suggestion.

[dave-howard]

Hi @stevensultana - I'll take a look and have a think on how we can resolve those circular imports

[dave-howard]

Hello - I've added some thoughts related to this PR against #22