Joshua Pettus | 18 Sep 17:19 2014
Picon

Re: XBoard 4.7.3: Full board textures + maximize window


On Sep 18, 2014, at 8:55 AM, Joshua Pettus <jshpettus <at> gmail.com> wrote:

>> From what I have seen from other
>> people, 12.04 has a completely new user interface that is complete crap. I
>> would never want that on any computer I actually had to work on. So if
>> 10.04 gets unworkable, I guess I would have to switch to another distro
>> (people recommend Fedora).
>> 
> 
> For the record, might I recommend XUbuntu?  I’m no fan of the Unity interface either, and this way you
still get to use Ubuntu’s vast library and support.  Also XFCE shares a lot in common with the old GNOME2 interface.
> You may want to give it a try anyway,  In general I find newer OS’s have much better hardware support then
their predecessors.  At least I had to jump through a lot less hoops to install it on my old 2007 mac laptop. 
Perhaps test it out on the live cd first?
> 
> Josh

Arun Persaud | 18 Sep 07:43 2014

some configure.ac questions/ possible gettext solution

Hi

I had another look at the configure.ac script.

For some reason we define X_LOCALE, RTU, DEFINED_SYS_ERRORLIST in
configure.ac but never use them later... does anyone know if they are
needed or checked in some library or can we remove those?

I also have two OS X issues. For one thing configure doesn't include the
macport dirs -L/opt/local/lib and -I/opt/local/include during tests for
gettext and other libraries, so currently you have to define those on
the configure command line. The only way I can think of fixing this is
to move the HOST check in configure.ac to the top of the configure
process. Anyone know if this is OK or if this is a problem?

The other problem is with redefining $localedir in configure.ac when
trying to build an OSX app file. We need to redefine this to a relative
path for the App, it's probably best to add a configure option
--enable-osx-app for which I would overwrite the install target in
Makefile.am to do what needs to be done to create the app. Is there a
better way of doing this?

As for the HOST check: we currently have checks for all kind of systems
in there solaris2, sunos4, sco, sysvr4... would xboard still build on
them? Is anyone still using those? Since we don't get feedback, what's a
good way of handling those? I would suggest we add something like

AC_MSG_WARN([Support for this OS will be removed in the next version, if
you are still using it, please contact xboard-devel... so that we can
keep supporting it.])
(Continue reading)

Sebastian Pipping | 15 Sep 21:32 2014

XBoard 4.7.3: Full board textures + maximize window

Hello!

On my journey trying to get a natural-looking Xiangqi mode running with
XBoard (rather than WinBoard), I ran into problems with rendering.

My call to xboard was

  xboard \
	-variant xiangqi \
	\
	-liteBackTextureFile ${D}/themes/textures/xqboard.png \
	-darkBackTextureFile ${D}/themes/textures/xqboard.png \
	-overrideLineGap 0 \
	\
	-pieceImageDirectory ${D}/themes/xiangqi \
	-trueColors true

Now when XBoard starts up this looks sane.

When I maximize the window to full screen, the boards starts to look
very weird, see [1].

I started inspecting BlankSquare and CutOutSquare in draw.c.  In
CutOutSquare there are guards

  if(textureW[kind] < W*squareSize)

and

  if(textureH[kind] < H*squareSize) .
(Continue reading)

H.G. Muller | 15 Sep 19:42 2014
Picon

Auto-instal of engines

I just equipped XBoard (not WinBoard) with an -autoInstall option,
which should still go into the 4.8.0 release. This option uses what I hope
will become the new standard for engine packages in Linux:

All engines should contain a 'plugin-spec' file <enginename>.eng, which they
should install in the directory /usr/share/games/plugins/≤protocol>/ , where
<protocol> = uci, xboard, etc. The file will contain a magic sentence 
"plugin spec 0.0",
the command line needed to start the engine for the given protocol (e.g.
"pos --io-mode xboard") and possibly a working directory (as a preceding 
cd command),
a list of games / variant groups (like chess, chess960, capablanca, 
xiangqi, shogi, fairychess,
loserchess, checkers, go; the recognized game names will still have to 
be defined).

When -autoInstall is not an empty string, XBoard wil append any newly 
installed engines for UCI and XBoard protocol that it sees for the first 
time (as based on the modification date of the .eng file and the user 
settings file), to the -firstChessProgramNames list. The line will 
specify the corresponding -fcp, -fd arguments, and in case of UCI 
engines add a -fUCI flag. In this first implementation the variants list 
is ignored; in the future it could be matched with the -autoInstall list 
to decide which engines should be installed, and which should be 
ignored. (e.g. -autoInstall "shogi" could only install engines that play 
Shogi).

