POG Object Oriented Bug

[Palantar]

Bleh, smaller version after google lost my first post:

It appears that a parent object in POG does not require_once the class
file for any child objects. This can result in runtime errors when
using Delete(true) and probably other functions if the client code has
not already included the child class file. This seems incorrect to
me. Thoughts?

Cheers

[Joel]

True,

However, we don't reference the database class either from any of the
objects. We assume (maybe wrongly) that users will include/auload all
the objects they need when they need it... Arguably, we try to make as
few architectural decisions as possible and leave that up to the
programmer. we just supply the objects.

But you're right, we could add a objects path in the configuration
file (similar to the plugin path) so that we can include objects from
anywhere in the app (since it'll be an absolute path).

I'll soon have some time to make a bunch of requested updates to POG,
so this could be one of them.