<?xml version="1.0" encoding="utf-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:dc="http://purl.org/dc/elements/1.1/"
         xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
         xmlns="http://purl.org/rss/1.0/">




    



<channel rdf:about="http://grok.zope.org/blog/aggregator/RSS">
  <title>Grok News and Blog</title>
  <link>http://grok.zope.org</link>
  
  <description>
    
       Chatter from the cave
       
  </description>
  
  
  
            <syn:updatePeriod>daily</syn:updatePeriod>
            <syn:updateFrequency>1</syn:updateFrequency>
            <syn:updateBase>2007-10-05T08:06:53Z</syn:updateBase>
        
  
  <image rdf:resource="http://grok.zope.org/logo.gif"/>

  <items>
    <rdf:Seq>
        
            <rdf:li rdf:resource="http://grok.zope.org/blog/chapter-about-grok-in-german-python-book"/>
        
        
            <rdf:li rdf:resource="http://grok.zope.org/blog/grok-0.13-is-released"/>
        
        
            <rdf:li rdf:resource="http://grok.zope.org/blog/grok-0.12.1-released"/>
        
        
            <rdf:li rdf:resource="http://grok.zope.org/blog/grok-0.12-released"/>
        
        
            <rdf:li rdf:resource="http://grok.zope.org/blog/grok-at-trade-shows-pictorial-evidence"/>
        
        
            <rdf:li rdf:resource="http://grok.zope.org/blog/grokkerdam-sprint"/>
        
        
            <rdf:li rdf:resource="http://grok.zope.org/blog/grok-in-the-google-summer-of-code-mentor-hunt"/>
        
        
            <rdf:li rdf:resource="http://grok.zope.org/blog/megrok.form-released"/>
        
        
            <rdf:li rdf:resource="http://grok.zope.org/blog/grok-at-the-snow-sprint-a-report"/>
        
        
            <rdf:li rdf:resource="http://grok.zope.org/blog/grok-web-site-relaunched"/>
        
        
            <rdf:li rdf:resource="http://grok.zope.org/project/releases/0.11.1/Grok-0.11.1"/>
        
        
            <rdf:li rdf:resource="http://grok.zope.org/blog/snow-sprint-2008-grok-presentation"/>
        
        
            <rdf:li rdf:resource="http://grok.zope.org/project/releases/0.11/grok-0.11-released"/>
        
        
            <rdf:li rdf:resource="http://grok.zope.org/project/releases/0.10.2/grok-0.10.2-released"/>
        
        
            <rdf:li rdf:resource="http://grok.zope.org/project/releases/0.10.1/grok-0.10.1-released"/>
        
    </rdf:Seq>
  </items>

</channel>

    <item rdf:about="http://grok.zope.org/blog/chapter-about-grok-in-german-python-book">        <title>German Python Book features chapter about Grok</title>        <link>http://grok.zope.org/blog/chapter-about-grok-in-german-python-book</link>        <description>A Python book for staff and students of 170 german universities presents grok as an example of a real world, professional Python project. The other presented projects are Plone and MoinMoin.&lt;p&gt;The book is part of a well known series in Germany (&lt;a class="external-link" href="http://www.rrzn.uni-hannover.de/buecher.html?&amp;amp;no_cache=1&amp;amp;tx_rrznbuecher_pi1[showUid]=215"&gt;the RRZN-Handbücher&lt;/a&gt;), which is only available for staff and students of universities. It was written by several members of the Python User Group of Cologne (&lt;a class="external-link" href="http://wiki.python.de/pycologne"&gt;PyCologne&lt;/a&gt;). The chapter about Grok was written by Grok contributor Uli Fouquet.&lt;/p&gt;

