The document summarizes new features and future plans for the Joomla Platform. Key points include: - The platform split from the CMS in 2011 and has since expanded database support, added a new slim MVC, and improved error handling and unit testing. - Version 12.1-12.2 added support for PostgreSQL, SQLite, Oracle databases and a database iterator. A new slim MVC using interfaces was introduced. - Future plans include fully implementing exceptions for error handling, isolating packages for individual use, improving testability, and leveraging modern PHP features. More API consumers like JFacebook and JMediawiki are planned.

1. What’s new in the
Joomla Platform?
2012 Edition
By Rouven Weßling

2. Who am I?

3. Who am I?
Active in the JBS since 2009

4. Who am I?
Active in the JBS since 2009
Platform maintainer for about a
year

5. Who am I?
Active in the JBS since 2009
Platform maintainer for about a
year
By pull requests most active
platform contributor

6. I talk really fast...

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

8. History
What’s new?
What’s in it for the future?

9. A brief history

10. A (very) brief history

12. Platform split (or “forked”) in early 2011

13. Platform split (or “forked”) in early 2011
First release (11.1) in July 2011 - mostly rebranded libraries from the CMS

14. Platform split (or “forked”) in early 2011
First release (11.1) in July 2011 - mostly rebranded libraries from the CMS
11.2 released only 3 weeks later

15. Platform split (or “forked”) in early 2011
First release (11.1) in July 2011 - mostly rebranded libraries from the CMS
11.2 released only 3 weeks later
shipped with Joomla! 1.7.0

16. Platform split (or “forked”) in early 2011
First release (11.1) in July 2011 - mostly rebranded libraries from the CMS
11.2 released only 3 weeks later
shipped with Joomla! 1.7.0
Not many big new features - but vastly better documentation.

17. Platform split (or “forked”) in early 2011
First release (11.1) in July 2011 - mostly rebranded libraries from the CMS
11.2 released only 3 weeks later
shipped with Joomla! 1.7.0
Not many big new features - but vastly better documentation.
One notable exception is support for CLI applications

19. 11.3 released in November 2011

20. 11.3 released in November 2011
Support for web applications (JWeb)

21. 11.3 released in November 2011
Support for web applications (JWeb)
HTTP client abstraction (JHttp)

22. 11.3 released in November 2011
Support for web applications (JWeb)
HTTP client abstraction (JHttp)
image manipulation (JImage)

23. 11.3 released in November 2011
Support for web applications (JWeb)
HTTP client abstraction (JHttp)
image manipulation (JImage)
GitHub API (JGitHub)

24. 11.3 released in November 2011
Support for web applications (JWeb)
HTTP client abstraction (JHttp)
image manipulation (JImage)
GitHub API (JGitHub)
Autoloader

27. 11.4 released in January 2012

28. 11.4 released in January 2012
shipped with Joomla! 2.5

29. 11.4 released in January 2012
shipped with Joomla! 2.5
Support for multiple databases

30. 11.4 released in January 2012
shipped with Joomla! 2.5
Support for multiple databases
Only MySQL and Microsoft SQL

31. Award winning
2012 J.O.S.C.A.R. as Innovation of the Year

32. What’s new?
In 12.1 and 12.2

33. Expanded database support

34. Expanded database support
PostgreSQL

35. Expanded database support
PostgreSQL
SQLite (PDO)

36. Expanded database support
PostgreSQL
SQLite (PDO)
Oracle (PDO)

37. Expanded database support
PostgreSQL
SQLite (PDO)
Oracle (PDO)
Previously supported

38. Expanded database support
PostgreSQL
SQLite (PDO)
Oracle (PDO)
Previously supported
MySQL

39. Expanded database support
PostgreSQL
SQLite (PDO)
Oracle (PDO)
Previously supported
MySQL
Microsoft SQL

40. Database iterator

41. Database iterator
Allows you to traverse trough rows 1 by 1

42. Database iterator
Allows you to traverse trough rows 1 by 1
Very efficient for large datasets

43. Database iterator
Allows you to traverse trough rows 1 by 1
Very efficient for large datasets
Even more efficient when you need to abort midway

44. Database iterator
Allows you to traverse trough rows 1 by 1
Very efficient for large datasets
Even more efficient when you need to abort midway
Very inefficient for small datasets

45. Database iterator
Allows you to traverse trough rows 1 by 1
Very efficient for large datasets
Even more efficient when you need to abort midway
Very inefficient for small datasets
JDatabaseDriver::getIterator()

46. New slim MVC

47. New slim MVC
Interface based

48. New slim MVC
Interface based
JController, JModel, JView

49. New slim MVC
Interface based
JController, JModel, JView
Old classes renamed to JControllerLegacy, etc.

50. New slim MVC
Interface based
JController, JModel, JView
Old classes renamed to JControllerLegacy, etc.
Some (very) basic classes (e.g. JModelBase, JModelDatabase) exist

