The new Joomla Framework was met with both skepticism and excitement in the community. What is the difference between the Platform and the Framework? Why is it a good idea? And how does this open us up to the wider PHP community? We'd like to give you some answers.

1. What is the Joomla
FrameworkAnd why do we need it?

2. Who am I?
Active in the JBS since 2009
JSST member since 2011
Platform Framework maintainer

3. I talk really fast...
...so stop me whenever you
need to! ;)

4. The Joomla Platform

5. The good
Strong focus on unit testing and continuous
integration
Independent release cycle
More decoupled code
Higher code quality achieved
J!Oscar 2011
Innovation of the Year

6. The bad
Confusing version numbers
Hard to use our great libraries in non Joomla based
apps
All or nothing
Need to maintain a high level of backwards
compatibility

7. The ugly
Huge baggage of CMS specific code
if (class_exists('JError')) {
! return JError::raiseWarning(100, 'Unable to
read archive');
} else {
! throw new RuntimeException('Unable to read
archive');
}

8. So we decided to kill it.

9. So we decided to kill it.kill rename
Why?

10. Change in philosophy
Joomla! Platform Joomla! Framework
Fotos: Rolf Obermaier (PD), Benjamin D. Esham (CC BY-SA

11. allows along availablebreakingchangesclear cmscode
communitycomposercontain currentdevelopers
documentationfolderframeworkfutureincluding
install issue joomlalibrarieslistmailing maintaining
makingname namespacing needs packagephpplan
platformpossible projectprovide ready releaseremoval
repositorysuite system talks team tests upgradeversionwider

12. Namespaces

13. New since PHP 5.3
Can be used to write much more readable code
Better code organization
Very hard to do in a way that’s backwards
compatible

14. <?php
$client = new JApplicationWebClient;

15. <?php
$client = new JoomlaApplicationWebWebClient;

16. <?php
use JoomlaApplicationWebWebClient;
$client = new WebClient;

17. <?php
use JoomlaApplicationWebWebClient as Client;
$client = new Client;

18. PSRs

19. PSR-0: Autoloading
PSR-1: Interoperable code
PSR-3: Logging
PSR-X: Cache
Prepared for future PSRs like Uris
PSRs and the Framework

20. What about PSR-2?
Nope.

21. PSR-0

22. Turns class names into path

23. JoomlaApplicationWebWebClient

24. Joomla/Application/Web/WebClient.php

25. Discrete packages

26. application archive cache
client compat controller crypt
data database date event
filesystem filter form github
google http image input
keychain language log model
oauth2 profiler registry router
session string test uri utilities
view

27. Composer

28. Per-project dependency management
Public repository on packagist.org
Or host your own using Satis
Adopted by Symfony2, Laravel 4, Zend Framework
2, Drupal 8 and many more
Creates an automatic autoloader

29. And the Framework?
Currently 33 packages
+ 1 for the entire framework

30. {
"name": "joomla/tracker",
"description": "Issue Tracking application built on the
Joomla! Framework integrating with GitHub to replace the
existing Joomlacode solution.",
"keywords": ["joomla","tracker"],
"homepage": "https://github.com/joomla/jissues",
"license": "GPL-2.0+",
! "version": "1.0.0-alpha",
"require": {
"php": ">=5.3.10",
"joomla/framework": "dev-master",
"symfony/http-foundation": "2.2.*",
"elkuku/console-progressbar": "1.0",
"twig/twig" : "1.*",
"mustache/mustache" : "2.1.*"
},
"autoload": {
"psr-0": {
"JoomlaTracker": "src/"
}
},
"minimum-stability": "dev"
}

31. Semantic versioning

32. }
Bugfix
}Feature
}
B/C break
1 . 2 . 3

33. Let’s talk community...

34. We not only want to offer our
code to the PHP community...

35. ...we also want to take theirs.

36. Support YAML in Registry thanks to Symfony2’s
YAML
Considering to adopt Symfony2’s Session system
Dropped JMail in favor of using Swift Mailer or
PHPMailer
Monolog will probably be the recommended logger

37. Currently in alpha state
Expected release in Q4 2013
80% done - but the last 20% are the hardest
Need to fully decouple unit test
String package not ready
Need the Cache PSR
How far are we?

38. And the CMS?

39. Used in the Joomla Tracker

40. Discrete packages

41. Interfaces to the rescue

42. Thank You.
@RouvenWessling
www.rouvenwessling.de
me@rouvenwessling.de