mittwald-typo3/flow-metamorph

This package is abandoned and no longer maintained. No replacement package was suggested.

Convert TYPO3 CMS extensions to TYPO3 Flow packages

Maintainers

Details

github.com/mittwald/flow-metamorph

Source

Issues

Installs: 34

Dependents: 1

Suggesters: 0

Security: 0

Stars: 6

Watchers: 3

Forks: 1

Open Issues: 1

Type:typo3-flow-package

dev-master 2015-09-24 07:47 UTC

Requires

MIT 60d04e7d7f48a45da3a52a9f1c0dc21e1ec6c39a

This package is auto-updated.

Last update: 2024-03-12 22:45:09 UTC

README

Table of Contents
Caution This package is currently unter heavy development and by no means stable! APIs and behaviour can change at any point without notice.

Synopsis

Metamorph is a tool intended for converting TYPO3 sites into TYPO3 Flow applications and (later) TYPO3 Neos sites.

Installation

Metamorph is a TYPO3 Flow package. Currently, the best way to install it is to use the distribution package, using Composer.

Alternatively, you can require it using composer:

{
    "require": {
        "mittwald-typo3/flow-metamorph": "*"
    }
}

Features (current)

  • Convert Extbase extensions into TYPO3 Flow packages. This includes:

    • Rewriting non-namespaced classes to namespaced classes

    • Replace Extbase classes with their TYPO3 Flow counterparts, where possible and provide compatibility classes otherwise

    • Replace Extbase annotations (like @inject) the respective Flow annotations (like @Flow\Inject), including namespace import.

    • Enrich Extbase domain models with annotations for the Doctrine2 ORM framework.

    • Translate locallang XML files to XLIFF.

    • Create Doctrine migrations for converted entity classes.

    • Option to keep the existing database structure

  • Convert pibase extensions into TYPO3 Flow packages. This includes:

    • Rewriting non-namespaced classes to namespaced classes

Features (planned)

  • More features for Extbase migration:

    • (add custom wishes here)

  • Convert pibase extensions into TYPO3 Flow packages. This includes:

    • Rewrite classes to use TYPO3 Flow APIs where possible, and provice compatibility classes otherwise

    • Generate controller classes wrapping the migrated plugin classes

  • Convert plugins (both Extbase and piBase) into TYPO3 Neos plugins.

  • Convert TYPO3’s page tree into the TYPO3 Neos content repository format

Further reading