Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 1999-06

[lazarus]

4 messages · 4 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Michael A. Hess
to Cliff Baeseman: Check it out XLib is the layer just above the graphics driver so that means we are down…
Cliff Baeseman wrote
This is programming low and it is not going to be an easy task but it will give us total component control.

That is what I like about. Does it mean more work. OH BROTHER does it ever. Will it be worth it. IMHO I think so. Let's put it this way. If Borland were to port Delphi to Linux, this is how they would be doing it.

==== Programming my first best destiny! ==== Michael A. Hess Miracle Concepts, Inc. http://www.miraclec.com

Reply by email

Cliff Baeseman

Check it out XLib is the layer just above the graphics driver so that means we are down to the lowest layer below QT and below GTK. GNOME and KDE are built on top of GTK+ and QT which for sure are talking to XLIB.

As for events we will have to setup out own event handler loop that will do a peek on the XLib event stack and send the coresponding WM...

Control placement and resize would be totally up to us since we would be in charge of rendering the components.

This is programming low and it is not going to be an easy task but it will give us total component control.

Cliff

Earlier message 74 lines
-----Original Message----- From: Shane Miller To: Date: Sunday, June 27, 1999 8:11 PM Subject: Re: [lazarus] >I'm not real familiar with XLib so let me ask this. Is the XLib the method >that was used to write KDE and other GUI's? Or is it simply another >component library? > >If it's what's used in the desktop environments then using it would be >great. It would again take some learning on our parts again. Can we then >create a unit that has a CREATECOMPONENT and SENDMESSAGE and such that will >interface with X11 library? I would think that's the best way to do it. >The Forms.pp file would contain a class called TFORMS and in it's create >constructor we would call a procedure called createform or createcomponent >and pass a component type. In the X11 unit we write we would have that >procedure call X11 stuff to get it done. I think that would solve some of >the problems we are now having, like positioning the controls, resizing >them, etc. > >Shane > >-----Original Message----- >From: Michael A. Hess >To: >Date: Sunday, June 27, 1999 5:32 PM >Subject: Re: [lazarus] > > >>Cliff Baeseman wrote: >>> >>> Yep I think we are barking up the same tree.... >>> >>> I say we program directly against XLib instead of GTK and QT. This >>> will allow us ultimate control over component rendering and event >>> handling. We can place in the win32 primatives at the same time. I >>> have both a windows and linux machine in which to test the code.... >>> >>> Much Much more work but alot cleaner and flexible solution... >>> >>> It would probably be alot less work in the long run. >> >>It might be more work but it puts total control of the FCL output in OUR >>hands. Otherwise we are trying to write widgets in FPC that call widgets >>in another package. In GTK case the widgets we are calling aren't even >>OOP. Doing it this way in no way hinders anyone from also using FPC or >>the FCL with their favorite API (GTK, Qt, etc) it just means they don't >>have to. They would most likely be able to create a complete GUI program >>that could be delivered with out the requirement of any additional >>libraries except those that are part of X11 in the first place. >> >>I inclined to try and climb up this particular barking tree. :-) >> >>Any more opinions?????? >> >>-- >>==== Programming my first best destiny! ==== >> >>Michael A. Hess Miracle Concepts, Inc. >> http://www.miraclec.com >> >>_________________________________________________________________ >> To unsubscribe: mail with >> "unsubscribe" as the Subject >> archives at http://www.miraclec.com/list_archives/lazarus >> > >_________________________________________________________________ > To unsubscribe: mail with > "unsubscribe" as the Subject > archives at http://www.miraclec.com/list_archives/lazarus >

Reply by email

Jeff Wormsley
to Cliff Baeseman
Show quoted text 6 lines
Hello, >Borland were to port Delphi to Linux, this is how they would be doing >it. And become incompatible with its own Windows stuff?

They would -have- to be incompatible with the Windows stuff just to be able to release it. They can't rewrite the entire Windows API, and neither can we. Cross platform programs are possible, but not when you get down to the lower levels. For instance, Delphi doesn't have native serial port components. You must use WinAPI calls like CreateFile, SetCommTimeouts, etc. to use a serial port. Do you want to write the code to duplicate that functionality in Linux? Ok, how about Mapi, or the Media player? Yeah, a lot of the GUI will be multiplatform, which is good. The guts will still have a large number of {$IFDEF WIN32} wincode {$ELSE} linuxcode {$ENDIF} areas. To my mind, that is the single reason Borland hasn't seriously considered Delphi for Linux. They know their customers would be very upset if they couldn't just recompile their Delphi apps, and they know it is far more work than they can afford to do.

Jeff.

Reply by email