[lazarus] Update

[Shane Miller]

I created a LINUX.PP file and was going to put the stuff in there.
------------------------------------------------------------
Shane Miller

Get paid to surf the net!
http://alladvantage.com/go.asp?refid=DEX-870

Home page : http://www.lakefield.net/~smiller

Auto-IP Publisher : http://www.lakefield.net/~smiller/autoip

Advanced Clipboard : http://www.lakefield.net/~smiller/advclipboard

Lazarus : http://www.miraclec.com/lazarus
----------------------------------------------------------
-----Original Message-----
From: Marc Weustink <weus at quicknet.nl>
To: lazarus at miraclec.com <lazarus at miraclec.com>
Date: Tuesday, October 26, 1999 2:49 PM
Subject: Re: [lazarus] Update


>At 14:46 26-10-99 -0500, Shane wrote:
>>I certainly could use the help with MWEDIT.  If you search (grep) for the
>words TODO: you can see an awful lot of procedures and functions that need
>to be written yet.
>>
>>Feel free...  :-)  It'll make mwedit a lot more fun once we get it to
compile
>
>OK, second attempt (the first time NT just locked and I loosed all)
>
>I looked at the TODO's and found:
>
>Windows:
>  GetDC
>  ReleaseDC
>  GetObject
>  SelectObject
>  DeleteObject
>  ShowCaret
>  HideCaret
>  SetCaretPos
>  GetSystemMetrics
>  RecreateWnd
>
>  Canvas: (*)
>    ExtTextOut
>
>  Font: (*)
>    GetTextMetrics
>    CreateFontIndirect
>
>  ScrollBar: (*)
>    SetScrollInfo
>    ShowScrollBar
>
>System:
>  StringOfChar
>
>Menus: (!)
>  ShortCut
>  ShortCutToKey
>
>other:
>  TRegistry
>  TBitmap.LoadFromResourceName
>  TFont.Pitch
>
>Now the question how to implement. I think thewre are a few options:
>1)
>Don't support direct API calls. Use their class counterparts. IE, dont use
>ExtTextOut(Canvas.Handle, ...) but use Canvas.ExtTextOut(...). This bereaks
>a lot of compatibility.
>
>2)
>Use a platform dependent windows.pp like the classes unit. However there
>aleady exists a rtl windows.pp (and linux.pp)
>
>3)
>Since linux.pp and windows.pp are rtl files, create ONE LCLwindows.pp. This
>file contains (win)API related implementations for every platform (if it is
>possible) or just a call to its InterfaceObject(since it's global)
>counterpart (all platform specific stuff in one place). Like
>LCLwindows.ExtTextOut calls InterfaceObject.ExtTextOut.
>
>Question is, what way to go. I think I prefer last one. It's only adding a
>reference to LCLwindows if needed. Any thoughts ?
>
>Marc
>
>(meanwhile doing some menu stuff)
>
>
>_________________________________________________________________
>     To unsubscribe: mail lazarus-request at miraclec.com with
>                "unsubscribe" as the Subject
>    archives at http://www.miraclec.com/list_archives/lazarus
>