[lazarus] Question about component structure

Curtis White osiriz at teleport.com
Fri Jul 30 15:19:35 EDT 1999


That is a good idea. We may want to consider creating a directory structure
similar to the RTL and FCL, where we have a directory for each platform (or in
our case, each different type of api). So we would have a lcl/gtk, lcl/qt, and
lcl/win32 directories that contain the gtkint code for each of those api's. This
will help us keep things organized as to what code is platform independent and
what code isn't. All the code in the lcl directory would be platform
independent. Then when we want to port to another platform, we just have to port
the code from either the gtk, qt, or win32 directory, whichever is closest to
the new platform. What do you all think?


Curtis

On 30-Jul-99 Jeff Wormsley wrote:
> Hello all,
> 
>   Working from memory (I am at work now, away from the code) the GTK stuff
> right now is localized to the GTKINT.PP file.  I assume that when QT, Win32
> native, etc. are put in, that they will be likewise in a QTINT.PP and a
> WIN32INT.PP file.  Will these files be located in the LCL directory, or will
> the LCL have further subdirectories for each of these?  Also, the GTK files
> are in \pp\source\gtk right now.  I assume there will be a \pp\source\qt and
> \pp\source\win32 as well?  Or will WIN32 stay as it is under
>  RTL and FCL?  I am a bit curious, but I would like to look at the WIN32 API
> this weekend, as I am a lot more familiar with it than GTK.  I want to know
> where to put things, and where to access things that are already there.
> 
> Jeff.
> 
> 
> _________________________________________________________________
>      To unsubscribe: mail lazarus-request at miraclec.com with
>                 "unsubscribe" as the Subject
>     archives at http://www.miraclec.com/list_archives/lazarus

----------------------------------
Curtis White
Curtis White <osiriz at teleport.com>
http://www.teleport.com/~osiriz/
----------------------------------






More information about the Lazarus mailing list