[lazarus] State of the union ?

[Marc Weustink]

+ From: michael@[195.207.84.152] [mailto:michael@[195.207.84.152]]On
+
+ On Thu, 16 Dec 1999, Michael A. Hess wrote:
+
+ > michael at tfdec1.fys.kuleuven.ac.be wrote:
+ > >
+ > > Good. How far are we with the IDE ?
+ >
+ > I'll have to leave Marc answer that one. From what I understand it is
+ > getting very close. One nasty problem, as I see it, is that one
+ > currently needs to be running XWindows in 8bit mode to see anything work
+ > or various items will core.

That just a temporary hack. If you want another resolution just change the
following line in TBitmap.Create:

constructor TBitmap.Create;
begin
  inherited Create;
  // supported: pf8bit, pf15bit, pf16bit, pf24bit, pf32bit (and some others)
  FPixelFormat := pf8bit; // <--- change this to the depth of your display
  FCanvas := TBitmapCanvas.Create(Self);
end;

At that time I wasn't able to get the depth of the system we are running on,
and to get things working for me (to get the editor running) I defaulted to
8.

+ > I run in 32bit so it is a pain to change over to check on things.

It should be possible to run a second X sesion on a second virtual console
;-)

+ > What say you Marc? Can you give us a brief but detailed
+ > report on what you have working with mwEdit and the IDE?

mwEdit AND the IDE ? On the editor I'm getting close. For some reason it
wont set the number of lines bigger than 0. This is done in the resize
method, and I just fixed some events to get a resize event. So thats the
current state. I expect I'm close. Since the moment it has more lines it
will display more lines.

After that I'll look after putting scrolbars support into
TWinControl/TCustomControl so we can scroll text :-)
And there after I might rush trough all events/components to fix the events
and the way of creation.
After that I might look after TImageList to complete (hmm.. I'll first fix
the Draw)


+ > > How many running components are there ?
+ >
+ > Hmmmmm. That is a very good question that I guess we really
+ > do need to figure out. Several previously working components have been
+ > broken due to the conversion to the WindProc method of doing things.

Hmm... the WindProc hasn't to do very much with this. It the change of
creating components and attaching signals. In the past this was done in the
constructor of the component and now its handled by TWinControl.

+ > That and other changes that were made for canvas and this and that.
+ > I will have to look at going back through and attempt to use some
+ > of the components to see what still does and doesn't work.

The moment I see a component not creating itself the way it should I fix it.

+ A small demo suite like the one with the dialogs would be a
+ good idea and a good test.

Thats a point. The Hello and ComDlgs demo apps are a good test case, but
they only test a limited amount of components. Maybe we should create a form
with all the components we have.

Marc