&lt;p&gt;The main authors of the book were Patrick Holz from the university of Cologne and Christopher Arndt.&lt;/p&gt;
</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>juh</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-06-26T08:40:20Z</dc:date>        <dc:type>News Item</dc:type>    </item>
    <item rdf:about="http://grok.zope.org/blog/grok-0.13-is-released">        <title>Grok 0.13 is released!</title>        <link>http://grok.zope.org/blog/grok-0.13-is-released</link>        <description>The Grok team is happy to announce the release of Grok 0.13, a new feature release of Grok.&lt;p&gt;The new Grok 0.13 is a major new feature release. It contains some large restructurings, a range of new features and bug fixes. For more about it Grok 0.13, read the &lt;a class="reference" href="http://grok.zope.org/project/releases/0.13/"&gt;release announcement&lt;/a&gt;. It also marks the first release that uses the new &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;grokcore.component&lt;/span&gt;&lt;/tt&gt; library, which can also be used independently in other Zope 3 applications, as well as in Zope 2.&lt;/p&gt;
</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>faassen</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-06-23T20:01:32Z</dc:date>        <dc:type>News Item</dc:type>    </item>
    <item rdf:about="http://grok.zope.org/blog/grok-0.12.1-released">        <title>Grok 0.12.1 released!</title>        <link>http://grok.zope.org/blog/grok-0.12.1-released</link>        <description>&lt;p&gt;The Grok team is happy to announce the release of Grok 0.12.1! This is a bugfix release.&lt;/p&gt;
&lt;p&gt;Grok is a web application framework built with Zope 3 technologies that aims to be easy to use.&lt;/p&gt;
&lt;p&gt;See also &lt;a class="reference" href="http://grok.zope.org/"&gt;http://grok.zope.org/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This release is available on PyPI and a new index of specific versions of packages used by this release has been frozen at
&lt;a class="reference" href="http://grok.zope.org/releaseinfo/grok-0.12.1.cfg"&gt;http://grok.zope.org/releaseinfo/grok-0.12.1.cfg&lt;/a&gt;. This means that new projects created with grokproject will start using this release right away.&lt;/p&gt;
&lt;div class="section"&gt;
&lt;h3&gt;&lt;a id="bug-fixes" name="bug-fixes"&gt;Bug fixes:&lt;/a&gt;&lt;/h3&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;Fix &lt;a class="reference" href="https://bugs.launchpad.net/grok/+bug/231106"&gt;https://bugs.launchpad.net/grok/+bug/231106&lt;/a&gt;: Use the viewletmanager.sort() method for sorting viewlets by using util.sort_components().&lt;/li&gt;
&lt;li&gt;grok.REST views now have a properly set __parent__ attribute and will correctly allow acquisition from parent objects, as it's used by the security policy for acquiring local grants, for example.&lt;/li&gt;
&lt;li&gt;Fix &lt;a class="reference" href="https://bugs.launchpad.net/grok/+bug/229677"&gt;https://bugs.launchpad.net/grok/+bug/229677&lt;/a&gt;: zope.app.securitypolicy egg missing. Now zope.app.securitypolicy 3.4.6 is additionally required by Grok and fetched by buildout.&lt;/li&gt;
&lt;li&gt;The grokkers for adapters and global utilities did not use the correct value for the provided interface in the configuration action discriminator. Because of this, uninformative and potentially wrong conflict errors would occur, as well as no conflict where a conflict should have occurred.&lt;/li&gt;
&lt;li&gt;The grokker for the global_utility() directive did immediate registrations instead of generating configuration actions. Therefore it did not provoke ConflictErrors for conflicting registrations.&lt;/li&gt;
&lt;li&gt;Removed quickly hacked testsetup code from grok.testing.&lt;/li&gt;
&lt;li&gt;Port fix of zope.formlib to correctly adapt the context to a FormField's interface, not the field.&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>jw</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-05-31T18:29:07Z</dc:date>        <dc:type>News Item</dc:type>    </item>
    <item rdf:about="http://grok.zope.org/blog/grok-0.12-released">        <title>Grok 0.12 released!</title>        <link>http://grok.zope.org/blog/grok-0.12-released</link>        <description>The Grok team is happy to announce the release of Grok 0.12, a new feature release of Grok.&lt;p&gt;The new Grok 0.12 release contains two major new features:&lt;/p&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;Viewlet support. Viewlets are highly configurable &amp;quot;part-of-page&amp;quot; components. Expect documentation on the website soon.&lt;/li&gt;
