<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel">
    <title>gmane.comp.web.zope.grok.devel</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.grok.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6600"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6599"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6598"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6597"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6596"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6595"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6594"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6593"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6592"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6591"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6590"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6589"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6588"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6587"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6586"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6585"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6584"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6583"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6582"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6581"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6600">
    <title>Re: Grokker to remove development code?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6600</link>
    <description>

Instead of introducing yet another labelling axis, could marker
interfaces be used instead?

 class MyView(grok.View):
    grok.implements(IDevelopmentOnly)

 &lt;grok:grok package="." interface_exclude="IDevelopmentOnly"&gt;

</description>
    <dc:creator>Brandon Craig Rhodes</dc:creator>
    <dc:date>2008-12-03T19:00:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6599">
    <title>Re: Grokker to remove development code?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6599</link>
    <description>
What we *should* do is extend martian so we can tag our classes:

class MyView(grok.View):
     grok.tag('dev')

and then have a way to run the application with different profiles that 
include or exclude particular tags. For starters we could extend the 
grok:grok directive with tag_exclude and tag_include attributes:

&lt;grok:grok package="." tag_exclude="dev"&gt;

though I think it's important to be able to configure this at a higher 
level, so that common tags can be used across packages and excluded and 
included.

Regards,

Martijn
</description>
    <dc:creator>Martijn Faassen</dc:creator>
    <dc:date>2008-12-03T18:55:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6598">
    <title>Re: grokcore.component in non-web application</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6598</link>
    <description>Martijn,
Thank you very mutch for explanation

I will try that and report back my experiences

My english is poor, but if i have success and my application will work i will write some simple howtos or post working source code

Regards
R.

-----Original Message-----
From: grok-dev-bounces&lt; at &gt;zope.org [mailto:grok-dev-bounces&lt; at &gt;zope.org] On Behalf Of Martijn Faassen
Sent: Wednesday, December 03, 2008 5:16 PM
To: grok-dev&lt; at &gt;zope.org
Subject: Re: [Grok-dev] grokcore.component in non-web application

Hey,

Lacko Roman wrote:

We're very happy to hear that!


I'll give you a code example. Perhaps you can contribute a document for
grok.zope.org (or the grokcore.component documentation) so that others
can find out how to do it.

You make your python project depend on grokcore.component in its
setup.py. This should pull in the right dependencies already.

Then in your own code:

from zope.configuration import xmlconfig

def main():
     import mypackage
     xmlconfig.file('configure.zcml', package=mypackage)

This will try</description>
    <dc:creator>Lacko Roman</dc:creator>
    <dc:date>2008-12-03T16:29:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6597">
    <title>Re: grokcore.component in non-web application</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6597</link>
    <description>Hey,

Lacko Roman wrote:

We're very happy to hear that!


I'll give you a code example. Perhaps you can contribute a document for 
grok.zope.org (or the grokcore.component documentation) so that others 
can find out how to do it.

You make your python project depend on grokcore.component in its 
setup.py. This should pull in the right dependencies already.

Then in your own code:

from zope.configuration import xmlconfig

def main():
     import mypackage
     xmlconfig.file('configure.zcml', package=mypackage)

This will try to process the 'configure.zcml' file in the package 
'mypackage' (which should be your project's Python package). This code 
should run at startup time of your application.

In configure.zcml, place the following

&lt;configure
     xmlns="http://namespaces.zope.org/zope"
     xmlns:grok="http://namespaces.zope.org/grok"&gt;

   &lt;include package="grokcore.component" file="meta.zcml" /&gt;

   &lt;grok:grok package="." /&gt;

&lt;/configure&gt;

This will first make sure that grokcore.component is registere</description>
    <dc:creator>Martijn Faassen</dc:creator>
    <dc:date>2008-12-03T16:16:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6596">
    <title>grokcore.component in non-web application</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6596</link>
    <description>_______________________________________________
Grok-dev mailing list
Grok-dev&lt; at &gt;zope.org
http://mail.zope.org/mailman/listinfo/grok-dev
</description>
    <dc:creator>Lacko Roman</dc:creator>
    <dc:date>2008-12-03T16:02:52</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6595">
    <title>Re: meet the Grok 1.0 release team</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6595</link>
    <description>I've read somewhere that for small ints and constant tuples the python
interpreter avoids recreating them (the empty tuple is the best known
example), but this is an internal memory optimization that shouldn't
be relied upon.

On Wed, Dec 3, 2008 at 10:38, Martijn Faassen &lt;faassen&lt; at &gt;startifact.com&gt; wrote:
</description>
    <dc:creator>Leonardo Rochael Almeida</dc:creator>
    <dc:date>2008-12-03T12:46:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6594">
    <title>Re: meet the Grok 1.0 release team</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6594</link>
    <description>Hey,

On Wed, Dec 3, 2008 at 1:23 PM, Brandon Craig Rhodes
&lt;brandon&lt; at &gt;rhodesmill.org&gt; wrote:

Looks like you're right. Interesting, I wonder how it manages to know
the difference internally.

Regards,

Martijn
</description>
    <dc:creator>Martijn Faassen</dc:creator>
    <dc:date>2008-12-03T12:38:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6593">
    <title>Re: meet the Grok 1.0 release team</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6593</link>
    <description>

I guess I was having fun. :-) I'll try to sound more official.


