The Lazarus team is glad to announce the release of:

Lazarus 1.0

At this important stage the current team would like to thank all the past and current people who were involved in getting us here.
* Thanks also go to the FPC team for providing the compiler that makes it all possible.
* Special thanks go to the founders of the project who started Lazarus more than a decade ago in 1999: Cliff Baeseman, Shane Miller and Michael A. Hess.
* A history of developers involved can be found at http://wiki.lazarus.freepascal.org/History. And a list of the many contributors comes with the distribution.

The release is available for download at the SourceForge download page: http://sourceforge.net/projects/lazarus/files/

Choose your CPU, OS, distro and then the "Lazarus 1.0" directory.

Minimum requirements:
Windows: 98, 2k, XP, Vista, 7, 32 or 64bit
FreeBSD/Linux: gtk 2.8 or qt4.5, 32 or 64bit
Mac OS X: 10.4, LCL only 32bit, non LCL apps can be 64bit

This release has been built with fpc 2.6.0 (the former release 0.9.30.4 was built with that too).

The svn tag is
http://svn.freepascal.org/svn/lazarus/tags/lazarus_1_0

The list of changes:
http://wiki.lazarus.freepascal.org/Lazarus_1.0_release_notes

For people who are blocked by SF, the Lazarus releases from sourceforge are mirrored at: ftp://freepascal.dfmk.hu/pub/lazarus/releases/
and later at (after some time for synchronization) http://michael-ep3.physik.uni-halle.de/Lazarus/releases/ and
http://mirrors.iwi.me/lazarus/

Mattias

Congratulations!. I am a big fan of Lazarus/FPC.

2012/8/29 Mattias Gaertner :

Wonderful job!

Marcos Douglas

On Wed, Aug 29, 2012 at 8:51 PM, Mattias Gaertner <

Great :D

Some one tweet it please,
and thanks for the mirrors.

Zaher Dirkey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120829/820b8939/attachment.html>

Mattias Gaertner wrote

The Lazarus team is glad to announce the release of: Lazarus 1.0

Well done to everybody!

Graeme.

<snip>

Mattias

Congratulations & thanks to everybody involved!

Regards,
Reinier

Congratulations! Let's spread the word!

2012/8/29 Reinier Olislagers

Is there an official press release so that the news portals that might happen to stumble over this news know what they need to write?

Bernd wrote

Is there an official press release so that the news portals that might happen to stumble over this news know what they need to write?

I've just done a bit of tidying-up on the wiki history page in case news editors use that link (which Mattias mentions) for information. But something custom-written for today is probably needed too.

Congratulation! (Even if it's only a number ;) ) Let's hope for many nice features and even more stability to come :)

Regards,
Sven

Yes, urgently. Starting off with a *concise* URL for Mattias's announcement, without any forum comments or whatever tacked on.

Congratulations and thank you for your valuable work!

J. W. D.

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- Dr. Johannes W. Dietrich, M.D.
-- Laboratory XU44, Endocrine Research
-- Medical Hospital I, Bergmannsheil University Hospitals -- Ruhr University of Bochum
-- Buerkle-de-la-Camp-Platz 1, D-44789 Bochum, NRW, Germany -- Phone: +49:234:302-6400, Fax: +49:234:302-6403
-- eMail: ""
-- WWW: http://medical-cybernetics.de
-- WWW: http://www.bergmannsheil.de
-- Researcher ID: C-3498-2009
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120829/97fcbe39/attachment-0001.html>

This is great news! This is best thing that happens after the release of Delphi 1. :-)

I want to thank all the developers and everyone who have contributed to this project. You all did a great job!

2012/8/29 Mattias Gaertner :

The Lazarus team is glad to announce the release of: Lazarus 1.0

Congratulations and thank you!
Great project, great community!

Kjow

Congratulations!, thanks for making this dream come true.

Congratulations and many thanks to everyone who has contributed to this great programming tool.

Malcolm

