I have added hints to the object inspector. When you move the mouse over the object inspector it will show the property name or the property value depending on where the mouse is.

I was kicking around having the hint always display the NAME:Value or something like that. Anyone have any cool ideas on what we could include in the hint to make it usefull? If not, it'll just display the name or value.

Shane

Shane Miller wrote

I changed the Object Inspector hints to show NAME of property, Value and property kind.

Very useful.

Does it all work cross-unit? Iow does it read dependant PPU's?

Added BringWindowToTop which should replace all the show/hide combinations we are using to bring forms to the top. This function get's passed the form's handle.

Added UnitWithForm to TProject. This allows me to pass the functon a form and get back the TUnitInfo for the unit that refers to that form. This is used in the DoBringToFrontFormOrUnit in Main.pp

The Toggle button to toggle between the Form you are designing and the unit's source now works. When you click on a form and press the Toggle button it brings up the SOurceEditor and set's the correct Unit to be active in the notebook on the SourceEditor.

Shane

I'm not sure what you mean. What information would you like to see?

Shane

I have added hints to the object inspector. When you move the mouse over the object inspector it will show the property name or the property value depending on where the mouse is. I was kicking around having the hint always display the NAME:Value or something like that. Anyone have any cool ideas on what we could include in the hint to make it usefull? If not, it'll just display the name or value.

Type information would be useful.

Mattias

I changed the Object Inspector hints to show NAME of property, Value and property kind.

Shane

Note that Lazarus works fine via remote-X. I regularly test lazarus running on my home-freebsd box from my work Win2000 box.

Hi,

- TComboBox now throws ?ButtonDown messages and ?ButtonUp messages.

- Double click events now work (again).
There is a method in the Object Inspector (CurrentEditDblClick) that gets the double clicks from the object inspector so we could add events now.

- The "smart" hints for the object inspector disappear when you click on the object inspector or in the currentedit box.

Shane

Sure they did. But no fix report yet.
A really nasty one is the bug 1652, which makes it impossible to use TPersistent. Probably there will be more bugs, but since you can't compile even the tiniest little lcl program, no one can tell.

I will check, if this has been secretly fixed...

Mattias

Linux:

Get the compiler : ftp://lazarus.freepascal.org/lazarus/fpc-1.0.5-laz.20010613.i386.rpm and install it.

Get lazarus via CVS (preferably). Read step 3a at http://www.lazarus.freepascal.org/how.php3?&language=english for the CVS info.

Once you install FPC and Lazarus, jump to your /opt/lazarus dir and type make lazarus. You will probably get errors linking like -lX?? not found. There are .so files in a ??/lib directory on your workstation that it's searching for. What I do is search for the X??.so.* . Usually there is a X??.so.1.2.4 and you need to create a symlink to it in your lib directory.

Create your symlinks. ln -s X?.so.1.2.4 X?.so
Lazarus should compile after 5-6 of those symlink problems.

Anything I missed, email here. Also, email your symlinks that you need to create. I'll add them to the web site.

Shane

>> Dalton Calford 11/21/01 08:27AM >>>

Hi Mattias,

And I will keep requesting for new developers. Ok, 12MB bad documented code is a mess. But you can simply help, with a new component or just adding some missing features to existing ones. It would also help, if we got more examples.

I have been following the project for a year or so, but, until now, I had no extra time to contribute to it.
I have noticed that the web site is not that up to date (and alot of versions/changes are going on all the time)
Can you post to the list, or point to a up to date web site, a complete, step by step procedure for someone who has never used fpc/lazarus/cvs so that they can put a development environment onto a linux and windows pc? We are a Delphi development house, and are willing to contribute, but, we would all like to have one solid starting environment to start our work on (and so that any bugs we find are real and not just a badly configured system).

We will be using win95/98/NT/2000/ME for the windows boxes and Linux Mandrake 8.1 for the linux boxes.

best regards

Dalton

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

You are so correct sir. I grabbed the wrong numbers myself. I infact meant the 0815 version. I new it was the Aug release but didn't realize that there were 2 of them and I took the numbers from the wrong one.

Use the 0815 version. That should be the one pointed to by the web site. I will make sure it points to that one.

Hi Mattias,

And I will keep requesting for new developers. Ok, 12MB bad documented code is a mess. But you can simply help, with a new component or just adding some missing features to existing ones. It would also help, if we got more examples.

I have been following the project for a year or so, but, until now, I had no extra time to contribute to it.
I have noticed that the web site is not that up to date (and alot of versions/changes are going on all the time)
Can you post to the list, or point to a up to date web site, a complete, step by step procedure for someone who has never used fpc/lazarus/cvs so that they can put a development environment onto a linux and windows pc? We are a Delphi development house, and are willing to contribute, but, we would all like to have one solid starting environment to start our work on (and so that any bugs we find are real and not just a badly configured system).

We will be using win95/98/NT/2000/ME for the windows boxes and Linux Mandrake 8.1 for the linux boxes.

best regards

Dalton

Shane Miller wrote

