"TestAll" and other removed example projects

[JuhaManninen]

Does anyone know who wrote 'testall' in the first place? I have lots of questions but no original author to ask?

In Linux console, active directory being the Lazarus git source root, I ran :

Code: [Select]

$ git log examples/testall*It gives the output copied below. The very first commit says the author is <christer.t.johansson@se.abb.com>. It was committed by somebody called stoppok.
A commit author name "lazarus" was used collectively by all core developers in the early days, much before I got involved.
A still better way to see the commits is the GUI app "gitk". There you can see also the diff for each commit interactively.
Like this:

Code: [Select]

$ gitk examples/testall* &
I have not heard of Christer T Johansson. Like often in FOSS development, original authors are not available and decisions must be made by other people.

Code: [Select]

commit 4e96538dd29e3a93a19e85ea11b6c2334f6fb8e8
Author: wp <wp.no-reply@lazarus-ide-org>
Date:   Thu Jul 1 21:59:50 2021 +0000

    examples: Fix typo in TestAll demo.
   
    git-svn-id: trunk@65337 -

commit 337b198136a9f964ff5207f8a215fe58572622aa
Author: juha <juha@lazarus-ide.org>
Date:   Thu Dec 10 22:12:35 2020 +0000

    Examples: Fix dir separator in testall.lpi.
   
    git-svn-id: trunk@64194 -

commit 5328b9a852b4612ff466bd01ce4444db454997e0
Author: juha <juha@lazarus-ide.org>
Date:   Mon May 6 11:32:58 2019 +0000

    Examples: Use '/' as path delimiter in project settings. Works also on Windows. Issue #35524.
   
    git-svn-id: trunk@61164 -

commit b5251d215211fdc3d492f15d93f5aa67c29b0ccb
Author: juha <juha@lazarus-ide.org>
Date:   Thu May 11 09:04:51 2017 +0000

    Examples: Remove PathDelim and LaunchingApplication settings from the projects.
   
    git-svn-id: trunk@54873 -

commit 6b1b3acb9fb514128bf90dab05cbf3b7dd2cb298
Author: mattias <nc-gaertnma@netcologne.de>
Date:   Sun Apr 9 09:25:32 2017 +0000

    examples: fixed testall.lpi
   
    git-svn-id: trunk@54587 -

commit 1de2cbf5869ce14117ba89ca8bb1d23fcdf90785
Author: joost <joost@lazarus-ide.org>
Date:   Sun Jan 29 21:04:32 2017 +0000

    general: Updated address of the Free Software Foundation in copyright messages
   
    git-svn-id: trunk@54031 -

commit bd5c9173409b4dd68d83ec99aa5ca97b8abe5461
Author: bart <9132501-flyingsheep@users.noreply.gitlab.com>
Date:   Sun Mar 6 11:15:52 2016 +0000

    Examples: TestAll: more dialog tests (provided by jc99, modifiedby me).
   
    git-svn-id: trunk@51832 -

commit 376303c792325ffa431ad8ea94a368420c0d0202
Author: bart <9132501-flyingsheep@users.noreply.gitlab.com>
Date:   Sat Mar 5 23:19:44 2016 +0000

    Examples: TestAll: add testallform.lfm, which I forgot in r51824 #87791326d0.
   
    git-svn-id: trunk@51831 -

commit 01358aea67fb7d74b6f2e1a8417c13594550293a
Author: bart <9132501-flyingsheep@users.noreply.gitlab.com>
Date:   Sat Mar 5 17:37:41 2016 +0000

    Examples: TestAll: don't write an extra '$' in front of Key when logging Key events.
   
    git-svn-id: trunk@51828 -

commit 36e0d69b90897e32141a48429ed23b552245897f
Author: bart <9132501-flyingsheep@users.noreply.gitlab.com>
Date:   Sat Mar 5 15:21:10 2016 +0000

    Examples: TestAll: more component tests.
   
    git-svn-id: trunk@51827 -