*Congratulations for everybody in Lazarus team.*

:-\ Through everything I had problem to install linux i386 version on Mageia2 (x86). Fpc and fpc-src were installed OK, but Lazarus does need fpc-2.6.0-fc (fedora package?) not fpc-2.6.0-0.laz (originally listed). I have installed it via CLI with --nodeps but it is little bit annoying.

One more Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120830/79fe39ef/attachment.html>

Congratulations to this remarkable milestone to all of the Lazarus team and contributors. Marcelo B Paula.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120829/46ec2279/attachment.html>

Wow! Excellent work all you done! I can't believe I saw that ! all going to put the news on some foruns...

Congratulations! Great job, guys!

Sorry. I uploaded a new lazarus-1.0-1.i386.rpm.

Mattias

Congratulations.

Ant?nio

2012/8/29 Mattias Gaertner :

Great news!
Wrote a post about it
(http://idkn.wordpress.com/2012/08/30/lazarus-1-0/ - in Hebrew) :)

Thank you guys for your amazing work you do with the IDE

Ido

Mattias Gaertner wrote

The Lazarus team is glad to announce the release of: Lazarus 1.0

Great ! (regarding the excellent work of the Lazarus Team)

But I'll not recommend using it to anybody, as long as there is no final decision and implementation on the handling of (Unicode) strings in FPC.

There is a strong tendency to follow the Delphi way and make String to be UTF-16 encoded "by default". Supposedly Lazarus will need to follow at some point in time and modify all the LCL's user interface functions.

Thus at the given time porting current Delphi Projects does not make much sense.

-Michael

Congratulations, well done :)

Also thanks for whoever controls the G+ page :) Please keep it up!

L.

Thank you for the excellent work, Lazarus and FPC teams! I'll promote Lazarus 1.0 around me.
Thierry
----- Mail original -----
De: "Mattias Gaertner"
?:
Envoy?: Mercredi 29 Ao?t 2012 19:51:11
Objet: [Lazarus] Lazarus 1.0 Release

The Lazarus team is glad to announce the release of:

Lazarus 1.0
<snip>

Mattias Gaertner wrote

The Lazarus team is glad to announce the release of: Lazarus 1.0

Congratulations!

Regards, Bernd.

Congratulations for the 1.0 release :-)

How that? What would need to be changed when "string" becomes something different from AnsiString?

DoDi

Everything that depends on string being ansistring, like passing strings to cdecl functions (which is done much more often in Lazarus to interface with existing libraries in C).

Hans-Peter Diettrich wrote

How that? What would need to be changed when "string" becomes something different from AnsiString?

