html php and firefox

What a winning combination.
Using the php coder from php.net I found out quickly that error checking is
a breeze.
Run and save the file, then load it with firefox and presto! Errors get
reported as they happen right in firefox.
Makes it easy because now you not only see the output, but exactly where in
the output the error is happening.

Richard

Richard wrote:
> What a winning combination.
> Using the php coder from php.net I found out quickly that error checking is
> a breeze.
> Run and save the file, then load it with firefox and presto! Errors get
> reported as they happen right in firefox.
> Makes it easy because now you not only see the output, but exactly where in
> the output the error is happening.
>
>

? hmmm yes. obviously.

--


x theSpaceGirl (miranda)

# lead designer @ http://www.dhnewmedia.com #
# remove NO SPAM to email, or use form on website #

"SpaceGirl" <> wrote
> Richard wrote:
> > What a winning combination.
> > Using the php coder from php.net I found out quickly that error checking
is
> > a breeze.
> > Run and save the file, then load it with firefox and presto! Errors get
> > reported as they happen right in firefox.

> ? hmmm yes. obviously.

One does wonder how a browser, any browser, even firefox, may be able to
determine if there are errors in the underlying server side PHP code.

Ah, yes, this is RtS at his best

"Richard" <Anonymous@127.001> wrote

> What a winning combination.
> Using the php coder from php.net I found out quickly that error checking
is
> a breeze.
> Run and save the file, then load it with firefox and presto! Errors get
> reported as they happen right in firefox.
> Makes it easy because now you not only see the output, but exactly where
in
> the output the error is happening.

Some of us write code that does not actually *have* errors.

Then again some of us don't just steal code at random form the net.

rf wrote:
> "SpaceGirl" <> wrote
>
>>Richard wrote:
>>
>>>What a winning combination.
>>>Using the php coder from php.net I found out quickly that error checking
>
> is
>
>>>a breeze.
>>>Run and save the file, then load it with firefox and presto! Errors get
>>>reported as they happen right in firefox.
>
>
>>? hmmm yes. obviously.
>
>
> One does wonder how a browser, any browser, even firefox, may be able to
> determine if there are errors in the underlying server side PHP code.
>
> Ah, yes, this is RtS at his best
>
>

I assumed he meant some javascripty thing. By default IE displays
"friendly errors" if something goes wrong in server side scripts.
FireFox doesn't, and actually displays the real message. Perhaps that's
what he meant? *shrug*

--


x theSpaceGirl (miranda)

# lead designer @ http://www.dhnewmedia.com #
# remove NO SPAM to email, or use form on website #

rf wrote:
> "Richard" <Anonymous@127.001> wrote
>
> > What a winning combination.
> > Using the php coder from php.net I found out quickly that error
checking
> is
> > a breeze.
> > Run and save the file, then load it with firefox and presto! Errors
get
> > reported as they happen right in firefox.
> > Makes it easy because now you not only see the output, but exactly
where
> in
> > the output the error is happening.
>
> Some of us write code that does not actually *have* errors.
>
> Then again some of us don't just steal code at random form the net.

If a program runs correctly first time it's not worth writing. I'm
sure someone said that years ago. Of course, that person was probably
a programmer, not an intellectually-challenged tosser like RtS.

--
Hywel

SpaceGirl wrote:
> rf wrote:
>> "SpaceGirl" <> wrote

>>>Richard wrote:

>>>>What a winning combination.
>>>>Using the php coder from php.net I found out quickly that error checking
>>>> is a breeze.
>>>>Run and save the file, then load it with firefox and presto! Errors get
>>>>reported as they happen right in firefox.

>>>? hmmm yes. obviously.

>> One does wonder how a browser, any browser, even firefox, may be able to
>> determine if there are errors in the underlying server side PHP code.

>> Ah, yes, this is RtS at his best

> I assumed he meant some javascripty thing. By default IE displays
> "friendly errors" if something goes wrong in server side scripts.
> FireFox doesn't, and actually displays the real message. Perhaps that's
> what he meant? *shrug*

I thought he was talking about some kind of DE or front end, and since
curiosity killed a cat, not a shark, I explored php.net and I couldn't
find anything that looked like a "php coder". I found, unsprisingly,
PHP. Zend has a plug there, but that's $250 worth, and I doubt that's
what he's talking about. Maybe you're right and he's just referring to
the Moz style of error reporting. Else, I'm stumped.

