August 2009
5 posts
Get me a standard agavi project, the fast way
More often than not I want to create a new agavi project the “standard” way, that is:
Change the projects name
Change the projects prefix
Use the defaults for all other options
Calling agavi project-wizard makes me answer all questions, one by one. Sure, pressing enter at every prompt works, but I value my time too much to press enter at every prompt. I’d rather go write a...
Third Agavi Article on IBM developerWorks
The third article in the series on Agavi over at IBM developerWorks has just been published.
This part focuses on creating an administration interface and on securing it. Go read it, rate it, blog about it and once again spread the word!
Finally, nightly documentation builds
Finally a nightly pdf build of the agavi guide is available. It’s based on trunk and can be downloaded from http://www.agavi.org/documentation-nightly-pdf.tar.gz. The tarball contains the pdf version of the guide and all stage tarballs.
The current build scheme is very simple and the file is replaced every night. The location may change if and when we decide to keep older versions of the...
Using your own build templates from second zero
Some tasks are nice to have around in each and every project, such as the JSLint task I wrote about earlier today. However, we still don’t want that in each and every project - where’s the point in having a js-lint in a project that does not use any javascript at all like a pure service oriented project without any html output? So we don’t want that task in the core agavi build...
Extending the build system - integrating JSLLint
Javascript errors are annoying and notoriously hard to track down due to limited IDE support and misleading error messages in browsers, but often it’s only a missing comma or a bracket in the wrong place. A linter helps by checking that your javascript is a least structurally sound. It’s the first check I run on any javascript that does not work, so having it right at my fingertips is...