> I guess you must be dizzy with versionitis right now with a new
> version of IBO, a new version of Delphi, and the new CLX framework for
> Delphi 6 and Kylix.

Yes, it has been a little bit of a challenge to maintain so many versions of
things. I'm holding up pretty well. I've had much more difficult assignments
where version control was concerned in the past so this is still not that
bad. I've about got it down to a science now.

> How are you going to sort that out?

It's just a matter of organization.

> Which version of IBO are you
> porting to Kylix?

I already have some groundwork laid there with the same base of code that
IBO 4 was started from. But, that was merely for learning and gaining
conceptual information. Just like I did with IBO4, I will start over again
(almost totally) and do it from the most clean and solid base of code that I
have. This way I will minimize the amount of time it will take to get a
production worthy release.

So, my game plan is to get IBO 4 released as production and then use it as
the base to rewrite the Kylix port using all of the information that I
already have gained by porting the 3.6 base of code.

3.6 will NOT be ported to Kylix. Only IBO 4 will be.

> And after completing the Kylix version, will you
> port that back to Delphi 6/CLX? Will you continue developing both a
> VCL and a CLX version in the future?

I will have a CLX version of IBO. Yes, I will support both VCL and CLX.

> For about a year now, I'm anxiously awaiting the moment when I can
> compile one and the same source code for both the Windows and Linux
> platform, so I would hope for a CLX version of IBO for both Kylix and
> Delphi 6.

I am anxiously looking forward to the day that I can provide this for you.

> I'd be glad if you could explain what we can expect (and maybe when?)

Please be involved with the BETA and IBO development and it will pay off
richly. I do listen to the suggestions of my customers.

Regards,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com