Should we deprecate autoload.php and do some code organization?

[F21]

Should we deprecate autoload.php and make invoking the autoloader directly the preferred approach?

Another approach would be to move autoload.php into the ArangoDB folder.

What do you guys think about moving the different PHP files into folders? For example, all the graph stuff in one folder etc.

This would break backwards compatibility though because the namespace will need to change to comply with psr-0 standards.

Let me know what you guys think :)

[frankmayer]

Hi @F21, I think, we should address both of these questions after the split (core/higher level). However this might take a bit more, as I am caught up right now. Let us just keep this open and revisit, ok? Sidenote on autoload.php: This is something that I am not quiet sure about having deprecated/removed.

[F21]

Looking forward to the split :) Is there a timeline as to when that will be done? I will also try and close #32 today.

Regarding autoload.php: Maybe we can move it so that it lives with all the other files in the library instead of being in the root of the project. This makes things more coherent. Perhaps we can rename it to something that will not be confused with autoloader.php. Maybe something like arangodb_required.php or arangodb_init.php or arangodb_register.php. This will of course, break backwards compatibility though.