You cannot post messages because only members can post, and you are not currently a member.
Description:
User support for the Aspen web server.
|
|
|
0.18.11: Single-file web apps
|
| |
All,
I discovered recently that, as a nice side-effect of switching to Python
for the configuration file syntax, Aspen can now be used to write
single-file web apps. This is something one sees promoted in lightweight
frameworks like Flask and CherryPy. Since Aspen depends so heavily on the
filesystem for URL dispatch an Aspen site can end up with a fair number of... more »
|
|
|
philosophy of 1.0
|
| |
All,
I've been reading Eric Raymond's *The Cathedral and the Bazaar*, and this
passage jumped out at me:
"In the closed-source world, Version 1.0 means: 'Don't touch this if you're
prudent.' In the open-source world, it reads something more like: 'The
developers are willing to bet their reputations on this'" [95].... more »
|
|
|
sprint tonight
|
| |
Hey all,
Pat Collins and I are going to be sprinting on Aspen this evening. We're
meeting at 6:00 at MAYA in Pittsburgh, where Pat works:
[link]
You can also join us on IRC:
irc://irc.freenode.net/#aspen
chad
|
|
|
Aspen 1.0 bumped to June 3
|
| |
Folks,
The Aspen 1.0 release, which was scheduled for tomorrow, May 5, is now
scheduled for Sunday, June 3.
Aspen saw major progress towards 1.0 over the past two months. The
request/response API, unicode support, and hooks and configuration systems
have all seen great improvements. Additionally, Aspen added two significant... more »
|
|
|
Jinja2 simplates todo
|
| |
Hi.
I wrote a basic Jinja2 simplate renderer (see below). I'd like to clarify
some things before I submit a pull request.
- how to decide template encoding? is it configuration's dynamic encoding
or what?
- how to implement error handling and pretty error messages?
-> with my current implementation tracebacks go to server console... more »
|
|
|
Simplate awereness
|
| |
Hi. Decided to take new Aspen version for a spin. I have to say it was a delight to rapidly develop my project. Documentation was for the most part top notch. I think the JSON simplate might be the best way to develop a Javascript only, client side web app. JSON API with REST kind of naturally flows with the filesystem paradigm. And your hard work with Unicode support... more »
|
|
|
aspen
|
| |
Dusty, Sweet, thank you! I've linked it from the homepage. Paul Jimenez (copied here) wrote an HTTP Digest integration which I've uploaded along with my broken old cookie module here: [link] I've been keeping design docs on sync.in, here's a few notes on auth design:... more »
|
|
|
Aspen runs on Jython
|
| |
Hey all, As of 0.14.2, Aspen runs on Jython. This means you have access to Java libraries from the most developer-friendly web framework around. Yay! Let us know if you do something cool with Aspen and Jython. chad
|
|
|
Aspen 1.0 planning
|
| |
Hey all, Aspen 1.0 is scheduled to be released on May 5, less than seven weeks from now. The major goal with this release is to solidify the API and documentation. Here's the milestone on Github<[link]> . Basically: - Solidify the API of the objects available inside simplates--request,... more »
|
|
|
Passing a dynamic name for a template into a simplate
|
| |
Hi All, Does anyone know if or how one can pass in a dynamic name of a template to a Aspen simplate page vs it being hard coded on a simplate page? Currently the way I have been doing this is in the 3rd ^L page {% include projectTemplate2.tpl %} What I would like to do is in the second ^L do something like... more »
|
|
|
