[Grok-dev] Re: SVN: grok/branches/ksmith_mcweekly-groklets/src/grok/ initial prototype

Kevin Smith kevin at mcweekly.com
Tue Oct 2 18:26:53 EDT 2007


Hi Phillip,

Good catch, thanks for taking a look, it's cruft.

My initial goal was to allow these groklets to be traversable to save 
some code in ahah-style applications. I haven't actually used groklets 
this way yet, and it seems like everyone has their own approach to ajax, 
so there may not be a strong enough use case to justify BrowserPage.

Unless there's a show stopper in this implementation, I think I've come 
up with a way for groklets to act as viewletmanagers as well.

Kevin


Philipp von Weitershausen wrote:
> Kevin Smith wrote:
>> Modified: grok/branches/ksmith_mcweekly-groklets/src/grok/components.py
>> ===================================================================
>> --- grok/branches/ksmith_mcweekly-groklets/src/grok/components.py    
>> 2007-10-01 20:38:37 UTC (rev 80454)
>> +++ grok/branches/ksmith_mcweekly-groklets/src/grok/components.py    
>> 2007-10-01 20:45:16 UTC (rev 80455)
>> @@ -480,3 +480,99 @@
>>  
>>  class Skin(object):
>>      pass
>> +
>> +class Groklet(BrowserPage):
>> +    """ Groklet - viewlets without viewletmanagers
>
> Why do groklets inherit from BrowserPage? Are they publishable via 
> URL? It seems to me this is more of an accident...
>
>


More information about the Grok-dev mailing list