Most of these bug fixes are OS INDEPENDANT. Meaning that the bug existed on Linux and Windows and is now fixed. The reason for this is that we are using one code base for both OS's. The fixes I made affected the IDE and the IDE is all OS independant (except the debugger). I'm not sure if the version number should be changed. For example, the file MAIN.pp has been updated 152 times. We could have a version like: 0.9.152 I suppose but it may become slightly difficult to maintain (when multiple updates are done by multiple people) and I'm not sure of it's use.

Just do the following:

unit main;
Const
  MainVersion = '$Id:$';

This will insert the CVS version number in the MainVersion constant. You can manipulate this string constant a bit to extract the build version automatically, and show it in the About box or wherever you want.

This causes no extra work at all, and gives a slight idea of the version.

Michael.

Do these bugs fixed / updates apply to Lazarus on Win32 / Linux / ?? or are they OS independant?

Thx to fpc, Lazarus has only a few hundred lines of OS dependent code (mostly the debugger) and less than 10% is widget dependent code.

These are compiled daily, right? Would it be useful to increment the Lazarus version in the Lazarus main menu each time a (set of) code update(s) has been applied?

Hmm. I think, we could increase the third version number every 20th or 50th cvs update.

Keep up the good work!!

And I will keep requesting for new developers.
Ok, 12MB bad documented code is a mess. But you can simply help, with a new component or just adding some missing features to existing ones. It would also help, if we got more examples.

Mattias

Dalton Calford wrote

I have noticed that the web site is not that up to date (and alot of versions/changes are going on all the time)

Actually we are still at the same version as indicated on the web site. The work that has been going on up to this point has been bug fixes and small but specific feature enhancements to the IDE itself.

Can you post to the list, or point to a up to date web site, a complete, step by step procedure ....

All the information indicated on the web site with regards to CVS, setup, build, etc. is still valid and correct. We are currently waiting for a few minor details in the 1.1 version of the compiler to switch the whole Lazarus base over to that version. At that point a new version release of Lazarus will be available with some features not possible with the current compiler version.

We will be using win95/98/NT/2000/ME for the windows boxes

The Windows version of Lazarus can be a little dodgy at times and this is due to the Windows version of GTK. The best platform to start working with is the Linux version since this is where the major development takes place.

FreeBSD versions are made on demand by me.

