[TYPO3-team-core-v5] FLOW3: First code sprint of F3PR

[Christopher Hlubek]

Hi FLOW3 gurus,

we finally made our code sprint for the first F3PR features in FLOW3.

The results can be found in the F3PR Wiki on Forge:
http://forge.typo3.org/wiki/flow3-f3pr/Sprint-0

Can someone have a look at our patch (the last one on the wiki page)?
None of us has SVN commit access so far but we need to commit these
changes to the FLOW3 Package.

The code sprint report http://forge.typo3.org/attachments/445/08.txt
from Thomas mentions the features we have done. Further on it proposes
some changes to the package structure to enable multiple versions of a
package. The key idea is to have the package contents in a folder with
the version number right in the package folder. For example:

Packages
| \- FLOW3
|  | \- activeDistribution
|  |  | \- Classes
|  |   \ - ...
|  | \- activeDevelopment
|  |  |\- Classes
|  |  \ - ...
|  |\- 1.1
|  |  |\- Classes
|  |  |\- ...
|  \ - 1.2
|  |  |\- Classes
|  |  |\- ...

To allow for context dependent activation of packages (could be used
for staging new package versions) we thought about copying the package
contents to a folder with the name of the context. Another idea was to
use a configuration that overrides the active version and to have the
latest package contents in a folder named something like "latest". But
this imposes severe problems for the FLOW3 package. Classes in FLOW3
are used and required before the configuration manager or even the
component manager is available. In some cases the path to the files
are simply hard-coded by now. So we either don't allow context
dependent version switching for FLOW3 and other system packages or use
an approach that doesn't rely on configurations, etc. and simply uses
a special folder structure.

Other opinions are highly appreciated!

BTW: How do we check our code for CGL conformance?

Greetings,

Christopher