Re: [pygame] starting the rewrite

[Shaun Mahood <s.mahood@xxxxxxxxx>]

As much fun as it is to watch everyone split apart to do their own
thing, I have a few questions (not knowing anything about either
Django or cherrypy).

Do both of the frameworks "hide" all the database interactions? If
possible, it could save a ton of headaches later on if a database
structure could be set for both teams to develop on. If there were a
common set of methods written as well to interact with the database,
then you would have a whole lot of common sections between the two
rewrites.

Is there a common set of agreed upon requirements for the new website?
This would at least give people a basis to compare things on, and
perhaps as time went on to make decisions on whether cherrypy or
django is a better fit for what we need.

Which of the two systems gives greater control for low level
operations? I'm attempting to learn Ruby on Rails right now to help
with prototyping and speeding up development, and am finding it to be
quite a pain to learn all sorts of very specific ways to manipulate
things. As much fun as it is to have your framework do all the heavy
lifting for you, I think there needs to be a relatively simple way to
jump into the database and play with the SQL code and the interactions
between the website and the database. I'm kind of assuming that both
frameworks allow you to play with the HTML, javascript and CSS easily
if you need to.

I think everyone involved is definitely smart enough to create a very
good website no matter what framework is chosen. For saving the
learning curve of future collaborators, I would put my vote to the
framework that allows the easiest low level manipulation without
having to learn a whole ton of extra stuff (thankfully for everyone,
my vote doesn't count :)

Good luck to everyone
Shaun




On Fri, May 1, 2009 at 10:40 AM, René Dudfield <renesd@xxxxxxxxx> wrote:
> On Fri, May 1, 2009 at 8:49 PM, Marcus von Appen <mva@xxxxxxxxxxxx> wrote:
>> On, Fri May 01, 2009, Nicholas Dudfield wrote:
>>>
>>> Has everyone decided that Django is to be used?
>>
>> From my perspective it was (more or less) settled to go with Django, if
>> Julian and Orcun (and pretty much everyone else, who wants to work on
>> the rewrite) are more comfortable with it than with something else.
>>
>> As far as I can see, noone else explicitly voted against it, but instead
>> cherrypy was mentioned as an alternative.
>> Personally, as I can read from Julian's and Orcun's GSoC proposals, they
>> have a lot of ideas with Django and how to implement the website with
>> it.
>>
>> In order to have a solid solution, I strongly support Django here for
>> the obvious (already mentioned) reasons of having two skilled developers
>> for it.
>>
>> Regards
>> Marcus
>>
>
>
> hi,
>
>
> the discussion never reached a conclusion for me... code just started
> being written.
>
> When the website rewrite process started in late January, cherrypy was
> suggested by pymike.
> http://groups.google.com/group/pygame-mirror-on-google-groups/browse_thread/thread/34a561e3ac7ebc26/1b36d71a37af7216
>
> Also in the rewrite thread cherrypy was suggested by me and Nicholas.
> Other people have said they were happy with either.  We also got a
> promise of support from the main author of cherrypy in case we have
> any nasty problems, and there was another offer of help from another
> person on the cherrypy mailing list to actually help writing the
> website.
>
> There are more than just two people interested in joining the website rewrite.
>
> I think there are more of the most active pygame contributors
> interested in contributing to a cherrypy based website.
>
>
> Since the other website rewrite has been started without concluding
> our discussion,  I too am just going to go forward and write a new
> website for pygame.org.
>
> As one of the people who has been maintaining pygame for a long time,
> and who has also made some(small) changes to the current website code,
> and written many pages on the website - I hope other people join the
> cherrypy based effort.
>
>
> May the best website win!
>
>
> cu,
>