commit 96ba7a6b4036f65806c2720da31331a29de63e1d
Author: bart <9132501-flyingsheep@users.noreply.gitlab.com>
Date:   Sat Mar 5 13:09:33 2016 +0000

    Examples: TestAll:
    - make dummy procedures for all tests and call them in the menu's onclick event
    - fix typo
    - refactor
    - cleanup
   
    git-svn-id: trunk@51826 -

commit b9a5f9bcc96b0145e8dc8ea7735ecf9380b57a90
Author: bart <9132501-flyingsheep@users.noreply.gitlab.com>
Date:   Fri Mar 4 18:13:13 2016 +0000

    Examples: TestAll: add a test (work in progress).
   
    git-svn-id: trunk@51825 -

commit 87791326d0da7a8bf46b1f06a9df425beb15f7bf
Author: bart <9132501-flyingsheep@users.noreply.gitlab.com>
Date:   Fri Mar 4 15:05:52 2016 +0000

    Examples: Start completely rewrting the TestAll apllication.
   
    git-svn-id: trunk@51824 -

commit 161225d29fe5481fc51eb70222c4f96c0763c90e
Author: bart <9132501-flyingsheep@users.noreply.gitlab.com>
Date:   Thu Mar 3 12:13:28 2016 +0000

    Examples: Make Debug and Release buildmodes for TestAll project.
   
    git-svn-id: trunk@51815 -