NetBSD builds are also possible but hard (since NetBSD can't link dynamically atm, and they have to be static)

I was hoping that was the case because I pulled the win version and it doesn't do much. :-)

Shane

>> 11/20/01 02:37PM >>>

Ronan van Riet wrote

One other thing I am curious about are the Lazarus Win32 binaries found at ftp://lazarus.freepascal.org/lazarus/lazarus_ide_installer.exe These are compiled daily, right?

Yes and no.

I have things setup to do nightly builds but I was having problems with the Win32 compiler back in Aug. At that point I turned off the nightly Win32 build until I got that straightened out.

Unfortunately I have yet to do so. I need to build or get hold of a current Win32 version of the compiler that is required for the current build of Lazarus. Once I get that I can turn on nightly builds again.

If I get a chance I can try to build a new version of the compiler tonight in an attempt to get that going again.

The Linux version of Lazarus are nightly builds.

Changes:

- I added the smart hints in the editor. They don't really do much yet. All it does is popup the word the mouse is over. It doesn't attempt to figure out what the word is. I don't have a good idea on how to accomplish that yet. It involves doing a quick compile and capturing information from the browser file or something similiar. Any ideas are appreciated. How they work:
Move the mouse in the editor. Once you stop the smart hint appears if the mouse is over some text in the editor.

Shane

as one of the users i would say

ftp://lazarus.freepascal.org/lazarus/fpc-1.0.5-laz.20010815.i386.rpm

since this is the latest known to work rpm on ftp
although i do not know if there are any differences in the 0802 and the 0815 version

satan

Hi

Is Lazarus ready for any sorta Interbase RDBMS activity? I hv a project on hand for IB on Linux. I dont prefer to go for Kylix ,even though it is touted to be identical to Delphi. Other option is to go for Interclient and Java.

Suggestions /Advices are invited for speedy development.

regards

Nataraj
India

Okay thanks for the update.

Kind regards,
Ronan van Riet

We actually have some interbase components for Lazarus from the LCL so you could look at them and decide if it's ready.

If you go into idecomp.pp you can remove the space in front of the DEFINE DATABASE and DEFINE INTERBASE and then re-compile. Then the interbase and database components will be displayed on the component palette. This requires interbase to be installed (version 6 I believe).

Shane

>> 11/24/01 08:55AM >>>

Hi

Is Lazarus ready for any sorta Interbase RDBMS activity? I hv a project on hand for IB on Linux. I dont prefer to go for Kylix ,even though it is touted to be identical to Delphi. Other option is to go for Interclient and Java.

Suggestions /Advices are invited for speedy development.

regards

Nataraj
India

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

I think it's better to add simply the date of the build, no?

Ronan van Riet wrote

One other thing I am curious about are the Lazarus Win32 binaries found at ftp://lazarus.freepascal.org/lazarus/lazarus_ide_installer.exe These are compiled daily, right?

Yes and no.

I have things setup to do nightly builds but I was having problems with the Win32 compiler back in Aug. At that point I turned off the nightly Win32 build until I got that straightened out.

Unfortunately I have yet to do so. I need to build or get hold of a current Win32 version of the compiler that is required for the current build of Lazarus. Once I get that I can turn on nightly builds again.

If I get a chance I can try to build a new version of the compiler tonight in an attempt to get that going again.

The Linux version of Lazarus are nightly builds.

Hey,

- improved the dragging and moving of controls on the forms when designing.
- can no longer drag controls off the form
- designer hints will not appear when a mouse button is down.

Shane

Changes:

- Hints are updated so they don't appear when another window is overlapping it and the mouse is actually in the other window.

- Double clicking update. Still not perfect, but adding events by double clicking the FIRST time works better. Events still don't stick.

Shane

- the core team page does not show the core team (I hate core team pages, but that is my personal problem)

Please remove me from any web pages, if I happen to still be on them. I do not have the time to devote to the project like I had hoped to. I will continue to read the list, but unless circumstances permit, I will not be able to contribute (in case anyone noticed I haven't in quite some time.)

Sorry,
Jeff.

Most of these bug fixes are OS INDEPENDANT. Meaning that the bug existed on Linux and Windows and is now fixed. The reason for this is that we are using one code base for both OS's. The fixes I made affected the IDE and the IDE is all OS independant (except the debugger).

I'm not sure if the version number should be changed. For example, the file MAIN.pp has been updated 152 times. We could have a version like: 0.9.152 I suppose but it may become slightly difficult to maintain (when multiple updates are done by multiple people) and I'm not sure of it's use.

Thanks
Shane

>> 11/20/01 01:37PM >>>

It seems a lot of Lazarus' bugs are being addressed and fixed. This is excellent!!

Do these bugs fixed / updates apply to Lazarus on Win32 / Linux / ?? or are they OS independant?
One other thing I am curious about are the Lazarus Win32 binaries found at ftp://lazarus.freepascal.org/lazarus/lazarus_ide_installer.exe These are compiled daily, right? Would it be useful to increment the Lazarus version in the Lazarus main menu each time a (set of) code update(s) has been applied?

Keep up the good work!!

Kind regards,
Ronan van Riet

Shane Miller wrote

Actually, mines version 1.0.5 2001/06/14

As pointed out by another user I should have said the 08/15 version. You might want to use this version. That is the one I use for nightly builds and it is the one that Mattias and Marc are using. That way we are all on the same page. :-)

The error is:

Not Found
The requested URL /cgi-bin/cvsweb was not found on this server

Kind regards,
Ronan van Riet

It seems a lot of Lazarus' bugs are being addressed and fixed. This is excellent!!

Do these bugs fixed / updates apply to Lazarus on Win32 / Linux / ?? or are they OS independant?
One other thing I am curious about are the Lazarus Win32 binaries found at ftp://lazarus.freepascal.org/lazarus/lazarus_ide_installer.exe These are compiled daily, right? Would it be useful to increment the Lazarus version in the Lazarus main menu each time a (set of) code update(s) has been applied?

Keep up the good work!!

Kind regards,
Ronan van Riet

The error is: Not Found The requested URL /cgi-bin/cvsweb was not found on this server

Cvsweb was just shut down due to very heavy usage (maybe even DOS), from a site in Poland.

What is missing/wrong in the 1.1 compiler?

Hey again,

- pressing DEL key when a form is selected no longer crashes lazarus.

Shane

I don't think it was anything missing it was some bugs that caused a problem. We discussed this on the developers list and made attempts to use the 1.1 version.

Marc and Mattias have a better idea of what was failing when they tried to build with 1.1. This was back around the end of last month so I sort of forget what the exact details were. I thought the other guys submitted bug reports to FPC but maybe they didn't.

Actually, mines version 1.0.5 2001/06/14

Shane

>> 11/21/01 09:47AM >>>

Don't you mean

ftp://lazarus.freepascal.org/lazarus/fpc-1.0.5-laz.20010802.i386.rpm

That is the one used for nightly builds and the one I believe the other guys are using.

Changes:

- You can now double click on values in the object inspector and they will change. For example, click on a boolean value, then double click and it'll switch from True to False. If there are multiple values in the combobox it'll select the next value. If the last is selected, it'll select the first.

- You can doulble click and create events in the object inspector. However, the code is not yet created in the editor and the event doesn't stick. I have to figure that out yet. That's been more of a Mattias task.

Shane

Don't you mean

ftp://lazarus.freepascal.org/lazarus/fpc-1.0.5-laz.20010802.i386.rpm

That is the one used for nightly builds and the one I believe the other guys are using.

We still have the goal to build a RAD like Delphi, that's true. But the web site is definitely out of date. For example:
- "by the 1st quarter of 2000"
- there is no discussion about the LFM file format.
- the "Add lazarus libs" to ppc386.cfg shows the wrong paths (2 times)
- it does not support screen solutions bigger than 1024
- the core team page does not show the core team (I hate core team pages, but that is my personal problem)
- ...

But since we have only programmers and no webdesigners, this is something we have to live with. Hopefully we will find someone, who is a better webdesigner than a coder.

Mattias