Neven wrote:
> Just a quick Kylix question -
> What are they goning to do about database access or are just going to use
> Kylix to write screen savers
I'd guess it will just support TDatasets just like now and anything they
choose to write a TDataset against will be available. Unlike the UI
components, much of the non-visual components codebase is not
Windows-specific and should port over to Kylix just fine.
So, the question really is what will they build TDatasets interfaces for?
In the unix world, there are some open ODBC toolkits and Interbase has
always had a unix C API so I imagine InterBase would be a no-brainer and
perhaps ODBC will be likely.
I expect they may also feel moved to do whatever coding is necessary to
support mSQL/mySQL and maybe Postgres if they feel keen. This would be
largely to appeal to the Linux core i.e. use the open source DB engine you
know and love right now (whatever it is) and use Kylix to build your GUI and
maintain it rather than Perl/tcl/X/whatever.
I wouldn't expect ADO or MSDE support anytime soon however - they ain't open
source so only MS can port them and I don't expect MS is any more likely to
produce those than ship MS Office for Linux. MS does not appear to be keen
for people to consider Linux a viable client/desktop OS for obvious
strategic reasons :-)
Mind you, what do people use to connect unix desktops to MS SQL Server? If
there is an existing unix C API then I suppose it could be co-opted and/or
reverse-engineered. Still, I don't imagine Inprise/Borland are going to
spend much R&D dollars in that direction since many Linux adopters are
trying to get _away_ from MS technologies.
And if Inprise/Borland don't write the TDataset interface to your DB engine
of choice, if it has a unix C API, you always have the option of writing the
TDataset interface yourself...
TTFN,
Paul.
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
