[Grok-dev] Re: ANN: New Grok Powered Website

Kevin Smith kevin at mcweekly.com
Mon Feb 25 13:00:27 EST 2008

Martijn Faassen wrote:
> Hey,
> Kevin Smith wrote:
> [snip]
>>> Is there a "sites using Grok" area on grok.zope.org? It'd be nice to 
>>> get this up there, if you'll agree.
>> Yes, if so, please list.
> We don't have such a list yet. Thanks for the permission to list it!
> I'd be nice to have one definitely. I think we may want to collect 
> more than 1 link, as only 1 link may scare people off. Do people have 
> other links of Grok-using sites?
> [snip]
>> There were a number of issues I've ran into in the past with other 
>> frameworks and CMS's in general and specifically. Inefficient data 
>> entry when handling large datasets.
> It'd be interesting to see a description of how the efficient data 
> entry works. I imagine what is efficient depends much on your use 
> cases and needs to be geared towards them, but it'd still be nice to 
> hear about good patterns you've discovered for this.
It's very use case dependent and under constant improvement, however the 
basics of what I've been using are good old html frames, javascript 
tabs, live search and filter lists 

I also use custom form's instead of the standard formlib CRUD to save 
screen real estate.

Lately been having some good luck with the jquery jframe plugin 
(http://garage.pimentech.net/scripts_doc_jquery_jframe/)  for simple but 
powerful AJAX.. If some good general patterns emerge from this I may 
implement a megrok.jframe library later this year as an alternative to KSS.

>> Poor scaling of search indexes to the point of near failure. 
> You also mentioned that you had trouble scaling the catalog indexes. 
> How did you resolve this problem?
As mentioned in the previous post, divide and conquer. Splitting the 
data by year.
>> "Fighting the framework" when trying to change a fundamental 
>> behaviour. Unacceptable RPS.
> What does "RPS" mean?
Requests per second.
>> Hours lost trying to understanding  the sometimes complex 
>> interactions of skins, layers, templates, styles, and layout. 
>> Inablility to adapt and evolve.
>> Also,  because I am spoiled rotten by Grok. :)
> It's good to hear you feel spoiled now. We need to work on getting the 
> message out on how Grok can spoil developers rotten (visions of a Grok 
> massaging a blissful web developer lying down on a rock). Any ideas?
I look forward to Grok integration with Zope3. Even if Grok we're used 
only for grok.View this alone can translate into hundreds of lines of 
type saved.

>> That said, right tool for the right job. I'm open to using a python 
>> powered CMS for the right project.
> I hope we'll see the publication of a bunch of Grok-powered CMSes in 
> time!
> Regards,
> Martijn
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> http://mail.zope.org/mailman/listinfo/grok-dev

More information about the Grok-dev mailing list