Overload Classes: Difference between revisions
No edit summary |
|||
| Line 13: | Line 13: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
In your mymodule module, create the node mynode, like this: | In your mymodule module, create the node mynode, like this: | ||
<syntaxhighlight lang="php"> | <syntaxhighlight lang="php"> | ||
atkimport("module.project.project"); | |||
class mynode extends project | class mynode extends project | ||
{ | { | ||
function action_admin() | public function action_admin() | ||
{ | { | ||
echo "Hello World"; | echo "Hello World"; | ||
} | } | ||
} </syntaxhighlight> | } | ||
</syntaxhighlight> | |||
In this example, the project node is replaced by a mynode node, which derives from project, but overrides its action_admin behaviour. | In this example, the project node is replaced by a mynode node, which derives from project, but overrides its action_admin behaviour. | ||
== Conclusion == | == Conclusion == | ||
It's not strictly necessary to derive from the original class, but this ensures that the overloader is compatible with the original. (The code in the application relies on the project node having certain attributes and behaviour, and by deriving from that class, we preserve this as much as possible.) | It's not strictly necessary to derive from the original class, but this ensures that the overloader is compatible with the original. (The code in the application relies on the project node having certain attributes and behaviour, and by deriving from that class, we preserve this as much as possible.) | ||
Revision as of 07:40, 10 February 2010
|
ATK Howto: Overload Classes
|
Intro
An overloader is a way of replacing one of the classes your app normally uses, with one of your own. A plain text example: "Use mymodule.mycustomprojectnode whereever the app normally uses the projects.project node". In other words, it is a way of modifying the app, without touching its code.
Note: This method is for overloading nodes only. for overloading base classes try atkClassLoader().
Example
To create an overloader, put this in your module.inc, near the top of the file (before the module definition):
$overloaders["project.project"] = "mymodule.mynode";
In your mymodule module, create the node mynode, like this:
atkimport("module.project.project");
class mynode extends project
{
public function action_admin()
{
echo "Hello World";
}
}
In this example, the project node is replaced by a mynode node, which derives from project, but overrides its action_admin behaviour.
Conclusion
It's not strictly necessary to derive from the original class, but this ensures that the overloader is compatible with the original. (The code in the application relies on the project node having certain attributes and behaviour, and by deriving from that class, we preserve this as much as possible.)
original from: http://forum.achievo.org/forum/viewtopic.php?t=1764