&lt;li&gt;automatic inclusion of dependencies. No more editing &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;configure.zcml&lt;/span&gt;&lt;/tt&gt; of your application when you add a new dependency to &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;setup.py&lt;/span&gt;&lt;/tt&gt; that has ZCML configuration. Grok now automatically should find this dependency and loads its ZCML configuration, so only editing &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;setup.py&lt;/span&gt;&lt;/tt&gt; and running &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;bin/buildout&lt;/span&gt;&lt;/tt&gt; should now be required.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Note also that the &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;Base&lt;/span&gt;&lt;/tt&gt; postfix feature has been removed. Classes with names that end with this postfix are not treated as Grok base classes anymore. Use the &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;grok.baseclass&lt;/span&gt;&lt;/tt&gt; directive instead.&lt;/p&gt;
&lt;p&gt;We recommend that everybody update &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;grokproject&lt;/span&gt;&lt;/tt&gt; first:&lt;/p&gt;
&lt;pre class="literal-block"&gt;
$ easy_install -U grokproject
&lt;/pre&gt;
&lt;p&gt;This will make new projects use the new auto-inclusion facility that now ships with Grok as well. See the upgrade notes for more details on how to upgrade your current projects to Grok 0.12:&lt;/p&gt;
&lt;p&gt;&lt;a class="reference" href="http://grok.zope.org/project/upgrade-notes"&gt;http://grok.zope.org/project/upgrade-notes&lt;/a&gt;&lt;/p&gt;
</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>faassen</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-04-22T16:31:08Z</dc:date>        <dc:type>News Item</dc:type>    </item>
    <item rdf:about="http://grok.zope.org/blog/grok-at-trade-shows-pictorial-evidence">        <title>Grok at trade shows: pictorial evidence</title>        <link>http://grok.zope.org/blog/grok-at-trade-shows-pictorial-evidence</link>        <description>Grok was present at CeBIT and the Chemnitzer Linux Tage earlier this month&lt;p&gt;Here are some &lt;a href="http://www.zope.de/redaktion/dzug/nachrichten/cebit/fotos-von-der-cebit-und-den-chemnitzer-linuxtagen"&gt;pictures of Grok's presence&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;There is some &lt;a href="http://www.zope.de/redaktion/dzug/nachrichten/cebit/cebit-2008-11.jpg/image_view_fullscreen"&gt;damning evidence&lt;/a&gt; of Grok meeting with stone-age girls.&lt;/p&gt;






</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>faassen</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-03-17T12:46:38Z</dc:date>        <dc:type>News Item</dc:type>    </item>
    <item rdf:about="http://grok.zope.org/blog/grokkerdam-sprint">        <title>Grokkerdam sprint!</title>        <link>http://grok.zope.org/blog/grokkerdam-sprint</link>        <description>It was planned for a long time, but at last we are going to hold a Grok sprint in the Netherlands. To be more precise, in Rotterdam. Rotterdam will be "Grokkerdam" for the duration of the sprint!&lt;p&gt;&lt;strong&gt;Where&lt;/strong&gt;: Rotterdam, the Netherlands&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;When&lt;/strong&gt;: 30 april - 5 may 2008&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Who&lt;/strong&gt;: hopefully, you!&lt;/p&gt;
