Heya:
On Wed, May 12, 2010 at 01:49:25PM -0700, Philip Olson wrote:
>
> There's been talk of allowing expanded pages within the documentation.
> For example, this page:
> - http://php.net/manual/en/reference.pcre.pattern.syntax.php
Oh, wow! Hadn't seen the new layout.
Sorry to get off on a tangent, but... It seems we're largely naming them
for the characters used rather than the name of the functionality.
Seems kind of weird. Are those titles the text we always used? Maybe
yet another thing I never noticed. Wouldn't it be clearer if the
sections were given titles based on their functionality with the the
character names in parentheses?
> The basic idea would allow users to choose (for lack of a better term)
> "full page"
That could be handy in some situations.
> - User notes: Two solutions come to mind: A) Not show them B) Show them
> all, together, but with simple titled breaks.
I was about to say do A to keep things simple, but then I thought it
could be helpful to have them all there so people could similarly search
through all of them easily.
When it comes to adding comments on the expanded page, that would either
a) need to be turned off and put a note saying go to the section page to
add comments, or b) provide separate add comment links to each section
and have it clearly say that the comments are only for that given
section. While b sounds good, it will likely lead to confused users
putting comments in the wrong section.
> - How to generate: We'd likely generate these additional pages, but
could re-factor our PHP output to do, for example, includes
> - UI for users: A) A link on these pages, e.g., 'expanded' B) Set
default view type via my.php
Good.
> - Load the entire page in memory each time, using javascript to render
desired chunks? (possible, but sounds wrong)
Yeah, blech.
Thanks,
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
data intensive web and database programming
http://www.AnalysisAndSolutions.com/
4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409