commit 6b8f2f492a1e81ff65562d83f97a9ed9157f3a14
Author: bart <9132501-flyingsheep@users.noreply.gitlab.com>
Date:   Thu Mar 3 12:09:01 2016 +0000

    Examples: Re-enable "Win32 GUI application" of TestAll project (accidentically introduced by me in r51813 #c83e1c15e5).
   
    git-svn-id: trunk@51814 -

commit c83e1c15e533cedfa9109fded543e96258876e92
Author: bart <9132501-flyingsheep@users.noreply.gitlab.com>
Date:   Thu Mar 3 11:30:47 2016 +0000

    Examples: Fix resource loading in TestAll project.
   
    git-svn-id: trunk@51813 -

commit 931c7a9de4714c4a8ef4e9a9bacca45befe03947
Author: juha <juha@lazarus-ide.org>
Date:   Sat Jul 4 23:08:27 2015 +0000

    Examples: Fix compilation when function wrappers in FileUtil are disabled (define NoLazUTF8Wrappers). Clean uses sections.
   
    git-svn-id: trunk@49495 -

commit 6b22a465f7480392f98b9979584f7665e6e81bc3
Author: mattias <nc-gaertnma@netcologne.de>
Date:   Mon Mar 2 18:57:39 2015 +0000

    examples: removed obsolete SrcPath
   
    git-svn-id: trunk@48101 -

commit 0e8dcc15e16b4cfacdeeaac527e31cfb42c62bf0
Author: paul <paul@lazarus-ide.org>
Date:   Sat Sep 28 15:25:27 2013 +0000

    examples: use FPC resources
   
    git-svn-id: trunk@43013 -

commit 844e61673882e1496c6a20d6c84a273d5afb2562
Author: juha <juha@lazarus-ide.org>
Date:   Mon Apr 9 08:24:59 2012 +0000

    IDE etc.: unify 3 dots in GUI string to have a space ( ...).
   
    git-svn-id: trunk@36666 -

commit 503169d0a118d8d31aa62bee50d371fdc9fa5617
Author: maxim <maxim@lazarus-ide.org>
Date:   Wed Aug 10 19:57:50 2011 +0000

    Examples: replaced 'inherited create' with 'inherited createnew'
   
    git-svn-id: trunk@31931 -

commit 01db3bb47c041d0fefeeb9ac8a5d27c9818a1af5
Author: juha <juha@lazarus-ide.org>
Date:   Sun Mar 13 18:21:51 2011 +0000

    LCL (mostly), Replace Assert(False... with //DebugLn(...  Now Assert can be used for its original purpose again.
   
    git-svn-id: trunk@29820 -

commit a460a9d3ee89d2b234de43a79dfac8358f8da54d
Author: maxim <maxim@lazarus-ide.org>
Date:   Wed Feb 16 23:45:39 2011 +0000

    Examples, TestAll: disabled TNotebook, enabled TPageControl instead
   
    git-svn-id: trunk@29584 -

commit 0e109ea1e1d2af01c571b215fd32ee4d6f03e245
Author: mattias <nc-gaertnma@netcologne.de>
Date:   Thu Feb 10 09:43:23 2011 +0000

    fixed typos: usefull
   
    git-svn-id: trunk@29446 -

commit a02fa3589a6fefa57d592ecea4876c39a85ae8e7
Author: vincents <vincents@lazarus-ide.org>
Date:   Fri Oct 29 13:32:57 2010 +0000

    testall example:
    * change form style form bsDialog to bsSizable, so that the main menu is shown (issue #16166)
    * fixed line ending in captions: #10#13 -> #13#10
   
    git-svn-id: trunk@27947 -

commit 2ca43e9903078a21efe0bc770cd7ab1447d83fbd
Author: martin <laz.git@mfriebe.de>
Date:   Thu Jul 23 12:13:00 2009 +0000

    Examples: Fix testallform for fpc2.3.1 (issue #14184)
   
    git-svn-id: trunk@20931 -

commit 298c34c4257896188516b29964c2fc96d59a174f
Author: paul <paul@lazarus-ide.org>
Date:   Sun May 10 07:54:53 2009 +0000

    examples: fix testall example (issue #0013679)
   
    git-svn-id: trunk@19903 -

commit b28e26843dc244e2d898ef16c920ac7eac2b3821
Author: paul <paul@lazarus-ide.org>
Date:   Mon May 4 05:37:46 2009 +0000

    examples: fix button resource name
   
    git-svn-id: trunk@19792 -

commit 04c9b5cd7426d752777dc8a2137cf9d734f46083
Author: paul <paul@lazarus-ide.org>
Date:   Sat Jan 31 12:02:35 2009 +0000

    examples: remove Crl3D, ParentCtl3D properties
   
    git-svn-id: trunk@18516 -

commit 4b344f137ae19f7397db4eafd237b7bb92148016
Author: laurent <laurent@lazarus-ide.org>
Date:   Tue Dec 2 13:28:21 2008 +0000

    IDE: rename the images to avoid overload
   
    git-svn-id: trunk@17660 -

commit 908ad54b8f606b309292d5f5aea3bafb96e24fc4
Author: mattias <nc-gaertnma@netcologne.de>
Date:   Mon Aug 25 22:40:11 2008 +0000

    examples: fixed compilation
   
    git-svn-id: trunk@16237 -

commit aecb1279934ea5062e5113c6118ffdb626ac93d3
Author: marc <marc@lazarus-ide.org>
Date:   Thu Apr 24 23:48:27 2008 +0000

    * Fixed compilation and some memleaks
   
    git-svn-id: trunk@14954 -

commit 83ebfd06726cbaf5f287b934d54a9e6205e4e1b6
Author: vincents <vincents@lazarus-ide.org>
Date:   Sat Feb 23 19:33:06 2008 +0000

    examples: fixed compilation after the removal of the clistbox unit from Maxim Ganetsky
   
    git-svn-id: trunk@14235 -

commit 7e9fc77a93b3511e99168f08526ae2eb0db2b547
Author: vincents <vincents@lazarus-ide.org>
Date:   Mon Apr 10 11:18:13 2006 +0000

    removed ShowScale
   
    git-svn-id: trunk@9113 -

commit 95ca76e85edc433d7d03f14daf28aafbcd92fa36
Author: mattias <nc-gaertnma@netcologne.de>
Date:   Sat Oct 1 00:38:04 2005 +0000

    added .lpi for examples
   
    git-svn-id: trunk@7869 -

commit a0311c2cbac64da9a893cbb5ba64f62d5f04e3cc
Author: vincents <vincents@lazarus-ide.org>
Date:   Mon Aug 22 12:30:03 2005 +0000

    removed cvs logs
   
    git-svn-id: trunk@7541 -

commit 225cd324660b1b29bf5950587f18c729c06a7968
Author: vincents <vincents@lazarus-ide.org>
Date:   Sat Sep 11 20:22:18 2004 +0000

    set form style to fsNormal, so that it becomes the mainform
   
    git-svn-id: trunk@5973 -

commit 59ace4ca3bf173cd1a2321cdd8ba9cccbdf886f9
Author: mattias <nc-gaertnma@netcologne.de>
Date:   Thu Feb 19 09:45:40 2004 +0000

    fixed compilation   from Vincent
   
    git-svn-id: trunk@5207 -

commit a3000e4875468a9c678d7ed3cb2b06dc5ab0e828
Author: mattias <nc-gaertnma@netcologne.de>
Date:   Mon Dec 8 14:27:16 2003 +0000

    fixed WaitForHandles
   
    git-svn-id: trunk@4881 -

commit ab426e35718c8ec7ca86d78b503c68ee1baa4f11
Author: mattias <nc-gaertnma@netcologne.de>
Date:   Tue Nov 25 09:15:55 2003 +0000

    fixed testall
   
    git-svn-id: trunk@4839 -

commit 5e5c1122a7a636e599ac5d8bb409a7b1599e82bd
Author: mattias <nc-gaertnma@netcologne.de>
Date:   Thu Sep 18 09:21:03 2003 +0000

    renamed LCLLinux to LCLIntf
   
    git-svn-id: trunk@4637 -

commit 0d883f89b8ef3e154e2e21d6664943857106a54b
Author: mattias <nc-gaertnma@netcologne.de>
Date:   Wed Jan 1 11:11:50 2003 +0000

    fixed testall example
   
    git-svn-id: trunk@3773 -

commit 09138261ffe900180e59df2d3c0ab21345d2c926
Author: lazarus <lazarus@lazarus-ide.org>
Date:   Tue Oct 29 08:22:33 2002 +0000

    MG: added interfaces unit
   
    git-svn-id: trunk@3578 -

commit bbc829a44b2c5f9dc5ff546fc72ba6be8ae1c9da
Author: lazarus <lazarus@lazarus-ide.org>
Date:   Tue Sep 10 14:08:54 2002 +0000

    MG: fixed compiling examples
   
    git-svn-id: trunk@3313 -

commit 98399ff1a9059e6d79531424cbc3c8fefbf5b673
Author: lazarus <lazarus@lazarus-ide.org>
Date:   Sun Aug 18 08:53:33 2002 +0000

    MG: TNoteBook now starts with no Page and TPage has no auto names
   
    git-svn-id: trunk@2753 -

commit 6c9464c470122f2f48889e91d031da545fbd9b4c
Author: lazarus <lazarus@lazarus-ide.org>
Date:   Fri May 10 06:57:51 2002 +0000

    MG: updated licenses
   
    git-svn-id: trunk@1668 -

commit 0f5c59201ba5c902614987d43a824eba0433a0a9
Author: lazarus <lazarus@lazarus-ide.org>
Date:   Sat Mar 23 21:02:02 2002 +0000

    + Enhanced testall-app with demo for TPanel, stoppok
   
    git-svn-id: trunk@1540 -

commit 09ca1546a5eb125a8560b91e10400c777384be9c
Author: lazarus <lazarus@lazarus-ide.org>
Date:   Sat Feb 9 02:30:23 2002 +0000

    MG: updated licenses
   
    git-svn-id: trunk@1399 -

commit c9e180acac39615fa5faf99ad009230539e38425
Author: lazarus <lazarus@lazarus-ide.org>
Date:   Sun Feb 3 00:24:02 2002 +0000

    TPanel implemented.
    Basic graphic primitives split into GraphType package, so that we can
    reference it from interface (GTK, Win32) units.
    New Frame3d canvas method that uses native (themed) drawing (GTK only).
    New overloaded Canvas.TextRect method.
    LCLLinux and Graphics was split, so a bunch of files had to be modified.
   
    git-svn-id: trunk@653 -

commit c1f59f9e4c5ef80b2347c349c26e89ec52412a1e
Author: lazarus <lazarus@lazarus-ide.org>
Date:   Mon Dec 10 07:47:00 2001 +0000

    MG: minor fixes
   
    git-svn-id: trunk@492 -

commit bfe772f3318f43dfff0147a58df5214064fbfd59
Author: lazarus <lazarus@lazarus-ide.org>
Date:   Tue Apr 17 21:36:15 2001 +0000

    * enhanced testdialog for TBevel
    * basic test for TPaintBox
    stoppok
   
    git-svn-id: trunk@264 -

commit d0de3587929fe250d4ec24bb87c0dbf2bda46dc2
Author: lazarus <lazarus@lazarus-ide.org>
Date:   Sun Feb 25 09:22:28 2001 +0000

    * Fixed crash caused by missing pixmaps
    * using resources now instead of xpm file
   
    git-svn-id: trunk@197 -

commit 2b8c03b5ea631f615970965cd6fe0fbfc8cb7b1a
Author: lazarus <lazarus@lazarus-ide.org>
Date:   Fri Sep 22 20:22:03 2000 +0000

    +Rebuilt from beginning to V0.2
    +Prepared for non existent components (total 60 components).
    (Changes by Christer, commited by stoppok)
   
    git-svn-id: trunk@37 -

commit 35cc9bddc63d721f7ace8cc1d69e1d4b5f497230
Author: lazarus <lazarus@lazarus-ide.org>
Date:   Mon Jul 31 20:33:33 2000 +0000

    + added "testall" demo provided by <christer.t.johansson@se.abb.com>
    stoppok
   
    git-svn-id: trunk@18 -


Of course I can help you guys to find bugs or unstable/incompatible things for a Windows 10 project.
I got myself latest stable Lazarus 2.2.2 (rev lazarus_2_2_2-0-g537f43754c) FPC 3.2.2 x86_64-win64-win32/win64 installed via FPC Update Deluxe program.
On my system I have that example installed, shall that be tested or a different version? If differen, please link 

https://gitlab.com/freepascal.org/lazarus/lazarus/-/branches
"main" is the default branch. It is active when you first clone the Lazarus Git repository.
Everybody involved in Lazarus development, including those testing changes made by others, must use it.

[Aruna]

At the same time it scared me to death, I was thinking 'Hell No! What did this guy smoke?

Yeah, it must have been good stuff !  But seriously, I reckon it was written for testing rather than demo. An, perhaps, it was written before the Lazarus Wizards got all the GUI designer in place. That is is the key to the "Rapid" bit.

Yes it was probably way before that. Like Juha showed us I ran

Code: Pascal  [Select][+][-]

1. git log examples/testallform.pp

and date of first commit was Mon Jul 31 20:33:33 2000 +0000 that is 22 years ago (Yikes!) and we have a name and a email now. See below for details please.

Code: Pascal  [Select][+][-]

1. commit 35cc9bddc63d721f7ace8cc1d69e1d4b5f497230
2. Author: lazarus <lazarus@lazarus-ide.org>
3. Date:   Mon Jul 31 20:33:33 2000 +0000
4.  
5.     + added "testall" demo provided by <christer.t.johansson@se.abb.com>
6.     stoppok
7.  

I personally always have about ten (ok, I counted them, 36 !) Virtual Box VMs ready to go. Its an absolute pain but if you don't test and find the problems, your users will do it for you !

He has 36 VM's ready to go  and I have a little surprise for you all. Please see attached screenshot. I am running 2.3.0 

[Aruna]

Sorry, I was not clear, I generally test on Windows 7 and Windows 11, if something works on those ends, it must be OK in the middle. Or so I hope.

I would think that makes a whole lot of sense but I tend to be extremely careful and cautious with Windows due to being left hanging high to dry so many countless times 

Its dead easy to build from source (with your existing FPC) and setup to not interfere in any way with your existing install, just make sure it uses a separate PCP. 

David I could use some help, please. Agreed it's dead easy to build from source which is what I did with 2.3.0 but then it threw up the first screenshot and I chose update then it showed me the second screenshot I chose ignore all. The IDE came up but undocked so I rebuilt and voila I have things back to what they were and so far no noticeable issues or hangs. I can work with this but it is annoying when this keeps happening at every time I start up the IDE. I am trying to figure out how to use the pcp so can use some help please?

I have worked through all the examples, set them all up with  metadata and quite a lot have a keyword in that metadata "needs work".  (note - Andreas fixed one today  )

Yep I saw that commit in Gitlab 

But you will not see all that in Lazaris 2.2.2, sorry !

I am running 2.3.0 and I am seeing all those nifty examples eh 

Thank you, Aruna

[dbannon]

David I could use some help, please. Agreed it's dead easy to build from source which is what I did with 2.3.0 but then it threw up the first screenshot and I chose update then it showed me the second screenshot I chose ignore all. The IDE came up but undocked so I rebuilt and voila I have things back to what they were and so far no noticeable issues or hangs. I can work with this but it is annoying when this keeps happening at every time I start up the IDE. I am trying to figure out how to use the pcp so can use some help please?

PCP ?  Primary Config Path. Start lazarus like this -

Code: [Select]

lazarus --pcp=/home/dbannon/bin/LazConfigs/lazarus-main
Or drop a file in the lazarus-main directory called lazarus.cfg and put "--pcp=/path/to/dir/for/config" and always cd to that dir to start that particular Lazarus.

I have a few scripts called, eg laz-main, in my bin dir, all they do is cd to the appropriate dir and start the version of lazarus in there. Each of those various lazarus directories have thier own .cfg file.

I keep all my configs in that dir (~/bin/LazConfigs), each in a subdir named after the particular Lazarus install. So, laz-fixes_2_2 is in ~/bin/LazConfigs/laz-fixes_2_2.
Don not let the configs get mixed up, Lazarus is smart enought to update an older version but when you try to run that older version later, bad things happen.

On the other hand, if will only ever run lazarus-main, just shut down Lazarus, blow away the default dir ~/.lazarus and start Lazarus up again, it will rebuild its config fine.

Now, another matter, you posted to the mailing list a link to a list of the files removed from the old Examples dir, in fact they were not all removed, most, almost all, found their way into their own directory where they are now very happy !


>>But you will not see all that in Lazaris 2.2.2, sorry !
>I am running 2.3.0 and I am seeing all those nifty examples eh 

those comments were directed to  KodeZwerg

[/quote]

[Aruna]

David I could use some help, please. Agreed it's dead easy to build from source which is what I did with 2.3.0 but then it threw up the first screenshot and I chose update then it showed me the second screenshot I chose ignore all. The IDE came up but undocked so I rebuilt and voila I have things back to what they were and so far no noticeable issues or hangs. I can work with this but it is annoying when this keeps happening at every time I start up the IDE. I am trying to figure out how to use the pcp so can use some help please?

PCP ?  Primary Config Path. Start lazarus like this -

Code: [Select]

lazarus --pcp=/home/dbannon/bin/LazConfigs/lazarus-main
Or drop a file in the lazarus-main directory called lazarus.cfg and put "--pcp=/path/to/dir/for/config" and always cd to that dir to start that particular Lazarus.

Alright, I will try that, thank you.

I have a few scripts called, eg laz-main, in my bin dir, all they do is cd to the appropriate dir and start the version of lazarus in there. Each of those various lazarus directories have thier own .cfg file.

I keep all my configs in that dir (~/bin/LazConfigs), each in a subdir named after the particular Lazarus install. So, laz-fixes_2_2 is in ~/bin/LazConfigs/laz-fixes_2_2.

I think I will do likewise...

Don not let the configs get mixed up, Lazarus is smart enought to update an older version but when you try to run that older version later, bad things happen.

What kind of bad things? What are the bad things that happened to you? The reason I am asking is if we know what went wrong then we can slowly fix things over time?

On the other hand, if will only ever run lazarus-main, just shut down Lazarus, blow away the default dir ~/.lazarus and start Lazarus up again, it will rebuild its config fine.

Right now it is just lazarus-main but as I progress I am sure that will change.

Now, another matter, you posted to the mailing list a link to a list of the files removed from the old Examples dir, in fact they were not all removed, most, almost all, found their way into their own directory where they are now very happy !

Where? Which directory?

>>But you will not see all that in Lazaris 2.2.2, sorry !
>I am running 2.3.0 and I am seeing all those nifty examples eh 

those comments were directed to  KodeZwerg

Ouch! Oh dear, my apologies. Please disregard what I said.. and very much appreciate the help and guidance.

[dbannon]

What kind of bad things? What are the bad things that happened to you? The reason I am asking is if we know what went wrong then we can slowly fix things over time?

Because each version of Lazarus has possibly different config they are incompatible. Generally Lazarus detects that and warns you (and reliably updrades). But, if you try hard you can force it and then (especially if going back to earlier version), some options may not make sense, some, if you are unlucky might just make sense but have different meanings. No different to any other software,

.... almost all, found their way into their own directory where they are now very happy !

Where? Which directory?

In the same place, lazarus/examples. For example, notebk.lpi is in  lazarus/examples/NoteBk/. combobox.lpi is in lazarus/examples/combobox/.

Many of the homeless projects, loose in /lazarus/examples, were more test code than examples.  But certainly not all.

Davo

[KodeZwerg]

Latest Lazarus on where you are testing things out.
I was reading all of your thread but I am really an absolute beginner with installation, thats why i did used the fpc update deluxe app  :'(

Is there a manual that explains me how to install that "/branches" on my windows machine please?
In attachment you see what my browser is offering me.

[Aruna]

What kind of bad things? What are the bad things that happened to you? The reason I am asking is if we know what went wrong then we can slowly fix things over time?

Because each version of Lazarus has possibly different config they are incompatible. Generally Lazarus detects that and warns you (and reliably updrades). But, if you try hard you can force it and then (especially if going back to earlier version), some options may not make sense, some, if you are unlucky might just make sense but have different meanings. No different to any other software,

I see.. I will be careful..

.... almost all, found their way into their own directory where they are now very happy !

Where? Which directory?

In the same place, lazarus/examples. For example, notebk.lpi is in  lazarus/examples/NoteBk/. combobox.lpi is in lazarus/examples/combobox/.

Many of the homeless projects, loose in /lazarus/examples, were more test code than examples.  But certainly not all.

Davo

Oh-kay sounds great, thank you.

[dbannon]

Latest Lazarus on where you are testing things out.
I was reading all of your thread but I am really an absolute beginner with installation, thats why i did used the fpc update deluxe app  :'(

Is there a manual that explains me how to install that "/branches" on my windows machine please?
In attachment you see what my browser is offering me.

KodeZwerg, its pretty easy. Unless you are chasing a quite specific issue, the things you see under Branches are probably not that interesting to you, right now 'main' and Fixes_2_2 would be about all. Further down under the same combo box, are Tags, again, maybe all you need there is lazarus_2_2_4, the current release and just maybe lazarus_2_2_0rc2, the last one to have a working GoTo Bookmark system in the IDE.

If you are planning to send in patches in an ongoing manner, then you should download with git, thats a whole different discussion. If you just want to get a specific version, easy and quick to download that Branch/Tag from the button one to left of the Blue "Clone" button, save it as a zip, unzip, cd into the new dir and type "make bigide" - all assuming you have a suitable FPC installed and correctly setup on your PATH. I keep a close eye on the linux page but assume, for you, its all documented on https://wiki.freepascal.org/Installing_Lazarus_on_Windows.

I have done it on Windows but I am a long way from authoritative, someone else here will be however.

We are probably drifting somewhat off topic here I expect .....

Davo

[Aruna]

Latest Lazarus on where you are testing things out.
I was reading all of your thread but I am really an absolute beginner with installation, thats why i did used the fpc update deluxe app  :'(

It's not hard to do an install. You can select the install that matches your OS of choice below.
Lazarus Downloads

Is there a manual that explains me how to install that "/branches" on my windows machine, please?
In attachment you see what my browser is offering me.

Those /branches your seeing are 'git' branches and they are all in a git repository. So the easiest thing to do is to clone the entire repository.
There are multiple ways to clone a repository. You will need to install 'git' if it is not available in your system.
You can download git from here

I have attached two screenshots.

The first screenshot is the main branch repository  there is a blue button at the top right
that says 'clone' and when you click this button you will see the second screenshot and there are many ways to clone/download the repository. Once
downloaded you can select the git branch you wish to work on by typing the command below in git-bash under Windows in this case I
want to work on the branch fixes_2_2

Code: Pascal  [Select][+][-]

1. git checkout fixese_2-2

Most people 'fork' the repository they want to work on then clone the repository they
just forked and work on that on their local system. Then when your changes are made
and tested and you want to get them merged into the main repository you push those
changes to your remote repository first then create a pull request or merge request for the original Lazarus repository.

If you use Visual Studio Code life will be easy. If you wish to 'experiment' I would advise you to absolutely do so... Google is your friend, there are many tutorials on
how to use git out there on the public domain internet. If you have difficulties you can always ask here and we will be happy to help.

[JuhaManninen]

Latest Lazarus on where you are testing things out.
I was reading all of your thread but I am really an absolute beginner with installation, thats why i did used the fpc update deluxe app  :'(

Is there a manual that explains me how to install that "/branches" on my windows machine please?
In attachment you see what my browser is offering me.

The branches link apparently confused you. For testing the latest changes you only need the "main" branch which is the default in our Git repo.
To get it see:
 https://wiki.lazarus.freepascal.org/Getting_Lazarus
starting from "Getting a Git client" and then forward.

You can also continue to use FpcUpDeluxe if you want. It has an option to get the development "main" branch.
But, you don't need FpcUpDeluxe for this simple task if you have FPC already installed. Shortly put just :
1. Create a directory in Windows for the repository, eg. "lazarus_git".
2. Clone the Lazarus Git repository there (using TortoiseGit maybe).
3. On a cmd line, cd to that directory.
4. Run "make". (On Windows "make" comes with FPC installation).
5. Run "lazarus.exe". No need to install anything. Installations of other Lazarus versions stay intact. Use --pcp parameter to use a different Lazarus configuration.

You need to learn some basic concepts of Git. There are plenty of resources for that. Do a web search "git for beginners".
If you and others want to discuss and share information about specific Git features, please do it in a new forum thread. There is a danger this "TestAll" thread will become a yet another Git tutorial.

[Aruna]

If you and others want to discuss and share information about specific Git features, please do it in a new forum thread. There is a danger this "TestAll" thread will become a yet another Git tutorial.

Hi Juha I am sorry for diverting from the initial subject of this thread. My sincere apologies. Maybe we can move this to a new thread just like how you did with my initial query on the mailing list?
Possibly from the point where KodeZwerg says..

Is there a manual that explains me how to install that "/branches" on my windows machine please?

I would have done this already but thought it would be best to ask you and others first.

[JuhaManninen]

I would have done this already but thought it would be best to ask you and others first.

Just create a new forum thread for Git related questions and there you go.

Back to the "TestAll" project:
I realized it had been been fixed and improved in "main" before it was removed.
It means its latest version from "main" should be used instead of a version from a released Lazarus.

[dbannon]

And if you need to make or edit the example metadata file for TestAll, look at this https://github.com/davidbannon/ExampleMetaData

While JSON is certainly human readable, I don't believe its quite so human writable.

Davo