&lt;p&gt;Sign up for the sprint on our wiki page, here:&lt;/p&gt;
&lt;p&gt;&lt;a class="reference" href="http://wiki.zope.org/grok/GrokkerdamSprint"&gt;http://wiki.zope.org/grok/GrokkerdamSprint&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;If you have any comments or questions, please mail Martijn Faassen at &lt;a class="reference" href="mailto:faassen&amp;#64;startifact.com"&gt;faassen&amp;#64;startifact.com&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Our generous host for this sprint is The Health Agency (&lt;a class="reference" href="http://www.thehealthagency.com/"&gt;http://www.thehealthagency.com/&lt;/a&gt;), a company that uses Grok for its own web applications here in Rotterdam.&lt;/p&gt;
&lt;p&gt;Note: this sprint is back-to-back with the &lt;a class="reference" href="http://www.openplans.org/projects/plone-3-paris-sprint/project-home"&gt;Plone 3 sprint&lt;/a&gt; in Paris (25-27 april), hosted by Ingeniweb. Rotterdam is 3 hours away from Paris by train. You could participate in both sprints and enjoy a few days of Paris (or Rotterdam) in between.&lt;/p&gt;
</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>faassen</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-03-11T19:44:41Z</dc:date>        <dc:type>News Item</dc:type>    </item>
    <item rdf:about="http://grok.zope.org/blog/grok-in-the-google-summer-of-code-mentor-hunt">        <title>Grok in the Google Summer of Code: mentor hunt!</title>        <link>http://grok.zope.org/blog/grok-in-the-google-summer-of-code-mentor-hunt</link>        <description>Grok needs mentors for the Summer of Code!&lt;p&gt;We are quickly approaching the Google of Summer of code again. The Zope Foundation's application needs to be in soon.&lt;/p&gt;
&lt;p&gt;In order to do a good application, we need to have a good selection of mentors. So, if you're a Grok developer and you want to mentor a student this summer, please add yourself to the list here:&lt;/p&gt;
&lt;p&gt;&lt;a class="reference" href="http://wiki.zope.org/gsoc/SummerOfCode2008"&gt;http://wiki.zope.org/gsoc/SummerOfCode2008&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Don't wait: the Zope Foundation's application needs to be in &lt;em&gt;very&lt;/em&gt; soon (by the 11th of march). The more mentors we have the better a chance we stand in getting projects accepted.&lt;/p&gt;
&lt;p&gt;Being a mentor isn't difficult and it can be very rewarding. I was very happy to see our two Grok students (Uli and Luciano) so active in our community: they are great additions to our project. We do expect mentors to stay in regular touch with their students. This means email and normal involvement on project mailing lists, but also in addition to this a weekly hour or so on irc and/or voice. We also have a few simple reporting requirements so that your mentor coordinator (Martijn Faassen) knows what's up and can solve any potential problems.&lt;/p&gt;
&lt;p&gt;Everybody (including mentors, students and others):&lt;/p&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;suggest projects, also on the same wiki page&lt;/li&gt;
&lt;li&gt;suggest mentors. Tell people who you &lt;em&gt;want&lt;/em&gt; to be mentors to sign up. Everybody likes to be told they can be mentors, so tell them in public and get them to sign up.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Students:&lt;/p&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;Mark the sign-up period on your calendar: it starts march 24. If we get accepted, then is the time to sign up.&lt;/li&gt;
&lt;/ul&gt;
</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>faassen</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-03-03T17:09:36Z</dc:date>        <dc:type>News Item</dc:type>    </item>
    <item rdf:about="http://grok.zope.org/blog/megrok.form-released">        <title>megrok.form released!</title>        <link>http://grok.zope.org/blog/megrok.form-released</link>        <description>Dirceu Pereira Tiegs has released megrok.form, an extension library that adds a lot of useful fields and widgets to Grok.&lt;p&gt;megrok.form is a helper package that provides some useful fields,
