<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">I am cross posting this to the Lazarus
list, since some of this relates to Lazarus.<br>
<br>
On 16/10/2024 01:07, Rainer Stratmann via fpc-pascal wrote:<br>
</div>
<blockquote type="cite" cite="mid:2117168.oxAcqbJhdy@debian1-3">
<pre wrap="" class="moz-quote-pre">- Lazarus looks very complicated with its many windows. And it is also
relatively complicated to understand and use. There are too many options that
are too nested.</pre>
</blockquote>
About the options: This is 2 fold.<br>
<br>
1) The count<br>
2) The presentation<br>
<br>
"Count": Of course (assuming that all those involved in the
decision making can be convinced) they can be reduced. Then
existing users will just have to live with the loss of their
favourite setting. Or be forced to install (included or 3rd party)
add ons. Or worst, leave.<br>
<br>
"Presentation": Oh, yeah, that could be a lot better. Including an
"advanced" mode, to reduce what is immediately show to a newby. And
Including a wizard.<br>
Just needs someone to do the work. <br>
Some part is bound to the underlaying structure where options are
stored => that makes it more work to change stuff.<br>
<br>
<blockquote type="cite" cite="mid:2117168.oxAcqbJhdy@debian1-3">
<pre wrap="" class="moz-quote-pre">- Crosscompiling: The compiler file name is hidden in Tools - Settings instead
of in the project settings. </pre>
</blockquote>
<br>
If it is cross compiling (using same compiler version), and if the
compiler is installed (as cross compiler):<br>
Project Options > Compiler opts > Config and Target<br>
<br>
<blockquote type="cite" cite="mid:2117168.oxAcqbJhdy@debian1-3">
<pre wrap="" class="moz-quote-pre">- For a new installation of Lazarus: The most important quick start icons have
to be configured again at the bottom of the source code window. So that fast
and smooth work is possible. Instead of placing them like this from the start.
The many confusing windows I have already mentioned above.</pre>
</blockquote>
You mean the editor toolbar? <br>
I don't know if it has ever been discussed, if/what the default
config for it should be.<br>
<br>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">Am Mittwoch, 16. Oktober 2024, 04:00:30 CEST schrieb DougC via fpc-pascal:
</pre>
<blockquote type="cite" style="color: #007cff;">
<pre wrap="" class="moz-quote-pre">I don't think the situations are vary similar, so I don't think the
comparison is useful.
</pre>
</blockquote>
<pre wrap="" class="moz-quote-pre">I mainly wanted to say that it is possible to do so without extensive
marketing. Linux is another example. Linux does not spend a huge amount of
money in marketing. It is widely used because it runs stable and for some
other reasons.
</pre>
</blockquote>
<br>
However, Linux is marketed by countless people blogging and making
videos, as well as mentioning in PC related press/magazines.<br>
<br>
IMHO its 50/50<br>
<br>
The impression a user gets when using the project can decide if they
stay or turn away. But it does rarely bring them to the project to
begin with.<br>
<br>
And, the impression is not just what they explore on their own, but
what help they have to explore. Not just language but also
environment.<br>
E.g., while I still prefer to search for text explanations of how to
get an app to do what I need, I would guess that many people want a
quick video showing them.<br>
Yet, of course, no amount of help will change if the environment
feels familiar or not. On the other hand, we don't want to pay for
that by driving away old users, so we must preserve (at least as
option) their preferred functionality and presentation. <br>
<br>
But all that does not bring anyone new. It does at best help to keep
them, once they are there. Word needs to be out, and it needs to be
out on all channels/media, and as much as possible. <br>
<br>
Hence IMHO: 50/50.<br>
<br>
And of course, it isn't just agreeing on this. We obviously don't
have many people for the marketing/social-media/... part. <br>
But we also are limited on the implementation side.<br>
Let's say we could find agreement on how to improve the
editor-toolbar => then who does it? (initial changes,
maintenance, options, ... not all needed for the toolbar, but for
other changes maybe...)<br>
<br>
</body>
</html>