I would prefer that the default activity code had a structure similar to this:
...
...
#Region VIEWS' EVENTS
#End Region
#Region METHODS
#Region PUBLIC METHODS
#End Region
#Region PRIVATE METHODS
#End Region
#End Region
#Region OTHER EVENTS
#End Region
and that the event routine created by Designer was placed after the last routine in the VIEWS' EVENTS Region
(This is not a my wish; I'm saying that yours,
@ilan, is very personal, according to your "tastes".
Also, my example is more similar to the structure that I give to my classes, because an activity does not have real public methods, even if they can be called via callsubdelayed)