widgets and constraints for Grok.&lt;/p&gt;
&lt;div class="section"&gt;
&lt;h3&gt;&lt;a id="fields" name="fields"&gt;Fields&lt;/a&gt;&lt;/h3&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;Email, a TextLine field with a default contraint&lt;/li&gt;
&lt;li&gt;HTML, a Text field that uses z3c.widget.tiny&lt;/li&gt;
&lt;li&gt;File, from collective.namedfile&lt;/li&gt;
&lt;li&gt;Image, from collective.namedfile&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;div class="section"&gt;
&lt;h3&gt;&lt;a id="widgets" name="widgets"&gt;Widgets&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;megrok.form overrides the default widgets for:&lt;/p&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;zope.interface.schema.Date (using zc.datetimewidget.widget.DateWidget)&lt;/li&gt;
&lt;li&gt;zope.interface.schema.Datetime (using zc.datetimewidget.widget.DatetimeWidget)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;And adds new widgets for Image and File (from collective.namedfile).&lt;/p&gt;
&lt;/div&gt;
&lt;div class="section"&gt;
&lt;h3&gt;&lt;a id="validators-constraints" name="validators-constraints"&gt;Validators/constraints&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;megrok.form adds constraints for:&lt;/p&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;SSN&lt;/li&gt;
&lt;li&gt;US Phone Numbers&lt;/li&gt;
&lt;li&gt;International Phone Numbers&lt;/li&gt;
&lt;li&gt;Zip Code&lt;/li&gt;
&lt;li&gt;URL&lt;/li&gt;
&lt;li&gt;Email&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You can add these to your application by listing 'megrok.form' as a dependency in your project's &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;setup.py&lt;/span&gt;&lt;/tt&gt; file and adding a &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;&amp;lt;include&lt;/span&gt; &lt;span class="pre"&gt;package=&amp;quot;megrok.form&amp;quot;&lt;/span&gt; &lt;span class="pre"&gt;/&amp;gt;&lt;/span&gt;&lt;/tt&gt; to your project's &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;configure.zcml&lt;/span&gt;&lt;/tt&gt;. See the &lt;a class="reference" href="http://grok.zope.org/documentation/how-to/make-use-of-add-ons-via-eggs"&gt;make use of add-ons tutorial&lt;/a&gt; for more information.&lt;/p&gt;
&lt;p&gt;If you want to help out with the code and add more useful fields and widgets, it is available at &lt;a class="reference" href="http://svn.zope.org/megrok.form"&gt;http://svn.zope.org/megrok.form&lt;/a&gt;, and you can check it out using &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;svn+ssh://svn.zope.org/repos/main/megrok.form/trunk&lt;/span&gt;&lt;/tt&gt;. Let us know what you're thinking about on &lt;a class="reference" href="http://mail.zope.org/mailman/listinfo/grok-dev"&gt;grok-dev&lt;/a&gt; and have fun!&lt;/p&gt;
&lt;/div&gt;
</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>faassen</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-02-26T20:23:22Z</dc:date>        <dc:type>News Item</dc:type>    </item>
    <item rdf:about="http://grok.zope.org/blog/grok-at-the-snow-sprint-a-report">        <title>Grok at the Snow Sprint: a report</title>        <link>http://grok.zope.org/blog/grok-at-the-snow-sprint-a-report</link>        <description>Grok was a popular topic at the Snow Sprint, high up on the mountains.
Martijn Faassen &lt;a href="http://faassen.n--tree.net/blog/view/weblog/2008/01/28/0"&gt;reports&lt;/a&gt; on what we were up to at the sprint and how it benefits Grok.


</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>faassen</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-02-26T20:12:57Z</dc:date>        <dc:type>News Item</dc:type>    </item>
    <item rdf:about="http://grok.zope.org/blog/grok-web-site-relaunched">        <title>Grok web site relaunch</title>        <link>http://grok.zope.org/blog/grok-web-site-relaunched</link>        <description>The Grok web site has been reworked and relaunched.&lt;img src="/images/grok-signet-c-big.png/image_mini" alt="Grok logo" style="float: right; margin: 0 0 1em 1em;" /&gt;

&lt;p&gt;
The Grok web site has been given a new look and feel. It is
now powered by the &lt;a href="http://plone.org"&gt;Plone Content Management System&lt;/a&gt;.
This provides the Grok web site with an always up-to-date site search,
RSS feeds of &lt;a href="/news/aggregator/RSS"&gt;site news&lt;/a&gt;, &lt;a href="/search_rss?sort_on=modified&amp;sort_order=descending&amp;path=/plone/public_website/documentation&amp;portal_type=HelpCenterFAQ&amp;portal_type=HelpCenterHowTo&amp;portal_type=HelpCenterTutorial&amp;portal_type=HelpCenterLink&amp;portal_type=HelpCenterErrorReference&amp;portal_type=HelpCenterDefinition&amp;portal_type=HelpCenterReferenceManual&amp;portal_type=HelpCenterInstructionalVideo"&gt;
documentation updates&lt;/a&gt; and &lt;a href="/all-content-updates/RSS"&gt;all site content updates&lt;/a&gt;.
Most importantly, the &lt;a href="/documentation" title="visit our documentation area"&gt;Grok Documentation area&lt;/a&gt; now allows you to create an account with the
web site and 
&lt;a href="/documentation/tutorial/contribute-to-the-grok-documentation"&gt;contribute structured documentation&lt;/a&gt;.
&lt;/p&gt;