(Please don't let me start ranting about calling UTF-8-coded information "AnsiString" :-( :-( :-( )

At least any myString[i] and _explicit_ usage of the integers used in Length(), Pos(), Copy(), and friends is effected.

Not a big deal when _creating_ a program (and you know what you are doing), but can result in a huge percentage of the effort when poring a large Delphi program to FPC (which right now _is_ as good idea regarding the latest moves of Embarcadero's).

If I port a program done with a Unicode aware Delphi version (16-Bit Strings) to the current version of Lazarus (8 Bit Strings), and after some months need to redo all the fixes I painfully did, (with rather normal German programs I more often than not need to be aware of the Unicode encoding with UTF-8, but close to never with UTF-16), I'll be _very_ frustrated.

So I'll recommend holding off.

-Michael

Hans-Peter Diettrich wrote

How that? What would need to be changed when "string" becomes something different from AnsiString?

The whole RTL must be changed. So too the FCL. I recently tried to compile the tiOPF v3 branch (designed for Delphi 2009+ only), but with every compiler error I got and fixed, I got ten new ones pop up. The FPC compiler might support Unicode to some extent, but without the Unicode-enabled RTL, it's useless. FPC is definitely NOT ready for Delphi 2009+ apps yet.

Lazarus follows FPC, so the fault [or hold-up] doesn't lie with Lazarus though.

Regards,
- Greame -

Everything that depends on string being ansistring, like passing strings to cdecl functions (which is done much more often in Lazarus to interface with existing libraries in C).

Where does the Lazarus code pass strings directly to cdecl functions?

Mattias

Have you tried actually ported an application from UTF8 to UTF16 or other way round?

Mattias

I mean in Lazarus apps, i'm not sure about Lazarus itself (although i would expect the GTK+ interface, for example, to do that). I do that myself very often for example.

Kostas "Bad Sector" Michalopoulos

I mean in Lazarus apps, i'm not sure about Lazarus itself (although i would expect the GTK+ interface, for example, to do that). I do that myself very often for example.

There are some type casts strings to PChar.
That would still work with UTF16 strings. gtk2 creates its own copies of "strings".

Note:
You have to check all places. And some needs adaption. But I doubt that much code needs to be changed.

Mattias

Mattias Gaertner wrote

Have you tried actually ported an application from UTF8 to UTF16 or other way round?

I tested converting old ANSI-Delphi code to UTF-8 Lazarus and found these issues.

My colleagues ported old ANSI-Delphi stuff to Unicode Delphi and lost a lot of hair.

So I am sure that modifying code the other way round will not be much easier.

-Michael

Congratulations to all of you!

Salvatore

2012/8/29 Mattias Gaertner :

Everything that depends on string being ansistring, like passing strings to cdecl functions (which is done much more often in Lazarus to interface with existing libraries in C).

This can be done inside the interface or, when the interface is retyped, it does not affect user code because of automatic conversion.

DoDi

This is not a requirement, and does not affect user code.

DoDi

Hi,

???? 29/8/2012 8:51 ??, ?/? Mattias Gaertner ??????:

The Lazarus team is glad to announce the release of: Lazarus 1.0

Congratulations! Now let's see if it can pass the Debian freeze policy ... I hope ...

We could have a "Lazarus press kit" like this:
http://git.postgresql.org/gitweb/?p=press.git

2012/8/30 Dimitrios Chr. Ioannidis

Mattias Gaertner wrote

The Lazarus team is glad to announce the release of: Lazarus 1.0

You guys regularly developing Lazarus - including the fpc developers of course - are really amazing! Withstanding the talk of pascal being dead you all made this finally happen.

Besides holding up the flag of being like Delphi, you managed to build Lazarus and fpc into something unique that'll never fade (in contrast e.g. to the company not even having a stable name ;).

And you managed to be a reliable source of help in times of trouble, answering on the mailing lists and fixing things very fast.

Many thanks and good luck!

Congratulations from a happy and satisfied user,
Marc

Hans-Peter Diettrich wrote

This can be done inside the interface or, when the interface is retyped, it does not affect user code because of automatic conversion.

If the type "String" is moved to 16 Bit Characters and at the same time the LCL "Interface" is (necessarily) retyped in the same way, there is no additional automatic conversion, but the user code, depending on the Type "String", needs to be checked all over the place if or if not the re-definition of "String" might result in any problems.

My colleagues painfully did this to their huge count of huge projects on Delphi when the String Type - and at the same time the VCL "Interface" - did the change from 8 bit to 16 Bit Characters.

Only difference: Delphi moved from 8 bit ANSI to 16 BIT Unicode, Lazarus will move from 8 Bit Unicode to 16 Bit Unicode.

Thus, porting big applications from either Delphi version (8 Bit ANSI or 16 Bit Unicode) to 8 Bit Unicode will create additional issues regarding porting from 16 Bit Unicode Delphi to 16 Bit Unicode Lazarus, IMHO, is depreciated, and waiting for a 16 Bit Unicode version of FPC and Lazarus is recommended.

IMHO, the FPC and Lazarus teams should do the move to 16 bit Unicode as #1 priority, regarding the latest seemingly rather abysmal moves of Embarcadero's, prohibiting client/server - programming with affordable Delphi versions.

-Michael