Sign in Join

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

Mailing lists / lazarus / 1999-06

GTK vs QT vs XLIB

3 messages · 3 people ·

Reply by email Subscribe to this list Your subscription

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

Shane Miller

Here's my suggestion: Lets continue on the way we are going but move the GTK stuff out into a seperate unit and access it through generic calls like sendmessage and createcomponent. That way once the IDE is done if we want to use QT or the XLIB we can simply create a new unit with those functions in it and put it in the uses clause. For now, lets get an IDE up and running....

Cliff, I need you to continue work on the LAzarus IDE. Tie in the compiler and I will set it up to be able to open multiple pages on tabs. I need someone to look at the RESIZZE problem. How should the components (gtk widgets) be placed on the forms? Look at the createcomponent function in controls.pas

I know some of you want to attack the xlib to get more functionality and flexibility, but if we build these classes correctly we will be able to do that later. Lets get a useable set of classes first, then we can set them to link into any widget set we want.....

We need others to create some controls. TTreeView, TListView, etc. Look at GTK and see what controls we are missing yet....

Shane

Reply by email

d0hb0y
to Shane Miller

At 09:18 AM 6/28/99 -0500, you wrote:
<snip>

I know some of you want to attack the xlib to get more functionality and flexibility, but if we build these classes correctly we will be able to do that later. Lets get a useable set of classes first, then we can set them to link into any widget set we want.....

I agree, lets get something functional. I am starting to lean towards building onto GTK myself, it sounds like the best direction to get this project rolling.

== Ron

Reply by email

Nicolas Aragon
to Shane Miller: Here's my suggestion: Lets continue on the way we are going but move the GTK stuff out…

Hello,

Here's my suggestion: Lets continue on the way we are going but move the GTK stuff out into a seperate unit and access it through generic calls like sendmessage and

Not too bad, but inheritance is a better way to communicate. You make a direct call to a method that's intended to do something, has a significative name and a descriptive list of parameters. Errors are detected at link time and you don't need a "lazarus messages reference", but only object pascal code.

greetings

Nico

Reply by email