> No!! At least that's not what I've gleaned about CLX, which is: CLX is a
> set of cross-platform components designed to replace the Windows component
> set. If you want to run on Linux, you obviously can't use the Windows
> components, so you're likely to use CLX components.
Correct, mostly. CLX defines "Tbutton" etc, so you can get some code
compatability, but you are going to get the best results going from CLX on
windows to CLX on Linux -or vice versa - rather than VCL to CLX.
That said, dbExpress stuff works just fine and dandy with VCL stuff - they
all appear to talk thru a TDataSource....
> But if that's not the
> case, then there's nothing to stop you using whatever you want, mixing and
> matching, using a CLX button here and a Windows button there, AFAIK. It's
> just a matter of using different units.
I think so, tho I dunno how the various implementation of things like TForm
and TApplication would handle it. I think (not sure yet) that you _can't_
use vCLX and VCL together, but you can use the non-visual stuff
(dbCLX/dbExpress) in any way you want.
> Besides, DBExpress is what they call DataCLX. I think this stands alone,
> ie. it's only similar to CLX because both will work cross-platform. I
doubt
> there will be much, if any, commonality between them because DataCLX
> shouldn't really require any visible controls.
_exactly_
Nic.
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