51. New slim MVC
Interface based
JController, JModel, JView
Old classes renamed to JControllerLegacy, etc.
Some (very) basic classes (e.g. JModelBase, JModelDatabase) exist
All other plumbing needs to be done by you (no CRUD)

52. How slim?

53. How slim?
interface JController extends Serializable
{
public function execute();
public function getApplication();
public function getInput();
}

54. How slim?
interface JModel
{
public function getState();
public function setState(JRegistry $state);
}

55. How slim?
interface JView
{
public function escape($output);
public function render();
}

56. Crypt package

57. Crypt package
Successor for JSimplecrypt

58. Crypt package
Successor for JSimplecrypt
Supports more algorithms

59. Crypt package
Successor for JSimplecrypt
Supports more algorithms
3DES

60. Crypt package
Successor for JSimplecrypt
Supports more algorithms
3DES
Blowfish

61. Crypt package
Successor for JSimplecrypt
Supports more algorithms
3DES
Blowfish
Rijndael 256

62. Crypt package
Successor for JSimplecrypt
Supports more algorithms
3DES
Blowfish
Rijndael 256
Based on mycrypt - uses native code.

63. Crypt package

64. Crypt package
A well tested source for random data

65. Crypt package
A well tested source for random data
JCrypt::genRandomBytes

66. Crypt package
A well tested source for random data
JCrypt::genRandomBytes
If possible we tap openssl_random_pseudo_bytes

67. Crypt package
A well tested source for random data
JCrypt::genRandomBytes
If possible we tap openssl_random_pseudo_bytes
If not we gather our own entropy

68. Crypt package
A well tested source for random data
JCrypt::genRandomBytes
If possible we tap openssl_random_pseudo_bytes
If not we gather our own entropy
Based on a research paper that found issues in several PHP application’s
random number generation - including Joomla!

69. Crypt package

70. Crypt package
Interface JCryptPassword

71. Crypt package
Interface JCryptPassword
Implementation JCryptPasswordSimple

72. Crypt package
Interface JCryptPassword
Implementation JCryptPasswordSimple
Supports MD5, PBDKF, Blowfish and “Joomla”

73. Crypt package
Interface JCryptPassword
Implementation JCryptPasswordSimple
Supports MD5, PBDKF, Blowfish and “Joomla”
Allows switching out the password handling library

74. Crypt package
Interface JCryptPassword
Implementation JCryptPasswordSimple
Supports MD5, PBDKF, Blowfish and “Joomla”
Allows switching out the password handling library
for example PHP-PasswordLib

75. Crypt package
Interface JCryptPassword
Implementation JCryptPasswordSimple
Supports MD5, PBDKF, Blowfish and “Joomla”
Allows switching out the password handling library
for example PHP-PasswordLib
Not yet used by JUser

76. Composer support

77. Composer support
Dependency management for
PHP

78. Composer support
Dependency management for
PHP
Allows for far easier integration of
the platform into other projects

79. Composer support
Dependency management for
PHP
Allows for far easier integration of
the platform into other projects
De facto standard in the PHP
community

80. Composer support
Dependency management for
PHP
Allows for far easier integration of
the platform into other projects
De facto standard in the PHP
community
For more info see http://
getcomposer.org

81. ...and much more

82. ...and much more
File patcher

83. ...and much more
File patcher
String inflecting and normalizing

84. ...and much more
File patcher
String inflecting and normalizing
Stemming

85. ...and much more
File patcher
String inflecting and normalizing
Stemming
new Router

86. What’s in it for the future?

87. Error handling

88. Error handling
JError is already on its way out

89. Error handling
JError is already on its way out
JObject::getError and
JObject::setError are going too

90. Error handling
JError is already on its way out
JObject::getError and
JObject::setError are going too
Exceptions are the future

91. Error handling
JError is already on its way out
JObject::getError and
JObject::setError are going too
Exceptions are the future
throw new Exception(“Ups!”);
throw new RuntimeException(“Ups!”);
throw new LogicException(“Ups!);

92. Package isolation

93. Package isolation
Currently the platform is one big package

94. Package isolation
Currently the platform is one big package
42 subpackages

95. Package isolation
Currently the platform is one big package
42 subpackages
We want to make them available as individual packages using composer

96. Package isolation
Currently the platform is one big package
42 subpackages
We want to make them available as individual packages using composer
Makes it easier for applications to cherry-pick what they need

97. Package isolation

98. Package isolation
We have a pretty good understanding of the dependencies between
subpackages

99. Package isolation
We have a pretty good understanding of the dependencies between
subpackages
There are too many

100. Package isolation
We have a pretty good understanding of the dependencies between
subpackages
There are too many
We want to reduce them as much as feasible

101. Package isolation examples

102. Package isolation examples
DirectoryIterator instead of JFolder::files() and JFolder::folders()

