As a consequence from our own experience with using FLOW3 and due to your feedback, the core has undergone some heavy refactoring. The persistence framework is now fully self-contained and works without the TYPO3 Content Repository. A few hundred class names have been renamed to enforce more consistent naming conventions. And finally the resource management has been completely reworked and now provides an easy way to upload, import and publish resources.
Persistence
In FLOW3, objects which are supposed to be persistent are managed by the "Persistence" sub package which on his part uses the TYPO3 Content Repository as a storage backend (which in turn stores objects in a database). This seemed to make sense in the beginning, as the content repository is tailored to handling nested objects as we usually find them in FLOW3 applications.
Stupidly enough this setting kept us from using the CR for what we originally intended it to use: for managing content in TYPO3 5.0. Because if TYPO3 had used the CR's API directly, it would have circumvented FLOW3's persistence mechanism. Furthermore storing regular objects of an average FLOW3 application was probably breaking a butterfly on a wheel. After some careful analysis we came to the conclusion that we better turn persistence upside down: The Content Repository should use FLOW3's persistence framework to store its nodes and not the other way round.
So Karsten refactored the persistence related codeparts so that FLOW3 now works completely independently from the TYPO3CR package. During the profiling sessions for the next version we expect to tease out a significant performance boost – which you'll surely appreciate.
Resources
The resource management of FLOW3 has been completely reworked for this release because we consider it an important aspect of the framework, especially in regard of the planned media and other asset capabilities of TYPO3 5.0.
Files or other data being imported or generated by FLOW3 are now automatically available as resource objects and benefit from FLOW3's advanced object management. From a developers perspective handling a file upload is therefore as easy as handling any other submission of data: most of it is taken care of transparently by FLOW3.
Publishing resources is equally simple and yet powerful: all resources used in Fluid templates are published automatically to the web folder. For more sophisticated applications FLOW3's resource manager is prepared to deliver files to content delivery networks or restrict access to certain resources in defined scenarios. While these features are not fully implemented yet, they have been considered in the design of the new mechanisms. As a bonus, the default resource publisher support SEO friendly URLs.
These new features are all documented in the new Resource Management section of FLOW3's manual.
Upgrading
Aside from the various minor improvements and bugfixes we have also changed a few hundred class names to make the naming more consistent and intuitive. These vast changes require adjustments in existing FLOW3.
However, we guessed that none of you is keen on searching and replacing hundreds of class names. Therefore we provide you with a migration script for the renaming of classes as well as migrating your existing data to the new persistence framework. It's all a matter of typing these two lines at the command line:
./flow3 migrate classnames
./flow3 migrate persistence
For further upgrading instructions please refer to the changelog
Next Version
The focus for the next release is on important features for the security framework and speed / stability improvements for persistence.
FLOW3 1.0.0 alpha 8 will be released on March 1st.
Source From: flow3.typo3.org
Persistence
In FLOW3, objects which are supposed to be persistent are managed by the "Persistence" sub package which on his part uses the TYPO3 Content Repository as a storage backend (which in turn stores objects in a database). This seemed to make sense in the beginning, as the content repository is tailored to handling nested objects as we usually find them in FLOW3 applications.Stupidly enough this setting kept us from using the CR for what we originally intended it to use: for managing content in TYPO3 5.0. Because if TYPO3 had used the CR's API directly, it would have circumvented FLOW3's persistence mechanism. Furthermore storing regular objects of an average FLOW3 application was probably breaking a butterfly on a wheel. After some careful analysis we came to the conclusion that we better turn persistence upside down: The Content Repository should use FLOW3's persistence framework to store its nodes and not the other way round.
So Karsten refactored the persistence related codeparts so that FLOW3 now works completely independently from the TYPO3CR package. During the profiling sessions for the next version we expect to tease out a significant performance boost – which you'll surely appreciate.
Resources
The resource management of FLOW3 has been completely reworked for this release because we consider it an important aspect of the framework, especially in regard of the planned media and other asset capabilities of TYPO3 5.0.Files or other data being imported or generated by FLOW3 are now automatically available as resource objects and benefit from FLOW3's advanced object management. From a developers perspective handling a file upload is therefore as easy as handling any other submission of data: most of it is taken care of transparently by FLOW3.
Publishing resources is equally simple and yet powerful: all resources used in Fluid templates are published automatically to the web folder. For more sophisticated applications FLOW3's resource manager is prepared to deliver files to content delivery networks or restrict access to certain resources in defined scenarios. While these features are not fully implemented yet, they have been considered in the design of the new mechanisms. As a bonus, the default resource publisher support SEO friendly URLs.
These new features are all documented in the new Resource Management section of FLOW3's manual.
Upgrading
Aside from the various minor improvements and bugfixes we have also changed a few hundred class names to make the naming more consistent and intuitive. These vast changes require adjustments in existing FLOW3.
However, we guessed that none of you is keen on searching and replacing hundreds of class names. Therefore we provide you with a migration script for the renaming of classes as well as migrating your existing data to the new persistence framework. It's all a matter of typing these two lines at the command line:
./flow3 migrate classnames
./flow3 migrate persistence
For further upgrading instructions please refer to the changelog
Next Version
The focus for the next release is on important features for the security framework and speed / stability improvements for persistence.
FLOW3 1.0.0 alpha 8 will be released on March 1st.
Source From: flow3.typo3.org
No comments:
Post a Comment