--
Blinky Linux Registered User 297263

Who has implemented Usenet Solution #45933:
Now killing all posts made with User-Agent G2

On Tue, 08 Feb 2005 10:50:26 GMT rf wrote:

> "SpaceGirl" <> wrote
>> Richard wrote:
>> > What a winning combination.
>> > Using the php coder from php.net I found out quickly that error
>> checking
> is
>> > a breeze.
>> > Run and save the file, then load it with firefox and presto! Errors
>> get
>> > reported as they happen right in firefox.

>> ? hmmm yes. obviously.

> One does wonder how a browser, any browser, even firefox, may be able
> to
> determine if there are errors in the underlying server side PHP code.

> Ah, yes, this is RtS at his best


Firefox only aids in reporting the errors.
I am assuming that the errors are generated by the "coder" and is shown in
the browser purely as a convenience to the user.

Unlike many others, I do give credit to those whose code I am using when
they are known.
Furthermore, like html, javascript is "public domain". Therefor, any one can
write a script for their use.
When someone comes along and screams, "Hey I've got a copyright on that
script and you're infringing on it", I say to them, so sue me. The only
thing original you created in javascript is perhaps a variable name. The
rest is not your original work.
Oh and before you go mouthing off, "well you can get copyrights on ......".
Sure you can. Because you have paid for a license that allows that.

Richard wrote:
> On Tue, 08 Feb 2005 10:50:26 GMT rf wrote:
>
>
>>"SpaceGirl" <> wrote
>>
>>>Richard wrote:
>>>
>>>>What a winning combination.
>>>>Using the php coder from php.net I found out quickly that error
>>>
>>>checking
>>
>>is
>>
>>>>a breeze.
>>>>Run and save the file, then load it with firefox and presto! Errors
>>>
>>>get
>>>
>>>>reported as they happen right in firefox.
>
>
>>>? hmmm yes. obviously.
>
>
>>One does wonder how a browser, any browser, even firefox, may be able
>>to
>>determine if there are errors in the underlying server side PHP code.
>
>
>>Ah, yes, this is RtS at his best
>
>
>
> Firefox only aids in reporting the errors.
> I am assuming that the errors are generated by the "coder" and is shown in
> the browser purely as a convenience to the user.
>
> Unlike many others, I do give credit to those whose code I am using when
> they are known.
> Furthermore, like html, javascript is "public domain". Therefor, any one can
> write a script for their use.
> When someone comes along and screams, "Hey I've got a copyright on that
> script and you're infringing on it", I say to them, so sue me. The only
> thing original you created in javascript is perhaps a variable name. The
> rest is not your original work.
> Oh and before you go mouthing off, "well you can get copyrights on ......".
> Sure you can. Because you have paid for a license that allows that.
>
>

Richard, that's a bit like saying you can't copyright a novel. After
all, it's just the same words all over again in a different order. It's
a really poor attitude to say "so sue me". It's this way of thinking
that kills off free resources as people dont feel obliged to help, or
offer anything for free.

Would you say the pages I designed over at www.subhuman.net is not
copyrightable? I wrote it all by hand, but it's all using HTML tags
which are public domain?

--


x theSpaceGirl (miranda)

# lead designer @ http://www.dhnewmedia.com #
# remove NO SPAM to email, or use form on website #

Richard wrote:

> On Tue, 08 Feb 2005 10:50:26 GMT rf wrote:
>
>> Ah, yes, this is RtS at his best

....
> Furthermore, like html, javascript is "public domain".

The *language* is free for all to use. Creations using it, by others,
are subject to usage constraints at the whim of the author.

> Therefor, any one can write a script for their [own] use.

Or, they can mark their *script* as public domain. If they do NOT, you
can't steal it.

> When someone comes along and screams, "Hey I've got a copyright on
> that script and you're infringing on it", I say to them, so sue me.

Somebody should.

> The only thing original you created in javascript is perhaps a
> variable name. The rest is not your original work.

Someday, you will learn. Oh, wait. Probably not.

> Oh and before you go mouthing off, "well you can get copyrights on
> ......". Sure you can. Because you have paid for a license that
> allows that.

Once again, one does not have to pay for a license. Weren't you paying
attention last week?

--
-bts
-This space intentionally left blank.