[TYPO3-50-general] Typo3 Phoenix Page categorization: extending Node and Aloha editor

[Dmitri Pisarev]

Hey I just wanted to bump my previous post.

As for the practical implementation, I decided to write a plugin for 
Phoenix with its own simple model, and not mess with typo3cr. But the 
question about content model and future of typo3cr I asked still puzzles 
me a lot.

Thanks!
Dmitri.

On 13.06.2011 16:47, Dmitri Pisarev wrote:
> Hey Sebastian,
> thanks a lot for the reply!
>
> I'm totally aware that t3Phoenix is miles away from being even alpha,
> but I still want to use this simple project to get into concepts of
> Phoenix. So I'm not afraid of things being dangerous or difficult:)
>
> I started digging into the idea of TYPO3CR and it has totally blown me
> away! However I have a million of questions) For example, why is there a
> need for contenttype field? Is it not duplicating the idea of
> contentobjectproxy?
> I'm trying to grasp this idea of mapping model objects onto nodes. Do I
> understand correctly, that it's something like thinking about website
> content in terms of DDD? Or not?
> Suppose I create the model from my example (Person, Category objects).
> Then should I just create single and list views in my plugin, put plugin
> instances into some nodes and be done with it? This way it's all clear,
> it's the old approach, which we have always used in TYPO3v4, but content
> model looks really weak this way, as it becomes isolated from domain model.
> Back in the days, the content (pages,tt_content) and plugins(i.e.
> tt_news) was practically the same thing. One could blend these things
> together, extend, render from TS, php plugin and so on. There was no
> confusion, just tables... Now everyone got used to DDD, but here is
> something very different.
> In plain words it's this: persistence level of flow3 seem to overlap
> with typo3cr, and it's not clear what to use and if using both, how
> should they be blended together...
> Sorry for not being able to describe things clearly, but I hope you
> still get my confusion.
>
> And about the practical side of things, if I create my own plugin with
> custom model, will it be hard to allow content editing via typo3 backend?
>
> Are there things to read on this subject?
>
> Regards,
> Dmitri.
>
> But I have some
> On 11.06.2011 19:23, Sebastian Kurfürst wrote:
>> Hey Dmitri,
>>
>> for the time being, I would suggest to write a FLOW3 application for
>> your needs.
>>
>> Phoenix is not yet at a point where it can be safely/easily extended,
>> and while we have some ideas and concepts in this area, it's just not
>> there yet.
>>
>> Greets,
>> Sebastian
>