103. Package isolation examples
DirectoryIterator instead of JFolder::files() and JFolder::folders()
Exceptions instead of JError

104. Package isolation examples
DirectoryIterator instead of JFolder::files() and JFolder::folders()
Exceptions instead of JError
Not using per-package exceptions (JDatabaseException,
LogException)

105. Unit testing and being testable

106. Unit testing and being testable
There’s a lot of old code that’s
hard or impossible to isolate for
testing

107. Unit testing and being testable
There’s a lot of old code that’s
hard or impossible to isolate for
testing
JRequest

108. Unit testing and being testable
There’s a lot of old code that’s
hard or impossible to isolate for
testing
JRequest
JError

109. Unit testing and being testable
There’s a lot of old code that’s
hard or impossible to isolate for
testing
JRequest
JError
Replacing these classes with
object oriented replacements

110. Unit testing and being testable
There’s a lot of old code that’s
hard or impossible to isolate for
testing
JRequest
JError
Replacing these classes with
object oriented replacements
JInput

111. Unit testing and being testable
There’s a lot of old code that’s
hard or impossible to isolate for
testing
JRequest
JError
Replacing these classes with
object oriented replacements
JInput
Exception

112. Removing CMS specific code

113. Removing CMS specific code
Moved in 3.0
JEditor
JHelp
JToolbar

114. Removing CMS specific code
Moved in 3.0
JEditor
JHelp
JToolbar
To be moved
JComponentHelper
JModuleHelper

115. Leveraging the power of PHP

116. Leveraging the power of PHP
Removing hacks and workarounds wherever possible (z.B.
JProfiler::getMemory)

117. Leveraging the power of PHP
Removing hacks and workarounds wherever possible (z.B.
JProfiler::getMemory)
Integrating with PHP trough interfaces like Countable, Serizeable,
JsonSeriazeable (PHP 5.4 only) Iterator and IteratorAggregate

118. Leveraging the power of PHP
Removing hacks and workarounds wherever possible (z.B.
JProfiler::getMemory)
Integrating with PHP trough interfaces like Countable, Serizeable,
JsonSeriazeable (PHP 5.4 only) Iterator and IteratorAggregate
Using SPL Exception (RuntimeException,
UnexpectedValueException)

119. Leveraging the power of PHP
Removing hacks and workarounds wherever possible (z.B.
JProfiler::getMemory)
Integrating with PHP trough interfaces like Countable, Serizeable,
JsonSeriazeable (PHP 5.4 only) Iterator and IteratorAggregate
Using SPL Exception (RuntimeException,
UnexpectedValueException)
Leveraging the SPL wherever possible (e.g. DirectoryItertor,
SplPriorityQueue)

120. Example
$var = JRequest::get();
echo count($var);
$input = new JInput;
echo = count($input);

121. More API consumers

122. More API consumers
JGithub (since 11.3)

123. More API consumers
JGithub (since 11.3)
OAuth client

124. More API consumers
JGithub (since 11.3)
OAuth client
OAuth2 included in 12.3

125. More API consumers
JGithub (since 11.3)
OAuth client
OAuth2 included in 12.3
JGoogle (since 12.3)

126. More API consumers
JGithub (since 11.3)
OAuth client
OAuth2 included in 12.3
JGoogle (since 12.3)
Many more in progress:

127. More API consumers
JGithub (since 11.3)
OAuth client
OAuth2 included in 12.3
JGoogle (since 12.3)
Many more in progress:
JFacebook

128. More API consumers
JGithub (since 11.3)
OAuth client
OAuth2 included in 12.3
JGoogle (since 12.3)
Many more in progress:
JFacebook
JMediawiki

129. New APIs in the future

130. New APIs in the future
JKeychain

131. New APIs in the future
JKeychain
Secure Key-Value-Storage based on JRegistry

132. New APIs in the future
JKeychain
Secure Key-Value-Storage based on JRegistry
New event system

133. New APIs in the future
JKeychain
Secure Key-Value-Storage based on JRegistry
New event system
Unified Content Model

134. PSR

135. PSR
PSR-2 support is almost complete
very few files don’t comply for good reason
the PSR-0 references is ignored
PSR-0 will be reconsidered when we move to namespaces. It’s all but
required for Composer
PSR-1 will not be supported

137. “Another development that force me to
rethink ZF approach is the maturity of
Joomla-Platform itself. Ever since Joomla
decided to split the cms and platform part
of Joomla saperately, we noticed a marked
improvement in the platform code.”
-Azrul, JomSocial

138. Thank you for your attention!
Rouven Weßling
@RouvenWessling
www.rouvenwessling.de
me@rouvenwessling.de

139. Thank you for your attention!
My Workshops tomorrow:
•Building a standalone application on the platform
•Using the new MVC with a platform based web app
Both in Room 150
Rouven Weßling
@RouvenWessling
www.rouvenwessling.de
me@rouvenwessling.de