Luke, Good point, this list is set up different in that "Reply" ONLY replies to the individual poster, not the list. Have to use "reply to all".
I have added the list address to this post. To all concerned, this thread contains some "off list" conversation that may be of interest, particularly to the original poster. Luke, I agree, both methods will probably work well, as you said, 'depending on the situation'. To expand on the issue of retrieving previously posted data into a multi-tabbed form. In this case, I would normally show the user a list of previous posts or perform a search. Selecting a previous post would load the form with the historical data to allow reviewing one tab at a time. Just like loading any normal edit/view form, but with the tabs breaking up the form into individual "parts" of the same record. Edits and updates are performed and posted using a similar process to the original post but using an UPDATE WHERE instead of an INSERT INTO statement. List, Sorry if this post is ugly. Delete as necessary. > -----Original Message----- > From: Luke Skywalker [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 16, 2003 9:19 PM > To: [EMAIL PROTECTED] > Subject: Re: [PHP-DB] Saving state > > > Yeah, i got ya, totally different concept, i was thinking the > tabs would be > like > |previous calls|add a call|statistics| (just an example) > > but i now know what you mean with hiding/showing the sections > thats a good > idea if its only for submitting, but what if they want to go > to a previous > calls tab (like i have there) all the previously submitted > calls wont be > still held in the form data > > and i havent used any query strings in my example, to pass > the values from > each form id use the form post and submit it with javascript, > so all the > values (including the hidden ones) are available through > $_POST['hiddenfieldname'] > > I think we have two different concepts entirely, i think > yours would work, > and mine would work, depending on the circumstances :) > > Maybe we should be posting this thread to the mailing list? > > Luke > ----- Original Message ----- > From: "Duane Lakoduk" <[EMAIL PROTECTED]> > To: "'Luke Skywalker'" <[EMAIL PROTECTED]> > Sent: Wednesday, September 17, 2003 12:04 PM > Subject: RE: [PHP-DB] Saving state > > > > Yes, I think so. Are you using the querystring to pass the > name=value > pairs > > for each form? If so, you could run into a querystring > length problem if > > the form is large. Let me know if I got this part right. > > > > The method that uses the tabbed form never posts the data > until you are > > completely done filling all tabs. These are not different > pages, I am > using > > DHTML to hide each successive tab. Simply hiding that tab > form data and > > exposing the next. Completing the part of the form on each > tab, then > click > > submit only when completed on all tabs. Note: each tab is > only a "part" > of > > the complete form. The form data is only submitted once > all tabs (parts > of > > the form) are complete. Make sense? > > > > Duane > > > > > > > -----Original Message----- > > > From: Luke Skywalker [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, September 16, 2003 8:52 PM > > > To: [EMAIL PROTECTED] > > > Subject: Re: [PHP-DB] Saving state > > > > > > > > > Yeah, i think i understand what you mean, the one form > used on each > > > different page, but Shiloh would have to transfer the > > > information from page > > > to page, and what would happen if a user wanted to click from > > > tab to tab the > > > tabs at the top of teh page (or side or wherever) would not > > > be forms, so the > > > information wouldnt be submitted to them, and hed have to > > > requery to get the > > > information back? but if the javascript code submits the > > > information to the > > > next page (and that javascript code can be assigned to any > > > hyperlink, thus > > > effectively turning any link into a submit button) do you > > > know what i mean? > > > > > > and yeah it is strange that you havent seen your post yet, it > > > has been sent > > > to the list, as i saw it there :/ > > > > > > Luke > > > ----- Original Message ----- > > > From: "Duane Lakoduk" <[EMAIL PROTECTED]> > > > To: "'Luke Skywalker'" <[EMAIL PROTECTED]> > > > Sent: Wednesday, September 17, 2003 11:43 AM > > > Subject: RE: [PHP-DB] Saving state > > > > > > > > > > Luke, > > > > > > > > I think you may have this out of sequence. I was replying > > > to Shiloh's > > > post. > > > > I commented on the hidden field process as well. I use > > > that for some > > > other > > > > forms and info pulled from Exchange or the Account SAM > > > database. I like > > > the > > > > tabbed approach as it is just one form regardless of the > > > number of tabs. > > > > Really have to look at these on a case by case basis. > > > > > > > > On another note, I haven't even gotten my own post to the > > > forum yet that > > > > you are replying to. Odd huh? > > > > > > > > > > > > Thanks > > > > > > > > > -----Original Message----- > > > > > From: Luke Skywalker [mailto:[EMAIL PROTECTED] > > > > > Sent: Tuesday, September 16, 2003 8:27 PM > > > > > To: [EMAIL PROTECTED] > > > > > Subject: Re: [PHP-DB] Saving state > > > > > > > > > > > > > > > Just something to keep in mind, if your users will support > > > > > JavaScript and > > > > > you want to submit the information from page to page, you can > > > > > keep all the > > > > > information in hidden form fields...and the easiest way to > > > > > transfer it is > > > > > using > > > > > > > > > > <a href="#" onClick="transferInfo('<?php echo $tabID; > > > ?>')">Transfer > > > > > Information</a> > > > > > > > > > > and include this in the page head > > > > > > > > > > <script language="JavaScript"> > > > > > <!--//hide code > > > > > function transferInfo(tabID){ > > > > > //this changes the page the form submits to > > > > > > > > > > document.invisibleform.action="tabs.php?tab="+tabID+"&otherarg > > > > > s=something"; > > > > > document.invisibleform.submit(); > > > > > } > > > > > //--> > > > > > </script> > > > > > > > > > > ive used that method for transferring invisible information > > > > > using hyperlinks > > > > > instead of having to greate forms everywhere with > submit buttons > > > > > > > > > > do you think that would work in your case? > > > > > > > > > > Luke > > > > > > > > > > ----- Original Message ----- > > > > > From: "Duane Lakoduk" <[EMAIL PROTECTED]> > > > > > To: "'Shiloh Madsen'" <[EMAIL PROTECTED]>; > > > > > <[EMAIL PROTECTED]> > > > > > Sent: Wednesday, September 17, 2003 11:10 AM > > > > > Subject: RE: [PHP-DB] Saving state > > > > > > > > > > > > > > > > > From: Shiloh Madsen [mailto:[EMAIL PROTECTED] > > > > > > > > > > > > > > Sorry about the cross posting, as im not exactly sure what > > > > > > > would be the best method to handle this, but im > trying to set > > > > > > > up a web application with a tabbed interface. > Each tab will > > > > > > > have a form to enter data, and the requisite save and > > > > > > > continue button. Heres where things get hard > though. I want > > > > > > > to be able to allow users to click on a previous tab to > > > > > > > refrence, change, update, etc the information on > those tabs. > > > > > > > How do i save the state of these tabs so that they can be > > > > > > > reaccessed? Just so you have a little more information, im > > > > > > > trying to make a kinda simple call logging system with a > > > > > > > customer tab which would hold customer info and a > calls tab > > > > > > > which would store call info and allow you to > switch between > > > > > > > call records. all of this data would be stored in > a database, > > > > > > > but i dont want to actually have to send a new > query to the > > > > > > > database just because the user clicked on a > previous tab...if > > > > > > > this would be possible. Also, if anyone has an > idea as to how > > > > > > > i can implement this a bit more intelligently, im open to > > > > > > > suggestions, but the tabbed interface seemed to > be the most > > > > > > > user friendly. And yes, the web interface is > important, which > > > > > > > is why im not trying to do it in c++ or something > like that. > > > > > > > > > > > > > > Shiloh > > > > > > > > > > > > > > > > > > > > > > > > > I have done this using multiple hidden <div> tables </div>. > > > > > Works well for > > > > > > large forms when you want to show only a small piece of it > > > > > at a time. Each > > > > > > tab exposes the current div table and hides the remaining > > > > > tables. No need > > > > > > to save state because all data is on one form. It is just > > > > > hidden from > > > > > view > > > > > > until you get to the final tab and submit. If you > are using any > > > > > drop-downs > > > > > > <select> tags, you will need to set their visibility to > > > > > 'none' along with > > > > > > that table because of their inherent visibilty over all > > > other html. > > > > > > > > > > > > I have also seen this done using successive forms, posting > > > > > one form to the > > > > > > next and creating hidden fields to save the data from one > > > > > form to the > > > > > next. > > > > > > This might be hard to handle though if you want to move > > > forward and > > > > > backward > > > > > > at will. > > > > > > > > > > > > > > > > > > Duane > > > > > > > > > > > > -- > > > > > > PHP Database Mailing List (http://www.php.net/) > > > > > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > > > > > > > > > > > > > > > > > > > > > > -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