&lt;h2 style="clear: both;"&gt;Contributors&lt;/h2&gt;

&lt;img src="images/grok-caveman10flat250.png" alt="Grok character" style="float: right; margin: 0 0 1em 1em;" /&gt;

&lt;p&gt;&lt;a href="http://bud.ca"&gt;Kevin Teague&lt;/a&gt; stepped up to be the official cat herder and dotter of i's
for the site relaunch. &lt;a href="http://www.acsr.de"&gt;Armin C. Stroß-Radschinski&lt;/a&gt; created an official Grok logo for the project as well as a stylized version of the Grok character.
Sebastian Ware provided the intial site redesign, while the Grok web team at the Neanderthal 2007 sprint
lead by Martijn Faassen used this to created the initial Plone theme and content. Uli Fouquet extended restructured-text support for the site to include additional directives as well as 
&lt;a href="/documentation/tutorial/contribute-to-the-grok-documentation/restructured-text-rest-extensions"&gt;syntax highlighting and line numbers&lt;/a&gt;. Finally Martijn Faassen poked people to keep the project moving.
&lt;/p&gt;
</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>kteague</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-02-22T01:58:49Z</dc:date>        <dc:type>News Item</dc:type>    </item>
    <item rdf:about="http://grok.zope.org/project/releases/0.11.1/Grok-0.11.1">        <title>Grok 0.11.1 released</title>        <link>http://grok.zope.org/project/releases/0.11.1/Grok-0.11.1</link>        <description>First maintenance release of the 0.11 series.&lt;p&gt;Grok 0.11.1 release manager Jan-Wijbrand Kolman is happy to announce the 0.11.1 release of Grok!&lt;/p&gt;
&lt;p&gt;This release is &lt;a class="reference" href="http://pypi.python.org/pypi/grok/0.11.1"&gt;available on PyPI&lt;/a&gt; and a new index of specific versions of packages
used by this release has been frozen at &lt;a class="reference" href="http://grok.zope.org/releaseinfo/grok-0.11.1.cfg"&gt;http://grok.zope.org/releaseinfo/grok-0.11.1.cfg&lt;/a&gt;. This means that new projects created with grokproject will start using this release right away.&lt;/p&gt;
&lt;p&gt;This is maintenance only release that just contains bug fixes and does not introduce any new features.&lt;/p&gt;
&lt;div class="section"&gt;
&lt;h3&gt;&lt;a id="upgrading" name="upgrading"&gt;Upgrading&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;To upgrade an existing project from 0.11 to 0.11.1 you have to:&lt;/p&gt;
&lt;blockquote&gt;
&lt;ol class="arabic simple"&gt;
&lt;li&gt;change the 'extends' directive in your project's buildout.cfg to
point to &lt;a class="reference" href="http://grok.zope.org/releaseinfo/grok-0.11.1.cfg"&gt;http://grok.zope.org/releaseinfo/grok-0.11.1.cfg&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;run bin/buildout in your project, to update the dependencies
including the 0.11.1 egg of Grok itself&lt;/li&gt;
&lt;/ol&gt;
&lt;/blockquote&gt;
&lt;/div&gt;
&lt;div class="section"&gt;
&lt;h3&gt;&lt;a id="bug-fixes" name="bug-fixes"&gt;Bug fixes&lt;/a&gt;&lt;/h3&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;Do not register the publishTraverse and browserDefault methods of the
JSON component as views.&lt;/li&gt;
&lt;li&gt;Methods with names that start with an '_' are not registered as views
for XMLRPC, REST and JSON components.&lt;/li&gt;
&lt;li&gt;Use a configuration action for the registration of the static directory.&lt;/li&gt;
&lt;li&gt;Fix &lt;a class="reference" href="https://bugs.launchpad.net/grok/+bug/161948"&gt;https://bugs.launchpad.net/grok/+bug/161948&lt;/a&gt;: grok.testing.grok()
now also loads the ZPT template factories so that unit tests that
need to configure views with ZPT templates continue to work.&lt;/li&gt;
&lt;li&gt;Changed a few remaining references to &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;grok.grok&lt;/span&gt;&lt;/tt&gt; and
&lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;grok.grok_component&lt;/span&gt;&lt;/tt&gt; to their correct equivalents in
&lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;grok.testing&lt;/span&gt;&lt;/tt&gt;.&lt;/li&gt;
&lt;li&gt;&lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;grok.testing.grok_component()&lt;/span&gt;&lt;/tt&gt; could not be used in a pure
doctest. This needed a bugfix in Martian (since 0.9.2). Add a test
that demonstrates this problem.&lt;/li&gt;
&lt;li&gt;Fix &lt;a class="reference" href="https://bugs.launchpad.net/grok/+bug/162437"&gt;https://bugs.launchpad.net/grok/+bug/162437&lt;/a&gt;: grok.Form and its
subclasses did not implement IBrowserView.&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>kteague</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-01-21T02:16:52Z</dc:date>        <dc:type>News Item</dc:type>    </item>
    <item rdf:about="http://grok.zope.org/blog/snow-sprint-2008-grok-presentation">        <title>Snow Sprint 2008 Grok presentation</title>        <link>http://grok.zope.org/blog/snow-sprint-2008-grok-presentation</link>        <description>Martijn Faassen gives a talk about Grok at the 2008 Snow Sprint.&lt;p&gt;