It looks to me like the interpreter builds tuples of constants only
once:

...    return (1,2,3)
...
3084583396L
3084583396L

You're entirely correct, though, that the presence of variables makes
the tuple a dynamically-constructed variable rather than a constant; I
have never thought through the difference before.  But note that
constant sub-structures are only built once, even in the presence of
variables:

...    return (x,9,(1,2))
...
3084584036L
3084583996L
3084582220L
3084582220L

What fun.  Now I have a small topic for the Python Atlanta meetup next
week. :-)

</description>
    <dc:creator>Brandon Craig Rhodes</dc:creator>
    <dc:date>2008-12-03T12:23:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6592">
    <title>Re: meet the Grok 1.0 release team</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6592</link>
    <description>Hi Brandon,

On Wed, Dec 3, 2008 at 5:45 AM, Brandon Craig Rhodes
&lt;brandon&lt; at &gt;rhodesmill.org&gt; wrote:

[snip]

I think this looks good overall and encourage you to continue.

Some comments about the text. I don't think the word 'pestering' is
very appropriate. Also Method Not Allowed errors aren't about being
attractive; it's a proper response when you access an object and the
method is not allowed. :) Perhaps the text should be modified to this:

 The REST views provided by this module are fallbacks that kick in when
         a request in a REST skin is made and objects do not have REST
views defined
         for specific HTTP methods. The fallback views return Method
Not Allowed responses.


To my knowledge tuples are allocated each time the code runs just as
much as lists are, and not only when the program runs first, otherwise
things like this wouldn't work:

mytuple = a, b

Regards,

Martijn
</description>
    <dc:creator>Martijn Faassen</dc:creator>
    <dc:date>2008-12-03T12:13:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6591">
    <title>Re: Grokker to remove development code?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6591</link>
    <description>Actually, I wanted to mark classes as "development code" so it gets  
automatically discarded when running the project on a production server.

I am guessing that with this solution I would have to add the code  
manually during deployment.

Mvh Sebastian

2 dec 2008 kl. 17.43 skrev Sylvain Viollon:

</description>
    <dc:creator>Sebastian Ware</dc:creator>
    <dc:date>2008-12-03T09:03:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6590">
    <title>Re: meet the Grok 1.0 release team</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6590</link>
    <description>

I have made a first pass at a simple file, the "src/grok/rest.py" file
in Grok trunk.  Take a look at it, and feel free to complain about any
of the following "features" of my work:

 - I made the changes in Grok trunk, rather than a branch, since they
   are cosmetic.

 - I aimed for PEP-8 style.

 - In the comments, I try to indicate why each class is present, rather
   than trying to explain how everything works.  My goal is to help
   newcomers find things more easily and understand what each component
   does, not to explain how the actual code works.

 - I have cleaned up all invisible whitespace, including blank lines at
   the end of the file.

 - I removed obsolete "import" statements.

 - I allowed myself small code tweaks.  For example, the _getAllow()
   "for" loop was previously constructing a new list to iterate over
   every time it was called; now it uses a tuple, which only gets
   allocated once, when the program first runs.

 - The docstrings use restructured text conventions, like surro</description>
    <dc:creator>Brandon Craig Rhodes</dc:creator>
    <dc:date>2008-12-03T04:45:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6589">
    <title>Re: grokui.admin pack</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6589</link>
    <description>_______________________________________________
Grok-dev mailing list
Grok-dev&lt; at &gt;zope.org
http://mail.zope.org/mailman/listinfo/grok-dev
</description>
    <dc:creator>Uli Fouquet</dc:creator>
    <dc:date>2008-12-03T00:41:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6588">
    <title>grokui.admin pack</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6588</link>
    <description>Hi Uli,

I created a zodb pack thing for grokui.admin on a branch[1], can you  
take a look at it and tell me if it is ready to be merged into the  
trunk?


Groet,
</description>
    <dc:creator>Jasper Spaans</dc:creator>
    <dc:date>2008-12-02T23:19:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6587">
    <title>Re: Grokker to remove development code?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6587</link>
    <description>_______________________________________________
