Brady Montz <bradym_at_cs.arizona.edu> writes:
...
> I see two other questions:
>
> 4. How many resources are we willing to use, both in code bloat and requiring
> people to install whichever files language X needs to operate.
>
> 5. How nicely does language X lend itself to embedding.
>
> My answers:
> 1. I want to be able to set the usual fvwm options (a=b type statements),
> maintain state about windows (so I can write functions to do things like
> SmartPlacement), and have real functions. I'd like to have it support a
> module interface, and multiple namespaces (ala python) so that I can
> write modules in that language which won't have namespace collisions with
> each other. Multithreading is probably a reasonably requirement.
>
> 2. I would probably do a LOT of programming in such a language, some of it
> released as modules.
>
> 3. guile or python
>
> 4. Either guile or python could be made to work with a minimal installation o
> f
> stuff, but the simplest thing for people to do is install the whole damn
> thing. Probably true for any interpreted language.
>
> 5. Both guile and python were designed from the beginning to be embedded. It'
> s
> probably fairly easy to map the window manager data structures onto python
> objects and vice versa. Guile might be more of a stretch.
I don't see how you have answered #4 above. Wouldn't having an
interpreter hooked up to fvwm2 consume lots of memory instantly
transforming fvwm2 into CDE?
Wouldn't any new "fvwm plus interpreter" project be redundant to the
scwm project? (It doesn't seem to me that it makes much of a
difference whether the interpreter is Scheme, Perl, Tcl, Java.)
I haven't come to any final opinion, I'd like to see how scwm works
out, but so far I'm not having many problems I can't solve with fvwm2.
> --
> Brady Montz
> bradym_at_cs.arizona.edu
--
Dan Espen Phone: (732) 699-5570
444 Hoes Lane Room RRC 1C-214 E-mail: dane_at_mk.bellcore.com
Piscataway, NJ 08854
--
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 Tue May 05 1998 - 15:51:06 BST