On 20 May, Donald H. Locker wrote:
> Hmmmm.
>
> Can't we
>
> AddToFunction AddPackage "I" Read $0
> + "I" Exec $0.Init
>
> (or some such)
Where is the file read from? From my understanding, it would be in
whatever directory the rc file was found. Plus, this hasn't added the
directory to the icon and bitmap path, which means that I will have to
install the pixmaps associated with, say, the Win95 look and feel into
another directory.
What I was suggesting was some sort of standardized way of packaging
things for fvwm. I cannot tell you how many times I've looked at
screen shots of various wm's with their "attached rc files" and hunting
through the rc files finding out how a particular effect was achieved.
And these RC files may name a certain pixmap file, but finding those
pixmaps can be a hassle.
Having a standard way to package these things could allow people to
display a screen shot and a minimalist package to achieve a particular
effect. Not everybody is going to create a specialized "AddPackage"
function for this; it's better if fvwm directly supported it so
everybody can use a package without having to write the function first.
and...
On 20 May, Bruce Stephens wrote:
> Why "packages", though---aren't these going to get called
> "themes", and shouldn't we just give in, and call them "themes"?
>
> Or are "themes" something else again?
Themes would seem to be what "decors" are in fvwm -- and I didn't want
the idea to be limited to just look and feel.
I can think of a number of useful "packages" for fvwm... win95, mac,
motif look and feels are just a start. How about a package that uses
FvwmPager and FvwmButtons to create a CDE work bar? How about a package
that uses FvwmButtons and FvwmIconMan to create a Win95 style task bar?
(Pssssst, Brady... FvwmIconMan doesn't support the use of multiple
confurations like 'Module FvwmButtons PagerButtons' does!)
Another example... what is the big difference between fvwm95 and fvwm2?
The Win95 look and feel. Also, they incorporated a FvwmTaskBar module,
which Chuck brought into 2.0.46. Why can't these two projects be
merged back into a single window manager with an supplied package that
optionally provides the fvwm95 look?
--
(void) lar3ry(); gensch_at_zk3.dec.com
"Sometimes it happens. People just explode. Natural causes."
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Wed May 20 1998 - 12:26:34 BST