On Wed, Aug 18, 2010 at 09:37:08AM +0300, Lars Nooden wrote: > On Mon, 16 Aug 2010, Thomas Adam wrote: > [snip] > > How would people feel about merging fvwm-crystal into fvwm-themes? > [snip] > > For those that have only a passing familiarity with either, what > differentiates the two?
Quite a lot -- fvwm-crystal bears no relation to fvwm-themes. fvwm-themes uses perllib which is FVWM's internal perl wrappers around FVWM's module interface to communicate with FVWM; allows for menu generation, etc., including use of FvwmScript. Fvwm-crystal just doesn't use this, instead making use of python. It would not be much work to take what fvwm-crystal does and throw them in to fvwm-themes as themes themselves -- the special menu code fvwm-crystal uses (by way of python) can easily be rewritten. Again, the similarities are such that fvwm-crystal and fvwm-themes allow you to integrate different theme components into one, if desired, or to use a defined theme outright. But of course, the correct answer for your question is for you to just *try* them for yourself, to see. -- Thomas Adam _______________________________________________ fvwm-crystal-users mailing list fvwm-crystal-users@gna.org https://mail.gna.org/listinfo/fvwm-crystal-users
