[Grok-dev] Re: An untapped area..?
Sebastian Ware
sebastian at urbantalk.se
Wed Jan 23 08:26:02 EST 2008
23 jan 2008 kl. 12.46 skrev Martijn Faassen:
> Sebastian Ware wrote:
>> 23 jan 2008 kl. 12.15 skrev Martijn Faassen:
>>> Customization can be done with Grok, depending on the patterns
>>> you're take. That is, you can write an extension to a core
>>> application that customizes that core application. You can plug in
>>> new content objects, add or override views (if you use skins),
>>> supply a different local utility, and so on. I've for instance
>>> been writing an application that has multiple deployments with a
>>> different set of content objects in each.
>> This was what I was thinking too, but I am guessing there are some
>> pitfalls... A best practice "howto" for this would be great! Even
>> if it is just a collection of notes to start with. I think this is
>> the documentation that Jeff was wishing for. I think a lot of us
>> Grok users would benefit from this.
>
> Yes, documentation would be great. Sort of design pattern
> documentation for the component architecture. One of the hardest
> kind of documentation to write, though, I suspect. I'll need to
> think about it.
>
True! But even notes are better than nothing. It just gets one
thinking along right tracks. It also sends a clear signal -- we care
about these questions because Grok is for real!
Mvh Sebastian
More information about the Grok-dev
mailing list