Complaint number one by developers using FLOW3 – and that includes the core team – has been the compilation speed in a development context. There are times FLOW3 needs to flush all code caches which can result in several seconds of waiting time on the next hit, when the proxy classes are rebuilt. In order to tackle this, we scheduled a whole week for a code sprint in Lübeck.
The proxy building routines are one of the oldest parts of FLOW3 and although we revised the actual compiler routines some time ago, the logic for matching classes and methods for the Aspect-Oriented Programming support has remained unchanged. Andreas Förthner, Christopher Hlubek and myself discussed ways to optimize the matching and during the past week Andi refined the concept and turned it into code.
We always hoped that our approach would speed up compilation time, but we didn't expect the big performance boost we eventually reached. Now, in turns of numbers that is … well, we keep the actual numbers as a little surprise for the first FLOW3 conference, but you'll certainly like it!
Christian Müller also joined us here in Lübeck and did a great job going through all pending issues, checking if they are still valid, asking questions to the reporters and solved various tickets right away. Christian really is our good soul when it comes to community support, there's hardly a day or night time you don't spot him in our IRC channel.
We seem to have most of the code done for a FLOW3 1.1 release, except the new HTTP support which is still in the making. Nevertheless, you may expect a 1.1 release during the next weeks, including a few neat surprises. We could also fix the few failing tests which gave Smilla reason to cry so desperately (see picture).
What are you looking forward to for future FLOW3 releases, what would delight you most?
Schaufi | 08.05.2012
Hey Robert,
can you please share some insights what kind of code made such a big improvement? Something like: before code and after code would be really nice.
Robert Lemke | 30.03.2012
Thanks for your feedback. I agree – documentation is the next number one feature of FLOW3. We'll get there ;-)
Franz Kugelmann | 27.03.2012
Great Job Guys!
Looking forward to see you in Rosenheim next weekend.
+1 for channel security (switch to ssl) and IP Patterns
phil | 27.03.2012
Flow3 looks really interesting but first steps are really complicate. You all make a ver good job - but please don't forget the world outside:
+1 for doku
+1 for supporting extbase/fluid team
Martin | 26.03.2012
my company rejected flow3 on the ground of too many "to be written"'s on the documentation and because of a small community. there are many developers (including me) who would love to be more active in the community and are willing to help others, but who need some starting help. there are too many gaps in the documentation at the moment and too many really important parts are missing.
so, i second the "please update the guide".
Jacob Floyd | 24.03.2012
HTTP is still in the works. I'd like to see what's done, but I can't find any development copies on github, git.typo3.org, or gerrit.
Even though it's incomplete can you publish your HTTP work somewhere?
Marco | 23.03.2012
Totally agree, great job guys, and yes, please, a complete comprehensive guide with lots and lots of quality code examples and screencasts !!
No good creating the world's best framework if only 15 people understand how to use it ;-)
chp | 22.03.2012
Great job. My feature request is an up2date and complete guide on the website.
Zach Davis | 22.03.2012
I've been watching the results of this code sprint with great interest. Indeed, the development compilation speed was our biggest complaint on our recent FLOW3 project.
Really looking forward to 1.1!
Michael | 22.03.2012
I'd like to debug the actual code in FLOW3 DEV context, not the generated proxy classes.
This would make developing and xdebugging in IDEs so much more intuitive.