In the future the plugin-spec files could contain extra lines to give 
additional information, e.g. about known non-compliancy with the 
protocol (e.g. UCI engines that do not implement "searchmoves" or do not 
(Continue reading)

H.G. Muller | 9 Sep 19:11 2014
Picon

Xaw build now ready for release?

I finally got to fixing the Xaw problems with the new ICS Interaction 
window.
This was really a feature that could only work in GTK (because it required
line-by-line colorization of texts), but I integrated it in the existing 
Chat window.
I solved the problems (I hope) in the following way:

In the Xaw version I let the initialization code remove the ICS output pane
from the ICS window, by turning it into a Skip option (instead of a 
TextBox).
The 'Hide' button, which would normally hide the Chat output pane, is
removed in a similar way, now there is nothing to hide behind. (In GTK
this collapses the Chat pane to make a larger ICS pane.) This makes the
ICS Interaction window look very similar to the old Chat window in Xaw.

So Xaw retains its Chat window, where Tab navigates to the next text
entry and Esc closes the window, as before. For sending commands
to the ICS it stays dependent on the old-style ICS Input Box or the X-term.
The ICS Input Box pops up automatically when you type towards the board.

The GTK version does away with the ICS Input Box, and absorbs it in the
ICS Interaction window, where the single input field is used for both
ICS commands and chat messages, depending on the currently displayed
output (one of the maximally 5 chats + ICS output, or just ICS output).
The <Tab> key here navigates between chats (or switches ICS command
-> chat), the <Esc> key goes from Chat to ICS command mode (closing
the chat pane) like the Hide button does, or in ICS command mode
transfers focus to the board (leaving the chat window open). Ctrl-N
navigates to an idle chat (if there is one), with focus on the (empty)
Chat Partner field, so you can assign it (unlike <Tab>, which only navigates
(Continue reading)

Joshua Pettus | 10 Jul 05:20 2014
Picon

App bundler script for Xboard OSX v3


Hello all,

I apologize if this sent before.  To me, it didn’t look like it did.

Anyway I did a little thinking and managed to git rid of the gtk related files (save the theme) by A) copying a
little more from the system install of gtk and B) configuring the various settings files with the sed and
echo commands in the script.  This way should look a lot better, and makes me less nervous of having files not
related to xboard directly.

Also to further remove extra clutter, I decided to have the script generate the info.command and
man.command launching scripts. This also stops the os from thinking they were downloaded whenever I try
to open them right after building the bundle. (One less dialog box in my life is a good thing :-) )

Regards,
Josh Pettus

Attachment (mac-appv3.zip): application/zip, 972 KiB
Joshua Pettus | 8 Jul 17:37 2014
Picon

Appbundler Script v3

In the interest of less clutter,  I decided to have the script generate the info.command and man.command
launching scripts.  Also stops the os from thinking they were downloaded whenever I try to open them right
after building the bundle. (One less dialog box in my life is a good thing :-) )

Attachment (mac-appv3.zip): application/zip, 972 KiB

Regards,
Josh
Attachment (smime.p7s): application/pkcs7-signature, 1905 bytes
Joshua Pettus | 8 Jul 08:28 2014
Picon

Appbundler script v2

Hello all,

I did a little thinking and managed to git rid of the gtk related files (save the theme) by A) copying a little
more from the system install and B) configuring the various settings files with the sed and echo commands. 
This way should look a lot better, and makes me less nervous of having files not related to xboard directly.

Regards,
Josh Pettus

Attachment (mac-appv2.zip): application/zip, 973 KiB
Attachment (smime.p7s): application/pkcs7-signature, 1905 bytes
Joshua Pettus | 6 Jul 16:15 2014
Picon

App bundler script for Xboard OSX

Hello all,

I finally managed to boil my process down to a simple shell script.  I took the liberty of putting it, and all
the supporting files, (including icons, xboard.conf, mans, gtk configs and a osx style gtk2 theme).  In
the included readme file, I describe how to setup macports properly to build xboard and run the script.  All
you have to do after is unzip the folder into a xboard source package and, after compiling the binary, run
the script.

Surely all this can be done within the makefiles itself, so someone with more knowledge in this department
can feel free to give it a try.

A few things though with the current make/configure file.  Right now it doesn’t properly link the
gtkmacintegration library.  I have to keep putting it in LDFLAGS in the make file before building.  Also if
someone could add the -headerpad_max_install_names flag, to the OSX gtk build process, that would be
very handy as it is always necessary to be able to relink the libraries.

————
And finally there are a couple of comments made by HGM that haven’t made it into any branch that are needed.

First in args.h there is some code that is necessary to keep the user.conf file portable with its directories:

args.h 

------
    case ArgFilename:
      if(*(char**)ad->argLoc == NULL) break; // just in case
      { char buf[MSG_SIZ];
        snprintf(buf, MSG_SIZ, "%s", *(char**)ad->argLoc);
#ifdef __APPLE__
        if(strstr(buf, DATADIR) == buf)
(Continue reading)

Translation Project Robot | 28 Jun 17:42 2014

New Spanish PO file for 'xboard' (version 4.7.2)

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'xboard' has been submitted
by the Spanish team of translators.  The file is available at:

    http://translationproject.org/latest/xboard/es.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/xboard/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/xboard.html

If any question arises, please contact the translation coordinator.
(Continue reading)

Tim Mann | 6 Apr 02:06 2014

Re: question

Sorry, I don't know anything about interoperating with Fritz. Copying
the group in case anyone else has advice for you.

Which web page is dead? We should take out the link, or update it if
anyone knows where it should go now.

On Fri, Apr 4, 2014 at 6:23 AM, Anders Ludvig Kleimark
<akleimark <at> gmail.com> wrote:
> Hello!
>
> I would like my engine to work in Fritz with xBoard protocol. Is there any
> specific commands that I need to implement?
> The webpage you mention in the manual seems to be dead.
>
> Regards,
> Kleimark, Anders.


Gmane