Primer reunion de planning!

I can't seem to add Trixta to our team... It complains no such user. Hmm.

We are planning on using a persistent world which can be modified by multiple players.

To achieve this, when game content is modified by a player, it will be uploaded to a server, then downloaded from the server by other players.

I think this breaks one of the pyweek rules about downloading content (in order to force get past a 20MB entry limit).

Are we still able to entertain this idea, or should I think about a different approach?

Hello everyone.

It's our first time taking part in PyWeek and we hope to have some fun competing with all of you, as well as to learn some new stuff. Our team consists of four people total: grzywacz&maciekl are responsible for coding, epi does the graphics and smart is going to provide us with some nice music.

I'm sure it's too late but a reallyu cool feature would be an rss feed so I can just check it for updates and posts instead of the site.

Hi all. Looking forward to competing. I probably won't be online until the first Monday, so if anyone wants a latecomer in their team, I might be interested.

for anyone who has been using pgu, this bug fix release addresses numerous minor bugs. it also includes some minor enhancements to make the system slightly more user-friendly. Please see examples/gui14.py and examples/gui15.py to see the cleanup and updates in action.

pgu website

I'll be available in #pyweek for the next two weeks as well as during the contest to answer any questions, provide help. Please check out this latest release, if any final bugs are found I can wrap those up before the contest as well.

- fixed: gui11, when everything is removed scroll bar is removed
    too soon!
- fixed: gui11, graphical crud shows up after removing stuff, sometimes
- fixed: Select can drop below window sometimes, and it looks bad.
    now Selects that are at the bottom of the screen may go upwards.
- added: ProgressBar widget & documentation.
- fixed: if the widget in the scroll doesn't fill it up,
    doing any scrolling causes a crash
- fixed: gui.Menus not working due to focus related fixes
- added: widget.connect gets *values, not just value to pass on
    so that you can have multi-param methods.  See widget.connect
    documentation for details.
- added: widget.send can send the event and the widget to
    the reciever if the receiving fnc has the params named
    _widget or _event or _code.  See widget.connect documentation.
- fixed: disabled items in scrollarea don't get alpha-ized due to 
   alpha image that is being drawn to.
- fixed: scrollers don't scroll quite like normal scrollers do...
- fixed: slider size can get too small
- added: scrollbars added in arrows, so that they are scrollbars
    instead of just sliders.
- fixed: sliders & scrollbars inconsistent, and don't look good
- fixed: weird border in scrollarea, sometimes...
- fixed: internal cleanup of ScrollBox, etc.  the scollers will
    automatically appear when the sub-widget gets bigger, smaller, etc.
- fixed: when you click on a disabled widget, 
    the click can slip to a non-disabled widget
- added: .disabled, .focusable attributes to widgets, 
    see widget.widget documentation
- fixed: .add, .remove for Container, Table, Document so they
    all work properly.  gui14.py adjusted to demo accordingly
- fixed: select to work, by adding an improper use of resize ;)
- fixed: a number of improper uses of resize()
- fixed: gui.Table to only resize() something a second time
    if it _really_ needs to
- fixed: gui.Table to clear() out old rows properly
- fixed: gui.Widget so that chsize() would work a lot faster (thus
    the gui13.py example is very nice and smooth now, doesn't feel like
    it is lagging anymore.)
- fixed: ScrollBox a lot faster by using double buffering
    this will, however, require a lot of memory for large buffers
    but hopefully that won't be a problem, it makes examples/gui12.py blaze
    during scrolling, whereas before it was quite slow even on my 2x3 GHz machine.
- fixed: "calling Button.event() before Button.paint() causes crash"
- fixed: "container.remove makes a widget stop working but not disappear"
- fixed: some docs about a bug whereby container.add(w) won't work     
    after the app is running

the olde battleaxe has its pyweek website (wiki) up and running at http://www.imitationpickles.org/pyweek2/

there isn't really anything to check out, so i'm not sure why i'm mentioning it. maybe just so as to publicly invite anyone who wants to deface it. have at :)

i guess on a team status line, i also got a subversion repository set up for the team and ftp set up for the team. rah rah.

richard, is there a place i can add this link to a description of my team or something? not super important, but it might be convenient.

Is the libraries list definitive? There are a few other game libraries  I've seen on pygame that might be useful and not violate the "from scratch" directive too much. In particular, the AStar   library might be useful to include. I've written my own version of this in the past, and I'm willing to do it again, but using it for pathfinding is so common, it kind of feels like we should add it. Plus, it leaves a lot of the fitness and spatial functions up to the implementor, so it doesn't do a whole lot of work for you, just takes out the tedious generic steps. Thoughts?

Welcome back to The Don, and Corazon! w00t!