"Charles Hines" <chuck_hines_at_VNET.IBM.COM> writes:
>
> I've toyed with the idea of the next one being a big rewrite, beyond
> just what I had in mind for the GSFR (this would be 3.x). Clean more
> stuff up, change rc syntax again (built in language, but add ways to
> change to other scripting languages for the folks who would like
> that), change module stuff (dynamic loading instead of or in addition
> to a cleaned up socket communications protocol), etc. Essentially
> redesign it. Scary thought, no?
>
> What I had in mind initially for 2.2.x was the GSFR and various
> associated cleanups, maintaining essentially the same rc syntax but
> clean up parts of it (mostly for consistency between commands), add
> some new features & bugfixes that are currently needed (eventually
> including some of those that would be for 3.x). Then 2.3 official
> could be releases, and then probably move on to 3.x...
>
> What does everyone else think? The latter is probably safer, but I
> find the former more appealing...
What do we think about what? I think just about any of the fvwm2 beta
releases could have been released without the word "beta" attached. I
think most people have caught on and realize that fvwm2 is not beta
quality, its fully functional.
I think releasing fvwm2 as a non-beta release will gather some
attention and may even get someone to contribute patches for the GSFR.
As far as the changes you describe, I would lean toward maintaining rc
file compatibility unless there was a really big payoff for the
change. Shared libraries (dynamic loading) would be nice, but most
users wouldn't even notice.
> Most important for me to do in the immediate future is to actually
> finish up the next beta... :) Sorry it's taking so long (again).
Hey, until we start paying you, how can we complain?
In fact no one's complaining, everyone here loves fvwm2 even if it is
perpetually beta.
> Chuck
>
--
Dan Espen Phone: (908) 699-5570
dane_at_bae.bellcore.com
444 Hoes Lane Room RRC 1C-214
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 Fri Jun 20 1997 - 15:20:53 BST