If necessary, we can temporarily write out the events by hand. There aren't that many of them.
On Wednesday, June 13, 2012 2:20:47 PM UTC-7, Steve wrote: > > Any progress here? We should try to get it together for 1.2. > > On Wednesday, April 11, 2012 4:50:21 PM UTC-7, Steve wrote: >> >> Ah, I misunderstood the functionality of the epydoc extension. >> >> Events! >> http://pyglet.org/doc/api/pyglet.window.Window-class.html >> >> On Apr 11, 4:01 pm, Nathan <[email protected]> wrote: >> > On Wed, Apr 11, 2012 at 10:01 AM, Steve <[email protected]> wrote: >> > >> Treatment of events will require a small extension. An extension is >> > >> slightly neater than an entire fork which is what epydoc needed. :) >> > >> > > Why? You can just create arbitrary reStructuredText pages. >> > >> > I'm sure he doesn't want to hand-craft the API documentation for each >> > change to the code. He'll want to generate it, which means 'pyglet >> > events' will need an extension so they can be treated differently than >> > regular methods. >> > >> > ~ Nathan > > -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To view this discussion on the web visit https://groups.google.com/d/msg/pyglet-users/-/NjXPjyemllQJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en.
