I think I'm not making myself clear. I would like to write and engine, and the simplest way to do it is by modifying an existing engine. In fact, I have done just that in the past, using Aurora as the starting point.
Bad idea.
The trouble is that Aurora has a very messy source, and uses several ugly hacks. I would rather like to start from an engine that provided me with the basic facilities that a novice engine writer would need. Namely, this barebone engine has the following properties: (1) draws all widgets using Cairo, (2) draws a custom focus marker using Cairo, (3) uses progress-bar animation, (4) is configurable through custom gtkrc parameters (a few examples should be included in this hypothetical engine's source), (5) uses the most current APIs and implements the most current code practices (such as having "hints" in the gtkrc file).
This engine would be used not only for aspiring engine writers like myself, but would also serve as a reference implementation or guideline to proper (clean, non-hacky, etc) engine-writing for the latest GTK version.
In any case, even if we do end up disagreeing, I thank you ahead of time for taking your time to read all this. And keep up the great work with Murrine.
PS: I think your Drupal filters are in the wrong order... They are messing up the HTML tags -- EDIT: apparently this only affects the previews?
I think I'm not making
I think I'm not making myself clear. I would like to write and engine, and the simplest way to do it is by modifying an existing engine. In fact, I have done just that in the past, using Aurora as the starting point.
Bad idea.
The trouble is that Aurora has a very messy source, and uses several ugly hacks. I would rather like to start from an engine that provided me with the basic facilities that a novice engine writer would need. Namely, this barebone engine has the following properties: (1) draws all widgets using Cairo, (2) draws a custom focus marker using Cairo, (3) uses progress-bar animation, (4) is configurable through custom gtkrc parameters (a few examples should be included in this hypothetical engine's source), (5) uses the most current APIs and implements the most current code practices (such as having "hints" in the gtkrc file).
This engine would be used not only for aspiring engine writers like myself, but would also serve as a reference implementation or guideline to proper (clean, non-hacky, etc) engine-writing for the latest GTK version.
In any case, even if we do end up disagreeing, I thank you ahead of time for taking your time to read all this. And keep up the great work with Murrine.
PS: I think your Drupal filters are in the wrong order... They are messing up the HTML tags -- EDIT: apparently this only affects the previews?