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

[Jigal van Hemert]

Hi,

On 12-8-2013 12:11, Gabriel Kaufmann | Typoworx wrote:
>> First of all, the extensive use of words like "old", "antique",
>> "dusty", etcetera gives a rather negative vibe. The fact that
>> technology or code wasn't created last week doesn't mean that it isn't
>> usable or maintained.
[...]
> updated, but somehow it's structure is "locked" in a state to maintain
> compatibility that it makes impossible to give it the new kick to
> modernize it.

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.

>> Same reason as 1.; you can use better relationships in your extensions.
> As long as the TYPO3-Kickstarter, TYPO3 Tutorials and Literature is
> introducing the function as it is, it will never be dropped by
> developers! In some cases I also need a feature like that, but I would
> prefer a solution that is modernized in it's backend/storage under the
> hood!

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.

> But I also think it may be possible to find a solution that makes the
> Core have a fallback-option that transparently changes the
> storage-solution. Only some Extensions using direct MySQL may lead to
> incompatibility which could be fixed by an Announcement and introducing
> a Core-function solving this issue.

"Only some extension use direct MySQL"? Most extensions out there use 
SQL queries directly instead of the TYPO3 API :-( (okay, they usually 
use the TYPO3 database class to execute the queries, but in many cases 
not other API functions to retrieve data).

>> Regarding FlexForms...
[...]
> But as you stated: FlexForms are rather the same than native TCA
> (PHP-Array). But why then some features documentated in TCA-Syntax
> simply don't work as expected then?
>
> To give only one banal example I am currently fighting with: FlexForms
> "Select" doesn't support foreign_table_where Markers (###REC_FIELD_[
> fieldname ]###) for a back-relation to the FlexForm-Fields itself!

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.

> ( Refer to: http://forge.typo3.org/issues/50785 )

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.

> But if there is a solution for a problem is provided "on tablet" with a
> patch that could be approved and used, I think those issues could be
> processed prefered as they may improve TYPO3 a lot. I also found
> sometimes really nerve-wracking bugs that I thought I post the bug as
> first-person - but then found out there exists a complete bug-track with
> a patch provided (that even works for us), but the Issue itself is
> sometimes older than one year where nobody takes notice of that!

Attaching patches to issues will not be noticed by many people (only the 
few that "watch" a particular issue). For instructions on how to 
contribute to TYPO3 see:
http://wiki.typo3.org/Contribution_Walkthrough_Tutorials

> For developers like me spending their time on such things, it is also
> frustrating if nobody of the community seems to care about that and the
> work was useless as it is not noticed for newer TYPO3 releases.

You are also part of that community!

> As noticed in my last post... I have eyes on NEOS and hope they don't do
> the same faults they've done on TYPO3 v.4 Extbase and TYPO3 6.x _not
> doing a clean-cut-off_ old paradigms.

Maybe you're a bit confused with all the product names and their relations:

- TYPO3 Neos is the next generation CMS product and built on top of Flow
- TYPO3 Flow is a PHP framework
- TYPO3 CMS is what was previously known as "TYPO3" (which is still used 
as the short name). TYPO3 6.x is *not* a different product than TYPO3 
4.x; we just skipped the version number 5.x because that number was used 
in the past for what is now Neos and it would be confusing for many 
people if the version number was re-used.
- TYPO3 Fluid is the templating engine for Neos and it is also included 
in TYPO3 CMS
- Extbase is a backport of large parts of Flow. The programming 
techniques of Flow can be used in TYPO3 this way. Because of the 
architectural differences

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.

-- 
Jigal van Hemert
TYPO3 CMS Active Contributor

TYPO3 .... inspiring people to share!
Get involved: typo3.org