Architecture
The architecture of phpSitemapNG is designed for a heavy usage of plugins.
The main code is just dumb code that displays and runs plugins at a specified time. :)
At the moment there is a main class PhpSitemapNG that handles the user input and control flow in a kind of state modell (not really, just a very simple kind of), a class called Gui that deals with the output and does some of the logic functions.
The settings are handled by special class Settings that behaves like a registry ( get and set values with the functions getValue and setValue) - this information will be stored into a session and also in a file.
For storing of the urls there is at the moment only a session based storage class available (called StorageSession) but there is no way to store urls onto the filesystem or into a database. But there will be soon. :)
The plugins are setup and handled by the PluginHandler class - this searches for available plugins and returns instances of them.
Available plugins are the Crawler and the Filesystem classes that have been used in the stable version of phpSitemapNG as input plugins and a simple output plugin called GoogleSitemaps that creates Google Sitemaps files (but no Sitemaps index files yet) with the GsgXml class.
If you would like to add some functionality to phpSitemapNG you should read the plugin section.
Do you have some questions or do you need more information - please post at the forum at the developers corner.
The main code is just dumb code that displays and runs plugins at a specified time. :)
At the moment there is a main class PhpSitemapNG that handles the user input and control flow in a kind of state modell (not really, just a very simple kind of), a class called Gui that deals with the output and does some of the logic functions.
The settings are handled by special class Settings that behaves like a registry ( get and set values with the functions getValue and setValue) - this information will be stored into a session and also in a file.
For storing of the urls there is at the moment only a session based storage class available (called StorageSession) but there is no way to store urls onto the filesystem or into a database. But there will be soon. :)
The plugins are setup and handled by the PluginHandler class - this searches for available plugins and returns instances of them.
Available plugins are the Crawler and the Filesystem classes that have been used in the stable version of phpSitemapNG as input plugins and a simple output plugin called GoogleSitemaps that creates Google Sitemaps files (but no Sitemaps index files yet) with the GsgXml class.
If you would like to add some functionality to phpSitemapNG you should read the plugin section.
Do you have some questions or do you need more information - please post at the forum at the developers corner.
