Skip to main content

Nevow of the Future

I am not a core Nevow developer, but am only a developer who uses it. I do talk a lot with the developers, and try to keep up with what is going on there. So, I do know a bit about what is going on, and where things are supposed to go. I know that contexts (a type of object passed around that gives access to the current tag being rendered, remembers adapters between interfaces, and does other stuff that isn't so good) is supposed to go away, eventually, at some point, somehow. There is little talk of how, when, and that sort of solid thinking on the subject.

So, for the heck of it, I'll propose a plan of action, and this is it.

Step #1
Fork it, so that all the refactoring can be done and if anyone needs a backward compatible Nevow, it can still be around for them. There is already xmantissa and xquotient, so it wouldn't be a stretch to add xnevow. My other favorite is to just say that Athena is the new Nevow (see Step #2)

Step #2
Pull everything out of the fork that Athena doesn't need, so things can be focused. Refactor so that there is no difference between Page and LivePage, and you can just make any page become live. At this point, things can start to change and context can be factored out entirely. New flatteners would be needed, of course, but those should be more or less straight forward to adapt.

Step #3
Expand the templating system to be smart enough to handle both server- and client-side work. I recommend a nevow:insert directive that defines sub-templates to fill and insert the resulting node at some place, which could replace nevow:pattern and also carry over for used in live pages on the client. While we're at it, add in some good widgets to start with, like containers and tabs and such.

Step #4
Create a fake nevow module that can map existing API calls to the new stuff that would be in xnevow/athena. This would allow for easier transitions to the new system.

I might try and convince the usefulness of this to an employeer and see if some of my project time can be spent sprucing up athena in such a way, depending on just how much this would take to be really useful, or just usable. Then I could contribue something useful, and get some moneys.

Comments

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

The Range of Content on Planet Python

I've gotten a number of requests lately to contribute only Python related material to the Planet Python feeds and to be honest these requests have both surprised and insulted me, but they've continued. I am pretty sure they've come from a very small number of people, but they have become consistent. This is probably because of my current habit of writing about NaNoWriMo every day and those who aren't interested not looking forward to having the rest of the month reading about my novel. Planet Python will be getting a feed of only relevant posts in the future, but I'm going to be honest: I am kind of upset about it. I don't care if anyone thinks it is unreasonable of me to be upset about it, because the truth is Planet Python means something to me. It was probably the first thing I did that I considered "being part of the community" when I submitted my meager RSS feed to be added some seven years ago. My blog and my name on the list of authors at Plan

Javascript Module Loaders Considered Harmful

Introduction I’m coming to an opinion of Javascript module loaders that is profoundly negative and I’d like to express why I think they are, generally, a bad idea. However, I do think they have a place, which I’ll get to at the end. Now, I understand I might be in the minority here. Between the competing specifications of CommonJS and AMD modules, loader systems like RequireJS or the (honestly really awesome) Google Module Server, and the huge cultural influence of Node on the Javascript world, you’d be hard pressed to argue against Javascript modules these days. Scripts are old hat, too stupid, too inflexible. Everyone knows that and no one would make an argument in their favor, right? I’m going to step out on a limb and say “Javascript Module Loaders Considered Harmful” and I know the baggage involved with declaring something “Considered Harmful”. I mean every ounce of context that phrase carries with it, and I hope I can persuade you. Harm #1: Confused Debuggers