Now that keynav has been removed from Tile, is it going to be
substituted
with something else or do we have to manage the bindings ourselves?
Also I have noticed that the ttk* header files aren't installed, is it
on
purposse? I ask mainly because there absence is the first problem
to solve in order to get TileQt to compile.
Thanks,
Andres
There are two different branches: there's the Tile extension,
which is still maintained for 8.4 and for development purposes,
and "Ttk", the parts of Tile that got pulled into Tk 8.5 beta.
The keynav package and ttk::dialog aren't included in Tk.
They're still included in Tile for now, but will be moving
to a separate project (provisionally at Google Code,
http://code.google.com/p/tile-extras/), to be distributed
separately.
>Also I have noticed that the ttk* header files aren't installed, is it
>on
>purposse? I ask mainly because there absence is the first problem
>to solve in order to get TileQt to compile.
Two choices: you can install the Tile extension and compile
against those headers; the resultant shared library will depend
on the Tile extension. Or you can compile against Tk 8.5 beta
private headers; the resultant shared library will only load
into Tk 8.5. Note also that somebody changed the header name
from "tkTheme.h" to "ttkTheme.h" during the integration.
Apologies for the inconvenience.
--Joe English
That was the plan, yes. (To date, not a whole lot of
development has been going on, but that was the plan.)
> For most of my applications I have no need
> for the text, canvas or legacy widgets. Is the Tile extension dependent
> on the Tk library?
Very much so. Tk is more than a widget set: it's also
a framework for building widgets. The tile widgets use
the same framework as the core widgets do.
> Is it possible to distribute an application that
> uses Tile without Tk?
Not really.
--JE