Randy said:
The Natural Philosopher said the following on 9/2/2007 6:05 AM:
If you have such a limited client base then I find it ironic that you
would list IE/Firefox/Opera/Safari as the target browsers. Reeks of the
"Oh, its an intranet" defense.
well the majority of users will be IE6, because they have PC's.
A few outside users will use whatever they have. Mainly IE6 on PC's an
safari on macs.
Opera is there because its one have for test purposes.
Not that "pixel perfect" mentality is it? People that use different
browsers expect the same page to look/act differently because it is a
different browser.
They may: I try not to. It doesn't take a huge amount of work to tie the
thing down to work reliably and predictably in all cases. Ive found
using pixel sizes, and specifying the correct font family families seems
to make it fairy bullet proof. What I want to avoid is gross
differences..stuff that bearely wors at all in a given browser.
I had a really ODD bug yesterday. Still not sure what caused it.
I had a couple of onclick() statements calling javascript routines of
VERY similar names..just the final few characters of the function name
were different. Safari refused to work on ONE routine. Until I changed
the routine name. Firefox was totally happy and reported no errors..
The PHP manual is definitely easier to navigate than a JS manual. And,
writing PHP for a wider audience of browsers is a lot simpler.
MM. Thats really where I got to as well. I have decided that the
internal stuff can be a bit clunkier and use as much native HTML as
possible whereas when I get to the customer facing stuff I'll spend more
time on it to tune it for super appearance.
Right now implementation speed is more an issue, so i've gone for a more
HTML based approach, just adding in script to make it a little more
obvious as to what is happening..
Where do you want the bulk of your processing happening? On the server
(along with server load) or on the client? If it is an intranet then you
can put the processing on the client and free up the server pretty
reliably if you control the client environment.
Mmm. Server probably. Although I have the javsacript manual and not the
php one,it already seems to me that the php is less impenetrable. And
less 'class based'. Coming from a strict C background that makes it a
bit faster for me to code. And at least, with php, there IS only one
interpreter that I have to code for...the one installed in the system!;-)