Version 1.0b includes a precompiled mipsel binary and an ugly icon.

BTP is an embracement of rc, and meant to be used on Agenda VR3. It begun its
life as an experiment with FLTK, and has evolved into a pretty usable thing.
The worst thing about it is the fingerprints on the Agenda display.

This version has a number of improvement over the previous one:
It's waaay faster, as rc is compiled in, instead of run externally.
It has a much better config format.
It can handle image buttons, courtesy of Fl_Pix_button:

-
Fl_Pix_Button for WidgetSet, Copyright (c) 1998 curtis Edwards (curt1@jps.net)
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose and without fee is hereby granted, provided
that the above copyright notice appear in all copies and that both the
copyright notice and this permission notice appear in supporting
documentation.  All work developed as a consequence of the use of
this program should duly acknowledge such use. No representations are
made about the suitability of this software for any purpose.  It is
provided "as is" without express or implied warranty.
-

This application also lacks a couple of things:
It doesn't do that nifty autorescaling seen in most Agenda apps, probably
because I ignore Flek most of the time.
It doesn't start lircd. You'll have to find the best lircd config file for
your equipment and feed it to lircd before trying btp out. And be sure you're
root, or you won't be allowed to do anything.

The .btprc file format:
V2     - Version tag, must be "V2\n".
cols   - Number of columns, 1-5. Defaults to 5, button width 32 pixels.
rows   - Number of rows, 1-7. Defaults to 7, button height 32 pixels.
row #  - Row number, from 0 to rows-1.
(button|image) number label command string;
       - Button creates an Fl_Button, image an Fl_Pix_Button.
       - Number is the X position of the button, 0 to cols-1.
       - Label is a string _without whitespace_, used as a label for the
         Fl_Button. If it begin with an @, it will be treated as an
         FL_SYMBOL_LABEL, otherwise as text. Up to 19 characters long.
         If you created an Fl_Pix_Button, label is a file name that point
         to the up and down images. btp will prepend this string with
         "btp-images/up_" and "btp-images/dn_" when loading the images.
       - Command is the arguments you normally give rc on the command line
         when writing in a shell to send the command, excluding "rc ".
         Up to 39 characters long.
       - The line must end with a ;.

BTP will combine the row number and X position, and place the button there.
There's nothing to stop you from placing more than one button at the same
spot, though I honestly don't think that would be useful.

Originally, I planned to include possibility to have different remotes on
different views, but the demand for such a feature seem very low. In fact,
the demand for this kind of application seem very low altogether. I got
response from one single person regarding btp, which doesn't feel like very
much. Anyway, I might implement the views when and if I need them. I still
don't have a good lirc config file for my VCR, meaning that the real remote
works way better than btp. Oh well.

You might have noticed that there's no Makefile. True, and a sad thing. I
never learned make. I use make.i386 and make.mipsel to compile it.

I hope btp will be of use to you!

/Sam