At 04:16 PM 12/06/2003 +0200, you wrote:

>At 10:23 AM 12/06/2003 +0000, Helen wrote:
>
> > (VCL and CLX are not interchangeable).
>
>I don't know what that means, but with a few conditional defines
>you sure can make an application that shares source AND uses VCL
>on Windows AND CLX on Linux. So, there is no need for a CLX/Win
>version of IBO, just CLX/Linux.

Hi Tobias,
'way off-topic here now...

What you say about *application code* is true (more or less: some things
about the DA layer can't be done with CLX and so they are simply missing).

But you miss my point that addressed Christoph's question: "What is the
timeframe for IBO that I can use in either Delphi or Kylix?"

There isn't a chance that you can take your existing IBO app source and
just compile it in Kylix. The only way that would be possible is if you
used CLX in all of the source - for which you would need Win/CLX data
access classes. So - with source developed for the VCL, there will be
defines to do to make your source compile in Kylix and run in some sort of
a fashion on Linux.

We are not likely to have a CLX/Win version of IBO. We do have a CLX/Linux
version of IBO. We do have VCL IBO. The CLX (for Linux) and VCL (Windows)
code for the data access layer is in the *same* code units (with a
gazillion conditional compiler directives, no problem) Wherever *possible*,
the classes work just as they do in Delphi. But there are things that we
do in our IBO Windows apps that are not possible with just Kylix as it
stands now.

Hence the concern to get some clearer picture from B. about where, if
anywhere, Kylix is going.

It's not Firebird (or InterBase, for that matter) that's the cause of these
problems, which makes it decidedly off-topic in ib-support, for which I
apologise. We should keep these non-support threads in firebird-general.

cheers,
heLen