Bug 6375 - sample clutter apps on moblin.org still based on old clutter-0.9
: sample clutter apps on moblin.org still based on old clutter-0.9
: NEW
: Sample Clutter Applications
Sample Clutter Applications
: upstream
: Netbook Moblin Linux
: Undecided major
: ---
:
:
:
:
 
 
Reported: 2009-09-23 06:19 PST by
Modified: 2009-09-24 01:10 PST (History)


Attachments




Description From 2009-09-23 06:19:04 PST
When run autogen.sh in sample_apps project,  error info popup that clutter-0.9
can't be found. Actually, moblin has used clutter-1.0 for quite a long time.

When modify clutter-0.9 to clutter-1.0 in configure.ac, build succeed, and the
sample app works fine in Moblin.
------- Comment #1 From 2009-09-23 08:08:48 PST -------
Bob, NOT sure you are right owner for it.
------- Comment #2 From 2009-09-23 10:34:43 PST -------
Wouldn't it make more sense to remove the whole project (most apps were already
removed in the beginning of the year), or does it still fulfill some role?
Quoth the README:
  The applications provided in this project are filler applications so that the 
  application launcher will have something to launch until real applications
are 
  built.  They also may be useful for verifying that a given platform supports 
  rendering OpenGL-based applications within a compositing window manager.
------- Comment #3 From 2009-09-23 18:57:30 PST -------
Mailing list show community people would like refer to the sample app to start
their first clutter try.
------- Comment #4 From 2009-09-24 01:10:17 PST -------
(In reply to comment #3)
> Mailing list show community people would like refer to the sample app to start
> their first clutter try.

Of course samples are needed, but new-comers don't really know where to look:
we need to point to the _right_ direction. The question is: should we point
these people to clutter source (with lots of tests), a real world clutter app
(something a bit less complex than hornsey would be nice) or a separate sample
app that exists only for that sake?

If the sample app is considered important _and_ is kept up-to-date (maybe it is
and this was just a fluke) then let's keep it. Otherwise keeping it available
will just hurt us just like it now has: people try the sample app and it does
not work.