Dominik Vogt <dominik.vogt_at_fvwm.org> writes:
> On Mon, Nov 15, 1999 at 11:29:38AM -0500, dane_at_mk.telcordia.com wrote:
> > "Matthew W. Roberts" <matt_at_lehi.tamu.edu> writes:
> > > There are obviously many ideas about themes and how to implement
> > > them. I'm wondering ... would it make sense to take an rfc approach
> > > with this issue? I would be willing to coordinate such an effort
> > > if that would help. I'm not an FVWM expert by any means, but I
> > > am willing to do what I can.
> >
> > Always willing to expose my ignorance, I don't know what an "rfc
> > approach" would be like. I've read RFCs, I'm just not familiar with
> > the creation process.
> >
> > I'd like to pursue this as patches to "sample.fvwmrc/decor_examples"
> > that would put a few basic decors into fvwm2 itself and then the
> > themes could reside wherever and be built on top. Note how
> > "decor_examples" creates a "DecorMenu". I would hope that part of
> > creating a theme would be to add an entry to the "DecorMenu".
>
> Uh, with all the work I spent with style changes, couldn't we
> just forget about decors and do it with separate files that
> read in certain groups of styles? Perhaps we need a better
> 'UseStyle' style that can be updated at run time.
I didn't mean to imply that we wouldn't have separate files. I'd just
like to migrate the stuff in "decor_examples" into whatever the new
scheme is. I wouldn't like to still have "decor_examples" when we are
done.
Its bad enough that we still have "system.fvwm2rc". I forget why that
wasn't deleted when all of it migrated to ConfigFvwmSetup, but there
was some objection.
> > I was hoping to hook this up to the config creation stuff in
> > "fvwm/ConfigFvwmSetup". I don't know if I'll get to this, so patches
> > would be nice.
> >
> > (All this is referring to new functionality that only appears in the
> > 2.3.x betas.)
>
> Al this 'Theme' stuff is closely related to a potential future
> configuration fvwm module/application/script. If we can write
> or edit the config files with such a tool we are already halfway
> there. Can FvwmForm be our config tool? What I dream about is
> an application that fakes a window or menu and where you can click
> on the parts to get a dialog to change the corresponding settings.
> If the output of such scripts is is grouped in several files,
> implementing a theme would be as easy as replacing one or more of
> the files and perhaps restart fvwm (I hope that this is not
> necessary).
I don't know if FvwmForm is flexible enough we'd have to see.
I think FvwmScript might be up to it, but I don't know the module yet.
But for pre-written themes, AddToMenu might be enough. (You read the
theme, and it adds itself to the menu.)
I'd prefer to stay away from anything that requires additional
packages.
I have more to say about reading in response to another mail...
--
Dan Espen
444 Hoes Lane Room RRC 1C-214 E-mail: dane_at_mk.telcordia.com
Piscataway, NJ 08854 Phone: (732) 699-5570
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Mon Nov 15 1999 - 13:00:29 GMT