Z
Zebee Johnstone
In comp.lang.perl.misc on 28 Aug 2004 11:52:38 -0700
YUp, and you are getting a rather nasty education in how to do that
explanation...
Start again. THis time, explain what the problem is you are trying to
solve, and include all the detail you can.
You know what you want to do, but you don't know what bits are important
and what bits aren't. You don't know what things you are doing have an
effect. You didn't, for example, realise that doing it from a web page
might be important, so you didn't mention it. THere might be other
things that are important, but you don't know what they are, and they
might seem unimportant to you. But they might make all the difference
to the answers you get.
So, start with a description of the problem you are trying to solve.
NOt the perl one, the people one. When you sit down at the computer,
what do you want to do? What's the final outcome? For example, is it
that you want to be able to edit a file on the webserver?
Lets assume that's it, that you want to fire up notepad on a windows
server and edit a file that lives on that server. So your question
would be something like:
I have a Windows XP machine running IIS 5.0. There are files
on a website on that machine that I want to edit using something
like notepad.
What I want to happen is I open a webpage, push a button on the
page, and up pops a textpad with the file in it to edit.
So I started by having a perl script that has
<insert full script here, not just the line you are having
truble with, and be sure it includes use strict and use warnings>
in it, and calling that with http://my.server/perlscript.pl but
nothing appears on the page, and I get a lot of cmd processes
on the server box which I can't kill.
I think the problem is the open statement with the spaces.
YOu will probably get a bunch of people calling you an idiot for trying
to do what you are doing, welcome to usenet. You will also probably get
someone pointing you to a book or tutorial, someone suggesting you use a
textarea in the web page, someone explaining what's going on, someone
correcting your code showing why it didn't work, and so on. And in all
that, you will almost certainly get enough hints - no matter how badly
expressed - that you can go what you want to do.
Remember that people here are helping you out of the goodness of their
hearts. They owe you *nothing*. You hope like hell they've had a good
day and are willing to spend their own time and effort on a total
stranger who, 90% of the time, won't even say thanks. You can increase
your chances of someone having that good day by giving them the
information they need to work with. Which is a coherent description of
the big problem you are trying to solve as well as the small code one
that you are focused on right now. And do it in a way that someone who
knows nothing at all about your particular circumstances can understand
what's going on.
Oh, you will also get brownie points for asking what tutorials or
documentation deals with what you are trying to do. Because there
probably is at least one, and it might save a lot of heartache to read
it.
In your case, you might want to hop over to http://learn.perl.org/ and
check out the online library, there are books there that will help a lot
with terminology and especially how web and programs and such fit
together, which might help you a lot.
Zebee
Tony McGuire said:I've tried to explain what I am trying to do.
YUp, and you are getting a rather nasty education in how to do that
explanation...
Start again. THis time, explain what the problem is you are trying to
solve, and include all the detail you can.
You know what you want to do, but you don't know what bits are important
and what bits aren't. You don't know what things you are doing have an
effect. You didn't, for example, realise that doing it from a web page
might be important, so you didn't mention it. THere might be other
things that are important, but you don't know what they are, and they
might seem unimportant to you. But they might make all the difference
to the answers you get.
So, start with a description of the problem you are trying to solve.
NOt the perl one, the people one. When you sit down at the computer,
what do you want to do? What's the final outcome? For example, is it
that you want to be able to edit a file on the webserver?
Lets assume that's it, that you want to fire up notepad on a windows
server and edit a file that lives on that server. So your question
would be something like:
I have a Windows XP machine running IIS 5.0. There are files
on a website on that machine that I want to edit using something
like notepad.
What I want to happen is I open a webpage, push a button on the
page, and up pops a textpad with the file in it to edit.
So I started by having a perl script that has
<insert full script here, not just the line you are having
truble with, and be sure it includes use strict and use warnings>
in it, and calling that with http://my.server/perlscript.pl but
nothing appears on the page, and I get a lot of cmd processes
on the server box which I can't kill.
I think the problem is the open statement with the spaces.
YOu will probably get a bunch of people calling you an idiot for trying
to do what you are doing, welcome to usenet. You will also probably get
someone pointing you to a book or tutorial, someone suggesting you use a
textarea in the web page, someone explaining what's going on, someone
correcting your code showing why it didn't work, and so on. And in all
that, you will almost certainly get enough hints - no matter how badly
expressed - that you can go what you want to do.
Remember that people here are helping you out of the goodness of their
hearts. They owe you *nothing*. You hope like hell they've had a good
day and are willing to spend their own time and effort on a total
stranger who, 90% of the time, won't even say thanks. You can increase
your chances of someone having that good day by giving them the
information they need to work with. Which is a coherent description of
the big problem you are trying to solve as well as the small code one
that you are focused on right now. And do it in a way that someone who
knows nothing at all about your particular circumstances can understand
what's going on.
Oh, you will also get brownie points for asking what tutorials or
documentation deals with what you are trying to do. Because there
probably is at least one, and it might save a lot of heartache to read
it.
In your case, you might want to hop over to http://learn.perl.org/ and
check out the online library, there are books there that will help a lot
with terminology and especially how web and programs and such fit
together, which might help you a lot.
Zebee