| Subject | Re: [IBO] About to start a project with IBO and firebird |
|---|---|
| Author | Helen Borrie |
| Post date | 2003-05-14T12:13:10Z |
Christoph,
Some quick answers to some of your questions:
At 11:32 AM 14/05/2003 +0000, you wrote:
you are working towards a production version of your work. If you need the
source code, you can write a private email to Jason or to me and make a
case for deferring your subscription until your app goes into commercial
production.
beta. For Delphi-style visual apps your current choices are to use the
TDataset-compatible data access with Borland and/or third-party data-aware
visual controls (widgets), or the native IBO data access with
non-data-aware widgets.
I think the likelihood of a full CLX version of everything that is
currently in IBO for Windows is between minute and nil. CLX on Windows is
a very limited beast. The native IBO data-aware controls are bound quite
tightly to Windows capabilities that are not currently available to widgets
on Linux, either because of non-implementation or because of licensing
constraints regarding the Linux and Windows API's for the QT subsystem.
common hierarchy. So, unless you are converting an application with a text
interface, such as a service console, it is not a question of conversion
but of total rewriting.
Our code for the non-visual components uses conditional defines so that
(theoretically) you can compile them on Windows using the VCL and on Linux
using CLX. We could get around to testing the non-visual CLX code on
Windows but it's not a priority.
AFAICT, cross-platform Delphi code for anything non-trivial that needs a
GUI seems fated to stay in Dreamland whilst Borland pursues its infatuation
with .NET.
Helen
Some quick answers to some of your questions:
At 11:32 AM 14/05/2003 +0000, you wrote:
>I am about to start a project with Delphi 7, IBO and firebird and IIf you are happy to use the evaluation version, then it's nice to know that
>have some questions:
>
>2. If I read it correctly the trustware licence allows me to develop
>my app and then pay for IBO when I sell my app? Is that correct. Do
>I need to notify anyone that I am starting development?
you are working towards a production version of your work. If you need the
source code, you can write a private email to Jason or to me and make a
case for deferring your subscription until your app goes into commercial
production.
>4. Is there likley to be a CLX version of IBO in the future?We already have the two streams of data access in CLX in the IBO-Kylix
beta. For Delphi-style visual apps your current choices are to use the
TDataset-compatible data access with Borland and/or third-party data-aware
visual controls (widgets), or the native IBO data access with
non-data-aware widgets.
I think the likelihood of a full CLX version of everything that is
currently in IBO for Windows is between minute and nil. CLX on Windows is
a very limited beast. The native IBO data-aware controls are bound quite
tightly to Windows capabilities that are not currently available to widgets
on Linux, either because of non-implementation or because of licensing
constraints regarding the Linux and Windows API's for the QT subsystem.
>If so,They are two incompatible systems of components. They don't even have a
>when is it likley and how much conversion will be nevessary?
common hierarchy. So, unless you are converting an application with a text
interface, such as a service console, it is not a question of conversion
but of total rewriting.
Our code for the non-visual components uses conditional defines so that
(theoretically) you can compile them on Windows using the VCL and on Linux
using CLX. We could get around to testing the non-visual CLX code on
Windows but it's not a priority.
AFAICT, cross-platform Delphi code for anything non-trivial that needs a
GUI seems fated to stay in Dreamland whilst Borland pursues its infatuation
with .NET.
Helen