Re: File - IMPORTANT - Functioning and policies of kylixgroup

On Monday 03 June 2002 07:40 am, you wrote:
> > > wow, the group is alive?
> >
> > There are people on this list, just not that many I supsect...
> >
> > I guess I have counted about 20 names since the list started -- how many
> > of those are still subscribed, and how many lurkers there may be I guess
> > only Ernesto would know...
>
> The group currently has almost 150 members.

Well, that's more than I'd have guessed...


> Since many questions will fall in an empty sack for a while -for the
> reasons I explaind above-, and since likely most of you will prefer not
> to make questions under these circumstances, maybe you'd like to start
> using the group simply to share your experiences with Kylix...
> successes, failures, discoveries, problems you got to solve and that
> others may have... This is an alternative group, so feel free to use
> it as an alternative group!

OK:

I've been using Kylix for about six months in a development environment, in 
fact I had never used Delphi until I started with Kylix, so for me it was a 
full learning curve, namely relearning Pascal (college days seem a long time 
ago), and learning the Kylix environment.

In all I'm very impressed with what Borland have achieved, although I wish 
there was better integration into the primary Linux desktop environments, 
considering CLX is built on Qt, I'd have thought that there would be at least 
a nod in the direction of KDE integration.  As for Gnome, I don't know what 
other peoples' experiences are, but I've found Kylix to be a complete sow 
when used under Gnome[1].  

Kylix is clearly orientated to server/services development, where Delphi 
seems much more general purpose, even without third party SDK's.  I can 
understand why Borland have chosen this direction for the Linux version of 
Delphi, but I hope that later versions of Kylix offer at least some Media 
layer support.  Oh, and Borland, if you are listening, any chance of fixing 
Scanline so that it doesn't cause an ungodly long pause before first 
assigning a pointer?[2]  It makes pixel level manipulations of a use visible 
image kind of unusable even on fast processors, and is really making my life 
hell. :(

[1] free clues anyone?

[2] I'm guessing since subsequent scanline accesses are quick, and that there 
seems to be a corresponding pause when calling draw after a scanline 
operation, that the canvas is being copied to and from a scanline ready state?

-- 
Adam