|Jason||QML HSpan HPanecan someone give me an example of these tags in context?||2012-03-24||9:09 AM|
|Brandon||Re:QML HSpan HPaneNo one has used them, as no current QML browser supports them. But Pharaoh would probably know how he imagined them to work, as he wrote the spec.||2012-03-24||9:37 AM|
|Jason||Re:QML HSpan HPaneyeah i was reading it for, oh, no reason...|
here we are boys.
|pharoah||Re:QML HSpan HPaneIIRC, the idea behind the hpanes was that they'd handle mult-column layouts. One hspan would be like a single row of an HTML table, and there would be one or more fixed-width hpanes (like cells) within them. This solves the problem of trying to make multi-column layouts without knowing whether the QML reader will add extra text onto the end of links, forms, and other things that would screw up the columns if you tried to align them yourself.||2012-03-24||10:09 PM|
|Jason||Re:QML GET FormI was reading the spec and I find a strange inconsistency between browsers. The syntax is [name>target. Most browsers seem to ignore the name argument. QBrowse seems to be the only reader that displays it. And if this is new news to you, and you're going to implement it, (ha) is there a line break after the GET Form name is printed?|
wow we posted nearly at the same time.
have you ever used it in your pages?
|pharoah||Re:QML HSpan HPaneThe form name is for "out-of-page" rendering of forms using a set of successive prompts (the way QBrowse 0.7 does it). It was intended to be an easier way to put forms in if you didn't want to get the interface details of in-page rendering working. The plan was for the name to display as a link with no line break, as it does in QBrowse IIRC.||2012-03-25||12:09 AM|
|Jason||Re:QML HSpan HPaneohh ok i'll make an option in the preferences.||2012-03-25||1:20 AM|
2021 Brandon Cornell
: Uncaught Error: Call to a member function close() on null in /homepages/11/d157582457/htdocs/mblog/footer.php:20
#0 /homepages/11/d157582457/htdocs/mblog/forum.php(88): include()
thrown in /homepages/11/d157582457/htdocs/mblog/footer.php on line 20