Hi,
>> 1 A library so that all actors can be imported in one job lot
>
> I'm not sure what this means, could you please elaborate?
I mean that you can import all actors which will make up your scene
into a library :)
Flash has this concept as do some of open source flash development
tools like swftools and haxe.
For example in swftools you have
<?xml version="1.0" encoding="iso-8859-1" ?>
<movie width="400" height="300" framerate="12">
<background color="#cccccc"/>
<!-- first frame -->
<frame>
<!-- add some assets to the library -->
<library>
<clip id="bg" import="images/bg.png"/>
</library>
<!-- import the numerical characters of vera.ttf
<font id="vera" import="fonts/vera.ttf" glyphs="0123456789"/>-->
</frame>
</movie>
which is then used in haxe like
class Preview {
static function main() {
var bg = flash.Lib.current.attachMovie("bg", "but001", 0);
but._x = 10;
but._y = 20;
}
}
each image is this case is assigned to a clip id which is then
imported into flash.Lib.
The concept extended to clutter would be something like
def __init__ (self):
clutter.Group.__init__(self)
self.library = clutter.Library(my_actors)
self.timeline = clutter.Timeline(100, 26)
self.timeline.set_loop(True)
in this instance it is not much benefit (over just using a uri to
create an actor) but
if creating a GUI which was mentioned below then the ability to import
all actors in one job lot could be crucial in terms of both usability
and performance
>> 2. Accessibility support for actors
>
> yes, this is a known issue which should be solved. in theory, we can
> reuse the current ATK infrastructure which is also used by GTK+ and the
> GNOME desktop, in order to share as much as possible. I plan to reserve
> some time by the end of this week to see how much effort it would
> require.
It should just be adding a couple of new properties:
accessible_name
accessible_desription
to the clutter-texture base class. like setting them in glade on a gtkImage
>> 3. A GUI for clutter development (this would be a lot of work but
>> extremely useful)
>
> it would indeed. at the moment, we've been discussing internally what
> kind of approach should be used for a UI designer, but not code has been
> written.
a stage ..actors on screen and waiting in the wings, a timeline, an
audience in the round (space in which the audience surrounds the stage
area.)
Ian
--
http://ianlawrence.info
_______________________________________________
Moblin dev Mailing List
[email protected]
To manage or unsubscribe from this mailing list visit:
https://lists.moblin.org/mailman/listinfo/dev or your user account on
http://moblin.org once logged in.
For more information on the Moblin Developer Mailing lists visit:
http://moblin.org/community/mailing-lists
