<div dir="ltr"><snip><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><blockquote type="cite"><div dir="ltr"><div class="gmail_quote"><div>Ah... thank you for the clarification. So any fix'es I
have to push to Gitlab then? <br>
</div>
</div>
</div>
</blockquote>
<br>
- Ideally as a "merge request" on Gitlab. (Fork, push to your fork,
create merge-request)<br>
- However Patches are accepted too. <br>
- And some developers may accept pull requests (in which case your
fork can be on any public accessible git).<br>
"some developers" => That is, if you interactively deal with a
member of the team, who told you they would be the one to accept
your changes.<br></div></blockquote><div><br>Sounds good to me.<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<br>
Any change should ideally be against the "main" branch.<br>
So in this case, that would be reintroducing the files.<br></div></blockquote><div><br>Understood!<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<br>
If you plan any "larger" work, best to query (as actually - by
coincidence - you do in this mail) if it would be accepted (or what
implementation requirements their might be).<br>
Ideally you will get response from some developer, who confirms that
they will accept and merge/apply your changes. <br></div></blockquote><div><br></div><div>Let's just say every time I use the Lazarus IDE or FPC or whenever I go through the documentation the more humbled I become and I think about the amount of time+thought and work that has gone into this the more I start to feel the need to be part of this and contribute within my limited skill sets. So yes the plan is to first teach myself how things work then get myself comfortable with doing Voodoo magic like ASerge did in the Lazarus forum when I asked a noob question. This is worth having a look at actually: <a href="https://forum.lazarus.freepascal.org/index.php/topic,61315.msg461061.html#msg461061">Voodoo Magic by ASerge</a> look for Reply #1, please.<strong> </strong>Hopefully, someday I will actually understand what ASerge did.<strong> <br></strong></div><div><strong></strong></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div> <br>
In the "main" branch the example folder was re-ordered.
During this process the "testall" appears to have been
removed. Not sure of the reasons...</div>
</blockquote>
<div> </div>
<div>Oh-kay that explains why I was unable to find it and am
sure the reasons were all good and valid :-) <br>
</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div> Maybe oversight, maybe because it did not work. If the
latter, then likely a working version can be re-added. </div>
</blockquote>
<div><br>
</div>
<div>Umm... well "testall" works on Windows I had zero issues
but needs a few fixes when running under Linux. I have
manged to get it to <br>
</div>
<div>work on my Debian system now. <br>
</div>
</div>
</div>
</blockquote>
If you plan to work on it, I would suggest to wait a day or two, for
further details on this to emerge.<br>
If it was removed because it did not work cross platform, then
re-adding after fixing should be ok.<br></div></blockquote><div><br></div><div>I just have to find a way to test in code if we are running on Windows or Linux then change the 'path' accordingly;y and we are good to go. That was one of the <br></div><div>reasons "testall" did not work on Linux. <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<br>
Maybe there were other reasons. Maybe it would be better to break it
into a small number of projects, each dealing with a subset of the
components.<br>
A "all in one" might make it very hard to read and understand the
code for a specific component.<br></div></blockquote><div><br>This is very true. I went through the "testall" code and it took me quite a while and a lot of asking around on the forum and irc and doing my own research to begin to start to</div><div>understand what is going on :-) <br><br>It is definitely not something a beginner/noob will understand or have fun trying to analyze why things are working when there is zilch <br></div><div>in the Form. It's good for folks coming in with 'experience' and who have years of some type of coding background then they will appreciate</div><div>the possibilities and freedom and the power of Lazarus+Free Pascal but to a total newbie, this is throwing him/her in the deep end of the pool with no life jacket :-) <br></div><div><br>When one does not understand what has been done or why a piece of code works the way it does it can soon lead to frustration which in turn usually turns folks away and <br></div><div>we lose good people who may have turned out to be very competent and capable programmers or analysts or simply people who could have contributed to the code and make</div><div>things better? It would be a very different story if the source to "testall" was "heavily" commented at each line then life becomes easier. This is my personal opinion and thoughts and</div><div>others may feel differently. When one is an experienced programmer sometimes we forget what is obvious to us in teh code may not necessarily be so to a newbie? That is why <br></div><div>commenting the code helps. Again my thoughts alone. <br></div><div></div><div><br></div><div>One of the primary reasons I love Lazarus and FPC is the community support. It is usually very fast/rapid and usually comes with a concrete-tested sample of code. I have never</div><div>experienced this in other coding communities so this is a very welcome and long prayed-for and wished-for thing. It empowers you and makes you want to be part of the larger <br></div><div>project in any small way.<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<br>
If you look at the examples (and the IDE menu Tools > "Example
projects" (in Lazarus 2.3), then you will find that many components
have there own examples already.<br></div></blockquote><div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
Repeating them, may not make much sense (unless for example to have
all buttons in one project, with settings/code explicitly showing
their differences).<br></div></blockquote><div><br></div><div>I have actually started building my own set of demos. A side effect of trying to learn and teach myself Lazarus+FPC if anyone wants to have a look I would be happy to share. <br></div><div>Who knows, some of them may actually be useful.<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<br>
Of course, depending on the course of action, the wiki may need
updates (it still is correct for the current release, but it wont be
for 2.4 / and it might easily be overlooked when the time comes)<br></div></blockquote><div><br></div><div>Understood again and thank you very much for your time and help Martin.</div><div><br></div><div>Talk again soon, Aruna<br></div><div> <br></div></div></div>