On Sun, Dec 4, 2011 at 5:25 PM, Jonathan Vanasco <[email protected]> wrote:
> Is akhet2 on your bitbucket ?  i've been planning on making a "sample
> application" that is mostly docs/reference of different ways to do
> things in pyramid - i'm trying to teach a few former colleagues it,
> and it would make sense to just open source it.

It's all in the Bitbucket repository. I've restructured the docs but
haven't deleted the scaffold files yet. I'm about 1/4 or 1/3 the way
through rewriting the docs. The new docs are based on Pyramid's
'alchemy' scaffold (in Pyramid 1.3-dev; same as the 'routesalchemy'
scaffold in Pyramid 1.2). Each Akhet feature will have a section
showing how to add it to an 'alchemy' application. I'll also discuss
alternatives to the Akhet features (e.g., @view_config,
config.add_static_view, and some PyPI packages), and the tradeoffs
between them.

There may be a tarball of modules for those who want to drop them in
to their 'alchemy' application rather than pasting the code. I think
that can be done by making a tarball for the inside of the Python
package (ZZz/zzz), using relative imports as the built-in scaffolds
now do, plus separate downloads for development.ini and the setup.py
dependencies. But I have to finish the docs and try it out to see if
it'll work.

Maintaining a scaffold turned out to be too much work. It was either
do this or retire Akhet completely. Because I get bug reports and
feature requests for the scaffold, or the Pyramid standards change,
and every little update or troubleshooting requires: change some code,
install it, create an application, install it, test the app, test some
more URLs, make changes directly in the app and then remember to
propagate them to the Akhet source, or make changes to the Akhet
source and then have to generate another app...  That plus the
limitations of the scaffold API just drive me up the wall. It's much
easier to just write docs and provide a tarball.

-- 
Mike Orr <[email protected]>

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en.

Reply via email to