On Sat, 25 Feb 2012 11:16:58 +0000 Thomas Adam <tho...@fvwm.org> wrote: > But until we decide to do it that way, it's a little moot, and it > would require some thought and design. > > Great for a project for GSoC I'd say, because thankfully I've plenty > of ideas on this. :P
I like these ideas too, although I'll admit at this point I'm only dimly aware there is some potential perl interface, and have never investigated that or I've never looked at FwvmCommand. However, I started using the perl-C XS interface stuff last year for something, and one of the thoughts I had tooling around with that, and being a fvwm user appreciative of the style of the text file configuration, was writing a WM with a perl interface. Ie, the text configuration would be a perl script using some XS modules. So, if there were to be a new fvwm lib intended in part for use in writing perl/python/whatever APIs with (I think this is a better idea than doing that directly), how feasible would it be to export initialization and configuration functions with that? This way, you could have perl/python/whatever scripts which launch and configure FWVM. :) I'm presuming that the relationship between the proposed socket and the .so would be to blackbox the socket, as with X, so that users simply initialize with a C (or whatever) API call like XOpenDisplay() and go from there, and the .so takes care of actual communication via socket (or, possibly, initializing it at start-up). Do I have that right? MK -- "Enthusiasm is not the enemy of the intellect." (said of Irving Howe) "The angel of history[...]is turned toward the past." (Walter Benjamin)
