I am aware of this (Unix read only issues), but the example subsystem should not force users of other systems
But the Unix Read Only problem is only one of the reasons that I mentioned. For the "average" user, its a good idea, maybe for you, not so good. But harmful ?
Note that all this is based on an installable package. What if a user does not install the "ExampleProjects" package?
Yes, I agree. But I was advised it was 'policy' to use packages where possible. Making Lazarus more modular does make sense.
Is the implication that your examples window supports only the examples distributed with Lazarus?
No, the Examples Window searches first the Lazarus source tree then the Lazarus Config dir, that way, picking up any compliant examples that have come in from, eg, OPM. It is my intention to make some metafiles for viable examples I find in, at least the OPM packages I use. Hopefully more.
Certain, pre determined directories in config are skipped, eg, we don't pickup working copies or the working copies
backup directories there.
Before your changes, all the grid examples were inside the equally named subfolder of "examples"...
Indeed, some were logically located. Most were not. You obviously feel very strongly about this, I don't so I will restore the ones in ~/examples that I can.
... I do maintain the examples which are interesting to me and which belong to the components that I maintain. Here the "copy in user space" is useless to me since my fixes are not in version control, and I have extra work to copy it back to git.
I agree thats a backward step for you specifically. Maybe for others who do maintain some examples. My overall impression was that the examples where, on average, quite unloved. But I wonder if you don't use the example window to find your Example, and I restore the ones important to you, it should be business as usual ?
Sorry for this criticism.....
Not at all, I need constructive criticism because I want my contribution to be useful. Yes, my focus is on new users and unashamedly so but we cannot, in that process, make things harder to maintain. So, important that I be told if I am getting off track in any way.
// Other message> error after editing the JSON, display the name of the erroneous file?
Yes, should be easy, I'll look at it. As an aside, I have a tool I made to edit the meta files, checks for correctness before saving. But most casual editing will be done with vi or equivalent.
> Picking up broken metafile in backup dir.
Sounds like I should exclude files in backup, too easy.
> Proceeding after encountering an error in a metafile.
Yes, I agree, a more graceful recovery is a must. Should be easy, somewhat surprised about your experience. Will deal.
// RelatedThe issue with newlines in JSON under Windows has left me somewhat surprised. I now understand that "\n" in C is not the same as "\n" in Java and therefore JS. (and my respect for Java has dropped even further). I'll deal with that issue too.
(Sincerely) thanks for feedback !
Davo