Go to: typo3.com Home TYPO3 Association Home typo3.org Home FLOW3 Bugtracker Forge (Development Platform) News Buzz (TYPO3 Blogs) Support (Mailinglist Archive, Beta) Wiki Mailing lists

Search:

The following list of questions and answers are meant to get an idea about how the 5.0 project is intended to be. Please send us any question which you think should be answered on this page.

NEW - There are more questions answered now about how TYPO3 5.0, FLOW3 and the Content Repository relate to each other. You find them on the FLOW3 site.

Please check our "About" page for more information.

This project has been launched in September 2006 and currently (as of 08.02.2008) most parts of the foundational framework (FLOW3) has been developed. A general roadmap has been defined and according to it we have created the FLOW3 framework, the TYPO3 Content Repository and some other packages.

The best is to check out our development website and the FLOW3 site where we also provide documentation containing coding guidelines and information about the packages.

Due to the iterative nature of our development, we realized that a classic roadmap is not the best way to display the current status. As a rule of thumb you can say that the nearer a milestone on our roadmap is, the more it matches our real plans.

As we learn from our experience with previous releases, we won't publish any binding release dates this time. We surely have goals for milestones internally, but it is not predictable when we publishing these or if they will be kept. TYPO3 5.0 and its parts will be published when they're ready, and we'll keep you updated on the current status.

Well, of course it is not said that after the initial 5.0 release we have to stick to such vague schedule statements ...

Yes, sure! And we even have some proper documentation as well. Just check out the TYPO3 Forge which also contains information about how to access our SVN repository and how you can download our nightly builds.

Sure we did. During the last years there were hundreds of discussions going on in news groups and in the real world which all circled around a next generation TYPO3. We tried to compile these ideas into a new architecture which we think makes TYPO3 a future proof content management framework. Of course we throwed a glance beyond our own nose and checked out other frameworks and technologies. We read lots of clever books and Martin Fowler has become one of our most intimate friends (well, he doesn't know about it, but we like his books at least).

We think that polling web agencies and other stakeholders for their feature list won't result in a different base architecture because typical feature requests are located on a higher level in the system pyramid. And of course we already got this kind of feedback by the TYPO3 users in the past.

Yes'n'no. We decided to take advantage of PHP6 and use some of the new features such as the Unicode support and namespaces. However we realized that we'd have to wait too long for an official release of PHP6 and therefore decided switching back to PHP5 again.

In short: Currently it works with PHP5 (as of 06.12.2007) but we will switch to PHP6 as soon as it makes sense (if that is not a clear statement ;-) )

Although PHP6 has not been released at the time of our decision, it was clear already that the Unicode support is a very important feature we don't want to miss. We never ever want to have character set nightmares anymore.

However, as mentioned above, we have to see through this dark transition phase in which we have to live with PHP5's lack of Unicode support.

JSR-170 is a clever specification defining a general purpose API to access a content repository. However, we will most likely not create a 100% compatible PHP version of this standard, because we will choose a more pragmatic approach.

During the brainstorming phase for 5.0 we asked ourselves how a flexible data source layer should look like and in the end we realized that probably all we need is already defined in the JSR-170 specification. Meanwhile we decided to go for JSR-283, the successor of JSR-170.

We think that a PHP implementation of this Content Repository Standard is an exciting task and an enrichment for the PHP community. You will only need PHP to run TYPO3 5.0 - no need to set up a Java based repository!

No. But it only runs with FLOW3. The plan is to create a PHP Content Repository based on the JSR-283 API which can be used by the whole PHP community. In fact we'd like to invite developers outside the TYPO3 community to join the content repository project.