No crashes here. What is the fuss about?

[JuhaManninen]

This should actually go to forum or mailing list but I didn't find those here in Github.
If this project has a forum, please let me know.

I am interested what are the current difficult issues. I could then try to help with them.
The wiki says:
"Even when we cleaned up the codetree and made specific configurationfiles for Lazarus per platform, it turned out not to be portable from one developer to another. What would compile and run succesfully for one person would totally crash for the next. In a multiple person development team this behaviour is totally unacceptable."

Lazarus + LCL are cross-platform and don't have dependencies for C libs or such.
I wonder what caused those crashes. Where can I find more info?
I was able to build and run BrewBuddy on Linux after installing the required packages and copying the fann shared libs.
At one point I saw HourGlass cursor all the time but not any more. It is caused by all handlers calling Update method and all setting the cursor. It could be improved by using enum flags + Application.OnIdle handler.
I played with the GUI but didn't see any crashes although some bug reports said so. (I don't understand Dutch but Google translate does.)
Having separate projects for different OS targets seems useless. The build targets can be defined in BuildModes inside one project.
Unit OSspecific is not used anywhere.

English translation would be important. I could copy the automatic translations to the .po file. They are rather good nowadays.

Unit bh_report did not compile with Lazarus trunk because it referred to "FChart.AxisList[0].Title.Font" in 3 lines but the Title has no Font any more. I guess TAChart changed since Lazarus 1.8.

Juha Manninen

[JuhaManninen]

Forgot to mention:
Mac Cocoa widgetset is in good shape in Lazarus trunk. That is what people say, I don't have a Mac myself.

[JuhaManninen]

Ok, I understand what you are talking about.
After some testing and tweaking I experienced some serious memory issues.
Please see my fork and pull request for details.