Re: [PHP-DOC] [HEADSUP] New phpweb branch
On Mon, 1 Sep 2008, Daniel Convissor wrote: > > How does http://pb11.php.net/design/styles.html look to you? > > > Anyway, the main text is still very small, and now even smaller. :) It's > also tiny in IE 7. I think it's too small too. regards, Derick -- HEAD before 5_3!: http://tinyurl.com/6d2esb http://derickrethans.nl | http://ezcomponents.org | http://xdebug.org
Re: [PHP-DOC] [HEADSUP] New phpweb branch
Hi Hannes: > How does http://pb11.php.net/design/styles.html look to you? http://www.analysisandsolutions.com/php/web.feedback.styles.1.png I'm using Firefox 3.0.1. Oh, one thing that may have been throwing you off before about the size of the headers is I had the "minimum font size" set. I turned it off for the screen shot above. Sorry for any confusion about that. Anyway, the main text is still very small, and now even smaller. :) It's also tiny in IE 7. 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
Re: [PHP-DOC] [HEADSUP] New phpweb branch
""Hannes Magnusson"" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] How does http://pb11.php.net/design/styles.html look to you? -Hannes I have a few suggestions: * Apply cursor: help; to acronym and abbr * You could change the highlighting for a blockquote - give it a lighter background for example -just a preference. It's looking great at the moment though! -- Ross Masters [EMAIL PROTECTED] http://www.uvshock.co.uk/
Re: [PHP-DOC] [HEADSUP] New phpweb branch
On Mon, Sep 1, 2008 at 22:09, Daniel Convissor <[EMAIL PROTECTED]> wrote: >> The footer text size should not be the same size as the main content. >> The main content size should not be the same size as menu items. > > Agreed. Another misunderstanding. Ross and I were discussing the > "resets" done at the top of the CSS file and how that impacts the rest > of the document. How does http://pb11.php.net/design/styles.html look to you? -Hannes
Re: [PHP-DOC] [HEADSUP] New phpweb branch
Hi Hannes: > I had a very hard time understanding what you meant with "hard coding" > as it definitely wasn't *hardcoded*. Using % and ems is the way to go > exactly for this reason; give the user the choice of resizing. Yup. Email conversations are rife with misunderstandings. :) > >> If we didn't set font-sizes at all all text would be the same size > >> (assuming we're using a CSS Reset) which is pretty ugly :-) > > > > Perhaps I misunderstand what you mean by "all text would be the same > > size." I downloaded the home page and CSS from pb11, took out all CSS > > except the resets, then refreshed. The various header (h1, h2, etc) > > element sizes behaved normally (with h2 being larger than normal and h1 > > being larger than that, etc). > > The footer text size should not be the same size as the main content. > The main content size should not be the same size as menu items. Agreed. Another misunderstanding. Ross and I were discussing the "resets" done at the top of the CSS file and how that impacts the rest of the document. 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
Re: [PHP-DOC] [HEADSUP] New phpweb branch
Hi Ross: > Sorry if I came across rudely there, that wasn't my intention. No, didn't take it that way at all. Similarly, sorry if I came across harshly. > As far as I see it the best practice is to not set a font-size for the > body tag and to allow to use whatever it wants. Then apply > proportional (em) font-sizes to headings and such to make them scale with > the browser sizes. Then we are in agreement. :) Can the existing HTML/CSS please be adjusted to do that? Sorry to be passing the buck on this rather than providing a patch. I need to finish plastering my bedroom before my wife kills me. 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
Re: [PHP-DOC] [HEADSUP] New phpweb branch
On Mon, Sep 1, 2008 at 16:38, Daniel Convissor
<[EMAIL PROTECTED]> wrote:
> Hi Ross:
>
> On Sat, Aug 30, 2008 at 11:57:55AM +0100, Ross Masters wrote:
>> On Sat, Aug 30, 2008 at 05:04 AM, Daniel Convissor wrote:
>>
The font size is nowhere hardcoded. It uses em and %.
>>>
>>> That's hard coding. We shouldn't be setting it at all.
>>
>> It's not hard coding here. Let me explain:
>>
>> Using em measurements we can set a font to be proportionally bigger or
>> smaller than the font-size for it's container. For example:
>>
>> body { font-size: 0.75em; } /* Set all fonts to be 0.75 * the browser
>> size */
>> body h1 { font-size: 1.25em; } /* Set h1 elements to be 1.25 * it's
>> container */
>> body p { font-size: 1.00em; } /* Set p elements to be the same size as
>> it's container (0.75) */
>
> Exactly. Okay, let's stop arguing about semantics of the meaning of
> "hard coding."
I had a very hard time understanding what you meant with "hard coding"
as it definitely wasn't *hardcoded*. Using % and ems is the way to go
exactly for this reason; give the user the choice of resizing.
> The example you're giving me above is telling the browser
> to render the fonts to .75 of normal. I am firmly against any CSS
> telling the browser to render a page's main content in any size other
> than the browser's default.
Thats interesting. Firebug tells me the font size is 100%..
>> If we didn't set font-sizes at all all text would be the same size
>> (assuming we're using a CSS Reset) which is pretty ugly :-)
>
> Perhaps I misunderstand what you mean by "all text would be the same
> size." I downloaded the home page and CSS from pb11, took out all CSS
> except the resets, then refreshed. The various header (h1, h2, etc)
> element sizes behaved normally (with h2 being larger than normal and h1
> being larger than that, etc).
The footer text size should not be the same size as the main content.
The main content size should not be the same size as menu items.
...
-Hannes
Re: [PHP-DOC] [HEADSUP] New phpweb branch
Hi Dan, Sorry if I came across rudely there, that wasn't my intention. "Daniel Convissor" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] Allow me to elaborate on what I mean by "main content" to avoid further semantic discussions/misunderstandings. Setting navigational elements, side bars, footers, etc is totally cool. This can be done by directly specifying a font size for those particular elements. Setting the font size of the main text (the section on pb11's home page that starts with "The PHP development team would like to announce the immediate availability of PHP 4.4.9...") is unnecessary and undesirable. So, in the case of pb11, I respectfully request that the HTML an CSS be tweaked to put each page block/section into their own div/span/whatever then setting the font size for each particular section. So, for example, the home page would contian the following elements: * search * nav header * left side bar * main content (don't set the font-size for this one) * right side bar * footer Oh, by the way, the CSS at http://pb11.php.net/styles/style_uncompressed.css is setting the the body to 62.5%, not 0.75em (at least as of 10:30 New York time). As far as I see it the best practice is to not set a font-size for the body tag and to allow to use whatever it wants. Then apply proportional (em) font-sizes to headings and such to make them scale with the browser sizes. Again, hope I didn't come across wrongly :-) Regards, Ross -- Ross Masters [EMAIL PROTECTED] http://www.uvshock.co.uk/
Re: [PHP-DOC] [HEADSUP] New phpweb branch
Hi Ross:
On Sat, Aug 30, 2008 at 11:57:55AM +0100, Ross Masters wrote:
> On Sat, Aug 30, 2008 at 05:04 AM, Daniel Convissor wrote:
>
>>> The font size is nowhere hardcoded. It uses em and %.
>>
>> That's hard coding. We shouldn't be setting it at all.
>
> It's not hard coding here. Let me explain:
>
> Using em measurements we can set a font to be proportionally bigger or
> smaller than the font-size for it's container. For example:
>
> body { font-size: 0.75em; } /* Set all fonts to be 0.75 * the browser
> size */
> body h1 { font-size: 1.25em; } /* Set h1 elements to be 1.25 * it's
> container */
> body p { font-size: 1.00em; } /* Set p elements to be the same size as
> it's container (0.75) */
Exactly. Okay, let's stop arguing about semantics of the meaning of
"hard coding." The example you're giving me above is telling the browser
to render the fonts to .75 of normal. I am firmly against any CSS
telling the browser to render a page's main content in any size other
than the browser's default.
Allow me to elaborate on what I mean by "main content" to avoid further
semantic discussions/misunderstandings. Setting navigational elements,
side bars, footers, etc is totally cool. This can be done by directly
specifying a font size for those particular elements.
Setting the font size of the main text (the section on pb11's home page
that starts with "The PHP development team would like to announce the
immediate availability of PHP 4.4.9...") is unnecessary and undesirable.
So, in the case of pb11, I respectfully request that the HTML an CSS be
tweaked to put each page block/section into their own div/span/whatever
then setting the font size for each particular section. So, for example,
the home page would contian the following elements:
* search
* nav header
* left side bar
* main content (don't set the font-size for this one)
* right side bar
* footer
Oh, by the way, the CSS at
http://pb11.php.net/styles/style_uncompressed.css is setting the the body
to 62.5%, not 0.75em (at least as of 10:30 New York time).
> If the end user had a visual impairment they would set their browser's
> font sizes to a larger setting.
Which I do.
> Because our font sizes are proportional
> to that setting their view of the page has larger text than someone who's
> browser font-size is set to normal.
Yes, but the CSS is then setting it to 62.5% of my setting. So it's no
longer at my setting.
> If we didn't set font-sizes at all all text would be the same size
> (assuming we're using a CSS Reset) which is pretty ugly :-)
Perhaps I misunderstand what you mean by "all text would be the same
size." I downloaded the home page and CSS from pb11, took out all CSS
except the resets, then refreshed. The various header (h1, h2, etc)
element sizes behaved normally (with h2 being larger than normal and h1
being larger than that, etc).
Thank you,
--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
Re: [PHP-DOC] [HEADSUP] New phpweb branch
On Sat, Aug 30, 2008 at 05:04 AM, Daniel Convissor wrote:
The font size is nowhere hardcoded. It uses em and %.
That's hard coding. We shouldn't be setting it at all.
It's not hard coding here. Let me explain:
Using em measurements we can set a font to be proportionally bigger or
smaller than the font-size for it's container. For example:
body { font-size: 0.75em; } /* Set all fonts to be 0.75 * the browser size
*/
body h1 { font-size: 1.25em; } /* Set h1 elements to be 1.25 * it's
container */
body p { font-size: 1.00em; } /* Set p elements to be the same size as it's
container (0.75) */
If the end user had a visual impairment they would set their browser's font
sizes to a larger setting. Because our font sizes are proportional to that
setting their view of the page has larger text than someone who's browser
font-size is set to normal.
If we didn't set font-sizes at all all text would be the same size (assuming
we're using a CSS Reset) which is pretty ugly :-)
--
Ross Masters
http://www.uvshock.co.uk/
Re: [PHP-DOC] [HEADSUP] New phpweb branch
Hi Hannes: On Thu, Aug 28, 2008 at 08:40:24AM +0200, Hannes Magnusson wrote: > > The is rendered from the DocBook markup. In context then this is > the second heading of that section, which is why its rendered as Ah. Thanks. > The font size is nowhere hardcoded. It uses em and %. That's hard coding. We shouldn't be setting it at all. > > http://www.analysisandsolutions.com/php/web.feedback.1.png > > What happened to your browser? This is flat out wrong I trust you're ignoring the whole color thing. :) That's my color prefs. The layout is _all_ Firefox 3.0.1. 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
Re: [PHP-DOC] [HEADSUP] New phpweb branch
On Thu, Aug 28, 2008 at 05:06, Daniel Convissor <[EMAIL PROTECTED]> wrote: > Hi Guys: > >> http://pb11.php.net/sitemap.php > > Overall, looks good. Thanks. Two minor suggestions, please. > > There's a lot of white space in the area between the top of the page and > the header at the top of the main content section. Hmm, minor nit, > that really should be an but styled to be the desired size. The is rendered from the DocBook markup. In context then this is the second heading of that section, which is why its rendered as > > The main section's font size is too small. The font size should not be > hard coded. It should be left up to the user's broser preferences, which > is what the web is all about. The font size is nowhere hardcoded. It uses em and %. > Here's a screen shot of what I see: > http://www.analysisandsolutions.com/php/web.feedback.1.png What happened to your browser? This is flat out wrong -Hannes
Re: [PHP-DOC] [HEADSUP] New phpweb branch
Hi Guys: > http://pb11.php.net/sitemap.php Overall, looks good. Thanks. Two minor suggestions, please. There's a lot of white space in the area between the top of the page and the header at the top of the main content section. Hmm, minor nit, that really should be an but styled to be the desired size. The main section's font size is too small. The font size should not be hard coded. It should be left up to the user's broser preferences, which is what the web is all about. Here's a screen shot of what I see: http://www.analysisandsolutions.com/php/web.feedback.1.png Thank you again, --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
Re: [PHP-DOC] [HEADSUP] New phpweb branch
On Fri, Aug 22, 2008 at 15:01, Kian T. Gould - AOE media GmbH <[EMAIL PROTECTED]> wrote: > Hi Hannes > > Thanks for your e-mail, although design feedback is better to give, when > still designing and not when coding is done already :-) Do you want us to > mockup how the design could be adjusted slightly? > I don't think a full blown mockup is necessary, just minor tweaks to the existing CSS file.. It would be appreciate if you could at least look into it :) -Hannes
Re: [PHP-DOC] [HEADSUP] New phpweb branch
Thanks for the feedback, appreciate it (sending it to our designer..) :) -Hannes On Fri, Aug 22, 2008 at 10:46, G. T. Stresen-Reuter <[EMAIL PROTECTED]> wrote: > On Aug 22, 2008, at 1:39 AM, Jean-Sébastien Goupil wrote: > >> That looks like really nice for now. >> I have just few comments about the new design. >> >> Personally, the first thought I had was "Mmm, it looks like a little less >> professional, but looks like the new era of web". >> >> And I spent just 10 minutes browsing it, I have no idea how far you are >> with updating the design but I just want to tell you what I think: >> - the "code examples" don't stick out enough >> - and the user contribution looks like it's part of the actual >> documentation content (I don't think it's good?) > > I know my feedback is unsolicited so I'll try to make it as constructive as > possible... > > One principal of design is "contrast"[1]: make things sufficiently different > to communicate their difference in meaning. For example, headers are > sufficiently larger, bolder, or different in color so as to not be confused > with other text elements that follow. > > I think there are three facets of the existing design that are good examples > of contrast: >- the white space used between headings and body text; >- the light blue boxes on a white background for each section; >- the indenting of the Parameters section. > > I find that the contrast between elements in the new design is not > sufficient enough (for my weary, old eyes) and requires a tad bit more > mental focus to read. > > Also, I bumped up the size of the text in my browser by one notch and found > things much easier to read. The text size is _really_ small in Safari. > > Although personally I like the rounded corners and color scheme, I think > accessibility experts may find the lack of contrast between links and > background to be less than ideal.[2] > > I know "design by committee" is an exercise in frustration so I hope my > feedback isn't taken the wrong way and those responsible find *something* > valuable in these comments. > > Respectfully, > > Ted Stresen-Reuter > http://tedmasterweb.com > > [1] The design principal of "CRAP" was originally presented in Robin > William's The Non-Designer's Design Book and is partially reproduced here > > http://www.lifehack.org/articles/communication/design-better-with-crap.html > [2] http://juicystudio.com/services/csstest.php#contrast > http://anthonyshort.com.au/blog/comments/how-to-get-cross-browser-compatibility-everytime/ > > and > > http://960.gs/ > > I know I'm coming in late here so this really is FWIW...
Re: [PHP-DOC] [HEADSUP] New phpweb branch
Thanks for the feedback, appreciate it (sending it to our designer..) :) -Hannes On Fri, Aug 22, 2008 at 02:39, Jean-Sébastien Goupil <[EMAIL PROTECTED]> wrote: > That looks like really nice for now. > I have just few comments about the new design. > > Personally, the first thought I had was "Mmm, it looks like a little less > professional, but looks like the new era of web". > > And I spent just 10 minutes browsing it, I have no idea how far you are with > updating the design but I just want to tell you what I think: > - the "code examples" don't stick out enough > - and the user contribution looks like it's part of the actual > documentation content (I don't think it's good?) > > Unfortunately, I don't have free time to work on this > Anyway, that's a nice job :) > > > -Jean-Sébastien > > On Thu, Aug 21, 2008 at 1:24 PM, Maciek Sokolewicz <[EMAIL PROTECTED]> wrote: >> >> Hannes Magnusson wrote: >>> >>> On Wed, Aug 20, 2008 at 11:43, Jiania Hung <[EMAIL PROTECTED]> wrote: Sounds like good idea.if you need help,call me anytime.:) >>> >>> Going through the pages listed on http://pb11.php.net/sitemap.php and >>> upgrade them would be awesome. >>> Currently only the pages linked from the main-top-menu have been >>> upgraded (plus manual pages), with the exception of the download and >>> mailinglist pages (waiting for better designs on those two). >>> >>> Its an extremely easy upgrade procedure, see: >>> http://cvs.php.net/viewvc.cgi/phpweb/sites.php?r1=1.46&r2=1.46.2.1 and >>> http://cvs.php.net/viewvc.cgi/phpweb/links.php?r1=1.211&r2=1.211.2.1 >>> for instance. >>> >>> See include/layout.inc (bottom) for the definition of the functions. >>> >>> >>> I don't think you have phpweb karma, do you? >>> If not I'm sure we can hook you up after seeing a patch for few files. >>> >>> >>> Ones the basic stuff is completed (see links above) we can start >>> looking into what else needs/should to be done in terms of code >>> rewrite... >>> >>> -Hannes >> >> Wow, that looks awesome! If you need more hands, feel free to say so, I've >> got some free time in the next couple of weeks. >> >> - Tul > > > > -- > Jean-Sébastien Goupil > [EMAIL PROTECTED] > http://www.lookstrike.com >
Re: [PHP-DOC] [HEADSUP] New phpweb branch
I forgot to include links to two very useful pages about cross-platform HTML design: http://anthonyshort.com.au/blog/comments/how-to-get-cross-browser-compatibility-everytime/ and http://960.gs/ I know I'm coming in late here so this really is FWIW... Ted S-R
Re: [PHP-DOC] [HEADSUP] New phpweb branch
On Aug 22, 2008, at 1:39 AM, Jean-Sébastien Goupil wrote: That looks like really nice for now. I have just few comments about the new design. Personally, the first thought I had was "Mmm, it looks like a little less professional, but looks like the new era of web". And I spent just 10 minutes browsing it, I have no idea how far you are with updating the design but I just want to tell you what I think: - the "code examples" don't stick out enough - and the user contribution looks like it's part of the actual documentation content (I don't think it's good?) I know my feedback is unsolicited so I'll try to make it as constructive as possible... One principal of design is "contrast"[1]: make things sufficiently different to communicate their difference in meaning. For example, headers are sufficiently larger, bolder, or different in color so as to not be confused with other text elements that follow. I think there are three facets of the existing design that are good examples of contrast: - the white space used between headings and body text; - the light blue boxes on a white background for each section; - the indenting of the Parameters section. I find that the contrast between elements in the new design is not sufficient enough (for my weary, old eyes) and requires a tad bit more mental focus to read. Also, I bumped up the size of the text in my browser by one notch and found things much easier to read. The text size is _really_ small in Safari. Although personally I like the rounded corners and color scheme, I think accessibility experts may find the lack of contrast between links and background to be less than ideal.[2] I know "design by committee" is an exercise in frustration so I hope my feedback isn't taken the wrong way and those responsible find *something* valuable in these comments. Respectfully, Ted Stresen-Reuter http://tedmasterweb.com [1] The design principal of "CRAP" was originally presented in Robin William's The Non-Designer's Design Book and is partially reproduced here http://www.lifehack.org/articles/communication/design-better- with-crap.html [2] http://juicystudio.com/services/csstest.php#contrast
Re: [PHP-DOC] [HEADSUP] New phpweb branch
That looks like really nice for now. I have just few comments about the new design. Personally, the first thought I had was "Mmm, it looks like a little less professional, but looks like the new era of web". And I spent just 10 minutes browsing it, I have no idea how far you are with updating the design but I just want to tell you what I think: - the "code examples" don't stick out enough - and the user contribution looks like it's part of the actual documentation content (I don't think it's good?) Unfortunately, I don't have free time to work on this Anyway, that's a nice job :) -Jean-Sébastien On Thu, Aug 21, 2008 at 1:24 PM, Maciek Sokolewicz <[EMAIL PROTECTED]> wrote: > Hannes Magnusson wrote: > >> On Wed, Aug 20, 2008 at 11:43, Jiania Hung <[EMAIL PROTECTED]> wrote: >> >>> Sounds like good idea.if you need help,call me anytime.:) >>> >> >> Going through the pages listed on http://pb11.php.net/sitemap.php and >> upgrade them would be awesome. >> Currently only the pages linked from the main-top-menu have been >> upgraded (plus manual pages), with the exception of the download and >> mailinglist pages (waiting for better designs on those two). >> >> Its an extremely easy upgrade procedure, see: >> http://cvs.php.net/viewvc.cgi/phpweb/sites.php?r1=1.46&r2=1.46.2.1 and >> http://cvs.php.net/viewvc.cgi/phpweb/links.php?r1=1.211&r2=1.211.2.1 >> for instance. >> >> See include/layout.inc (bottom) for the definition of the functions. >> >> >> I don't think you have phpweb karma, do you? >> If not I'm sure we can hook you up after seeing a patch for few files. >> >> >> Ones the basic stuff is completed (see links above) we can start >> looking into what else needs/should to be done in terms of code >> rewrite... >> >> -Hannes >> > > Wow, that looks awesome! If you need more hands, feel free to say so, I've > got some free time in the next couple of weeks. > > - Tul > -- Jean-Sébastien Goupil [EMAIL PROTECTED] http://www.lookstrike.com
Re: [PHP-DOC] [HEADSUP] New phpweb branch
Hannes Magnusson wrote: On Wed, Aug 20, 2008 at 11:43, Jiania Hung <[EMAIL PROTECTED]> wrote: Sounds like good idea.if you need help,call me anytime.:) Going through the pages listed on http://pb11.php.net/sitemap.php and upgrade them would be awesome. Currently only the pages linked from the main-top-menu have been upgraded (plus manual pages), with the exception of the download and mailinglist pages (waiting for better designs on those two). Its an extremely easy upgrade procedure, see: http://cvs.php.net/viewvc.cgi/phpweb/sites.php?r1=1.46&r2=1.46.2.1 and http://cvs.php.net/viewvc.cgi/phpweb/links.php?r1=1.211&r2=1.211.2.1 for instance. See include/layout.inc (bottom) for the definition of the functions. I don't think you have phpweb karma, do you? If not I'm sure we can hook you up after seeing a patch for few files. Ones the basic stuff is completed (see links above) we can start looking into what else needs/should to be done in terms of code rewrite... -Hannes Wow, that looks awesome! If you need more hands, feel free to say so, I've got some free time in the next couple of weeks. - Tul
Re: [PHP-DOC] [HEADSUP] New phpweb branch
On Wed, Aug 20, 2008 at 11:43, Jiania Hung <[EMAIL PROTECTED]> wrote: > Sounds like good idea.if you need help,call me anytime.:) Going through the pages listed on http://pb11.php.net/sitemap.php and upgrade them would be awesome. Currently only the pages linked from the main-top-menu have been upgraded (plus manual pages), with the exception of the download and mailinglist pages (waiting for better designs on those two). Its an extremely easy upgrade procedure, see: http://cvs.php.net/viewvc.cgi/phpweb/sites.php?r1=1.46&r2=1.46.2.1 and http://cvs.php.net/viewvc.cgi/phpweb/links.php?r1=1.211&r2=1.211.2.1 for instance. See include/layout.inc (bottom) for the definition of the functions. I don't think you have phpweb karma, do you? If not I'm sure we can hook you up after seeing a patch for few files. Ones the basic stuff is completed (see links above) we can start looking into what else needs/should to be done in terms of code rewrite... -Hannes
Re: [PHP-DOC] [HEADSUP] New phpweb branch
Sounds like good idea.if you need help,call me anytime.:) 2008/8/19 Philip Olson <[EMAIL PROTECTED]> > That being said, I'd like to switch docs.php.net over to the new >> branch if there are no objections? >> > > > Sounds like a good idea. Also, let's work together on getting the new doc > box up and running... see you on IRC soon. :) > > Regards, > Philip > -- Jiania J Hung Interal SPL The PHP.net dev team * Mobile: +86 1352517 E-mail: [EMAIL PROTECTED] *
Re: [PHP-DOC] [HEADSUP] New phpweb branch
That being said, I'd like to switch docs.php.net over to the new branch if there are no objections? Sounds like a good idea. Also, let's work together on getting the new doc box up and running... see you on IRC soon. :) Regards, Philip
