39 comments

[ 3.0 ms ] story [ 93.1 ms ] thread
The favicon is pretty amusing, once you've grokked Simplates. One notable feature is that Aspen now uses the Diesel non-blocking socket engine.
Using a character that one needs a tutorial on how to type AND isn't copyandpastable easily seems annoying...
Meh. Keeps out the riff-raff. ;^)
Ok, page updated to address this concern: http://aspen.io/form-feed/

:^)

The concern is really that it's a poor character to choose IMO, not that there isn't enough documentation on it :)
Personally, I appreciated the addition of the rationale.

The "revelation" about Barry Warsaw being an Emacs user won't be news to those who have visited his home page! http://barry.warsaw.us/elisp/

Ok, added links to Barry's site and to the Emacs docs: http://aspen.io/form-feed/
Wow, I had no idea that Emacs had commands specifically for navigating around the pages delimited by the form-feed character.

Going to see if I can find an Emacs mode that does the right thing in syntax highlighting the pages appropriately.

I'm hoping that nXhtml mode and its support for Multiple Major Modes might do the trick here http://ourcomments.org/Emacs/nXhtml/doc/nxhtml.html
Good find. "Another important feature is the ability to mix several languages in one buffer and get the correct syntax highlighting and indentation for each of them." It looks like they're inferring mode blocks based on things like "<?php>".

http://ourcomments.org/Emacs/nXhtml/doc/nxhtml.html#php

What is wanted for Aspen simplates is to use Python for the first two pages, and use the file extension to determine the mode/highlighting for the third page. The first two pages are optional.

Touche, sausagefeet. As evangineer mentions, I've upgraded the snark to a rationale: http://aspen.io/form-feed/

One idea would be to use an actual "^" "L", or at least give a warning somewhere if these are in a file.

Do you have any other ideas?

Nope, I'm just the peanut gallery :)

I do prefer the actual ^L though. I think sticking to printable characters and being copy and pastable from the web are good things for your project though, keep up the good work!

I think this is an incredibly innovative approach to web apps in Python, very fast dev turnaround and not a lot to grok.
It allows you to start off by sketching a webapp with Sinatra-like simplicity & get as complex & modular as needed.
I'm disappointed by the lack of discussion regarding the Simplates concept. It does for webapp code organisation what Python's whitespace does for code layout.

This means that from the outset, you get more maintainable webapps even it starts out as a one file hack. That should more than compensate for having to figure out how to enter an obscure character into your code in your editor/IDE of choice.

Thank you, yes! The tool support for ^L is weak right now, but if the simplates concept is valid then one hopes the tool support will follow.
Thanks for the link evangineer. Happy to answer any questions.
Hi.

For old Zope2 (and quixote) dev, looks promising and way easier than Django to get started on a project (and fun).

Could you maybe extend the tutorial with using tornado's template inheritance for basic page template. Like for repeating html, header, footer and perhaps navigation block. Tornado's documentation for that is in the template module so that kinda slows down the learning process.

I'll try this for my next project.

There's an IRC chat and a Google Group that you can check out when you start on your project. Both are linked directly from the home page on http://aspen.io
Google group was invite only, so HN was faster to get question across. I put my request in.

Templating page answered my question, thanks. Don't know how I managed to miss that... Perhaps you could add a link from the simplates page to it.

It didn't exist before you asked; I wrote it in response to your question. I've linked it from the simplates page and from the index.

Approved your gg request. Have to do that for anti-spam. :^/

@whit537, I really like how responsive you've been to questions and suggestions on this HN discussion. Gives one confidence that Aspen will be well maintained.
Thanks man. I've been sitting on aspen/simplates for years, and I think its time may have arrived.
I'm doing some weekend hacking using Aspen. I'm finding that Aspen is staying out of the way and any issues are actually my own shortcomings. Currently in the process of adding some Ajax to my web app.
On windows you would need to type [Alt]+0+1+2. The numbers have to be on the numeric pad, which on some laptops without that would include further function keys to be setup to type the character.

Some editors will accept this and display a [FF] representation (notepad2, notepad++). Others just don't work (eclipse, wordpad, notepad). gVim can still use [Ctrl]+L

This is a really bad choice if your code can only be edited by some text editors. Perhaps a secondary string to use for splitting in addition?

Does it depend on Windows, or on your editor? In seem to remember remapping ctrl-L to form feed in UltraEdit, for example ...
Seeing projects like this puts suggestion of hn quality going down to the back of my mind, really excited to try this out. Is there a framework which inspired this?
I evolved the page break discussion to talk about tool support and ugliness. Bottom line: "If you like simplates but dislike the page break, then you have until Aspen 1.0 to come up with something that works perfectly with existing tools /and/ isn’t ugly."

http://aspen.io/page-break/

Ok, Internet, how about this. I've added a page_break knob to aspen.conf so that you can override the ASCII page break default for your application.

http://aspen.io/aspen.conf/

Is that acceptable?