lvh / holtz Goto Github PK

holtz should serve things with the correct MIME type. There should be a way to resolve MIME types given a path (preferably a filepath).

Programmers want to have lots of different CSS/JS/... files because that makes them easy to work with. Browsers want to see one big file because that's easier/faster to download (although that might have caching consequences).

\.*\.css(+.*\.css)*\: Join() | Minify()

Basically this means that a request for admin.css+base.css would take admin.css and base.css, merge them

This might be a problem if any particular part of the pipeline insists that a file actually exists before it can be served. Also, processors only see the previous producer which kind of sucks. I suppose we could mandate that something like Join is the first in the chain. Otherwise we could make it a fundamental feature or something.

Note that there's other tickets that want this behavior too: #10.

It would be cool if we a request for foo.js would look up foo.cs and serve that, or something. Content type negotiation with browsers is too hard.

Holtz should have some elegant form of specifying configuration.

holtz should recognize whenever any of the assets it serves changes (note that this may also be because of a change in a different file; eg css or less imports). Once it detects such a change, it should inform whatever browser is looking at that page of the change, so that the browser can update the page.

Ideally this would be implemented using a bookmarklet.

Python 2.5 incompatibility might not be very important, but we really ought to support 2.6. Recently, tox support was added so verifying that it doesn't work is easy.

Almost all of the exceptions are this one:

exceptions.ValueError: zero length field name in format

So, basically, I think compatibility will be ensured if we just replace a bunch of {} with {0}.

Something like this:

One(...) | Two(...) | Three(...)

holtz should support less.

Similar to twisted.web.woven's directory lister, but with special holtz-specific mechanics, like showing what would be hidden and what wouldn't.

Processors should be implemented through twisted.plugin. There should be basic mechanics for that in place.

Part one of this is defining the IProcessor interface. Processors are at the very least consumers (consuming the output of the previous thing in the pipeline; since processors are not chainable right now, this is always a FileProducer). They either are or have a producer.