On Sun, 13 Oct 2002 09:18:30 +0100
Jim Lesurf <jcgl@...> wrote:
> > This is fixed in version 1.3.3 of Clock which should be at
> > http://www.kerofin.demon.co.uk/rox/ If it isn't then I forgot to
> > upload it.
> I am finding that the version of Clock I now have does not seem to
> display text anti-aliased. Does 1.3.3 do this? Can I get anti-aliased
> text by modifying so it compiles using gtk2? So far as possible, I'd
> like all text on display to be anti-aliased.
Clock uses Gtk 1.2, as does ROX-CLib. At some point I'll call ROX-CLib
version 1.0.0, then begin work on 1.1.0 which will use gtk2.
> Whilst considering the clock (and therefore time): Is the format for
> specifying the display documented somewhere? Ideally I prefer something
> like "13th Oct" to "13/10/02" for the date. Also, how does one set/alter
> the time? I haven't seen this done under linux. Given that the easiest
> way to do this under RO is using it's clock/alarm app, can I suggest
> that it would be excellent if 'Clock' did this as well? :-) (Or does
> it already do this, and I have missed it?)
You need the user-defined format which is explained on the manual page for
> Since I am asking about an applet, I'll wander even further off topic
> and ask about a totally different one. ;-> When I got my laptop it
> booted up into the standard Gnome desktop. I quickly abandoned that for
> ROX [ :-) ] however one applet I miss.
> This was one that displayed the battery charge state, etc, of the PSU of
> my portable. Alas, I don't know what this applet was called, and can't
> find any info on it in any of the books, etc, I have. Is it possible to
> have this on the panel of ROX-session as an applet?
There is a Battery applet for ROX, at http://www.csai.unipa.it/peri
> Finally: Afraid I am still fairly ignorant (as you can tell) of how
> things work. So I'd appreciate some info on some other points as I wish
> to understand how things work.
> As I outlined, I detarred and compiled ROX-CLib in a particular
> subdirectory. I then copied everything in Linux-ix86/bin into ~/bin, and
> everything from Linux-ix86/lib into ~/lib. Did I need to do all this?
> The webpage only specifies rox_run / run_rox and makes no mention of
> anything else.
> So, what steps are actually required? Is *only* rox_run needed in ~/bin?
> Or was it actually necessary for me to copy the other items? Do I now
> also need to keep ROX-Clib where I complied it in order for
> apps/applications to be able to 'find' it? Since the libraries are
> dynamic, are they required at runtime as well as when compiling?
What happens is that ROX-CLib needs to be in a directory where rox_run can
find it, either on $PATH or in ~lib:/usr/local/lib. If that is done then
you don't need to copy any files out of it, other than rox_run.
To see how it works
rox_run ROX-CLib --help
(this locates ROX-CLib then executes ROX-CLib/AppRun --help).
The --cflags and --libs arguments are used when building programs. The
--runtime argument is used when executing to put the shared libraries in
the linkers search path, removing the need to modify /etc/ld.so.conf or
Stephen Watson <URL:http://www.kerofin.demon.co.uk>