bahtiar: /* Relevant howto's */

2010-01-10T08:43:41Z

Relevant howto's

← Older revision		Revision as of 08:43, 10 January 2010
Line 33:		Line 33:
	* [[Ordering attributes within a node]]		* [[Ordering attributes within a node]]
	* [[Displaying content on left, right and top section of node view/edit]]		* [[Displaying content on left, right and top section of node view/edit]]

			== Relevant documentation ==

			* [[Hollywood Calls]]

	== Criticism ==		== Criticism ==

	One of the critiques of the current implementation of the atkNode is that business logic (AF_OBLIGATORY, overrides etc.) and view parameters (AF_SEARCHABLE, AF_HIDE_EDIT etc.) are mixed. The rationale behind this is that a node not only defines the data structure and business logic, but also the way it should be handled in a CRUD environment. Since this is ATK's focus, this is relatively OK. There are some thoughts about [[Splitting view and business logic]] even more, but the disadvantage would be that in many cases, this would lead to extra code, which would be in conflict with the [[Code minimization philosophy]].		One of the critiques of the current implementation of the atkNode is that business logic (AF_OBLIGATORY, overrides etc.) and view parameters (AF_SEARCHABLE, AF_HIDE_EDIT etc.) are mixed. The rationale behind this is that a node not only defines the data structure and business logic, but also the way it should be handled in a CRUD environment. Since this is ATK's focus, this is relatively OK. There are some thoughts about [[Splitting view and business logic]] even more, but the disadvantage would be that in many cases, this would lead to extra code, which would be in conflict with the [[Code minimization philosophy]].

bahtiar: New page: {{class|atk}} == Description == The atkNode class is the single most important class in the ATK framework. A 'node' can be considered an 'entity' or a representation of a database table....

2008-09-01T23:02:47Z

New page: {{class|atk}} == Description == The atkNode class is the single most important class in the ATK framework. A 'node' can be considered an 'entity' or a representation of a database table....

New page

{{class|atk}}

== Description ==

The atkNode class is the single most important class in the ATK framework. A 'node' can be considered an 'entity' or a representation of a database table. Developing applications in ATK means developing nodes, which are classes that are derived from atkNode.

== Examples ==

Here is an example of a typical node:

<syntaxhighlight lang="php">
class employee extends atkNode
{
function __construct()
{
parent::__construct("employee");

$this->add(new atkAttribute("id", AF_AUTOKEY));
$this->add(new atkAttribute("name", AF_SEARCHABLE));

$this->setTable("employee");
}
}
</syntaxhighlight>

== Relevant howto's ==

* [[Custom (record) actions]]
* [[Using modifiers]]
* [[Including modifiers when extending nodes]]
* [[Use a workflow on a node]]
* [[Increase performance on nodes with millions of records]]
* [[Ordering attributes within a node]]
* [[Displaying content on left, right and top section of node view/edit]]

== Criticism ==

One of the critiques of the current implementation of the atkNode is that business logic (AF_OBLIGATORY, overrides etc.) and view parameters (AF_SEARCHABLE, AF_HIDE_EDIT etc.) are mixed. The rationale behind this is that a node not only defines the data structure and business logic, but also the way it should be handled in a CRUD environment. Since this is ATK's focus, this is relatively OK. There are some thoughts about [[Splitting view and business logic]] even more, but the disadvantage would be that in many cases, this would lead to extra code, which would be in conflict with the [[Code minimization philosophy]].

AtkNode - Revision history

bahtiar: /* Relevant howto's */

bahtiar: New page: {{class|atk}} == Description == The atkNode class is the single most important class in the ATK framework. A 'node' can be considered an 'entity' or a representation of a database table....