Re: [Tile-dev] Tile merged into the core

[Joe E. <jen...@fl...>]

Georgios Petasis wrote:
>
> While this is definitely good news, I got a little worried about the the
> themed parts
> changes (for the tileqt extension :-)). Tileqt parts are tightly related
> to the ones defined by tile, so any changes will affect also tileqt. So,
> what is the plan now?

Current plan: I'm in the middle of re-syncing the Tile and
core codebases, and trying to figure out a reasonable way to
keep them in sync in future.

The Tile 0.8.0 release will match the API in Tk 8.5b1, and
will also include deprecated aliases for the benefit of
code written against the 0.7.* API.

Then I plan to get back to what I was doing re: theme reorganization.

> Is tile going to remain a separate package for Tk 8.4 only?

I plan to continue to maintain Tile as an 8.4-compatible package
for as long as Tk 8.4 remains a viable platform.  Once 8.5 is
released and widely available, and 8.4 is EOLed, Tile as a separate
package will also go into maintenance-only mode.  (That should
take a couple years; hopefully by then it'll be finished :-)

> Will changes in 8.5 tile be backported to 8.4 tile package?

It'll probably go the other way around, at least initially --
new development will continue in Tile CVS HEAD, and changes
will get forward-ported to 8.5 once stable.

At least that's how I think it'll work.  Or maybe I'll just
do everything in a GIT repository and push out parallel patches.
I really don't know yet.

> Or is the 8.4 tile package considered "feature complete", and only bug
> fix releases will happen from now on?
> I am asking because tileqt must follow a similar scheme :-)

For tileqt: in principle, if you build against core 8.4 headers and
link with the Tile stub library, the resulting binary should
be loadable into wish8.4+tile.so and into wish8.5 equally well.
(The latter doesn't work at the moment, the stubs mechanism
got broken during the merge, but it'll get fixed once I figure
out how.)


--Joe English

  jen...@fl...