Re: [XBoard-devel] Development release

[Joshua Pettus]

Other problems to consider is that first you have to let people know that this 
feature exists, in which case you are back to square one.  They are still going 
to use google.

And far more important, I would say that most people don’t know how to use 
button3 on their system or that it even exists, particularly with laptops (and 
a few like apple annoyingly do not have it available at all).

Really you are just trading one problem for another

Again, your idea can still work, but I still see universal online documentation 
as the real solution to the problem.

Perhaps I should, stop whining and make it happen ;).

Josh

> On Mar 9, 2016, at 11:35 AM, Joshua Pettus <address@hidden> wrote:
> 
> 
> I’ve been giving this more thought. If people are using google, then the 
> thing to do would be to overhaul the online documentation  (which could also 
> be useful for winboard’s aging help file as well).  With HTML we can use 
> anchor tags to make your idea work a lot more professionally.  If they are 
> offline (how did they install xboard? XD) then that’s what man pages are for.
> 
> Josh
> 
> 
> 
>> On Mar 9, 2016, at 9:52 AM, Joshua Pettus <address@hidden> wrote:
>> 
>> 
>> Well historically everybody ignores linux man and info pages.  Even in 
>> linux.  Google is going to be the main looking point no matter what you do.  
>> That said, they both have their own built in pattern searching.  If you are 
>> use to linux man/info pages it’s not a big deal.  Really I like your Online 
>> HTML documentation better.  The screenshots really help out to describe the 
>> features, and is just more readable and visually appealing overall.
>> 
>> Josh
>> 
>> 
>>> People seem increasingly unwilling to consult manuals, and rather use
>>> Google to find a post of someone who had the same problem (and often
>>> solved it the wrong way...). Would it be a good idea to attach a
>>> button3-click handler to all dialog controls, which would pop up a dialog
>>> with the relevant paragraph of the man file?
>>> 
>>> This might not be as hard as it sounds, because all dialogs are created
>>> through GenericPopup() from lists, and the name in the list is usually
>>> exactly mentioned in an @item or @cindex line in the texi file. So XBoard
>>> could run through the texi file until it encounters the @cindex line of
>>> the clicked Option, and then dump all text until the next @item line to
>>> the help dialog. It might require a bit of reorganization of the texi file
>>> to make it work everywhere, but for a large part the current texi file
>>> would already provide the info.
>>> 
>>> 
>> 
>