<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-15">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hello,<br>
<br>
<tt>we at the Free University Berlin </tt><strong>are holding a
contest, where </strong>top-class teams of three programmers
compete to implement the same requirements for a web-based system
within two days, using different technology platforms
(<a class="moz-txt-link-freetext" href="https://www.plat-forms.org/">https://www.plat-forms.org/</a>). <strong>Its purpose</strong> is not
to determine "the" best platform, but rather to provide new insights
into the real (rather than purported) pros, cons, and emergent
properties of each platform. <br>
<br>
We used to discern platforms by language, but found that similar web
frameworks can make properties of solutions similar over different
languages. So, because it is one, we are also investing the
properties of grok :-)<br>
And this is where I need your help on two questions:<br>
<br>
- what is the typical development procedure when developing a
web application with grok?<br>
We want to find out in what steps a developer implements an
application in a framework, for example whether they start with
models, templates or tests.<br>
Is this somewhat similar to the procedure in this tutorial?<br>
<a class="moz-txt-link-freetext" href="http://grok.zope.org/documentation/tutorial/grok-poller-tutorial">http://grok.zope.org/documentation/tutorial/grok-poller-tutorial</a><br>
<br>
1. bootstrap grok<br>
2. write model classes<br>
3. for each user story<br>
a. write views<br>
b. write tests<br>
c. write templates<br>
<br>
- what is the mental model when writing a grok application? Do
you think in terms of URLs, actions, form, components?<br>
<br>
Regards,<br>
Holger<br>
</body>
</html>