[ubuntu-art] New Wave (Engine)

[Mikkel Kamstrup Erlandsen]

2008/5/8 Anton Kerezov <ankere at gmail.com>:

> В 20:48 +0200 на 06.05.2008 (вт), Mikkel Kamstrup Erlandsen написа:
> > Start by checking out Murrine from Gnome svn:
> >
> >   svn co http://svn.gnome.org/svn/murrine/trunk murrine
> >
> > Use an svn checkout to make it easier to create diffs/patches ('svn
> > diff > mypatch.patch'). To set up a development environment use:
> >
> >
> >   sudo apt-get install libcairo2-doc libgtk2.0-doc devhelp anjuta
> >   sudo apt-get build-dep gtk2-engines-murrine
> >
> > Now you should be able to build murrine from source - Run
> >
> >   ./autogen.sh (only needed the first time)
> >   make
> >   (don't do 'make install')
> >
> > Now https://wiki.ubuntu.com/MikkelKamstrupErlandsen/ThemeEngineTricks
> > will tell you how to create a symlink in your home dir to have the
> > system pick the compiled engine up (you should not have murrine
> > installed).
> >
> > Anjuta is a nice code editor and devhelp is a documentation viewer.
> >
> > Get hacking :-) Cheers,
> > Mikkel
>
> Hi Mikkel,
> Right now make builds all the themes but I want it to only build
> clearlooks. Can you help me with the
> makefile I need to build CL? Anybody else, Who ? (I attach the necessary
> files)
>
> I'm thinking of adding new style to CL like GUMMY or GLOSSY that will be
> called NEWWAVE or smth. And I planned to make a separate
> clearloocs_draw_newwave.xxx file to do the new style. What do you think?
>

Sorry for the late reply, but I was on vacation.

If you only hack inside Clearlooks then 'make' should only rebuild the
clearlooks engine, with fairly little overhead from checking if other files
have changed.

Anyways; I think it is important that you 'write your engine' as a patch for
upstream Gnome. This also means that you should not rip it out of the source
tree. It is generally frowned upon to just fork engines (like Fedora forked
Murrine to create Nodoko) and it is also a great maintenance burden. If you
can get it included as a patch upstream you are pretty much safe, and will
benefit from later developments (including security fixes!) of the
Clearlooks engine.

The tricky part is getting it into upstream. To maximize your chances
consider the following:

 * Make sure to touch as little as possible of the existing code
 * Follow the code style and terminology of the existing code base
 * Make the code easily understandable (fx good variable names, and comment
the non-obvious sections)

Make sure you have a clean current svn snapshot by running 'svn up' and
resolving any conflicts (likely none if you've kept your changes
non-intrusive). Then run 'svn diff > new_wave_style.patch' and attach it to
a bug report on Gnome's bugzilla (bugzilla.gnome.org product: gnome-themes
and component: theme-clearlooks) shortly describing why we need it (maybe
link to mockups/screenshots).

At your service,
Mikkel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/ubuntu-art/attachments/20080512/a2b942c1/attachment.htm