Ian Bicking wrote:

Certainly interesting ideas, though.  DHTML might be a better solution
to many of the problems of intermediate pages, though (i.e., use DHTML
to avoid intermediate, highly derivative pages).

The DHTML angle is very interesting and easy, if you ignore old browsers!

Not 10 minuted ago I wrote a JavaScript function that hints at the possibilities:

Here is a pseudo-mockup of client-side code:

<script>
//run this code aftetr page load:
var fname = document.createElement("TEXT");
hitEditButton.value = '%(user.FirstName)s';
hitEditButton.name = 'fname';
document.editForm.appendChild(fname);
//Add more fields...

function Step2(){
fname.style.display="none"
var addressfname = document.createElement("TEXT");
addressfname.value = '%(user.addressfname )s';
addressfname name = 'addressfname ';
document.editForm.appendChild(addressfname );
document.editForm.addressfname.focus()
...More fields here.
}

var step
step = 1
function goToNextStep(){
if (step ==1 )
if (fname has good data) {
Step2()
step = 2
}
if (step==2){
if (addressfname has good data){
either so a javascript submit() call or something like:
self.location="saveDataPage?uid=%(userID)s&_action_updateRecord=Yes&fname=escape(fname.value)


-Aaron




------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to