&lt;a href="http://www.openplans.org/projects/snow-sprint-2008/"&gt;Snow Sprint 2008&lt;/a&gt; is taking place from January 18th to 25th, 2008 in Berghof Piz Buin, Austria. This is a gathering of  50 Zope developers who have come together to hack on all things Zope related. The focus this year is on Zope 3 and high traffic related topics.
&lt;/p&gt;

&lt;p&gt;
Martijn Faassen was in attendance and give a &lt;i&gt;Grok from a Zope 3 perspective&lt;/i&gt; focused talk at the sprint, which was recorded and made available online by Christian Scholz, multimedia chronicler of all things Zope, as a &lt;a href="http://mrtopf.de/blog/meetups/snow-sprint-2008-martijn-faassen-about-grok-technical/"&gt;
broadcast of the MrTopf Show&lt;/a&gt;.
&lt;/p&gt;

&lt;p&gt;Note that the video may be a bit choppy right near the start of the video, butit
should stream fine for the bulk of the presentation.
&lt;/p&gt;</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>kteague</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-01-21T04:39:26Z</dc:date>        <dc:type>News Item</dc:type>    </item>
    <item rdf:about="http://grok.zope.org/project/releases/0.11/grok-0.11-released">        <title>Grok 0.11 released</title>        <link>http://grok.zope.org/project/releases/0.11/grok-0.11-released</link>        <description>The Grok team is happy to announce the release of Grok 0.11!&lt;p&gt;Grok is
a web application framework built with Zope 3 technologies that aims
to be easy to use.&lt;/p&gt;
&lt;p&gt;Grok 0.11 is a feature release of Grok, introducing important new features:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt; Layers and skinning support. It is now easy to place views in
layers, and to define skins so that these layers can be browsed.
&lt;/li&gt;

&lt;li&gt; REST support. There is an easy way to create RESTful web services
with Grok now. Create special REST protocols that support GET, POST,
PUT and DELETE. See the &lt;a href="/documentation/how-to/rest-support-in-grok"&gt;REST Tutorial&lt;/a&gt; for more information.
&lt;/li&gt;

&lt;li&gt; pluggable template languages. Besides the built-in support for Zope
Page Templates, Grok now allows you to plug in other template
languages as well. See
http://grok.zope.org/minitutorials/template-languages.html for
instructions on how to integrate a template language into Grok. We are
planning on releasing a Genshi plugin for Grok next week.
&lt;/li&gt;

