[Grok-dev] libraries to use with Grok

[Kent Tenney]

On Thu, Nov 19, 2009 at 5:35 AM, Santiago Videla
<santiago.videla at gmail.com> wrote:
> Hey,
> I think that the list could become really large...
> megrok.*
> : http://pypi.python.org/pypi?:action=search&term=megrok&submit=search
> hurry.*
> : http://pypi.python.org/pypi?:action=search&term=hurry&submit=search
> dolmen.* http://pypi.python.org/pypi?:action=search&term=dolmen&submit=search

I would welcome a brief description of the namespace collections, who is
behind them, a bit of history, target niche etc.
hurry, megrok, dolmen, zc, z3c, zope, repoze, lazr ...


> or the idea it's to include just some of those packages??
> Maybe we should use something similar to the Plone Software Center, but
> simpler. A basic content type with the following fields
> - Library Name
> - Description
> - Dependencies
> - License
> - Latest release date
> - Pypi url
> - Sources url
> By using keywords, we could define: "Static resources", "File storage",
> "Relational Database", "Url dispatch", "Workflow", etc., and show each of
> these as Collections of something...
> just an idea...
> Best Regards
> On Thu, Nov 19, 2009 at 7:33 AM, Souheil CHELFOUH <trollfot at gmail.com>
> wrote:
>>
>> Well, I have a lot of things to add on that page
>> How can we make it easy to work together on description ?
>> What about a SVN repository with some RST docs, so we could work on
>> that properly ?
>> Not that I want to push my work forward, but I can at least add all
>> the Dolmen libraries I coded
>>
>> 2009/11/19 Sebastian Ware <sebastian at urbantalk.se>:
>> > Fantastic list! I have allready found stuff I wasn't aware existed and
>> > that I will probably have use for soon.
>> >
>> > 19 nov 2009 kl. 05.55 skrev Steve Schmechel:
>> >
>> >> It was rather sad to note that most of the "useful" libraries are
>> >> not covered in the Grok how-to's and tutorials.  Seems peculiar and
>> >> maybe we should think of ways to address that.
>> >
>> >
>> > I don't think we should get too worried about this right now. In it's
>> > current state, Grok suits developers who don't mind looking at the
>> > documentation availble in doctests and readme.txt files. I think we
>> > should be quite open with that.
>> >
>> > I don't see it as a flaw, but rather a characteristic of the framework.
>> >
>> > It is like unix, if you don't feel comfortable with a command prompt,
>> > you won't appreciate unix.
>> >
>> > Mvh Sebastian
>> >
>> > _______________________________________________
>> > Grok-dev mailing list
>> > Grok-dev at zope.org
>> > https://mail.zope.org/mailman/listinfo/grok-dev
>> >
>> _______________________________________________
>> Grok-dev mailing list
>> Grok-dev at zope.org
>> https://mail.zope.org/mailman/listinfo/grok-dev
>
>
>
> --
> Santiago Videla
> http://www.linkedin.com/in/svidela
>
> Sigue la mata dando de que hablar siempre abajo y a la izquierda donde el
> pensamiento que se hace corazón resplandece con la palabra sencilla y
> humilde que l at s tod at s somos.
>
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> https://mail.zope.org/mailman/listinfo/grok-dev
>
>