The all point about Gluon is that it is finished in the sense that it
has a minum set of API there were stable since day one and I will
guarentee backward compatibility for future versions. There will be
bug fixes (assuming bugs are found) and there may be new features (if
users request them) but the basic API will not change. The admin
interface may change because use are encouraged to design a better
one. The present one works fine for me and it is very scalable.
Gluon was developed because both Django and Pylons have API that
change amost weekly and that is not acceptable.
About the use of pass for closing blocks. This is a convention used by
Python programmers who use emacs. In fact pass in Python is a command
that does nothing and therefore it is assumed to indicate the end of a
block. Emacs and Gluon automatically indent the code using similar
algorithms.
The generation of html in controllers is not a good idea but there are
occasions when it is unavoidable. Gluon provides helpers for those
rare situations but encourages users to put html in the models.
