No subject
Wed May 23 23:23:08 CEST 2007
<br>
page<br>
form<br>
tabs<br>
tab1<br>
tab2<br>
tab3<br>
form contents of tab pages<br>
div id contents<br>
div id tab1<br>
div id tab2<br>
div id tab3<br>
submit button<br>
<br>
The rest could only be CSS and a tiny bit of javascript, as you'd have<br>
to avoid sending back a request to the server, as you'd lose your<br>
entered data with it.<br>
<br>
The default CSS for this page would be<br>
<br>
div#contents > div { display: none; }<br>
div#tab1 { display: block; }<br>
<br>
to display only the first content page and hide the others.<br>
The links of the tabs would only need to update the style properties,<br>
e.g. by hiding all of them and displaying only their corresponding div.<br>
<br>
With this setup, you get the complete form with the original page load,<br>
you only see one tab page at a time, your browser remembers your entered<br>
data as you switch between tabs, and the final click on the submit<br>
button sends the complete form back to the server in one go.<br>
<br>
Now the question: Do WebTabs work this way?<br>
<br>
If not, you'd probably have to send the data back to the server<br>
piecewise, using onBlur event handlers, but this might become ugly<br>
quickly.<br>
<br>
Just making Smalltalk,</blockquote><div><br></div></div>Wow. At some point, I hope to start picking up the details of "how the web works," for when I need to drop down lower than the level of Aida (CSS, Javascript). For now, though, I am still trying to just figure out the Aida framework!<br>
<br>The solution Janko suggested is actually an Ajax one, built into the WebElements in the Aida framework. However, it sounds like if I had your background I might be able to troubleshoot why it is not working for me with my WebCheckBox(es)!<br>
<br>Thank you for the suggestions,<br><br>Rob<br>
------=_Part_18839_2730714.1213574266146--
More information about the Aida
mailing list