Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2025-02

New MacOS user

3 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

DougC

I've just decided to get back into programming and will be using the Lazarus IDE on my two Mac's (M1 and M4 models).

In the past I have been thoroughly confused by the installation and configuration instructions that came with Lazarus and FPC. That led me to give up on them and go back to Delphi. But now I'm solidly entrenched in MacOS, so Lazarus and FPC are my only real options.

I'd really like to contribute to the Lazarus and FPC projects, but I need to get familiar with them more before making suggestions. I think I would be most helpful in editing documentation, but we will see.

While I do this I think it will be worthwhile to test if the current state of the documentation is as good as we want it to be. So, I'll be doing what I think are smart steps and reporting on the problems I encounter. That way we can turn around and clarify instructions where it seems necessary.

So, I'll be going to the websites, downloading what I find, following the directions, and asking for help when I need it. My questions may become annoying, so I just want to let everyone know that my intentions are honorable and I do not mean to be annoying.

Off to lazarus-ide.org to get started!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20250227/ab2e694d/attachment.htm>

Reply by email

Juha Manninen
to DougC

On Fri, Feb 28, 2025 at 8:56?AM DougC via lazarus <

Show quoted text 11 lines
wrote: I'd really like to contribute to the Lazarus and FPC projects, but I need to get familiar with them more before making suggestions. I think I would be most helpful in editing documentation, but we will see. While I do this I think it will be worthwhile to test if the current state of the documentation is as good as we want it to be. So, I'll be doing what I think are smart steps and reporting on the problems I encounter. That way we can turn around and clarify instructions where it seems necessary.

There is HTML documentation for the public APIs, functions and components. Other instructions for installation and usage etc. are in a community wiki. It has the same problems as any community wiki, namely poorly structured and partly duplicate data spread around because there is no editor-in-chief. If you make corrections there, observe how the bigger structure looks. Don't be afraid to remove data when it is outdated or duplicate.

Juha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20250228/08b2bbb7/attachment.htm>

Reply by email

Matthieu Giroux
to Juha Manninen

I am searching Mac OS packagers and testers with www.Ancestromania.eu .

Matthieu Giroux 13 Rue Fr Tanguy PRIGENT A.15 - 35000 RennesT?l : 09 61 37 01 82 - 06 44 733 008 http://www.liberlog.fr

Le vendredi 28 f?vrier 2025 ? 11:10:52 UTC+1, Juha Manninen via lazarus a ?crit :

On Fri, Feb 28, 2025 at 8:56?AM DougC via lazarus wrote:

I'd really like to contribute to the Lazarus and FPC projects, but I need to get familiar with them more before making suggestions. I think I would be most helpful in editing documentation, but we will see.

While I do this I think it will be worthwhile to test if the current state of the documentation is as good as we want it to be. So, I'll be doing what I think are smart steps and reporting on the problems I encounter. That way we can turn around and clarify instructions where it seems necessary.

There is HTML documentation for the public APIs, functions and components.Other instructions for installation and usage etc. are in a community wiki. It has the same problems as any?community wiki, namely poorly structured and partly duplicate data spread around because there is no editor-in-chief.If you make corrections there, observe how the bigger structure looks. Don't be afraid to remove data when it is outdated or duplicate. Juha

Reply by email