morrisonlevi / web-php Goto Github PK

Discussion points:

• Client Side vs Server Side
• Choice of Library

Other points to consider:

• User comments and documentation use different highlighters, ideally these will want to be highlighted using the same source.

This breaks pretty regularly on live PHP.net. I don't want this happening for our rebuild.

Copying to the clipboard can be done in modern browsers with JavaScript's document.execCommand('copy', ...) which will copy the current selection. I'm not sure the way to feature detect support.

Essentially when a user clicks the button we need to highlight the code snippet and then copy it.

Do not use a php file; see https://bugs.php.net/bug.php?id=73813 (though that firewall is stupid).

I think our current SVG logo has issues with IE and scaling; it may be as simple as adding <view viewBox="24 12 192 96" /> to get it to work.

Maybe align it to the right (but not float it).

old italian translations (some are php 5.0 old) keep appearing on google results

in the past i asked on bugs.php.net to disable the localization but it was only removed from the selectbox, which basically solved nothing

i believe this is a problem for many other locales, because people are actually looking how to disable results from php.net that aren't in english

can we do this?

Currently:

public string Qux::foo( string $baz , string $bar )

Should be (kinda):

public function /* Qux:: */ foo(string $baz , string $bar) : string, throws WhateverException;

It's often hard to figure out (or it's even not specified) that methods throw.
Exceptions aren't less important than return, so they must be documented just as well.

(unless the func takes 0 args)

Leaves a lot of "not good looking empty space" on the right, on larger resolutions, but it's way more comfortable to read. Methods within class synopsis (eg the methods listed here http://php.net/manual/en/class.intltimezone.php) may continue to stay on one line each.

The mechanism that generates manual-lookup.sqlite is old and somewhat broken.

For example, for APIs with both OOP/procedural commands, it does not find the procedural variant. For example, it finds mysqli::select_db() but not mysqli_select_db().

It's been a long time since I looked into it, but I vaguely also remember other problems and concerns.

public string getErrorMessage ( void ) 

should be converted to

public function getErrorMessage(): string

or even brackets around optional parameters, etc.

The php syntax alone is enough to describe itself, there is no need for stuff that belongs to other languages. In fact, i'm sure that the manual syntax not matching php's, makes thing more difficult for novices.

The current user notes contain people starting their notes with: "In response to", "to clarify foo's message" etc.

Maybe we can provide a way to actually reply to an existing user note and either have levels or some either way to display the relation to the parent.

Hi,

that's @nikic's idea but I think it's good and deserves to be discussed here:

A somewhat related point: The manual currently does not really distinguish
between core extensions and PECL extensions. The only real indication you
get is a small (PECL xxx >= yyy) in the version line, otherwise it might as
well be a core function. This is suboptimal, because a very large fraction
of PHP developers is limited to the use of core extensions, and it's not
possible to see at a glance which is which. I'd like to see a much larger
distinction here. "Large" on the order of switching the header from green
to blue and replacing the "php" logo with "pecl".

http://news.php.net/php.doc/969386436

For now, let's assume it's possible on the side of docs rendering (I think it actually is). What do you think? If you think a general idea is good, how should it be implemented?