Re: Proposal: add strikethrough effect to removed functions and gray out deprecated functions in function lists

From: Date: Tue, 12 Nov 2013 15:36:53 +0000
Subject: Re: Proposal: add strikethrough effect to removed functions and gray out deprecated functions in function lists
References: 1 2 3 4 5  Groups: php.doc 
Request: Send a blank email to phpdoc+get-969384730@lists.php.net to get a copy of this message
On 12 November 2013 15:29, Andrea Faulds <ajf@ajf.me> wrote: > > On 12/11/13 15:27, Sherif Ramadan wrote: > >> >> It doesn't make it obvious when the function was removed. It could end >> up being more confusing than helpful. Don't forget that php.net >> <http://php.net> also documents PECL extensions. >> I'm not sure how >> >> difficult it would be to pull that off trying to generate the CSS. >> > > Well, I think any confusion would hopefully be cleared up the moment > someone clicks the function name. > So long as we make it absolutely clear what the different colour/decoration means, I like the idea... in theory. If we can clearly communicate that greyed-out functions are deprecated and strike-through means removed "in the latest (numerically, not necessarily chronologically) stable release" (or wherever we drew the line), that would be nice. If we can't be absolutely clear and obvious what is meant by the different styling, I'd be hesitant to introduce it. Especially given we have loads of information readily available on the function page proper. P.S. Shouldn't these suggestions be being made for the "beta" site? > > I don't expect the CSS would be much of an issue. > > > -- > Andrea Faulds > http://ajf.me/ >

« previous php.doc (#969384730) next »