Psh. If it were Python...

Better idea from sjl:

actually, check upon startup and set a flag somewhere, then if it's not
successful you can skip highlighting the code so it doesn't break, and
display a warning like "syntax highlighting is not available because
pygments isn't installed"

Wow, that's definitely my run-on sentence of the day...

Might need to pass linenos parameter to pygments.

http://pygments.org/docs/formatters/

A side note here for ubuntu/debian users, use "apt-get install libxml2-utils" to install xmllint.

libxml2 for any Windows users, http://gnuwin32.sourceforge.net/packages/libxml2.htm

xmllint: http://code.google.com/p/xmllint/

I haven't tested either, but should be a good place to start.

I found there was a libxml2 formula for homebrew, which I used when installing. The documentation should be changed from 'brew install xmllint' to 'brew install libxml2'

Merged in, thanks!

I'm re-opening this for now... the UI needs to be made more consistent with the rest of the app (e.g. the labels)

Well, other text inputs don't have labels, so how do you want them to look? I thought abut using the "title" hack you're using for URL field but it doesn't seem a good fit and conflicts with default values.

Sorry, I was the one who rejected the change. I like the idea of URI templates but I want to reconsider the implementation.

I don't see any good use-case for dynamically making fields while typing in a URL... why not just put the values in the URL??

However, I do see another use-case:

API documentation for a website (such as Twitter) could use a link to Hurl with a URL parameter containing URI templates. Then Hurl could supply the input fields matching the URI template.

Hey Leah, thanks for commenting.

Now, your idea of sites providing the URI template in the URL to hurl.it is good:

http://hurl.it/?url=http://this.is/{some}/{template}

But I'm afraid it won't scale; the resulting hyperlink would be huge because URI templates are often very large and there's a possibility it might hit some limit of what a specific user agent could cram in a GET request. So my idea with this implementation was that the URI template itself is saved as a hurl—the resulting permalink is easy to share.

A drawback with my approach is exactly what you noticed: input fields appear dynamically, but someone who is entering this URI template doesn't have an intention of filling them in—he or she just wants to share the template with a nice permalink.

Proposed solution:
1. no input fields appear dynamically,
2. when the URL submitted to Hurl is a URI template, it is saved as a special Hurl and no external HTTP hits are performed at this point,
3. the special Hurl is shared and when you open it you are presented with input fields that populate the template (like in my screenshot),
4. once you fill in the fields and submit, the result gets processed and saved as a regular hurl (with response headers, body and such).

Thoughts?