Grok-dev mailing list
Grok-dev&lt; at &gt;zope.org
http://mail.zope.org/mailman/listinfo/grok-dev
</description>
    <dc:creator>Sylvain Viollon</dc:creator>
    <dc:date>2008-12-02T16:43:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6586">
    <title>Grokker to remove development code?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6586</link>
    <description>I often have the odd class here and there that is mainly intended for  
development purposes. It would be great if I could mark them somehow  
in order to exclude them from being registered on the production server.

Could this be easily achieved with a custom grokker?

Is there any other best practice for this use case?

Mvh Sebastian
</description>
    <dc:creator>Sebastian Ware</dc:creator>
    <dc:date>2008-12-02T15:02:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6585">
    <title>Re: Problems serving iepngfix.htc for transparent PNG inIE6</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6585</link>
    <description>Variations of this seems to be the solution that is generally used.  
Many of the solutions I have seen replace the image with a blank gif  
which is given the correct dimensions. The iepngfix.htc is quite  
nicely packaged so I am using variations of that one now that I got it  
to work.

Mvh Sebastian

2 dec 2008 kl. 11.51 skrev Wichert Akkerman:

</description>
    <dc:creator>Sebastian Ware</dc:creator>
    <dc:date>2008-12-02T13:30:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6584">
    <title>meet the Grok 1.0 release team</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6584</link>
    <description>Hi there,

Since people volunteered (thank you!) I put together a list:

Release manager - Jan-Wijbrand Kolman

JW has been doing this for a while, so this should go well. I'll assist 
him in this. We'll tweak the list of release dates as we go forward.

Documentation release manager - Carlos de la Guardia

I've boldly put Carlos in charge of this, as I know he's very interested 
in our documentation efforts. Carlos, you should definitely seek the 
help of Kevin Teague as he's done a lot for our website and 
documentation efforts. Uli Fouquet has also done a lot of work 
surrounding the Sphinx tools to generate our official docs.

Bug manager - Todd Matsumoto

I know Todd from Infrae. Todd, your job is that our launchpad bug list 
is complete (given what goes on here on grok-dev and whatever else comes 
up), and to monitor what these bugs actually are. If any of them look 
important to you (or you're told by the devs that they are), I'd be good 
if you gave us a, say, weekly update email with the status. Tod</description>
    <dc:creator>Martijn Faassen</dc:creator>
    <dc:date>2008-12-02T12:51:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6583">
    <title>Re: Problems serving iepngfix.htc for transparent PNG in IE6</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6583</link>
    <description>_______________________________________________
Grok-dev mailing list
Grok-dev&lt; at &gt;zope.org
http://mail.zope.org/mailman/listinfo/grok-dev
</description>
    <dc:creator>Wichert Akkerman</dc:creator>
    <dc:date>2008-12-02T12:03:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6582">
    <title>Re: About plugged templates... bug or coming soonfeature??</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6582</link>
    <description>
I think so. It was so long ago it's all a bit fuzzy. ;)


</description>
    <dc:creator>Lennart Regebro</dc:creator>
    <dc:date>2008-12-02T11:59:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6581">
    <title>Re: Problems serving iepngfix.htc for transparent PNG in IE6</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6581</link>
    <description>_______________________________________________
Grok-dev mailing list
Grok-dev&lt; at &gt;zope.org
http://mail.zope.org/mailman/listinfo/grok-dev
</description>
    <dc:creator>Sylvain Viollon</dc:creator>
    <dc:date>2008-12-02T11:50:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6580">
    <title>Re: Problems serving iepngfix.htc for transparent PNG inIE6</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6580</link>
    <description>We recently came up with a very simple bit of javascript that works
wonders:

    var ie55 = (navigator.appName == "Microsoft Internet Explorer" &amp;&amp; parseInt(navigator.appVersion) == 4 &amp;&amp; navigator.appVersion.indexOf("MSIE 5.5") != -1);
    var ie6 = (navigator.appName == "Microsoft Internet Explorer" &amp;&amp; parseInt(navigator.appVersion) == 4 &amp;&amp; navigator.appVersion.indexOf("MSIE 6.0") != -1);

    if (jQuery.browser.msie &amp;&amp; (ie55 || ie6)) {
        root.find("img[&lt; at &gt;src$=.png]").each(function() {
            $(this).css({
                    height: "0px",
                    width: $(this).width()+"px",
                    "padding-top" : $(this) .height()+"px",
                    overflow : "hidden",
                    filter : "progid:DXImageTransform.Microsoft.AlphaImageLoader(src='" + $(this).attr("src") + "', sizingMethod='scale')"
                    });
        });
    }

for some reason most people seem to want to wrap images in spans or mess
around with dummy images like the komodomedia.com snippet do</description>
    <dc:creator>Wichert Akkerman</dc:creator>
    <dc:date>2008-12-02T10:51:02</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.web.zope.grok.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.web.zope.grok.devel</link>
  </textinput>
</rdf:RDF>
