On Feb 11, 2008 10:31 AM, Ricardo <[EMAIL PROTECTED]> wrote:
> 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.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pyglet-users" group.
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to