&lt;li&gt; Improved permission and role support. See the &lt;a href="/documentation/tutorial/permissions"&gt;Permissions Tutorial&lt;/a&gt;
 for more information. If you were already using these in your existing Grok
code you need to change your code a bit. The &lt;a href="./upgrade"&gt;upgrade notes&lt;/a&gt; contain more information about these changes.
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;
One important change is rather hidden from view so bears a bit of
explanation. Grok is based on Zope 3. Grok could always reuse Zope 3
libraries without problems. The other way around wasn't so nice
however: Zope 3-based code could not use Grok-based code so easily, as
Grok would not emit configuration actions. Grok 0.11 now does emit
such configuration actions and this is a major step on the way towards
backwards compatibility with Zope 3. If you have custom Grokkers in
your code, you probably have to change them: please see the 
&lt;a href="./upgrade"&gt;upgrade notes&lt;/a&gt; for information how to upgrade these.&lt;/p&gt;

&lt;p&gt;
For the detailed changelog, see 
&lt;a href="http://pypi.python.org/pypi/grok"&gt;Grok's PyPI entry page&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;
For upgrade notes, including how to change your application, see
http://grok.zope.org/upgrade.html&lt;/p&gt;

&lt;p&gt;
For installation instructions and much more on how to use Grok, see
the Grok tutorial: http://grok.zope.org/tutorial.html&lt;/p&gt;

&lt;p&gt;
If you enjoy Grok, please subscribe to the 
&lt;a href="http://mail.zope.org/mailman/listinfo/grok-dev"&gt;grok-dev mailing list&lt;/a&gt; and join us in the #grok channel on irc.freenode.net.&lt;/p&gt;

&lt;p&gt;
We hope to see you there!&lt;/p&gt;
</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>kteague</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-01-31T23:07:40Z</dc:date>        <dc:type>News Item</dc:type>    </item>
    <item rdf:about="http://grok.zope.org/project/releases/0.10.2/grok-0.10.2-released">        <title>Grok 0.10.2 released</title>        <link>http://grok.zope.org/project/releases/0.10.2/grok-0.10.2-released</link>        <description>Maintenance release for the 0.10 series
&lt;p&gt;To upgrade an existing project from 0.10.1 to 0.10.2 you have to:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt; change the 'extends' directive in your project's buildout.cfg to
      point to http://grok.zope.org/releaseinfo/grok-0.10.2.cfg&lt;/li&gt;
&lt;li&gt; run bin/buildout in your project, to update the dependencies
      including the 0.10.2 egg of Grok itself&lt;/li&gt;&lt;/ol&gt;
</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>kteague</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-01-21T01:42:15Z</dc:date>        <dc:type>News Item</dc:type>    </item>
    <item rdf:about="http://grok.zope.org/project/releases/0.10.1/grok-0.10.1-released">        <title>Grok 0.10.1 released</title>        <link>http://grok.zope.org/project/releases/0.10.1/grok-0.10.1-released</link>        <description>Maintenance release of the 0.10 series&lt;p&gt;
Grok 0.10.1 is a bugfix release of Grok, and the first outcome of the
Neanderthal Grok sprint that was hosted by GfU Cyrus in Cologne,
Germany, last week.
&lt;/p&gt;

&lt;p&gt;
The sole aim of this release is to fix Grok's installation story.
Releases of Zope 3 components that Grok relied on had the tendency to
break Grok. Since Grok now uses a fixed list of versions it relies on,
this problem should now be solved. The grokproject tool has also been
updated to 0.6, and now automatically uses the version list feature.
&lt;/p&gt;

&lt;p&gt;
To update grokproject to 0.6, please type the following:
&lt;/p&gt;

&lt;pre&gt;
$ easy_install -U grokproject
&lt;/pre&gt;

&lt;p&gt;
For more information about this release, including instructions on how
to update existing buildouts to use the version list feature, see
here: http://grok.zope.org/releaseinfo/readme.html
&lt;/p&gt;

</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>kteague</dc:creator>        <dc:rights></dc:rights>                <dc:date>2008-01-21T01:43:02Z</dc:date>        <dc:type>News Item</dc:type>    </item>




</rdf:RDF>
