pyglet & pyweek
Ricardo
I was wondering if the next version of pyglet (1.1 ??) will be ready for pyweek (before Febraury, 29th).
What new features will the new version have ?
Thanks,
riq.
--
ser humano
http://monodiario.blogspot.com
Alex Holkner
> Hi list,
> I was wondering if the next version of pyglet (1.1 ??) will be ready for
> pyweek (before Febraury, 29th).
An alpha or beta release _might_ be ready by then, with some
documentation lacking. Don't bet on it though.
> What new features will the new version have ?
Lots of good things are already in SVN... rest assured I'll be talking
more about these when documentation starts appearing and the holes are
plugged. Briefly, pyglet 1.1 introduces:
* An optional pyglet-controlled event loop (pyglet.app). I know you
all like to write your own event loops, but trust me, this one is more
efficient, plays nicer with the CPU and OS, and allows for such
niceties as live window moving & resizing and easier management of
multiple windows.
* A low-level graphics API (pyglet.graphics). This is for hardcore
OpenGL programmers only; it provides an abstraction of vertex arrays
and buffer objects. Internally this is used by pyglet for faster text
and image rendering.
* Animated GIF support (pyglet.image.load_animation).
* New image attributes: anchor_x and anchor_y, permit the "origin" of
an image to be moved from the default bottom-left corner. This is to
simplify use of...
* Sprites (pyglet.sprite). Support for position, scale, rotation and
animation. A "batch" of sprites can be drawn all at once much, much
faster than calling "blit" on each image individually.
* Text layout (pyglet.text). Multiple fonts, styles and paragraph
formatting can be combined and drawn much faster than with the (now
deprecated) pyglet.font.Text class. Text can be efficiently modified
incrementally, making it suitable for use in a text field.
* Resource loading (pyglet.resource). Locates images and other files
on a "resource path" which can include zip files. This solves quite a
few problems when applications are started from outside their working
directory. The resource module also optimises image loading by
packing multiple small images into larger textures.
A couple more neat tricks that are not really features:
* You don't need to import pyglet submodules any more. e.g., you can
import pyglet, then use pyglet.window.Window straight away.
* Textures, fonts, etc can be loaded before creating a window.
I keep a rough track of progress at
http://code.google.com/p/pyglet/wiki/ReleaseSchedule
Alex.
Ricardo
> What new features will the new version have ?Lots of good things are already in SVN... rest assured I'll be talking
more about these when documentation starts appearing and the holes are
plugged. Briefly, pyglet 1.1 introduces:
Cool, nice features!! :-)
riq.
Shu Ning Bian
I look forward to 1.1 with great anticipation! Good work Alex,
Richard, and others!
Cheers,
Steve
Greg Jandl
>
> Lots of good things are already in SVN... rest assured I'll be talking
> more about these when documentation starts appearing and the holes are
> plugged. Briefly, pyglet 1.1 introduces:
<snip feature pr0n>
Apologies for bringing down the signal/noise ratio, but ...
<droool>
Seriously, the new feature list is bang-on with the pain points I've
found so far with Pyglet.
With the understanding that you'd have released an alpha if SVN head
was really ready for alpha, could you (or anyone on the list) comment
on how stable the new APIs are, anyway? I'd love to start getting some
use out of the new features for my own non-critical projects, but have
to few cycles right now to dive in before the API is mostly dry.
Again, kudos on a fine design, both of Pyglet 1.0 and of what appears
to be coming for 1.1!
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on USENET and in e-mail?
Alex Holkner
>
> On Feb 10, 2008 6:18 PM, Alex Holkner <alex.h...@gmail.com> wrote:
> >
> > Lots of good things are already in SVN... rest assured I'll be talking
> > more about these when documentation starts appearing and the holes are
> > plugged. Briefly, pyglet 1.1 introduces:
>
> <snip feature pr0n>
>
> Apologies for bringing down the signal/noise ratio, but ...
>
> <droool>
>
> Seriously, the new feature list is bang-on with the pain points I've
> found so far with Pyglet.
>
> With the understanding that you'd have released an alpha if SVN head
> was really ready for alpha, could you (or anyone on the list) comment
> on how stable the new APIs are, anyway? I'd love to start getting some
> use out of the new features for my own non-critical projects, but have
> to few cycles right now to dive in before the API is mostly dry.
The app module is complete. Changes to existing modules are also
complete, with the exception of the new Animation class in
pyglet.image, which needs fleshing out.
The graphics, resource and sprite modules have some holes (missing
functions/methods) but are otherwise unlikely to change.
The text module is maybe 80% complete, and some class names may change.
Most of the new modules are entirely undocumented. Changes to
existing modules have been documented in the docstrings, but I haven't
updated the programming guide at all yet.
Alex.
Greg Jandl
> The app module is complete. Changes to existing modules are also
> complete, with the exception of the new Animation class in
> pyglet.image, which needs fleshing out.
>
> The graphics, resource and sprite modules have some holes (missing
> functions/methods) but are otherwise unlikely to change.
>
> The text module is maybe 80% complete, and some class names may change.
>
> Most of the new modules are entirely undocumented. Changes to
> existing modules have been documented in the docstrings, but I haven't
> updated the programming guide at all yet.
Very cool. Thanks for taking the time out outline the current state in
such detail. I'm sure I'm not the only one who was curious.
Nathan
~ Nathan