The document discusses building an application using only components in Nette Framework. It recommends using events for communication between components and creating custom requests to allow components to link to other parts of the app. Presenters should manage redirects and compose the component views, while keeping components isolated with their own data handling and templates. Building applications this way improves component isolation, testability and styling, though it requires more code than using presenters directly.

1. Independent Components
“Can we build an app only from components?”
Adam Štipák | @new_POPE | adam.stipak@gmail.com

2. Problem?
Using Presenter in Component.

3. Problem?
Using Presenter in Component.
● no point because Presenter is PresenterComponent.
● what is the benefit?
● dont use Presenter but use Events.

4. Wish.
I want build app “only” from Components

5. Wish.
I want build app “only” from Components
without dependency to Presenters

6. No problem! Just use Events.
Use events
or KdybyEvents
class BarPresenter {
protected function createFoo() {
$control = new FooControl;
$control->onSomething[] =
function(FooControl $foo, … ) {
$this->redirect(‘Bar:’);
};
}
}
Best practice tip: http://pla.nette.org/cs/best-practise-formulare-jako-komponenty#toc-ui-control

7. Solved.

8. But no!
The dependency is still there.

9. Dependency is here.
If you are using
{plink Presenter:action}
or
NextrasLinkFactory
->link(‘Presenter:’);
the devil is still here.
FooPresenter
FooComponent
{plink Bar:}
BarPresenter

10. We can wrap it.
class MyRequest
extends NetteApplicationRequest {
function __construct( … ) {
parent::__construct( … );
$this->name = “Presenter”;
//action is in the parameters now :(
$this->action = “action”;
}
}
// in FooComponent only setup request
LinkFactory::link(
MyRequest::setParameters( … )
);
FooPresenter
FooComponent
MyRequest BarPresenter
parameters

11. Components are isolated.
● are isolated
● requests are dependencies
● has own “universe”
○ can create links but only to itself!
● still using events for everything other
○ like redirect after some action (form save and so on)

12. Presenters managing redirects.
● managing redirects
● creating components
● composing views from components

13. Pros
● better component isolation
● better testability
● better styling (preprocessors)
● component factory

14. Cons
● more writing
● not fit for CLI apps (use KdybyConsole)
● component factory (?do=foo-bar)

15. How to write
APP?

16. Everything will be a Component
Bar.default.latte
{control mainMenu}
{control langSelector}
{control login}
{control mainMenu:small}
Bar.default.latte
Home | Project | About | Contact
EN | SK | CZ
Email Password
Log me in
home | project | about | contact

17. 2 types of Component
● Static component
○ templates/components/…
● Dynamic component
○ instance of NetteApplicationUIControl
○ has own Service for:
■ data storage
■ data manipulation
■ listening Events (KdybyEvents)
■ …

18. Summary
● use events for “in app” communication
● use Requests
○ if Component needs to “call” another part of the app
● “Component first access”
○ build app only from Components
● keep Presenters clean
○ only setup components for redirects

19. Thanks
Thanks to SMACSS and AngularJS for the idea
Adam Štipák | @new_POPE | adam.stipak@gmail.com | 2014