hi everyone;

clutter 1.0 is now really near. clutter 0.9.0 is going to be released
very soon, still one branch left to be merged. clutter 0.9.0 is going to
be "API slushy" -- which means that developers can start porting
applications to the new API, and bindings developers can start updating
their projects.

= development branch: (master) =

+ merged branch 'cogl-float':
  - COGL is now internally using floating point values. testing on
    embedded devices with GLES 1.1 and with the GLES 2.0 simulator
    revealed that the branch had no performance losses against
    fixed-point. we kept the fixed point API (CoglFixed) for
    embedded users still concerned over too much floating point
    computations in third party code
  - Units are now floating point values as well
  - this merge solves basically all the issues we had regarding
    range and precision in Clutter
+ merged branch 'float-alpha-value'
  - moved the alpha value used by ClutterAlpha to a floating
    point value in the [ -1.0, 2.0 ] range; this allowed us to
    implement all the easing functions commonly used in toolkits
    like jQuery.

= experimental branches =

+ new experimental branches for 1.0 features that are going
  to be merged or are being considered for merging:
  - generic-actor-clone: an actor that can "clone" any other
    actor, superceding CloneTexture but with different usage
    and scope from the FBO support in ClutterTexture

= stable branch: (clutter-0-8) =

+ no changes

= releases =

+ clutter-0.9.0 is being planned for Monday, January 26th, after the
  cogl-material branch lands

= bugzilla =

+ 95 bugs opened against Clutter core (-17% since last week)
+ 9 bugs with 0.8 target milestone (bugs that can, or may be fixed in
  'master' and backported to the current stable branch) (-10% since
  last week)
+ 13 bugs with 1.0 target milestone (bugs that should be fixed in
  'master' before 1.0.0 is released) (-18% since last week)

ciao,
 Emmanuele.

-- 
Emmanuele Bassi, Intel Open Source Technology Center

-- 
To unsubscribe send a mail to [email protected]

Reply via email to