[lazarus] LCL Structure Discussion

[Baeseman, Cliff]

Well first of all it will gain us access to every widget set on a even
ground. It would also give us access to all of the C++ libs and there is a
bunch of them. Say for instance we needed to load a image to a widget. I
could do it inside of the library with just a few simple lines of C++
because of all of the libs that already exist for it. I definately see this
as a way to speed along development. Say we wish to use the editor for GEdit
or KWrite we can do this with a couple of lines of code in the library to
expose the methods.

Now that I think about it a little I would not be suprised if borland did
not go this route.

Cliff

-----Original Message-----
From: Michael A. Hess [mailto:mhess at miraclec.com]
Sent: Tuesday, October 12, 1999 10:00 AM
To: lazarus at miraclec.com
Subject: Re: [lazarus] LCL Structure Discussion


Cliff Baeseman wrote:
> 
> I would like to open up something here for discussion.
> 
> 
> Now here is where I am going with all of this. Say I was to build a
> C++ library that could handle all of the UI calls by passing something
> like IntSendMessage(int Message, int WidgetID,  pointer
> varDataRecord). We then define a single call back routine that would
> pass back the WidgetID and a event message constant.

What am I missing here. Isn't this exactly the same thing we are already
doing? The only difference is that you have it as an external library
instead of linked code. Is that the difference?

> The linux side of the world would have to be written in C++ ....

Why??

-- 
==== Programming my first best destiny! ====

Michael A. Hess      Miracle Concepts, Inc.
mhess at miraclec.com   http://www.miraclec.com

_________________________________________________________________
     To unsubscribe: mail lazarus-request at miraclec.com with
                "unsubscribe" as the Subject
    archives at http://www.miraclec.com/list_archives/lazarus