I spent last 4 days with Kylix OE and I must say it's pain in the ass,
looks cool, but IDE is crashing every 20 minutes, if you reset running application, the process remains (and is hard to kill :-( ) and the QT dependency is really annoying, it ships with qt2.2.4 and RedHat 7.1 comes with 2.3.0. : KDE doesn't work with Kylix version and Kylix app crashes with 2.3.0.

O must say, that first impression is really bad.

Vit Kavan

______________________________________________________________________ Jake bude pocasi? http://pocasi.seznam.cz

I spent last 4 days with Kylix OE and I must say it's pain in the ass, looks cool, but IDE is crashing every 20 minutes, if you reset running application, the process remains

'Program reset' is not the correct way to shut the app down. It has similar problems in Windows, friends don't let friends do 'program reset'. I'm a professional Delphi trainer.. believe me I know what I'm talking about ;-)

Does Borland claim Kylix runs under 7.1? If not, don't expect it to magically work. Linux isn't like Windows in this respect.

(and is hard to kill :-( ) and the QT dependency is really annoying, it ships with qt2.2.4 and RedHat 7.1 comes with 2.3.0.

Runs fine under KDE 2.1. Don't upgrade to the latest version ;-)

The truth is you have to do 'funny things' with your SO path so that Kylix apps find the right version of QT and KDE finds it's favoured version. The problem with Linux is that every Distro tries to out league every other distro - release beta/non-working versions of stuff just to look 'newer better shinier' that the other guys. This kind of problem then arises! Roll on Kylix 2 with direct C++ linkage I say!!

: KDE doesn't work with Kylix version and Kylix app crashes with 2.3.0.

I've still never had any problems with Kylix under Mandrake 7.2 ... It's a fact of life that QT will continue to evolve. Shame for Borland though :-(

O must say, that first impression is really bad.

I was a beta tester. I saw pretty much every version along the way. Just be glad they didn't release Field Test 2.. lol.. that was nasty indeed. Very unstable.

Matt

Never had a problem with this. The only bad thing that might happen (at least in Windows 98) is that too much icons/buttons in the toolbar and in the application during tests are bad for the health of the GDI, otherwise, i have experienced so far no problem with the reset in either Delphi or Kylix.....

Does Borland claim Kylix runs under 7.1? If not, don't expect it to magically work. Linux isn't like Windows in this respect.

In a certain way, Linux with all the different distribution is way worth than different Windows version ever were....

With the IDE, i actually had no problems with Mandrake 8.0 or RedHat 7.1.......

The truth is you have to do 'funny things' with your SO path so that Kylix apps find the right version of QT and KDE finds it's favoured version. The problem with Linux is that every Distro tries to out league every other distro - release beta/non-working versions of stuff just to look 'newer

Well, that is my experience too. After developing an app on Mandrake 8.0, it was a pain to get the path to the QT libraries right in different distribution to get my program running.

better shinier' that the other guys. This kind of problem then arises! Roll on Kylix 2 with direct C++ linkage I say!!

Who really needs this if you have more than one good Pascal based compiler...;-)))

Let's see how this whole thing goes on.

Well, for a 1.0 version, it could have definitely be worse, but i haven't tried the OE version yet, though i wouldn't expect much difference in the IDE, just the libraries....

Ralf

I program in Delphi for 6 years professionaly and I use 'Program Reset' a lot and the crash-rate is acceptable.

Ad. QT: I did a simple trick: I renamed libqt,libqtintf to libqx,libqxintf and a simple FPC program modifies the Kylix built ELF to use them :-) really nasty

Vitek

______________________________________________________________________ Nejenom anglicko-cesky slovnik: http://slovnik.seznam.cz

Quoting "Ralf A. Quint" :

Create a BDE based app. Run it, open tables, run queries. Program reset it. Repeat this. In the end you'll get a 'Out of Memory' style message because Delphi hasn't closed down the BDE properly. Works best with DBase, though Paradox will work too.

Whilst using Delphi on an underpowered machine, program reset can randomly crash the IDE with an Access violation. Happened more in Delphi 4 than 5 however.

I program in Delphi for 6 years professionaly and I use 'Program Reset' a lot and the crash-rate is acceptable.

Today I was running the 4th day in the Borland Delphi Foundations cource (that's the official Borland course..) and one of my students insisted on using Program Reset repeatedly. The individiual in question ignored me, and promptly killed the BDE - running with a local Interbase Server. I rest my case ;-)

I'll admit I use Program Reset from time to time, but it leaves the IDE in such an unstable state that you'll often get an Access Violation (commonly in one of the VCL BPL's, frequently VCL50.BPL) soon after. Maybe we have larger apps than you ;-P, maybe we use more creative techniques, but it happens regularly. In any one day I can vouch that the IDE will crash a minimum of 2 times, just from writing fairly simple code. The worst case scenario (and one that only happens rarely) is when Delphi loses contact with the app it's debugging.. that can take Windows 9x with it. Thankfully NT/200 usually survives.

Ad. QT: I did a simple trick: I renamed libqt,libqtintf to libqx,libqxintf and a simple FPC program modifies the Kylix built ELF to use them :-) really nasty

That's a bit extreme. That also make distribution tricky.

Matt

Perhaps I am fortunate... I never use the BDE, instead using Extended Systems Advantage Local tables. Program Reset never kills the IDE for me.

The worst case scenario (and one that only happens rarely) is when Delphi loses contact with the app it's debugging.. that can take Windows 9x with it. Thankfully NT/200 usually survives.

I can make this happen without Program Reset fairly easily. Heck, just calling up a help screen in a program running under D5 can do it (the dreaded unwanted CPU window bit; do it two or three times, and blammo).

Jeff.

r

I can imagine no other way to stop multithreaded application when there is a bug in the thread and I loose control of it.

Ad. BDE: I don't use it, the last time I used it was with Delphi3 (around 400 kLines of source), now we use proprietary interface for PostgreSQL (the only todays DB which makes sense I think).

Vit Kavan

PS.: enough offtopics here :-))

______________________________________________________________________ Vylepsete svuj prohlizec Internetu na http://software.seznam.cz/listicka

Well, no problem here, i don't use the BDE (never have, never will)...;-)))

Whilst using Delphi on an underpowered machine, program reset can randomly crash the IDE with an Access violation. Happened more in Delphi 4 than 5 however.

How do you define underpowered? The least powerfull machine i have used it on for a while was a Pentium 233, 64MB RAM and 2x8GB HD...., normally i use either a PII/300, 192MB, 10+20GB at home or a PIII/450, 256MB, 10+30GB at work, both with Delphi 5 (Standard and Enterprise), while i currently run Kylix on a K6-2/300 with 128MB RAM....

Ralf