!!! THIS LIST IS FINALIZED BY FRIDAY !!! * Title * Short abstract (As much as you need to describe it roughly) * How many slots you think you'll need? (1 slot: 3,5 hours) * Do you need a projector? * What is the maximum number of attendees? * Your name * A photo of you TUTORIAL: People will learn something WORKSHOP: We want some result in the end -> Target Group -> Number of possible attendees General Idea: Lend towards TYPO3 Phoenix ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ **[READY FOR HAND-IN|** - Fluid and TypoScript harmony: The new rendering concept of TYPO3 Phoenix (Tutorial) (Christopher, Sebastian) [Phoenix] -> “Tutorial” to build and adjust Phoenix website rendering; should be quite in the beginning of the DevDays * - 1 Slot * - projector: yes * - max number of attendees: open * TypoScript and Fluid are both core concepts of TYPO3 Phoenix, being available for rendering content. However, until now, it was unclear how TypoScript and Fluid can play well together. In the last months, we have analyzed Fluid, TypoScript (both in v4 and Phoenix) and lots of other approaches such as CSS, XPath or jQuery in great detail, discussing the pros and cons of each approach. After this in-depth analysis, we were able to distill the core concepts of TypoScript, and developed a new way of collaboration between TypoScript and Fluid. This is what we will present in this tutorial: The new TypoScript. Starting from simple examples, you will learn step-by-step how advanced examples can be implemented. You will see the power of Eel, an expression language for FLOW3, and FlowQuery, a mechanism for selecting nodes. Furthermore, we'll see how you can use TypoScript to build any kind of extensible FLOW3 application, not being limited to the content management domain. This workshop will be in the style of a tutorial. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ **[READY FOR HAND-IN]** - Build your first Phoenix website (Christian, Markus), [Phoenix] * -> should be after "Fluid and TypoScript Harmony" talk * -> Tutorial * A first version of Phoenix will be released this year so we want to show how you build your website with Phoenix and let the participants of this workshop build their own Phoenix website, so bring your own template. * We will go over building a site package for your page, how to setup your (fluid) page templates, the Typoscript and finally also the Sites.xml with which you can import content right away. The result of this workshop should be that participants have an idea on how building a Phoenix website will work and be able to do it themselves. Maybe this also opens up possibilities helping in Phoenix development * * This workshop will be in the style of a tutorial. * * - a clean clone of the TYPO3 Phoenix base distribution is necessary * - 1 Slot * - projector: yes * - max number of attendees: 15-20 * ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ **[READY FOR HAND-IN]** - EmberJS Tutorial (Rens, Markus) [Phoenix] * -> Tutorial * * At the Developer Days in July 2011 the phoenix team decided to develop the Phoenix Backend by using some other technologies than the ExtJS JavaScript framework. This other JavaScript Framework is called Ember (\url{http://emberjs.com/)} which was formerly known as SproutCore (\url{http://yehudakatz.com/2011/12/12/amber-js-formerly-sproutcore-2-0-is-now-ember-js/)}. * Ember is built on jQuery which delivers a reduced feature set: It only allows to connect the user interface to a data model and adjusts the user interface when the model changes. This "data binding" enables to build very loosely-coupled, interactive applications, and makes composition of components very easy and understandable. As there is no need for complex event handling code anymore, complex features can be implemented in less time. * * The tutorial is an introduction into EmberJS and its history and will show how it is used for the Phoenix Development. In the end we’ll try to let you make your hands dirty with Phoenix Development. * * - 1 Slot * - projector: yes * - max number of attendees: 15-20 * - Rens Admiraal, Markus Goldbeck ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ **[READY FOR HAND-IN]** - Extension / Package Builder UI Development based on EmberJS (Rens) [FLOW3 / v4 / Extbase \& Fluid] * -> should be after EmberJS tutorial * -> Workshop * On T3DD10 we started thinking about a new interface for the Extension Builder, since then most of the progress on the Extension Builder has been made on the roundtripping part. Recent plans and development on the Extension Builder are to use the same user interface for a FLOW3 Package Builder as we have for the Extension Builder. * * This workshop will be about the current state of the Extension Builder, but also about the technical challenges we face during development of the Package / Extension Builder interface (based on EmberJS). * * The goal is to get more people on the team and get the stalled development of the rich user interface up to speed again. * - Workshop * - 1 Slot * - projector: yes * - max number of attendees: 15-20 * - Rens Admiraal, Nico de Haen ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ **[READY FOR HAND-IN]** - The Form Project (Bastian) [FLOW3] -> mostly Tutorial, maybe a bit of Workshop at the end -> first: tutorial about secret Form Framework (open source by then) -> integrate it in Phoenix (“TCEFORMS Milennium Edition”) - start prototype * Gain an insight into the new Form Framework that will be released as FLOW3 Package just before T3DD12. With the flexible Form API it will be easier than ever before to create web forms, attach custom validation rules and configure so called Finishers that allow you to save the submitted data in a database or send it via email. With the Graphical User Interface aka "Form Builder" you can even create complex forms in just a few clicks. After the tutorial session we'll glance at the not-so-far future of "TCEforms reloaded" - the integration of the Form API into TYPO3 Phoenix. - Track: FLOW3 - Tutorial / Workshop - 1 Slot - projector: yes - max number of attendees: open - Bastian Waidelich ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ **[READY FOR HAND-IN]** - TYPO3 Phoenix Key Concepts [Phoenix] Presentation and discussion of the key feature set and foundational concepts for Phoenix. The workshop starts with an overview of the status quo, which features have been implemented, which have been planned for this year and the long term goals. Afterwards we'll discuss the priorities, technical implications and next steps to take. The goal is to get a clear idea for everybody inside and outside the team of where we stand and what the next steps are. If you play with the idea of joining or supporting the Phoenix team, this is the workshop to get you in touch with the team and recent development. - Track: TYPO3 - Workshop - 1 Slot - projector: yes - max number of attendees: open - Robert Lemke -> everybody from the Phoenix/FLOW3 team: Please join :) ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ **[READY FOR HAND-IN][!!! extremely important to us]** - Developing the TYPO3 Phoenix Backend Concept (Berit, Aske, Sebastian) [Phoenix] -> Workshop -> what modules do we need? -> how do they basically work? (pagetree, general structure, …) -> everybody from the Phoenix/FLOW3 team: Please join :) -> should be AFTER "TYPO3 Phoenix Key Concepts" * Workshop * 2 Slots * projector: yes * max number of attendees: 20-25 So far, development of the TYPO3 Phoenix User Interface has been focussed on the content editing part. In the last months, we have started creating the technical foundations for the other modules: Management, Layout, Reports and System. During this workshop we want to create a concept for the other modules, mainly the Management View of TYPO3 Phoenix. After a short introduction to the basic ideas and an insight into our personas and the already planned modules we will extend the existing use cases and bring them to life. Based on those we want to split up into smaller groups and create an overall concept for the management view itself as well as detail concepts for every module. Which elements will be needed? Are there similarities between the different modules? Which needs do the different views have? Our goal is to generate wireframes for each module and extract a general UI concept for the management view. Experience in wireframe creation, for example with OmniGraffle, Balsamiq Mockups or pen/paper would be good. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ **[READY FOR HAND-IN]** - Tutorial: Create a TYPO3 Phoenix plugin [FLOW3] (Karsten, Bastian) * Tutorial * 1 Slot * projector: yes * max number of attendees: open Starting with a barebones TYPO3 Phoenix setup, a new FLOW3 package will be created and made a TYPO3 Phoenix plugin. The tutorial will show how easy it is to transform (almost) any FLOW3 package into a plugin for use in TYPO3 Phoenix. Please have a TYPO3 Phoenix setup running before the tutorial, so we do not have to invest time into the very basics before we can actually start. That means: * a clean clone of the TYPO3 Phoenix base distribution * correct file permissions have been set * a database is set up for use in the tutorial * database migrations have been run ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ **[READY FOR HAND-IN]** * - v4 => Phoenix Content Migration tool (Nicolas Forgerit / Christian) tutorial/workshop It's time to think about content migration from TYPO3v4 to Phoenix. Therefore, last year a Google Summer of Code Project was initiated which was about transforming v4 XML contents to Phoenix ready-to-import data via XSLT. Until the T3DD12 workshop, a prototype will be released which already brings some framework-alike structures, ready for testing on a basic v4-instance. Nonetheless, for covering the major part of all existing TYPO3v4 instances, there is still a lot of thoughts and development to be done. Thus, we are eager to recruit some interested developers and testers to the project for making the huge step forwards to Phoenix as nice and easy as it can possibly be. Therefore, we will introduce the audience to the problem, our general idea of solving it and provide some initial thoughts and directions to invest some work on. If needed, we could also teach some basic XSLT stuff. Generally interested attendees need nothing but themselves, whereas eager developers need a v4 and a Phoenix instance running on their laptop. Bring along some v4 to-be-transferred data with you on which we could chew on together. * 1 slots * workshop * projector: yes * number of attendees: open * Christian Müller/Nicolas Forgerit ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ - Talk: What's new in FLOW3 1.1 (Robert) -- 45 minutes [TODO: write abstract here] ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ - Cleaning up Security Framework (Andi) -> Workshop -> fix the loose ends in security framework [TODO: write abstract here] ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------