[TYPO3-team-core-v5] Scrum protocol (18.06.10)
Robert Lemke
robert at typo3.org
Fri Jun 18 18:13:35 CEST 2010
Attending: Ben, Robert, Karsten and Bastian
ROBERT:
- worked on the Menu user story
- there won't be HMENU, TMENU etc. anymore, just MENU
- .special will be replaced by individual TypoScript objects such as "Menu", "BreadcrumbMenu", "Sitemap" etc.
- BreadcrumbMenu and Menu is now basically implemented, but only supports 1 level at the time
- the following TypoScript template is used for rendering the demo site:
/**
* Root TypoScript template for the TYPO3 Phoenix Demo Site
*/
page = Page
page.content = Content
page.template.source = 'resource://PhoenixDemoTypo3Org/Private/Templates/Page/Default.html'
# Other parts of the page:
page.parts {
breadcrumbMenu = BreadcrumbMenu
firstLevelMenu = Menu
firstLevelMenu {
firstLevel = 1
lastLevel = 1
}
secondLevelMenu = Menu
secondLevelMenu {
firstLevel = 2
}
}
- a demo for the menus can be seen e.g. on http://latest.phoenix.demo.typo3.org/homepage/secondpage.html
- the PageRoutepartHandler is already in charge of rendering the URLs
- the menus (as well as all other TS objects) is Fluid template based:
http://forge.typo3.org/projects/package-typo3/repository/show/trunk/Resources/Private/TypoScript/Templates
KARSTEN:
- because we needed some better fixtures for testing the menu rendering, Karsten took over the task to create more pages and sub pages
- instead of creating the content through the PHP API in the SetupController we now create the site and pages by importing a newly
created XML format. Here's an example for such a file:
http://forge.typo3.org/projects/package-phoenixdemotypo3org/repository/entry/trunk/Resources/Private/Content/Sites.xml
- the setup controller now supports importing such XML files (just call http://yoursite/typo3/setup)
- later on this import functionality will be used to import whole sites directly from FLOW3 packages
- we'll have to see if importing very big XML files in one chunk is realistic or need to be parsed with an event based XML parser
- Ben asks: "What's the preferred database?"
Karsten: We use MySQL in ANSI mode so that's probably not optimal. Considering its design, SQLite does a surprisingly good job for
small applications. But what's really interesting to see is how NoSQL db such as Cassandra will behave together with the CR approach
of TYPO3 / FLOW3. (http://cassandra.apache.org/)
BASTIAN:
- worked on solving Fluid issues
More information about the TYPO3-team-core-v5
mailing list