<HTML><BODY>
<P>You're right. I'll use the full version. And an electronic manual wouldn't be practical in my case.</P>
<P>Which is: </P>
<P>begin</P>
<P>"We need this." </P>
<P>repeat </P>
<P>"Is this what you need?";</P>
<P> "No, modify";</P>
<P>Mod_soft;</P>
<P>until Response = "OK, this is it.";</P>
<P>write(manual);</P>
<P>burn(CD);</P>
<P>install_all;</P>
<P>end.</P>
<P>So basically it's the end of the development cycle for that specifical program. </P>
<P>That's why I think to specify the particular version of wine and linux distro that I'm certain it works with and throw in a note that experiences with other wine versions / linux distros / different OS may be different (with other words of course). </P>
<P>And when/if the time comes for a v 2.0 of my soft, I'll test that against the latest wine that exists at the time of 2.0 release, and if it works, do the same with the 2.0 manual.</P>
<P>Basically I was asking if there was a pre-existing template for such a case - a finished program which works out-of-the-box under wine at the time of the soft finalization...</P></BODY></HTML>