[UPHPU] web-based project management software

[Richard K Miller]

On Nov 10, 2006, at 1:15 PM, Wade Preston Shearer wrote:

>> I think you missed Wade's point.  Cross-browser compatibility is not
>> another task to do which requires a priority.  It is just  
>> something you
>> need to consider when doing your initial development.  It doesn't  
>> have
>> to require much more time at all.
>>
>> Don't just blow through an IE only design, just to find out later you
>> have to rework the whole thing to get it to work with standard  
>> browsers.
>>  That kind of development may save you a small fraction of time in  
>> the
>> beginning, but waste a great many hours later getting your IE hack  
>> job
>> to work in the rest of the worlds browsers.
>>
>> Save time and design your applications to standards that work
>> everywhere.  Don't think of Cross-browser compatibility as a  
>> step.  It
>> is only a concern to have, like coding standards, design goals, etc.
>
> That's exactly what I was trying to say.
>

The problem I commonly find is that IE doesn't fully implement the  
standards.  I shoot for clean, intelligent, semantic markup using my  
default browser Safari, occasionally checking in Firefox, and then  
someone on IE will say it doesn't work for them.  Therefore, as the  
developer, I can't use <q> tags; I can't use advanced CSS  
like :child; if I popup a graph, the form elements behind it bleed  
through; IE7 won't ignore the self-signed certificates on my dev  
machine, and on and on...

I need Firefox and Safari plugins that reduce their functionality to  
the lowest common denominator of their competitor so I don't shoot so  
high.  :)