Mercurial > MadButterfly

view dox/MadButterfly_Clutter.h @ 1139:a2b068594412

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Use pybind with new DOM API (at PYNode). - MBScene.document is a PYDocument instead of PYSPDocument. - MBScene.root is a PYNode isntead of PYSPItem. - getNext() was replaced by next(). - attribute() was replaced by getAttribute(). - getID() was removed, use setAttribute() instead. - MBScene.dom was removed, use MBScene.document.root() instead. - MBScene.nodeToItem was removed, use PYNode.spitem instead.
author Thinker K.F. Li <thinker@codemud.net>
date Wed, 22 Dec 2010 13:27:37 +0800
parents 8d97455811a8
children
line wrap: on
line source

/*! \page mb_clutter What is MadButterfly different from Clutter?
 *
 * Maybe some people would ask, "why don't you just use Clutter?"
 * The anwser is the author of MadButterfly know name of Clutter,
 * but he don't know what is Clutter exactly when he start the project.
 * The author of MadButterfly is some kind of cowboy, he make things
 * just because he have some ideas.  Actually, he know what Clutter
 * just one week after starting the project.  Some guy send him a
 * video from Andre Schmidt.  Andre implements a software to control
 * volumne of sound card as a concept proving for idea of using
 * SVG as a media to connect UI designers and application programmers.
 * The work of Andre is based on Clutter.  It is first time the author
 * of MadButterfly know what Clutter is exactly.
 *
 * Although, they are so similar.  We can also find some thing different.
 * Clutter is heavily depend on OpenGL/OpenGL ES.  Most embedded systems
 * do not have OpenGL included.  MadButterfly have a static/compile time
 * SVG to C translator.  MadButterfly is focus on implementing mechanism
 * to adapt SVG to C and other languages.  Clutter is about more and more
 * heavy.
 *
 * MadButterfly is supposed to be a light-weight GUI toolkit for embedded
 * or small devices.
 */