Clean old & unuseful files about phpexcel HOT 16 CLOSED

@MarkBaker Is it possible to not include help for JAMA ?

from phpexcel.

The old files can go, Documentation/assets may contain some that we want to keep (basically architectural schemas)

from phpexcel.

@maartenba But with PHPDoc, normally, we have a class hierarchy (like that : http://demo.phpdoc.org/Responsive/graph_class.html) which can replace that ?

from phpexcel.

Indeed. In that case, I think it's safe to remove those files

from phpexcel.

The assets images appear in the documentation and are a lot easier to read because they show just the few relevant elements from the phpdoc mapping, in the context of the documentation. As such, I think they should remain.

from phpexcel.

@MarkBaker : Are they uptodate ?

from phpexcel.

The ones I'm looking at are up to date, though they may not all be.... I'll check later. Most are simply xml files, or images created from those xml files.
It might be an idea to switch them to a different (more generic) format like GraphViz which would make them easier to edit.

from phpexcel.

In the directory, we can include a phpdoc of PHPExcel correctly generated with graphviz (the render is perfect, i try it this morning)

OR

We can create a branch (or a repo) dedicated to the doc (including Users documentation and PHPDoc for developpers) which permit to answer in part to the bug GH-#1

from phpexcel.

@MarkBaker In this zip (http://dl.free.fr/vqf8kX2if), there is the generation of PHPExcel's documentation with PHPDoc.

You can see the generated graphviz.

from phpexcel.

@MarkBaker Another idea : I create GitHub Pages for managing pages for PHPExcel (GH #17) which create a branch gh-pages... and in a directory of this branch, we store a generation of PHPExcel documenation with PHPDoc...

This permits developers to see it online easily and solve in part the GH #1

from phpexcel.

With commits f2803e8 and 9907ef9, @MarkBaker has cleaned JAMA.

from phpexcel.

Could we move documentation in phpoffice.github.com repo ?

from phpexcel.

@MarkBaker & @maartenba : What do you think about putting documentation in a dedicated branch, or a dedicated repo ? And why not in repo https://github.com/PHPOffice/phpoffice.github.com which manages http://phpoffice.github.com/ ?

from phpexcel.

Sounds good

from phpexcel.

@maartenba for which one ? 😜

from phpexcel.

Both :-)

from phpexcel.