[albatross-users] ctx.req_equals() question.

[Andrew McNamara]

>Okay, I'll try the ".x" part.  Hopefully that will work and not run into
>the other req_equals issue I'm having.  I do think it's a bit counter
>intuitive, to work this way.  I had assumed that mybutton was a 2 arg
>tuple od (x,y) since that's what it returns as ctx.locals.mybutton.

Yep - I'll agree it's a wart. It's this way because ctx.req_equals is
a thin veneer over the Request class, which, in turn, is a thin veneer
over the standard library cgi.FieldStorage class.

I'm forever coming up with schemes to hide this behaviour in my
apps. Albatross should help - maybe ctx.req_equals should check for the
.x form? This would be a compatibility problem, however. Any preferences?

>It's great that there is a lot of documentation, but the layout is very
>hard to use for reference.  I would expect this under 5.1.2.7 <al-input
>type="image"> rather than 4.3 The Popview App.  Input file was the same
>way, I had to play around with it to figure out how to access the data
>sent.

Good point - we'll try to address this in the next release. All
suggestions for improving Albatross are gratefully received... 8-)

>BTW, how is this abusing html?  This is how you would implement
>server-side image maps, and is nothing new.  It's also the basis of how
>prev and next buttons.

I guess it's abusing the spirit of HTML, rather than any technical
problem.  HTML 4 (I think) added explicit button inputs, but they require
javascript to be enabled to work, which sort of defeats the purpose.

-- 
Andrew McNamara, Senior Developer, Object Craft
http://www.object-craft.com.au/