[TYPO3-GSoC] Re: TYPO3.Boilerplate Status Update

[Jacob Floyd]

Update: 05 June 2013

✔ Studied how the repository+persistence layer works in Flow to see if I can reuse that to treat a folder (like Packages/Application) like a "repository" and make Builders feel more domain-driven...
➜??? I need to figure out how to detach a set of models from the persistence layer in flow so that it uses my own persistence layer (that works w/ files). What is the status on having multiple persistence layers in Flow? It wouldn't make sense to have anything in my model persisted to a DB.
- I can reimplement stuff in the Repository and not extend the Flow Repository+Persistence
- There are a lot of nice features in the Flow Repository stuff that I would love to have
- kdambekalns told me I probably should not use the generic persistence layer
➜ Continue investigating various flow components for inspiration
➜ Investigate Filicious to see if that makes working with the package files feel more flow-ish


ⓘ Please vote on names for Builder[Base/Foundation/Abstract/Commons]:
- http://tricider.com/brainstorming/uqjv
ⓘ Current plans and notes available (newest first):
- http://bit.ly/CBP-Chart-Scope (Charts and what is in-scope for this GSoC here)
- http://bit.ly/CBP-Basics
- http://bit.ly/Design-T3BP
- http://bit.ly/FluidBPProposal
ⓘ I will be working in my namespace, Cognifire, until everything is ready to be pushed to git.typo3.org
ⓘ Follow my GSoC work on github:
- https://github.com/cognifloyd/Cognifire.BuilderBase
- https://github.com/cognifloyd/Cognifire.TemplateBuilder

~~~
Legend:

✔ done
➜ next steps
☠ impediment
ⓘ background info
♫ celebrated