Philip Ronan <in*****@invalid.invalid> wrote in message news:<BE6F4B0B.2D2A9%in*****@invalid.invalid>...
Paul Eden wrote:
I'm using input.htm to take some data using radio and a text field
from the user, which then "get"s them to update.php.
Now then, there is a lot of data to input, so i need to go back to
input.htm repeatedly
Then why don't you use a php file (let's call it "input.php") that submits
the data to itself. That way you can enter a new set of data straight away
while the server gets on with whatever process it has to do. If you like,
you can get the server to populate the form with the data you entered last
time you submitted it.
so, at the bottom of update.php, there is an
image which has a javascript onload command, that loads up update.php.
That sounds ugly. You've got a page that loads itself into an image? What
for?
You probably know where this is going by now? After a short while, I
end up with a screen full of browsers and it's annoying me.
Why is your screen full of browsers?
What is my best way forward here? Can I make pass the data from
input.htm to update.php without it firing up a new browser
Do you mean without opening a new window? This won't happen if you avoid
using javascript pop-ups and target attributes in your links.
or should
I be thinking about how to make update.php close itself after the
javascript onload has executed?
I don't understand what you're doing here. Sorry :-(
Any guidance on which route, or any other for that matter and how I
might implement them would be greatly appreciated
Could you provide a URL so we can see what you're trying to do?
Yeah, sorry. I'm not being very clear. Let me start again.
In a FPS game my clan plays and the game awards points. I wanted to
take the points awarded and make a league, so we could see who was
best.
So, I have input.htm, which has a form. Firstly, the user selects
which player they are entering a score for (radio button) then a
textspace to enter the score. When they click submit, input.htm sends
the playerid and score to update.php, which reads the player/score
datafile and writes it back to disk.
Now. update.php has, at the bottom of the page, an image, with a
javascript onload command that tells is to reload input.htm, as there
as more scores to enter.
The problem is, that the onload fires up a new browser, when I'd like
it to be in the same one. My current form of attack is to use the
<body close> as suggested earlier, to automatically close update.php.
This does sort of have the required effect, except that as the new
browser opens and the old one closes, it "marches" across the screen.
Obviously, this is pretty inelegant. Ideally, the java onload would be
told to use itself as a target browser.
