Thomas Adam <tho...@fvwm.org> writes: > On Mon, Aug 18, 2014 at 12:37:37PM +0100, Michael Treibton wrote: >> On 18 August 2014 05:50, Dan Espen <des...@verizon.net> wrote: >> > Brian <bvamund...@yahoo.com> writes: >> > >> >> On Sun, 17 Aug 2014 15:25:43 +0100 >> >> Michael Treibton <mtreib...@googlemail.com> wrote: >> >> >> >>> On 15 August 2014 21:05, Dominik Vogt <dominik.v...@gmx.de> wrote: >> >>> > I'll start a new mail thread about parsing with the prefix >> >>> > "REWRITE: " in a minute. >> >>> > >> >>> > In the mean time I've created a github user id 'domivogt' and >> >>> > cloned the mvwm repository and would be happy if you gave me push >> >>> > access so that I can start to work in topic branches there. >> >>> >> >>> Can I help in some way? >> >>> >> >>> Michael >> >> >> >> I too would like to help someway. Is there a person to send a >> >> skills resume to for review and assignment to the project? >> >> Brian Amundsen in Minnesota. >> > >> > Read this: >> > >> > http://fvwm.org/documentation/dev_cvs.php >> > >> > anyone can write and submit a patch. >> >> Thank you, Dan. I was hoping more for mvwm. I can't see how the >> instructions would be the same? > > They're not the same, but at the present time, there's nothing in term of > mvwm development we need, other than to document the way the parser works at > the moment, which is what Dominik and I are currently working on.
Ah, I see. I haven't examined mvwm all that closely. I had assumed that the mvwm work would eventually fold back into Fvwm. I read the parsing write up. My guess is that you are trying to develop a table driven parser for all (or most) fvwm commands? I just did something similar for a work project. But I didn't have a lifetime, so I just implemented the table driven parser for the commands I was dealing with at the time. Since then I've gone back and added a few more commands. -- Dan Espen
