[TYPO3-mvc] TYPO3-Core complete rebuild to realize modern development paradigms?

[Gabriel Kaufmann | Typoworx]

Hello Jiga,

thanks for your response.


> That's why there is TYPO3 Neos. This will use all the modern 
> programming technology you can dream of without the need to be 
> backwards compatible. 
That sounds great and we will have a look on it and try to convince our 
customers to give that system the same trust that TYPO3 our customers 
beliebe into.

I think that's the common main problem I already discussed with some 
customers/companies.


> In the kickstarter extension you can check the option to create 
> mm-table relations. The TYPO3 documentation documents all 
> possibilities, also the ones using the mm-table features. Even two-way 
> relations are fully supported by the TYPO3 CMS core. 

I think the presence of the old piBase still is the culprit. Of course 
removing this will break some extensions. But in fact TYPO3 6.x still 
breaks a whole bunch of them, but still supports PiBase on the other hand.

I'm glad to hear that NEOS is trying to do the clean-cut I recently 
hoped to find in the 6.x tree.


> In this particular case you regard the configuration of a plugin as 
> the "record". In fact there is no real record and so REC_FIELD_* does 
> not make sense. 
Well just to clear some misunderstandings. Of course I know the 
difference of Plugin and Data-Record.

The TCA clearly implies the usage of type "flex" to be used in records. 
So I don't think this is my missunderstanding and for some more complex 
tasks flexforms are really helpful to have an intuitive usage in 
Data-Records.

> This is a feature (accessing other fields in a flexform). Make your 
> patch for current master and push it to Gerrit. There is still some 
> time before the feature freeze of 6.2. 
I already attached a patch and since your notes regarding the 
instructions on contributing them, I will try my best to help that way.

>
> You are also part of that community! 
I know and I'm already active in a bunch of issues/tasks/patches. I 
don't belong to those one's just taking TYPO3 without giving...


> Maybe you're a bit confused with all the product names and their relations
I don't think I am. But thanks for the explanation ;-)


> Because Neos will use new techniques and new concepts the TYPO3 
> product will focus more on backwards compatibility. This way it is 
> easier to maintain an existing website until people are ready to take 
> the jump to Neos.
> For Neos there will be an effort in the future to make conversion tool 
> that can migrate as much content as possible from TYPO3 CMS sites to 
> TYPO3 Neos. 
Sounds great I think I need to have a closer look into it now. May be I 
can contribute there something useful, too.

I also could imagine that NEOS is the missing link a was missing, 
because I didn't have a closer look yet on it.


Best regards

Gabriel