nette / component-model

⚛ Component model foundation for Nette.

Nette Framework

Nette Framework is a popular tool for PHP web development. It is designed to be as usable and as friendly as possible. It focuses on security and performance and is definitely one of the safest PHP frameworks.

Nette Framework speaks your language and helps you to easily build better websites.

The Quick Start tutorial gives you a first introduction to the framework by creating a simple database driven application.

Over 10 Yrs of Development

We have been developing Nette for over 10 years- and counting! Libraries we provide are therefore highly mature, stable and widely used. They are trusted by a number of global corporations and many significant websites rely on us.

Catching Bronze

We aim to create Nette as a fun and easy to use framework, that programmers can fall in love with. And we seem to be doing it well! We were rated as the 3rd most popular framework in a survey Best PHP Framework for 2015 by a well-know magazine SitePoint.

Security Is a Priority

There is nothing we care about more than security. That is why we had built Nette as the safest PHP framework. It had passed many audits with flying colours, it eliminates safety traps like XSS, CSRF and brings out ground-breaking methods.

Libraries & Framework

Nette consists of a number of handy standalone libraries, which can be used in any codebase, for example combined with WordPress or another framework. Careful, some of them are highly addictive! These are the components that Nette Framework is built on:

• Application – The kernel of web application
• Bootstrap – Bootstrap of your application
• Caching – Cache layer with set of storages
• Component Model – Foundation for component systems
• DI – Dependency Injection Container
• Finder – Find files and directories with an intuitive API
• Database – Database layer
• Forms – Greatly facilitates secure web forms
• Http – Layer for the HTTP request & response
• Latte – Amazing template engine
• Mail – Sending E-mails
• Neon – Loads and dumps NEON format
• Php Generator – PHP code generator
• Robot Loader – The most comfortable autoloading
• Routing – Routing
• Safe Stream – Safe atomic operations with files
• Security – Provides access control system
• Schema – User data validation
• Tester – Enjoyable unit testing in PHP
• Tracy – Debugging tool you will love ♥
• Tokenizer – Source code tokenizer
• Utils – Utilities and Core Classes

component-model's Issues

attached() is called more than once with the same monitored class

When component monitors e.g. interface and monitors its descendant too, the attached() method is called twice with the same monitored object.

Following sandbox branch calls attached() with Presenter twice:

VladaHejda:double-monitoring

IContainer::getComponent() is incompatible with Container::getComponent()

Either IContainer::getComponent() must have @throws annotation or Container::getComponent() must not throw by default (i.e. default value of bool $throw by me false).

Can Container implement IteratorAgregate?

Describe use case:
If i prepare structure of the form by $form->addContainer('foo'); in every template i must use {foreach $form->getComponent('foo')->getComponents() as $key => $input} this help make shorter {foreach $form->getComponent('foo') as $key => $input}, because i never need parameters from getComponents() $deep and $fileter in template.

Implementation is easy.

namespace Nette\ComponentModel;

use Nette;

class Container extends Component implements IContainer, \IteratorAggregate
{

	public function getIterator()
	{
		return $this->getComponents();
	}

}

What do you think?

Container::getComponent() throws exception for already attached components

Because there is a check for component parent presence in https://github.com/nette/component-model/blob/master/src/ComponentModel/Container.php#L142 it's impossible return already created and attached controls.

class MyControl {

protected function createComponentTest() {
  return $this->anotherControlParent->getComponent("Test");
}

If another parent has attached component "test", exception about unknown component "test" is thrown. Throw such exception in this situation is misleading.

Maybe such component don't need to be attached to current parent but getComponent() method can return such component. That component is already attached to another parent doesn't matter.