Hi
will this also work on OS X and other UNIX variations or do we need to
have this in an #ifdef and check for xdg-* during configure (which we
are doing already anyway)?
> seems to work. At least it brings up some "Evolution configure" page. As I
> have no e-mailer on my Linux I cannot really test it; perhaps you can try
> if the "Help -> Email Bug Report" item works for you. I have no experience
> with mailto: links, so I don't know how to make a template.
I think you can do things like
mailto:address@hidden?subject=Bug%20in%20XBoard&body=Bug%20report
This way we could add information about the version, operating system,
etc in the email and ask the user to add a description too... you just
need to escape space and linebreaks, etc. correctly.
> [user guide]
> Well, for now I linked to the web page I expect to appear at
> xboard/user_guide/UserGuide.html. I suppose there are html-to-texi
> converters?
I guess so, in the long term it would be good if the user guide would be
written in texi and then we create html and pdfs from it. It could also
just be the first chapter in our current texi documentation and then we
could crosslink to the more detailed sections in the existing
documentation which would be nice... texi can include pictures, etc, so
that should be no problem and we could put it in an ifdef, so that the
picture (or perhaps the whole chapter) doesn't show up in the info file.
Perhaps something for 4.6.1...
> About the News Page. Perhaps directly linking to the 4.6.0 news page is a
> bad idea after all, because at some point there will be newer stuff, and
> the user could also be interested in the that, but would never see it
> appear. OTOH, the whats_new/index.html page is a very dull one, and I
> don't want the user to arrive there.
yep, that page could be made to look nicer or we just use the home page
and have a better "what's new" section in there with a link to a more
detailed version.
> This was so much easier than I thought it would be that maybe we should
> include it with 4.6.0 after all.
ok... just push it to master and v4.6.x and let me know when it's ready
and I can package and release it.
> I have been getting worrisome reports about the -stickyWindows option: it
> seems it is incompatible with Compiz Desktop Effects. I don't know if this
> is also the cause of the problems Byrial seemed to have with it. I put a
> call on TalkChess for Linuxers to test it, to get an idea for how many
> people it works, and for how many it doesn't. If it causes too many
> problems, we probably should configure it as off in 4.6.0. It is currently
> not documented anyway, we might even take out the menu control to switch
> it on (and only leave the command-line option).
hmm, we could leave it out or label it experimental and enable it during
configure.
cheers
ARUN