Re: cvs: php-bugs-web / bug.php style.css /include functions.inc

From: Date: Mon, 15 Dec 2003 22:43:03 +0000
Subject: Re: cvs: php-bugs-web / bug.php style.css /include functions.inc
References: 1 2 3 4 5  Groups: php.mirrors 
Request: Send a blank email to php-mirrors+get-22571@lists.php.net to get a copy of this message
On Mon, 15 Dec 2003, Gabor Hojtsy wrote: >>>>2. Don't you think that adding a monospaced font for the div would solve >>>>the whole problem (since that was the only problem with highlighting >>>>wasn't it?). >>> >>>Hm, well it was already in <code>, so it was fine monospaced... So what >>>was the problem with the highlighted version??? >> >> Unreadable, adds unnecessary overhead to the already high load, >> won't work for scripts without <?php ?>, doesn't make handling >> the reports any easier..etc.,etc.. > >Well, we have introduced highlighting to user notes and manual examples >lately, and the user not introduction proved that people tend to learn >and add the PHP start and end code if they see, that it is worth it. It >is not a question that if this feature is not available, then generally >there is not much point in adding the PHP start and end delimiters, >since everybody knows that we are talking about PHP. It doesn't make any difference if people learn or not, the old reports will still have the 'broken' code. >It is also true that it adds more HTML overhead. I still think that >people would find it useful to see colored examples where appropriate, >but I am not that heavy a user of the bug system, so I am not going to >push this further... It seems the patch also made the clickable urls not work anymore either. So don't push it. :) "If it works, DO NOT TOUCH IT!" :) --Jani

« previous php.mirrors (#22571) next »