Re: [pygame] Improving pygame web docs
Hmm, I guess part of the problem for me is that it is fixed width in size - and I have a rather wide monitor, so I just see a lot of the texture on both sides, which is annoying. Slightly smaller circles (or rather larger, like 60 pixels maybe?) circles would be better I think - but mainly allow the site to be larger in width, I think... On Fri, Jul 31, 2009 at 10:28 PM, Brian Fisher wrote: > I really didn't notice the background myself, so I don't think it's a > problem. > > What does actually bug me though, is the project list down the right side. > I appreciate wanting to make the project listings a focus of the site, but > it's taking up space and distracting from the focus of a page where I told > you by clicking on things that what I want to do right now is read > documentation. Plus it makes stuff weirdly off center as I scroll down. > > > > On Fri, Jul 31, 2009 at 2:20 PM, Devon Scott-Tunkin > wrote: > >> >> "The background is too busy, IMHO" >> >> I thought it looked good, but I can see how it is busy with such a large >> texture repetition, although it doesn't seem to negatively effect me when >> using the site. The plain gradient was too boring for me, at least when it >> was the extreme colors it used to be. Perhaps I am too attached to the >> effect of layering two backgrounds over each other. Yay css :). >> >> Do you think larger or smaller circles would look better, or perhaps even >> more transparency? Or can you suggest a different texture, I thought circles >> were fun and reminded me of snake skin. Both perfect for pygame. >> >> Devon >> >> >> --- On Thu, 7/30/09, RB[0] wrote: >> >> > From: RB[0] >> > Subject: Re: [pygame] Improving pygame web docs >> > To: pygame-users@seul.org >> > Date: Thursday, July 30, 2009, 9:19 PM >> > The background is too busy, IMHO >> > And I agree with what greg wrote... >> > Otherwise, looking good :) >> > >> > On Thu, Jul 30, 2009 at 7:55 PM, >> > Greg Ewing >> > wrote: >> > >> > jug wrote: >> > >> > >> > >> > >> > http://pygameweb.no-ip.org/docs/surface.html >> > ist not really easy to read, but I don't know exactly >> > why. >> > >> > >> > >> > >> > It looks all right to me, except for one thing: Every >> > >> > link to the docs for a method embedded in the text >> > >> > seems to be followed by a comment in small print, e.g. >> > >> > in the paragraph about Surface.convert, >> > >> > >> > >> > ...arguments can be used, similar to the >> > >> > pygame.Surface - [pygame object for representing >> > >> > images] call... >> > >> > >> > >> > IMO these embedded comments are pointless and >> > >> > distracting and make the text hard to read. Just >> > >> > make the method name into a link and leave it at >> > >> > that. >> > >> > >> > >> > Also a minor suggestion would be to leave some >> > >> > space between the heading for a method and its >> > >> > call prototypes, and between the prototypes and the >> > >> > following text, e.g. instead of >> > >> > >> > >> > Surface.convert - change the pixel format of an image >> > >> > Surface.convert(Surface): return Surface >> > >> > Surface.convert(depth, flags=0): return Surface >> > >> > Surface.convert(masks, flags=0): return Surface >> > >> > Surface.convert(): return Surface >> > >> > Creates a new copy of the Surface with the pixel >> > format >> > >> > changed. The new pixel format can... >> > >> > >> > >> > space it out slightly: >> > >> > >> > >> > Surface.convert - change the pixel format of an image >> > >> > >> > >> > Surface.convert(Surface): return Surface >> > >> > Surface.convert(depth, flags=0): return Surface >> > >> > Surface.convert(masks, flags=0): return Surface >> > >> > Surface.convert(): return Surface >> > >> > >> > >> > Creates a new copy of the Surface with the pixel >> > format >> > >> > changed. The new pixel format can... >> > >> > >> > >> > Also generally leave space between paragraphs if >> > you're >> > >> > not going to indent the first line of each paragraph. >> > >> > Otherwise the text tends to look like one huge paragraph, >> > >> > which is not good for reading. >> > >> > >> > >> > -- >> > >> > Greg >> > >> > >> > >> > >> >> >> >> >
Re: [pygame] Improving pygame web docs
I really didn't notice the background myself, so I don't think it's a problem. What does actually bug me though, is the project list down the right side. I appreciate wanting to make the project listings a focus of the site, but it's taking up space and distracting from the focus of a page where I told you by clicking on things that what I want to do right now is read documentation. Plus it makes stuff weirdly off center as I scroll down. On Fri, Jul 31, 2009 at 2:20 PM, Devon Scott-Tunkin wrote: > > "The background is too busy, IMHO" > > I thought it looked good, but I can see how it is busy with such a large > texture repetition, although it doesn't seem to negatively effect me when > using the site. The plain gradient was too boring for me, at least when it > was the extreme colors it used to be. Perhaps I am too attached to the > effect of layering two backgrounds over each other. Yay css :). > > Do you think larger or smaller circles would look better, or perhaps even > more transparency? Or can you suggest a different texture, I thought circles > were fun and reminded me of snake skin. Both perfect for pygame. > > Devon > > > --- On Thu, 7/30/09, RB[0] wrote: > > > From: RB[0] > > Subject: Re: [pygame] Improving pygame web docs > > To: pygame-users@seul.org > > Date: Thursday, July 30, 2009, 9:19 PM > > The background is too busy, IMHO > > And I agree with what greg wrote... > > Otherwise, looking good :) > > > > On Thu, Jul 30, 2009 at 7:55 PM, > > Greg Ewing > > wrote: > > > > jug wrote: > > > > > > > > > > http://pygameweb.no-ip.org/docs/surface.html > > ist not really easy to read, but I don't know exactly > > why. > > > > > > > > > > It looks all right to me, except for one thing: Every > > > > link to the docs for a method embedded in the text > > > > seems to be followed by a comment in small print, e.g. > > > > in the paragraph about Surface.convert, > > > > > > > > ...arguments can be used, similar to the > > > > pygame.Surface - [pygame object for representing > > > > images] call... > > > > > > > > IMO these embedded comments are pointless and > > > > distracting and make the text hard to read. Just > > > > make the method name into a link and leave it at > > > > that. > > > > > > > > Also a minor suggestion would be to leave some > > > > space between the heading for a method and its > > > > call prototypes, and between the prototypes and the > > > > following text, e.g. instead of > > > > > > > > Surface.convert - change the pixel format of an image > > > > Surface.convert(Surface): return Surface > > > > Surface.convert(depth, flags=0): return Surface > > > > Surface.convert(masks, flags=0): return Surface > > > > Surface.convert(): return Surface > > > > Creates a new copy of the Surface with the pixel > > format > > > > changed. The new pixel format can... > > > > > > > > space it out slightly: > > > > > > > > Surface.convert - change the pixel format of an image > > > > > > > > Surface.convert(Surface): return Surface > > > > Surface.convert(depth, flags=0): return Surface > > > > Surface.convert(masks, flags=0): return Surface > > > > Surface.convert(): return Surface > > > > > > > > Creates a new copy of the Surface with the pixel > > format > > > > changed. The new pixel format can... > > > > > > > > Also generally leave space between paragraphs if > > you're > > > > not going to indent the first line of each paragraph. > > > > Otherwise the text tends to look like one huge paragraph, > > > > which is not good for reading. > > > > > > > > -- > > > > Greg > > > > > > > > > > > >
Re: [pygame] Improving pygame web docs
"The background is too busy, IMHO" I thought it looked good, but I can see how it is busy with such a large texture repetition, although it doesn't seem to negatively effect me when using the site. The plain gradient was too boring for me, at least when it was the extreme colors it used to be. Perhaps I am too attached to the effect of layering two backgrounds over each other. Yay css :). Do you think larger or smaller circles would look better, or perhaps even more transparency? Or can you suggest a different texture, I thought circles were fun and reminded me of snake skin. Both perfect for pygame. Devon --- On Thu, 7/30/09, RB[0] wrote: > From: RB[0] > Subject: Re: [pygame] Improving pygame web docs > To: pygame-users@seul.org > Date: Thursday, July 30, 2009, 9:19 PM > The background is too busy, IMHO > And I agree with what greg wrote... > Otherwise, looking good :) > > On Thu, Jul 30, 2009 at 7:55 PM, > Greg Ewing > wrote: > > jug wrote: > > > > > http://pygameweb.no-ip.org/docs/surface.html > ist not really easy to read, but I don't know exactly > why. > > > > > It looks all right to me, except for one thing: Every > > link to the docs for a method embedded in the text > > seems to be followed by a comment in small print, e.g. > > in the paragraph about Surface.convert, > > > > ...arguments can be used, similar to the > > pygame.Surface - [pygame object for representing > > images] call... > > > > IMO these embedded comments are pointless and > > distracting and make the text hard to read. Just > > make the method name into a link and leave it at > > that. > > > > Also a minor suggestion would be to leave some > > space between the heading for a method and its > > call prototypes, and between the prototypes and the > > following text, e.g. instead of > > > > Surface.convert - change the pixel format of an image > > Surface.convert(Surface): return Surface > > Surface.convert(depth, flags=0): return Surface > > Surface.convert(masks, flags=0): return Surface > > Surface.convert(): return Surface > > Creates a new copy of the Surface with the pixel > format > > changed. The new pixel format can... > > > > space it out slightly: > > > > Surface.convert - change the pixel format of an image > > > > Surface.convert(Surface): return Surface > > Surface.convert(depth, flags=0): return Surface > > Surface.convert(masks, flags=0): return Surface > > Surface.convert(): return Surface > > > > Creates a new copy of the Surface with the pixel > format > > changed. The new pixel format can... > > > > Also generally leave space between paragraphs if > you're > > not going to indent the first line of each paragraph. > > Otherwise the text tends to look like one huge paragraph, > > which is not good for reading. > > > > -- > > Greg > > > >
Re: [pygame] Improving pygame web docs
The background is too busy, IMHO And I agree with what greg wrote... Otherwise, looking good :) On Thu, Jul 30, 2009 at 7:55 PM, Greg Ewing wrote: > jug wrote: > > http://pygameweb.no-ip.org/docs/surface.html ist not really easy to read, >> but I don't know exactly why. >> > > It looks all right to me, except for one thing: Every > link to the docs for a method embedded in the text > seems to be followed by a comment in small print, e.g. > in the paragraph about Surface.convert, > > ...arguments can be used, similar to the > pygame.Surface - [pygame object for representing > images] call... > > IMO these embedded comments are pointless and > distracting and make the text hard to read. Just > make the method name into a link and leave it at > that. > > Also a minor suggestion would be to leave some > space between the heading for a method and its > call prototypes, and between the prototypes and the > following text, e.g. instead of > > Surface.convert - change the pixel format of an image >Surface.convert(Surface): return Surface >Surface.convert(depth, flags=0): return Surface >Surface.convert(masks, flags=0): return Surface >Surface.convert(): return Surface >Creates a new copy of the Surface with the pixel format >changed. The new pixel format can... > > space it out slightly: > > Surface.convert - change the pixel format of an image > >Surface.convert(Surface): return Surface >Surface.convert(depth, flags=0): return Surface >Surface.convert(masks, flags=0): return Surface >Surface.convert(): return Surface > >Creates a new copy of the Surface with the pixel format >changed. The new pixel format can... > > Also generally leave space between paragraphs if you're > not going to indent the first line of each paragraph. > Otherwise the text tends to look like one huge paragraph, > which is not good for reading. > > -- > Greg >
[pygame] Improving pygame web docs
jug wrote: http://pygameweb.no-ip.org/docs/surface.html ist not really easy to read, but I don't know exactly why. It looks all right to me, except for one thing: Every link to the docs for a method embedded in the text seems to be followed by a comment in small print, e.g. in the paragraph about Surface.convert, ...arguments can be used, similar to the pygame.Surface - [pygame object for representing images] call... IMO these embedded comments are pointless and distracting and make the text hard to read. Just make the method name into a link and leave it at that. Also a minor suggestion would be to leave some space between the heading for a method and its call prototypes, and between the prototypes and the following text, e.g. instead of Surface.convert - change the pixel format of an image Surface.convert(Surface): return Surface Surface.convert(depth, flags=0): return Surface Surface.convert(masks, flags=0): return Surface Surface.convert(): return Surface Creates a new copy of the Surface with the pixel format changed. The new pixel format can... space it out slightly: Surface.convert - change the pixel format of an image Surface.convert(Surface): return Surface Surface.convert(depth, flags=0): return Surface Surface.convert(masks, flags=0): return Surface Surface.convert(): return Surface Creates a new copy of the Surface with the pixel format changed. The new pixel format can... Also generally leave space between paragraphs if you're not going to indent the first line of each paragraph. Otherwise the text tends to look like one huge paragraph, which is not good for reading. -- Greg
