Re: [pygame] Re: Announce: PygWeb2.0rc
B W wrote: I like the aesthetics of your redesign, and the layout is very friendly. Thanks. I'm curious to see if your conversion will fix HTML-wrapping issues like this: http://www.pygame.org/wiki/2DVectorClass. And whether project screenshots will be ported and the default N/A images will be replaced. I don't see any errors there. Since the pygame developers who run pygame.org are not interested in the website, it will (probably) run as a individual website, independent of pygame.org (if anyone is interested, email me). In this case, it will not migrate any data from pygame.org. We did not migrate screenshots for the demo cause its just a lot of data (of course it would be possible). One content-related feedback. This occurs on the following converted snippet from the Pygame Code Repository. http://pygameweb.no-ip.org/snippets/28/ The original distribution bundles files critical to the code's function. While your converstion exposes the code for convenient viewing--a very nice touch--it seems to have lost the other components: an image file, and POV files if anyone should want to dig into the 3D image with POV. I predict this would be a frustrating discovery for anyone wishing to see the code in action. I do not know how many are like this, but I'm sure you would want to follow up on it, in the spirit of insuring converted content is either unchanged or improved. :) There are a few snippets that have additional data like images or extra files with it. Normally, Snippets (on pygWeb) are just code and maybe some explanatory text. Thus, migrating additional files it not possible (when using a converter script). Of course these extra data may be important. Not for the demo, but for a productive usage. The problem is, that there is no option for normal users to attach any files to snippets (which is, I think, basically appropriate). So these snippets either have to work without additional data or host this data somewhere else and link to it or use the wiki that allows attachments (but is not meant for code hosting). Devon Scott-Tunkin wrote: I can't remember right now if the code was using different templates than the rest of the site. Yes, the code tab is the one handled by Trac (with its own templates and style sheets). -- Julian
Re: [pygame] Re: Announce: PygWeb2.0rc
Yes, the code tab is the one handled by Trac (with its own templates and style sheets). Okay, then I probably just forgot to update the trac one when I changed the django one, I'll fix that. It would be so nice if I could figure out how they could use the same style sheets... Devon On Mon, Dec 7, 2009 at 8:00 AM, jug j...@fantasymail.de wrote: B W wrote: I like the aesthetics of your redesign, and the layout is very friendly. Thanks. I'm curious to see if your conversion will fix HTML-wrapping issues like this: http://www.pygame.org/wiki/2DVectorClass. And whether project screenshots will be ported and the default N/A images will be replaced. I don't see any errors there. Since the pygame developers who run pygame.org are not interested in the website, it will (probably) run as a individual website, independent of pygame.org (if anyone is interested, email me). In this case, it will not migrate any data from pygame.org. We did not migrate screenshots for the demo cause its just a lot of data (of course it would be possible). One content-related feedback. This occurs on the following converted snippet from the Pygame Code Repository. http://pygameweb.no-ip.org/snippets/28/ The original distribution bundles files critical to the code's function. While your converstion exposes the code for convenient viewing--a very nice touch--it seems to have lost the other components: an image file, and POV files if anyone should want to dig into the 3D image with POV. I predict this would be a frustrating discovery for anyone wishing to see the code in action. I do not know how many are like this, but I'm sure you would want to follow up on it, in the spirit of insuring converted content is either unchanged or improved. :) There are a few snippets that have additional data like images or extra files with it. Normally, Snippets (on pygWeb) are just code and maybe some explanatory text. Thus, migrating additional files it not possible (when using a converter script). Of course these extra data may be important. Not for the demo, but for a productive usage. The problem is, that there is no option for normal users to attach any files to snippets (which is, I think, basically appropriate). So these snippets either have to work without additional data or host this data somewhere else and link to it or use the wiki that allows attachments (but is not meant for code hosting). Devon Scott-Tunkin wrote: I can't remember right now if the code was using different templates than the rest of the site. Yes, the code tab is the one handled by Trac (with its own templates and style sheets). -- Julian
Re: [pygame] Re: Announce: PygWeb2.0rc
On Dec 7, 2009, at 12:49 PM, Devon Scott-Tunkin wrote: Yes, the code tab is the one handled by Trac (with its own templates and style sheets). Okay, then I probably just forgot to update the trac one when I changed the django one, I'll fix that. It would be so nice if I could figure out how they could use the same style sheets... Did you try sticking the Django site style into the Trac code after the Trac CSS? Trac has a few of its own specific classes and such that won't be overridden by the Django one, but having the Django one last should bring many things in the Trac site in line pretty quick. S
Re: [pygame] Re: Announce: PygWeb2.0rc
Hey, Thanks for the feedback. I have a suggestion: If you download a code snippet, it gets named like '49.py' or '55.py'. But a filename would be more useful, like 'ZoomScreen.py' instead of '55.py Good idea, I've changed that. if clicking on the code tab, the whol website recenter and has smaller width (1024) than before. you may have to test with high browser resolution I know that. Not yet sure whats better. The smaller, fixed width was the original style, but sometimes its not enough space for the entire content (logged in as admin or with very long user name). I only have one question; how is updating the new site different from the old? Is the Django site still serving most things from static pages and just using the database to store comments and such, or did they use one of the little CMS doo-dads available for use with Django? The site runs with an own database. Currently its sqlite, but since its done with Django, most other db backends should work as well. All content except the documentation is stored in the database. It's possible to convert data from the current pygame.org db, but you cannot use the same data or database without converting. The issue is some people felt Jug and the others went ahead without proper discussion before-hand. Some people wanted to rewrite the website as well, but not with Django. The discussion got nowhere fast, so we just started (otherwise, I think we would be still discussing). Also, those who wanted to write a website with other tools, did not do that (afaik). The same applies to the details. You cannot discuss every single detail on such a mailing list. Everyone has his own opinion, but you can only implement it one way. So we did it how we deemed it right and then showed it to the list so that everyone could have a look at it, test it, and tell us whether it is ok or he found any no-go's. -- Julian
Re: [pygame] Re: Announce: PygWeb2.0rc
Hi, jug. I like the aesthetics of your redesign, and the layout is very friendly. I'm curious to see if your conversion will fix HTML-wrapping issues like this: http://www.pygame.org/wiki/2DVectorClass. And whether project screenshots will be ported and the default N/A images will be replaced. One content-related feedback. This occurs on the following converted snippet from the Pygame Code Repository. http://pygameweb.no-ip.org/snippets/28/ The original distribution bundles files critical to the code's function. While your converstion exposes the code for convenient viewing--a very nice touch--it seems to have lost the other components: an image file, and POV files if anyone should want to dig into the 3D image with POV. I predict this would be a frustrating discovery for anyone wishing to see the code in action. I do not know how many are like this, but I'm sure you would want to follow up on it, in the spirit of insuring converted content is either unchanged or improved. :) Cheers. Gumm
[pygame] Re: Announce: PygWeb2.0rc
On Nov 29, 7:32 am, jug j...@fantasymail.de wrote: Hello! We would like to announce we have finished working on the PygWeb website that was originally intended to replace the current site on pygame.org http://pygame.org. I'm kind of new to PyGame but the new site looks far better than the old one and, being in Django, would seem to be a huge step forward. What's the issue? Is there some reason that a better web site would not be better? S
Re: [pygame] Re: Announce: PygWeb2.0rc
I'm only recounting what I saw and what was said, not commenting on this: The issue is some people felt Jug and the others went ahead without proper discussion before-hand. /me signs off. On Sun, Nov 29, 2009 at 8:01 AM, ssteinerX sstein...@gmail.com wrote: On Nov 29, 7:32 am, jug j...@fantasymail.de wrote: Hello! We would like to announce we have finished working on the PygWeb website that was originally intended to replace the current site on pygame.org http://pygame.org. I'm kind of new to PyGame but the new site looks far better than the old one and, being in Django, would seem to be a huge step forward. What's the issue? Is there some reason that a better web site would not be better? S -- Tyler Laing Science and Tech Editor The Phoenix Newspaper (1) 250 863-4869 University of British Columbia - Okanagan University Way Kelowna, BC UNC 109 Student Services Building
Re: [pygame] Re: Announce: PygWeb2.0rc
On Nov 29, 2009, at 12:40 PM, Tyler Laing wrote: I'm only recounting what I saw and what was said, not commenting on this: The issue is some people felt Jug and the others went ahead without proper discussion before-hand. Ok, well I'd say the results speak for themselves. I only have one question; how is updating the new site different from the old? Is the Django site still serving most things from static pages and just using the database to store comments and such, or did they use one of the little CMS doo-dads available for use with Django? S
