Here's an example of a with a lot of example code: http://arcade.academy/examples/index.html
Arcade it built on Pyglet, but designed to be easier for new programmers. On Thursday, June 22, 2017 at 10:10:20 AM UTC-5, Benjamin Moran wrote: > Thanks for your comments, Max. > > I've asked around on different forums, and the feedback I've seen has been > similar to yours. > > I'm very grateful to Steve for stepping up to the plate here and getting > things moving. I've been busy this last week, but im going through the > programming guide a little each day and making small changes and fixes. > When I'm done with that, I will start reworking Steve's guide into a new > section. I think I'm also going to drop the "upgrading from 1.1" section, > since that's really out of date at this point. There are maybe some good > points in there, however, so if it makes sense these can get added to the > other sections. > > I'll let you guys know when I've pushed those docs, and hopefull we can > get a few eyes on it. > > > > On Thursday, June 22, 2017 at 10:43:59 PM UTC+9, Max Greason wrote: >> >> Hello! I'm a new user to Pyglet - I was looking for a >> graphics-and-other-stuff library to get started on making applications with >> more than a CLI, and when looking at what options were out there, Pyglet >> seemed like an attractive option. (I kept seeing opinions of the form >> "Pyglet would be a better API than Pygame, but I can't recommend it because >> the community is dead, the documentation is a bit crap, and it's not >> maintained." Since Pyglet seems to be maintained again, and I was willing >> to try looking through source if the docs were insufficient, I thought I'd >> take a crack.) >> >> So from the perspective of a new user, I can absolutely vouch that the >> "Writing a Pyglet Application" section really, really, needs something like >> an "Example application" section. Right now, it simply ends with "The >> examples presented in this chapter should have given you enough information >> to get started writing simple arcade and point-and-click-based games", >> which - no. Given what information is actually provided by the examples, >> not only is that deeply intimidating, it's borderline **insulting**. >> "Here's "Hello, World." Here's a way to draw a static image. Here's a way >> to play an .mp3 file. Here's a way to do something when someone presses a >> key. If you can't figure out how to make Space Invaders from that, kindly >> fuck off." It *sort of* looks like enough, but the moment you try to >> actually do something with it, you start running into questions like "Where >> do I put my game logic? Surely not all inside on_key_press?" and "Once I've >> drawn an object, how do I make it move?" >> >> Judging from the comments I saw elsewhere where people were asking about >> Pyglet vs Pygame, this experience seems to be typical. >> >> (And there's no mention of sprites at all, which as far as I can tell are >> how you're actually *supposed* to draw images for game stuff judging by the >> rest of the docs) >> >> An example arcade-type game would be *extremely* valuable. The 2009 >> tutorial that Steve Johnson posted up there for a simple Asteroids game >> would be basically perfect, if updated to 1.3. >> >> On Sunday, June 11, 2017 at 9:40:38 PM UTC-5, Benjamin Moran wrote: >>> >>> I started pitching in a little by going through the programming guide >>> and making some small changes for clarity. >>> >>> After a first pass over, I'll start adapting your game example. Right >>> now, the "Writing a Pyglet Application" ends with "Where to next?". I'm >>> thinking that we need a new top level section (perhaps at the bottom), >>> titled something like "A more in-depth example application", or "Example >>> Application #1" (if we plan to add more). The "Where to next" can point to >>> that. >>> >>> I'm also thinking that it's long past time to remove "Appendix: >>> Migrating to pyglet 1.1". There is a lot of useful information in there, >>> however, so we should also improve the relevant sections with this info if >>> it makes sense. >>> >>> >>> >>> >>> -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to pyglet-users+unsubscr...@googlegroups.com. To post to this group, send email to pyglet-users@googlegroups.com. Visit this group at https://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
