From uaigh at icloud.com Wed Jan 1 23:37:24 2025 From: uaigh at icloud.com (Noel Duffy) Date: Thu, 2 Jan 2025 11:37:24 +1300 Subject: [Lazarus] Invalid project filename for project filenames containing a dash Message-ID: Lazarus 3.6 on MacOS behaves strangely when attempting to save a project filename that contains a dash (-). It produces the error message: Invalid project filename "/Users/noelduffy/tmp/a-b.lpi" is an invalid project name. Please choose another (e.g. project1.lpi)? If the dash is removed, Lazarus saves the project filename. But why does it reject filenames with a dash in them? The dash is a perfectly valid character for a filename on MacOS, Linux and other Unixes, and Windows. I tested this on Fedora 40 running Lazarus 3.6 too, and it does the same thing there. That is, it rejects a project filename if there?s a dash in it. From uaigh at icloud.com Wed Jan 1 23:37:24 2025 From: uaigh at icloud.com (Noel Duffy) Date: Thu, 2 Jan 2025 11:37:24 +1300 Subject: [Lazarus] Invalid project filename for project filenames containing a dash Message-ID: Lazarus 3.6 on MacOS behaves strangely when attempting to save a project filename that contains a dash (-). It produces the error message: Invalid project filename "/Users/noelduffy/tmp/a-b.lpi" is an invalid project name. Please choose another (e.g. project1.lpi)? If the dash is removed, Lazarus saves the project filename. But why does it reject filenames with a dash in them? The dash is a perfectly valid character for a filename on MacOS, Linux and other Unixes, and Windows. I tested this on Fedora 40 running Lazarus 3.6 too, and it does the same thing there. That is, it rejects a project filename if there?s a dash in it. From bartjunk64 at gmail.com Thu Jan 2 00:02:44 2025 From: bartjunk64 at gmail.com (Bart) Date: Thu, 2 Jan 2025 00:02:44 +0100 Subject: [Lazarus] Invalid project filename for project filenames containing a dash In-Reply-To: References: Message-ID: On Wed, Jan 1, 2025 at 11:37?PM Noel Duffy via lazarus wrote: > Lazarus 3.6 on MacOS behaves strangely when attempting to save a project filename that contains a dash (-). It produces the error message: .. > If the dash is removed, Lazarus saves the project filename. But why does it reject filenames with a dash in them? The dash is a perfectly valid character for a filename on MacOS, Linux and other Unixes, and Windows. > Some identifier with a '-' in it, is NOT a valid Pascal identifier (see: IsValidIdent function in sysutils unit) E.g. you cannot name a variable like this: var a-b: integer; Unit names (and a such program names) must be valid identifiers. This is Delphi compatible. -- Bart From nc-gaertnma at netcologne.de Thu Jan 2 00:07:49 2025 From: nc-gaertnma at netcologne.de (Mattias Gaertner) Date: Thu, 2 Jan 2025 00:07:49 +0100 Subject: [Lazarus] Invalid project filename for project filenames containing a dash In-Reply-To: References: Message-ID: <77fea545-ee11-4adb-9b0b-cc1ee53c556a@netcologne.de> On 1/1/25 23:37, Noel Duffy via lazarus wrote: > Lazarus 3.6 on MacOS behaves strangely when attempting to save a project filename that contains a dash (-). It produces the error message: > > Invalid project filename > "/Users/noelduffy/tmp/a-b.lpi" is an invalid project name. > Please choose another (e.g. project1.lpi)? Fixed. Mattias From nc-gaertnma at netcologne.de Thu Jan 2 00:14:22 2025 From: nc-gaertnma at netcologne.de (Mattias Gaertner) Date: Thu, 2 Jan 2025 00:14:22 +0100 Subject: [Lazarus] Invalid project filename for project filenames containing a dash In-Reply-To: References: Message-ID: On 1/2/25 00:02, Bart via lazarus wrote: > On Wed, Jan 1, 2025 at 11:37?PM Noel Duffy via lazarus > wrote: >[...] > Unit names (and a such program names) must be valid identifiers. Only unit names must be valid identifiers. Program filenames can be any filename and their source name don't need to correspond. The program source name must be a valid identifier. This is for example useful for instantfpc programs. Mattias From uaigh at icloud.com Fri Jan 3 00:42:53 2025 From: uaigh at icloud.com (Noel Duffy) Date: Fri, 3 Jan 2025 12:42:53 +1300 Subject: [Lazarus] Invalid project filename for project filenames containing a dash In-Reply-To: References: Message-ID: <5CAB14C2-5DD7-49B5-9516-B79395DE40D9@icloud.com> > On Thu, 2 Jan 2025 00:07:49 +0100, Mattias Gaertner wrote: > > On 1/1/25 23:37, Noel Duffy via lazarus wrote: >> Lazarus 3.6 on MacOS behaves strangely when attempting to save a project filename that contains a dash (-). It produces the error message: >> >> Invalid project filename >> "/Users/noelduffy/tmp/a-b.lpi" is an invalid project name. >> Please choose another (e.g. project1.lpi)? > > Fixed. Great, thanks for the swift response. Turns out, it?s easy enough to work around this, if all one wants is to have dashes in the executable filename. Setting Target File Name in project options does the trick. From michael at freepascal.org Sat Jan 4 16:02:40 2025 From: michael at freepascal.org (Michael Van Canneyt) Date: Sat, 4 Jan 2025 16:02:40 +0100 (CET) Subject: [Lazarus] AI Assistant added Message-ID: Hi, I've added an AI assistant (AIssist) to the Lazarus codebase. Check out components/aissist. It is a first, rudimentary, implementation that has been tested with Jan AI. (Jan AI must be installed separately, see https://jan.ai/) It currently offers: - a chat window in which you can chat with an AI (menu: view - AIssist chat) - an 'Explain code' menu entry in the source menu - a settings dialog under tools. The actual AI REST API has been abstracted away, so it should be possible to add other APIs. The "Jan AI" REST API is compatible to the ChatGPT API, so it should be possible to extend the implementation to include authentication and connect to ChatGPT. All this is meant to provide a start for a CoPilot-kind of functionality, as well as a possibility to generate e.g. fpdoc documentation for code. As said, it is an initial implementation, ideas for improvements or new functionality are of course more than welcome. Michael. PS. If you run the AI locally, make sure you have a good graphics card with lots of memory, or be prepared to wait for some time for answers: 30 seconds is the average wait time on my nearly-10-year old PC... From zeljko at holobit.hr Sun Jan 5 11:39:03 2025 From: zeljko at holobit.hr (zeljko) Date: Sun, 5 Jan 2025 11:39:03 +0100 Subject: [Lazarus] AI Assistant added In-Reply-To: References: Message-ID: <0688801d-d038-429b-859b-02bc6cd638f7@holobit.hr> On 04. 01. 2025. 16:02, Michael Van Canneyt via lazarus wrote: > > Hi, > > I've added an AI assistant (AIssist) to the Lazarus codebase. > Check out components/aissist. > > It is a first, rudimentary, implementation that has been tested with Jan > AI. > (Jan AI must be installed separately, see https://jan.ai/) > > It currently offers: > > - a chat window in which you can chat with an AI (menu: view - AIssist > chat) > > - an 'Explain code' menu entry in the source menu > > - a settings dialog under tools. > > The actual AI REST API has been abstracted away, so it should be > possible to > add other APIs. > > The "Jan AI" REST API is compatible to the ChatGPT API, so it should be > possible to extend the implementation to include authentication and > connect to ChatGPT. > > All this is meant to provide a start for a CoPilot-kind of > functionality, as well as a possibility to generate e.g. fpdoc > documentation for code. > > As said, it is an initial implementation, ideas for improvements or new > functionality are of course more than welcome. Great news, thanks ! :) zeljko From freepascal at ypa-software.de Sun Jan 5 11:43:14 2025 From: freepascal at ypa-software.de (Michael Fuchs) Date: Sun, 5 Jan 2025 11:43:14 +0100 Subject: [Lazarus] AI Assistant added In-Reply-To: References: Message-ID: <6d6ba2ff-eb53-4333-84c3-62478056ce66@ypa-software.de> Am 04.01.25 um 16:02 schrieb Michael Van Canneyt via lazarus: > I've added an AI assistant (AIssist) to the Lazarus codebase. > Check out components/aissist. But why? > All this is meant to provide a start for a CoPilot-kind of > functionality, as well as a possibility to generate e.g. fpdoc > documentation for code. Great, we have a pile of rubbish generated and then we have documentation. THAT will help. Michael From michael at freepascal.org Sun Jan 5 12:27:39 2025 From: michael at freepascal.org (Michael Van Canneyt) Date: Sun, 5 Jan 2025 12:27:39 +0100 (CET) Subject: [Lazarus] AI Assistant added In-Reply-To: <6d6ba2ff-eb53-4333-84c3-62478056ce66@ypa-software.de> References: <6d6ba2ff-eb53-4333-84c3-62478056ce66@ypa-software.de> Message-ID: <63d229f5-fb53-bd89-7cbf-595ef25eb@freepascal.org> On Sun, 5 Jan 2025, Michael Fuchs via lazarus wrote: > Am 04.01.25 um 16:02 schrieb Michael Van Canneyt via lazarus: >> I've added an AI assistant (AIssist) to the Lazarus codebase. >> Check out components/aissist. > > But why? 2 reasons: - Because it was requested by a user. - Lazarus is perceived as a tool from the 90-ies (last century). Showing that one can integrate an AI can help to counter that perception. There was also no pressing reason to create the "IDE scout" plugin, but it was made with the same goal: show that Lazarus is not "outdated" and can do the same things a 'modern' (whatever that is) IDE can do. Both are plugins, no need to use it if you don't want/like/trust it. >> All this is meant to provide a start for a CoPilot-kind of functionality, >> as well as a possibility to generate e.g. fpdoc documentation for code. > > Great, we have a pile of rubbish generated and then we have documentation. > THAT will help. Personally, I would not let the AI generate code - every serious question I asked till now generated rubbish answers on all AIs I tried online, but for generating textual descriptions (aka "docs") of existing code, it does a reasonable job. I'm very critical of AI as a code generating tool: we're hopefully all aware that currently an AI cannot "reason". Therefore I consider AI a serious misnomer. But as a replacement/enhancement of google search or a documentation tool it can make sense. You might even try to use it to generate icons. I am horrible at creating icons, and so I did some experiments, what came out was better than what I came up with... Like most tools, you must use it correctly. I can hammer in a nail with a screwdriver, but that doesn't mean it is a good idea. Same with "AI"... Michael. From andrewd207 at aol.com Wed Jan 8 01:33:57 2025 From: andrewd207 at aol.com (Andrew Haines) Date: Tue, 7 Jan 2025 19:33:57 -0500 Subject: [Lazarus] AI Assistant added In-Reply-To: <0688801d-d038-429b-859b-02bc6cd638f7@holobit.hr> References: <0688801d-d038-429b-859b-02bc6cd638f7@holobit.hr> Message-ID: <10327a88-8113-4c82-8a58-aea42b1ee854@aol.com> On 1/5/25 5:39 AM, zeljko via lazarus wrote: > > > On 04. 01. 2025. 16:02, Michael Van Canneyt via lazarus wrote: >> >> Hi, >> >> I've added an AI assistant (AIssist) to the Lazarus codebase. >> Check out components/aissist. >> > > Great news, thanks ! :) > > zeljko > > I agree! Thanks :) From freepascal at ypa-software.de Wed Jan 8 12:34:41 2025 From: freepascal at ypa-software.de (Michael Fuchs) Date: Wed, 8 Jan 2025 12:34:41 +0100 Subject: [Lazarus] AI Assistant added In-Reply-To: <63d229f5-fb53-bd89-7cbf-595ef25eb@freepascal.org> References: <6d6ba2ff-eb53-4333-84c3-62478056ce66@ypa-software.de> <63d229f5-fb53-bd89-7cbf-595ef25eb@freepascal.org> Message-ID: <43b96f9c-0165-46e2-9bf7-f204cfed3f3d@ypa-software.de> Am 05.01.25 um 12:27 schrieb Michael Van Canneyt via lazarus: > - Lazarus is perceived as a tool from the 90-ies (last century). > Showing that one can integrate an AI can help to counter that > perception. Excuse me? That's a reason? Lazarus suddenly becomes more attractive because it serves a dubious hype? There are certainly better ways to present Lazarus as a modern tool. > Personally, I would not let the AI generate code - every serious > question I asked till now generated rubbish answers on all AIs I tried > online, but for > generating textual descriptions (aka "docs") of existing code, it does a > reasonable job. It will only lead to incorrect documentation, because everything is happily pressed through the so-called ?AI? and then no longer checked. Don't get me wrong, certain applications of deep learning such as automated translation are a real step forward. But even there, you have to keep a close eye on what deepl and similar tools have spit out. But generating documentation from source code just like that? > I'm very critical of AI as a code generating tool: we're hopefully all > aware that currently an AI cannot "reason". > Therefore I consider AI a serious misnomer. 100% approval > But as a replacement/enhancement of google search or a documentation > tool it can make sense. Its use as a ?search engine? has already been advertised to me several times. Apart from the fact that I didn't see any speed advantages in the test, there is also the enormous energy consumption for all the chatbots. That alone makes me stay far away from it. > You might even try to use it to generate icons. I am horrible at > creating icons, and so I did some experiments, what came out was better > than what I came up with... And uses existing works by graphic designers who were not asked whether their icons and other images were used for these tools. If I remember, it was always a big issue not to take any source code from Delphi to avoid copyright problems... Then I find this problem-free use of stolen graphic data quite strange. But I don't want to start another ?AI? discussion here - just this much: you should think very carefully about how useful these tools really are and how much damage they cause. g Michael From badsector at runtimeterror.com Wed Jan 8 20:02:07 2025 From: badsector at runtimeterror.com (Kostas Michalopoulos) Date: Wed, 8 Jan 2025 21:02:07 +0200 Subject: [Lazarus] AI Assistant added In-Reply-To: <43b96f9c-0165-46e2-9bf7-f204cfed3f3d@ypa-software.de> References: <6d6ba2ff-eb53-4333-84c3-62478056ce66@ypa-software.de> <63d229f5-fb53-bd89-7cbf-595ef25eb@freepascal.org> <43b96f9c-0165-46e2-9bf7-f204cfed3f3d@ypa-software.de> Message-ID: <3efcfa91-57ae-4c42-a026-b38b6fa61139@runtimeterror.com> On 1/8/25 1:34 PM, Michael Fuchs via lazarus wrote: > It will only lead to incorrect documentation, because everything is > happily pressed through the so-called ?AI? and then no longer checked. [...] But generating documentation from source code just like that? This is solved very easily by not "no longer checking" what it is produced. At the end of the day, if you use AI or write the text yourself by hand, you are the one responsible for whatever you submit. You don't blame Notepad, Vim, Emacs, Word, OpenOffice or whatever other tool you may use to write text when you write something wrong, so it doesn't make sense to blame some AI either. > Its use as a ?search engine? has already been advertised to me several > times. Some AIs can be used more as an augmentation for a search engine in that you can ask them things and they can point you to various concepts. I've used Mixtral recently (an "open weights" model you can download on your PC, though i used it from duck.ai) and it produced decent results. However i used it together with a search engine to look for things (other AIs create links to sources but Mixtral didn't - however if i'm going to use some AI i'd rather use something i can run on my own PC, at least in theory until i get a better one :-P). In that way it worked more as an "optimization" to finding stuff than a replacement, but i still found it useful. I think in general it depends *a lot* in how you use these things and how you approach the problems you want to solve yourself to see any benefit or not. Personally for example i can't think of any advantage in my workflow for AIs like co-pilot (i tried it a bit some time ago in Visual Studio in a VM and found it more annoying than helpful) but there are people who claim they can be much more productive with these. > And uses existing works by graphic designers who were not asked whether > their icons and other images were used for these tools. If I remember, > it was always a big issue not to take any source code from Delphi to > avoid copyright problems... Then I find this problem-free use of stolen > graphic data quite strange. If copyright of the training data is the concern then AFAICT from the recent EU AI Act, using copyrighted data for training is permitted unless there is a machine readable way (the act doesn't specify the exact means, it is something that is still in the works, but there are a couple of solutions already) to opt-out from that (with an exception for some special cases, like research purposes, which can ignore the opt-out). The reasoning (AFAICT) is that AIs need to be trained in large amounts of data to work in the first place but at the same time some individuals may not want to be part of that. AFAIK the UK and the US are also going in the same direction. Kostas From nc-gaertnma at netcologne.de Thu Jan 9 09:21:56 2025 From: nc-gaertnma at netcologne.de (Mattias Gaertner) Date: Thu, 9 Jan 2025 09:21:56 +0100 Subject: [Lazarus] Lazarus Release Candidate 2 of 4.0 Message-ID: <2e7dda2a-8306-417f-8222-fb532b211ed7@netcologne.de> The Lazarus team is glad to announce the second release candidate of Lazarus 4.0. This release was built with FPC 3.2.2. Here is the list of changes for Lazarus and Free Pascal: http://wiki.lazarus.freepascal.org/Lazarus_4.0_release_notes http://wiki.lazarus.freepascal.org/User_Changes_3.2.2 Here is the list of fixes for Lazarus 4.x: https://gitlab.com/freepascal.org/lazarus/lazarus/-/commits/fixes_4/ The release is available for download on SourceForge: http://sourceforge.net/projects/lazarus/files/ Choose your CPU, OS, distro and then the "Lazarus 4.0RC2" directory. Checksums for the SourceForge files: https://www.lazarus-ide.org/index.php?page=checksums#4_0RC2 Minimum requirements: Windows: 2k, 32 or 64bit, Qt, Qt5, Qt6 (64bit only) FreeBSD/Linux: gtk 2.24 for gtk2, qt4.5 for qt, qt5.6 for qt5, Qt6.2 for qt6, 32 or 64bit. Mac OS X: Cocoa (64bit) 10.12, Carbon (32bit) 10.5 to 10.14, Qt and Qt5 (32 or 64bit), Qt6 (64bit only). The gitlab page: https://gitlab.com/freepascal.org/lazarus/lazarus/-/tree/lazarus_4_0RC2 For people who are blocked by SF, the Lazarus releases from SourceForge are mirrored at: https://download.lazarus-ide.org/ ftp://ftp.freepascal.org/pub/lazarus/releases/ == Why should everybody (including you) test the release candidate? == In the past weeks the Lazarus team has stabilized the 4.0 fixes branch. The resulting 4.0RC2 is now stable enough to be used by any one for test purposes. While we have tested those ourselves, there may still be problems that only occur with very specific configurations or one project in a million. Yes, it may be that you are the only person with a project, that will not work in the new IDE. So if you do not test, we can not fix it. Please do not wait for the final release, in order to test. It may be too late. Once the release is out we will have to be more selective about which fixes can be merged for further 4.x releases. So it may be, that we can not merge the fix you require. And then you will miss out on all the new features. == How to test == Download and install the 4.0 RC2. - On Windows you can install as a 2ndary install, that will not affect your current install: http://wiki.lazarus.freepascal.org/Multiple_Lazarus#Installation_of_multiple_Lazarus - On other platforms, if you install to a new location you need to use --primary-config-path In either case you should make backups. (including your primary config) Open your project in your current Lazarus, and use "Publish Project" from the project menu. This creates a clean copy of your project. You can then open that copy in the 4.0RC2. Please test: - If you can edit forms in the designer - rename components / change properties in Object inspector / Add new events - Add components to form / Move components on form - Frames, if you use them - If you can navigate the source code (e.g. jump to implementation) - Auto completion in source code - Compile, debug and run - Anything else you use in your daily work Mattias From the.tail.kinker at gmail.com Fri Jan 10 18:01:35 2025 From: the.tail.kinker at gmail.com (Timothy Groves) Date: Fri, 10 Jan 2025 12:01:35 -0500 Subject: [Lazarus] FPWritePS? Message-ID: Was there ever a unit to handle writing binary image data to Postscript files? From tony.whyman at mccallumwhyman.com Sat Jan 11 16:17:50 2025 From: tony.whyman at mccallumwhyman.com (Tony Whyman) Date: Sat, 11 Jan 2025 15:17:50 +0000 Subject: [Lazarus] Online Package Manager Questions Message-ID: <76cf0324-36cb-4dd5-acfa-8d0844ef678b@mccallumwhyman.com> I recently had a support question for IBX for Lazarus and for an issue that was fixed a couple of years ago. The response was inevitably a "please upgrade to the next version". However, what surprised me was that the user came back pointing out that he was using the most recent version of IBX on OPM. This was a surprise to me as I had not uploaded IBX to the Online Package Manager nor do I recall a request to do so. On the other hand, an out-of-date version (2.5.0) of IBX is on OPM. I don't object to IBX being on OPM - its probably a good idea, but it does raise a few questions: 1. Who makes the decision about what is uploaded to the OPM repository? 2. How is a package put there and what precautions are taken to ensure that the package is genuine and does not contain malicious code - especially when the upload was not done by the original author.? 3. How are the OPM repository maintainers told that a new version of a package is now available? Tony Whyman https://www.mwasoftware.co.uk https://github.com/MWASoftware From werner.pamler at freenet.de Sat Jan 11 19:50:32 2025 From: werner.pamler at freenet.de (Werner Pamler) Date: Sat, 11 Jan 2025 19:50:32 +0100 Subject: [Lazarus] Online Package Manager Questions In-Reply-To: <76cf0324-36cb-4dd5-acfa-8d0844ef678b@mccallumwhyman.com> References: <76cf0324-36cb-4dd5-acfa-8d0844ef678b@mccallumwhyman.com> Message-ID: <559f458e-e47b-415a-9787-17e41eb46130@freenet.de> First of all: OPM was written and maintained by Balazs Szekely (aka GetMem). For a year, however, I have not heard from him any more - I really really hope that he is doing fine. For the moment OPM is maintained by myself. Your questions: Am 11.01.2025 um 16:17 schrieb Tony Whyman via lazarus: > 1. Who makes the decision about what is uploaded to the OPM repository? > 2. How is a package put there and what precautions are taken to ensure > that the package is genuine and does not contain malicious code - > especially when the upload was not done by the original author.? > 3. How are the OPM repository maintainers told that a new version of a > package is now available? When the package owner has the feeling that a new version should be released to OPM he notifies the OPM maintainer by mail to opm at lazarus-ide.com containing a link to the new version or a zipped file as attachment. I look over the code, compile it and run some of the sample projects provided. Anybody can submit packages for inclusion in OPM.? Of course, I don't know any of the submitters personally, and I have no idea whether he/she is the original author. So, sorry that the your IBX files made it into OPM without your knowledge. But I don't see a way how to improve that without building up a huge beaurocracy. Criteria to accept a package are for me (maybe they were different for Balasz): * The library must be a package. Individual, isolated units cannot be handled by OPM. * It must contain a brief description in the meta data and package file. * It must contain a statement on the license. Commercial licenses are rejected. I also reject packages which "smell" like being pirated (for example, when there is the original Borland header in the units). * The package and its files must be in English - this is an international community, and there is no other way to communicate. * It must compile at least under the current releases of Lazarus/FPC. Of course, the more combinations are welcome. The working combinations should be specified in the meta-data (json), as well as the widgetset for which it works. * There should be at least one sample project. Otherwise I have no way to test whether the code is working (I am not willing to write test projects for foreign code). * Ideally there should be some documentation, either included as help files in the package, or as a separate wiki page, or similar. * The package submitter must express his/her commitment to maintain the package if, for example, it does not compile any more due to compiler or widgetset changes. Unfortunately we have many unmaintained packages already now, and I tend to remove a non-functioning unmaintained package. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tony.whyman at mccallumwhyman.com Sun Jan 12 11:51:00 2025 From: tony.whyman at mccallumwhyman.com (Tony Whyman) Date: Sun, 12 Jan 2025 10:51:00 +0000 Subject: [Lazarus] Online Package Manager Questions In-Reply-To: <559f458e-e47b-415a-9787-17e41eb46130@freenet.de> References: <76cf0324-36cb-4dd5-acfa-8d0844ef678b@mccallumwhyman.com> <559f458e-e47b-415a-9787-17e41eb46130@freenet.de> Message-ID: Werner, I can certainly sympathise with with your workload for maintaining the OPM archive, and your reply was very useful. There are two threads that lead from this for me. The first is to get IBX on OPM up-to-date and that we should deal with by direct EMail. The second is really more general and to hopefully have a wider discussion on the how the OPM archive should be maintained in future. Looking at your response, the issue that leapt out for me is "accountability". You seem to be taking on too much accountability when it comes to code published on the OPM archive and especially when it comes to checking that the code is at least compilable and is of an appropriate standard. You said "There should be at least one sample project. Otherwise I have no way to test whether the code is working (I am not willing to write test projects for foreign code)." This implies that you are going to compile, test and look at the results for every package submitted to OPM and potentially for each update (i.e. lots of work for you). In the case of IBX you do at least have 17 example projects to choose from plus a comprehensive regression test suite with 29 individual tests for the main package and a further 22 for the underlying Firebird Pascal Interface package (fbintf) - but you need to set up your own Firebird server to perform the tests/examples. The regression tests make for a very stable and reliable package, but it seems to be asking a lot for you to check the results and validate the package as "good to go". My day job has been in safety critical aviation software and so I am well aware as to how much work goes into third party software certification. Have you thought about requiring that submitted packages are signed by the author/submitter? The author can then take responsibility for at least the provenance of the code, correct licensing and that it compiles - I would not go as far as "fitness for purpose" as open source software can only work if the user accepts that part of the deal. That way you can limit your checks to when the package is first submitted and with updates the checking can be limited to signature verification with the occasional deeper check. Do you also send out automated regular EMails (e.g. every 6 months after a package was first submitted asking authors to re-affirm that the package is up-to-date - and removing any where the author has gone AWOL)? If not, then that would be one way of avoiding stale packages on the archive. Tony Whyman On 11/01/2025 18:50, Werner Pamler via lazarus wrote: > > First of all: OPM was written and maintained by Balazs Szekely (aka > GetMem). For a year, however, I have not heard from him any more - I > really really hope that he is doing fine. For the moment OPM is > maintained by myself. > > Your questions: > > Am 11.01.2025 um 16:17 schrieb Tony Whyman via lazarus: >> 1. Who makes the decision about what is uploaded to the OPM repository? >> 2. How is a package put there and what precautions are taken to >> ensure that the package is genuine and does not contain malicious >> code - especially when the upload was not done by the original author.? >> 3. How are the OPM repository maintainers told that a new version of >> a package is now available? > > When the package owner has the feeling that a new version should be > released to OPM he notifies the OPM maintainer by mail to > opm at lazarus-ide.com containing a link to the new version or a zipped > file as attachment. I look over the code, compile it and run some of > the sample projects provided. > > Anybody can submit packages for inclusion in OPM.? Of course, I don't > know any of the submitters personally, and I have no idea whether > he/she is the original author. So, sorry that the your IBX files made > it into OPM without your knowledge. But I don't see a way how to > improve that without building up a huge beaurocracy. > > Criteria to accept a package are for me (maybe they were different for > Balasz): > > * The library must be a package. Individual, isolated units cannot > be handled by OPM. > * It must contain a brief description in the meta data and package file. > * It must contain a statement on the license. Commercial licenses > are rejected. I also reject packages which "smell" like being > pirated (for example, when there is the original Borland header in > the units). > * The package and its files must be in English - this is an > international community, and there is no other way to communicate. > * It must compile at least under the current releases of > Lazarus/FPC. Of course, the more combinations are welcome. The > working combinations should be specified in the meta-data (json), > as well as the widgetset for which it works. > * There should be at least one sample project. Otherwise I have no > way to test whether the code is working (I am not willing to write > test projects for foreign code). > * Ideally there should be some documentation, either included as > help files in the package, or as a separate wiki page, or similar. > * The package submitter must express his/her commitment to maintain > the package if, for example, it does not compile any more due to > compiler or widgetset changes. Unfortunately we have many > unmaintained packages already now, and I tend to remove a > non-functioning unmaintained package. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marc at dommelstein.nl Sun Jan 12 22:12:28 2025 From: marc at dommelstein.nl (Marc Weustink) Date: Sun, 12 Jan 2025 22:12:28 +0100 Subject: [Lazarus] Online Package Manager Questions In-Reply-To: <559f458e-e47b-415a-9787-17e41eb46130@freenet.de> References: <76cf0324-36cb-4dd5-acfa-8d0844ef678b@mccallumwhyman.com> <559f458e-e47b-415a-9787-17e41eb46130@freenet.de> Message-ID: <66290B6E-E781-47A9-B47F-E952BCF8263B@dommelstein.nl> Please note that the opm email address mentioned should be sent to lazarus-ide.ORG and not to .COM Marc On January 11, 2025 7:50:32 PM GMT+01:00, Werner Pamler via lazarus wrote: >First of all: OPM was written and maintained by Balazs Szekely (aka GetMem). For a year, however, I have not heard from him any more - I really really hope that he is doing fine. For the moment OPM is maintained by myself. > >Your questions: > >Am 11.01.2025 um 16:17 schrieb Tony Whyman via lazarus: >> 1. Who makes the decision about what is uploaded to the OPM repository? >> 2. How is a package put there and what precautions are taken to ensure that the package is genuine and does not contain malicious code - especially when the upload was not done by the original author.? >> 3. How are the OPM repository maintainers told that a new version of a package is now available? > >When the package owner has the feeling that a new version should be released to OPM he notifies the OPM maintainer by mail to opm at lazarus-ide.com containing a link to the new version or a zipped file as attachment. I look over the code, compile it and run some of the sample projects provided. > >Anybody can submit packages for inclusion in OPM.? Of course, I don't know any of the submitters personally, and I have no idea whether he/she is the original author. So, sorry that the your IBX files made it into OPM without your knowledge. But I don't see a way how to improve that without building up a huge beaurocracy. > >Criteria to accept a package are for me (maybe they were different for Balasz): > > * The library must be a package. Individual, isolated units cannot be > handled by OPM. > * It must contain a brief description in the meta data and package file. > * It must contain a statement on the license. Commercial licenses are > rejected. I also reject packages which "smell" like being pirated > (for example, when there is the original Borland header in the units). > * The package and its files must be in English - this is an > international community, and there is no other way to communicate. > * It must compile at least under the current releases of Lazarus/FPC. > Of course, the more combinations are welcome. The working > combinations should be specified in the meta-data (json), as well as > the widgetset for which it works. > * There should be at least one sample project. Otherwise I have no way > to test whether the code is working (I am not willing to write test > projects for foreign code). > * Ideally there should be some documentation, either included as help > files in the package, or as a separate wiki page, or similar. > * The package submitter must express his/her commitment to maintain > the package if, for example, it does not compile any more due to > compiler or widgetset changes. Unfortunately we have many > unmaintained packages already now, and I tend to remove a > non-functioning unmaintained package. From werner.pamler at freenet.de Sun Jan 12 23:14:09 2025 From: werner.pamler at freenet.de (Werner Pamler) Date: Sun, 12 Jan 2025 23:14:09 +0100 Subject: [Lazarus] Online Package Manager Questions In-Reply-To: References: <76cf0324-36cb-4dd5-acfa-8d0844ef678b@mccallumwhyman.com> <559f458e-e47b-415a-9787-17e41eb46130@freenet.de> Message-ID: <61f0f240-a7ae-434e-a195-94bd573e152a@freenet.de> Am 12.01.2025 um 11:51 schrieb Tony Whyman: > You said "There should be at least one sample project. Otherwise I > have no way to test whether the code is working (I am not willing to > write test projects for foreign code)." > > This implies that you are going to compile, test and look at the > results for every package submitted to OPM and potentially for each > update (i.e. lots of work for you). In the case of IBX you do at least > have 17 example projects to choose from plus a comprehensive > regression test suite with 29 individual tests for the main package > and a further 22 for the underlying Firebird Pascal Interface package > (fbintf) - but you need to set up your own Firebird server to perform > the tests/examples. > There is no general rule. I certainly will not run all sample projects, and in fact, before I uploaded your new version to OPM today, I ran only two. I knew that you were the author, the overall impression of the code was good. This makes me "trust" you. If the author would have been unknown, or assuming that there were massive preparations to test (installing third-party servers/clients etc), I would have asked the author to first present the package(s) in the forum to hear about the experience of others. And this, in fact, is the way it usually goes: People have an idea for a component/package and "exhibit" it in the forum first. When it gets good feedback they ask for adding to OPM. > The regression tests make for a very stable and reliable package, but > it seems to be asking a lot for you to check the results and validate > the package as "good to go". Most of the OPM packages do not contain unit tests at all, I probably would not see them at all. And even if I'd run the tests: what if there were fails? Would this be enough to reject the update? Not knowing the details of that software, I would still accept the submission and let the users decide. > Have you thought about requiring that submitted packages are signed by > the author/submitter? The author can then take responsibility for at > least the provenance of the code, correct licensing and that it > compiles - I would not go as far as "fitness for purpose" as open > source software can only work if the user accepts that part of the deal. > No beaurocarcy please. Requiring authors to sign their contributions would kill OPM. > Do you also send out automated regular EMails (e.g. every 6 months > after a package was first submitted asking authors to re-affirm that > the package is up-to-date - and removing any where the author has gone > AWOL)? If not, then that would be one way of avoiding stale packages > on the archive. Again: too much beaurocracy, now for me - I don't even have e-mail addresses of authors at hand. And what if the author/maintainer does not respond? To be honest, once a package has made it into OPM it has a "safe life" there. There is no chance to re-test all existing packages at all. But sometimes, usually after changes in FPC or in the LCL, users report in the forum that packages do not work any more. In this case, the user (or I) contacts the author or files a bug report in the author's repository, and the issue gets fixed. In other cases, the author is not active any more: when there is an easy fix I patch the component byself and replace the non-functional package. When this is not possible, the package is removed. From werner.pamler at freenet.de Sun Jan 12 23:16:25 2025 From: werner.pamler at freenet.de (Werner Pamler) Date: Sun, 12 Jan 2025 23:16:25 +0100 Subject: [Lazarus] Online Package Manager Questions In-Reply-To: <66290B6E-E781-47A9-B47F-E952BCF8263B@dommelstein.nl> References: <76cf0324-36cb-4dd5-acfa-8d0844ef678b@mccallumwhyman.com> <559f458e-e47b-415a-9787-17e41eb46130@freenet.de> <66290B6E-E781-47A9-B47F-E952BCF8263B@dommelstein.nl> Message-ID: Am 12.01.2025 um 22:12 schrieb Marc Weustink via lazarus: > Please note that the opm email address mentioned should be sent to lazarus-ide.ORG and not to .COM You are right. Sorry for the typo. -------------- next part -------------- An HTML attachment was scrubbed... URL: From badsector at runtimeterror.com Mon Jan 13 02:59:16 2025 From: badsector at runtimeterror.com (Kostas Michalopoulos) Date: Mon, 13 Jan 2025 03:59:16 +0200 Subject: [Lazarus] Online Package Manager Questions In-Reply-To: <61f0f240-a7ae-434e-a195-94bd573e152a@freenet.de> References: <76cf0324-36cb-4dd5-acfa-8d0844ef678b@mccallumwhyman.com> <559f458e-e47b-415a-9787-17e41eb46130@freenet.de> <61f0f240-a7ae-434e-a195-94bd573e152a@freenet.de> Message-ID: <1e422e52-035d-4329-b614-ab3ee1f22ad6@runtimeterror.com> On 1/13/25 12:14 AM, Werner Pamler via lazarus wrote: > To be honest, once a package has made it into OPM it has a "safe life" > there. There is no chance to re-test all existing packages at all. But > sometimes, usually after changes in FPC or in the LCL, users report in > the forum that packages do not work any more. In this case, the user (or > I) contacts the author or files a bug report in the author's repository, > and the issue gets fixed. In other cases, the author is not active any > more: when there is an easy fix I patch the component byself and replace > the non-functional package. When this is not possible, the package is > removed. Would it be possible to do some periodic 'smoke tests' where all packages are compiled against latest (main) Lazarus (preferably with latest/main FPC too, at least as an extra pass - i.e. main branch Lazarus compiled with main branch FPC) to find any packages that won't compile and even run automated tests for those packages that provide them? Perhaps this could help not only to find early which packages might break but also - and most importantly IMO - will help find 'obvious' backward compatibility regressions in Lazarus (and FPC, if a pass for main FPC branch is used) before any releases are made. Of course this wont help with packages that compile and have tests that pass (or wont have any tests at all) that still have their behavior affected negatively by changes in Lazarus / FPC, but it could still be useful to find and avoid some regressions. Kostas From werner.pamler at freenet.de Mon Jan 13 19:30:25 2025 From: werner.pamler at freenet.de (Werner Pamler) Date: Mon, 13 Jan 2025 19:30:25 +0100 Subject: [Lazarus] Online Package Manager Questions In-Reply-To: <1e422e52-035d-4329-b614-ab3ee1f22ad6@runtimeterror.com> References: <76cf0324-36cb-4dd5-acfa-8d0844ef678b@mccallumwhyman.com> <559f458e-e47b-415a-9787-17e41eb46130@freenet.de> <61f0f240-a7ae-434e-a195-94bd573e152a@freenet.de> <1e422e52-035d-4329-b614-ab3ee1f22ad6@runtimeterror.com> Message-ID: Am 13.01.2025 um 02:59 schrieb Kostas Michalopoulos via lazarus: > Would it be possible to do some periodic 'smoke tests' where all > packages are compiled against latest (main) Lazarus (preferably with > latest/main FPC too, at least as an extra pass - i.e. main branch > Lazarus compiled with main branch FPC) to find any packages that won't > compile and even run automated tests for those packages that provide > them? Good idea but cannot be done manually (there are 280 repository packages with 350 lpk files at the moment). "Somebody" should write a script for that. On a local PC, it would probably require a dedicated test installation of Lazarus for this sole purpose because I don't know if Lazarus would still be usable with so many packages installed. Or maybe "github actions" or similar to run the job on a remove server? Experienced volonteers are welcome... From lazarus at mfriebe.de Mon Jan 13 20:43:06 2025 From: lazarus at mfriebe.de (Martin Frb) Date: Mon, 13 Jan 2025 20:43:06 +0100 Subject: [Lazarus] Online Package Manager Questions In-Reply-To: References: <76cf0324-36cb-4dd5-acfa-8d0844ef678b@mccallumwhyman.com> <559f458e-e47b-415a-9787-17e41eb46130@freenet.de> <61f0f240-a7ae-434e-a195-94bd573e152a@freenet.de> <1e422e52-035d-4329-b614-ab3ee1f22ad6@runtimeterror.com> Message-ID: <96aaf281-fe0f-4bb6-972f-176aab544d4b@mfriebe.de> On 13/01/2025 19:30, Werner Pamler via lazarus wrote: > Am 13.01.2025 um 02:59 schrieb Kostas Michalopoulos via lazarus: >> Would it be possible to do some periodic 'smoke tests' where all >> packages are compiled against latest (main) Lazarus (preferably with >> latest/main FPC too, at least as an extra pass - i.e. main branch >> Lazarus compiled with main branch FPC) to find any packages that >> won't compile and even run automated tests for those packages that >> provide them? > Good idea but cannot be done manually (there are 280 repository > packages with 350 lpk files at the moment). "Somebody" should write a > script for that. On a local PC, it would probably require a dedicated > test installation of Lazarus for this sole purpose because I don't > know if Lazarus would still be usable with so many packages installed. > Or maybe "github actions" or similar to run the job on a remove > server? Experienced volonteers are welcome... You don't need to install them all. Just compile each package against the lazarus directory (e.g. using lazbuild). That checks that the package can be build with a given LCL + IdeIntf => meaning it would be compilable as part of the IDE. Of course package that are already tested as dependency of another don't need to be done by themself again. Running it is of course a different beast. I don't know how much time that would need to build them all. In terms of available CI minutes on gitlab => it is possible to have tasks that run only on request => but if it failed it would need several reruns... From nc-gaertnma at netcologne.de Wed Jan 22 14:51:32 2025 From: nc-gaertnma at netcologne.de (Mattias Gaertner) Date: Wed, 22 Jan 2025 14:51:32 +0100 Subject: [Lazarus] Lazarus Bugfix Release 3.6 Message-ID: <51ffcffb-8672-4952-8ebe-fad799109e12@netcologne.de> The Lazarus team is glad to announce the release of Lazarus 3.8. This is a bugfix release and was built with FPC 3.2.2. Here is the list of changes for Lazarus and Free Pascal: http://wiki.lazarus.freepascal.org/Lazarus_3.0_release_notes http://wiki.lazarus.freepascal.org/User_Changes_3.2.2 Here is the list of fixes for Lazarus 3.x: https://gitlab.com/freepascal.org/lazarus/lazarus/-/commits/fixes_3_0/ The release is available for download on SourceForge: http://sourceforge.net/projects/lazarus/files/ Choose your CPU, OS, distro and then the "Lazarus 3.8" directory. Checksums for the SourceForge files: https://www.lazarus-ide.org/index.php?page=checksums#3_8 The Windows installers are now code signed. The signature uses the name of the Foundation: "Stichting Programming Free Pascal & Lazarus Foundation" Minimum requirements: Windows: 2k, 32 or 64bit, Qt, Qt5, Qt6 (64bit only) FreeBSD/Linux: gtk 2.24 for gtk2, qt4.5 for qt, qt5.6 for qt5, Qt6.2 for qt6, 32 or 64bit. Mac OS X: Cocoa (64bit) 10.12, Carbon (32bit) 10.5 to 10.14, Qt and Qt5 (32 or 64bit), Qt6 (64bit only). Note: Since Macos Sonoma 14 debugging takes some time to start the application, especially on first start. The gitlab page: https://gitlab.com/freepascal.org/lazarus/lazarus/-/tree/lazarus_3_8 For people who are blocked by SF, the Lazarus releases from SourceForge are mirrored at: https://download.lazarus-ide.org/ ftp://ftp.freepascal.org/pub/lazarus/releases/ Mattias From larrydalton71 at gmail.com Thu Jan 23 14:40:08 2025 From: larrydalton71 at gmail.com (Larry Dalton) Date: Thu, 23 Jan 2025 08:40:08 -0500 Subject: [Lazarus] libmysql.dll Message-ID: I am using 3.4, fpc 3.2.2. Has libmysql.dll been included in that? I am using xampp phpmyadmin, on my laptop, and don't have libmysql.dll in my windows/system directory or the root directory of my application, and it does not seem to require it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael at freepascal.org Thu Jan 23 14:44:29 2025 From: michael at freepascal.org (Michael Van Canneyt) Date: Thu, 23 Jan 2025 14:44:29 +0100 (CET) Subject: [Lazarus] libmysql.dll In-Reply-To: References: Message-ID: <5d662e5e-8986-58c9-4ff-b9d996cc37f6@freepascal.org> On Thu, 23 Jan 2025, Larry Dalton via lazarus wrote: > I am using 3.4, fpc 3.2.2. Has libmysql.dll been included in that? I am > using xampp phpmyadmin, on my laptop, and don't have libmysql.dll in my > windows/system directory or the root directory of my application, and it > does not seem to require it. We don't distribute libraries. If you have phpmyadmin, then normally you must have a mysql client library somewhere (unless php was compiled with a static version of the lib). It's probably named differently. libmysqlclient or somesuch. Michael. From larrydalton71 at gmail.com Thu Jan 23 17:02:04 2025 From: larrydalton71 at gmail.com (Larry Dalton) Date: Thu, 23 Jan 2025 11:02:04 -0500 Subject: [Lazarus] libmysql.dll In-Reply-To: <5d662e5e-8986-58c9-4ff-b9d996cc37f6@freepascal.org> References: <5d662e5e-8986-58c9-4ff-b9d996cc37f6@freepascal.org> Message-ID: I?ll try that. I have removed all instances of libmysql.dll from my laptop and it runs fine. However, my desktop doesn?t On Thu, Jan 23, 2025 at 08:44 Michael Van Canneyt via lazarus < lazarus at lists.lazarus-ide.org> wrote: > > > On Thu, 23 Jan 2025, Larry Dalton via lazarus wrote: > > > I am using 3.4, fpc 3.2.2. Has libmysql.dll been included in that? I am > > using xampp phpmyadmin, on my laptop, and don't have libmysql.dll in my > > windows/system directory or the root directory of my application, and it > > does not seem to require it. > > We don't distribute libraries. > > If you have phpmyadmin, then normally you must have a mysql client library > somewhere (unless php was compiled with a static version of the lib). > It's probably named differently. libmysqlclient or somesuch. > > Michael. > -- > _______________________________________________ > lazarus mailing list > lazarus at lists.lazarus-ide.org > https://lists.lazarus-ide.org/listinfo/lazarus > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmlandmesser at gmx.de Thu Jan 23 18:32:25 2025 From: jmlandmesser at gmx.de (John Landmesser) Date: Thu, 23 Jan 2025 18:32:25 +0100 Subject: [Lazarus] libmysql.dll In-Reply-To: References: <5d662e5e-8986-58c9-4ff-b9d996cc37f6@freepascal.org> Message-ID: Am 23.01.25 um 17:02 schrieb Larry Dalton via lazarus: > I?ll try that. I have removed all instances of libmysql.dll from my > laptop and it runs fine. However, my desktop doesn?t > > On Thu, Jan 23, 2025 at 08:44 Michael Van Canneyt via lazarus > wrote: > > > > On Thu, 23 Jan 2025, Larry Dalton via lazarus wrote: > > > I am using 3.4, fpc 3.2.2. Has libmysql.dll been included in > that? I am > > using xampp phpmyadmin, on my laptop, and don't have > libmysql.dll in my > > windows/system directory or the root directory of my > application, and it > > does not seem to require it. > > We don't distribute libraries. > > If you have phpmyadmin, then normally you must have a mysql client > library > somewhere (unless php was compiled with a static version of the lib). > It's probably named differently. libmysqlclient or somesuch. > > Michael. > -- > _______________________________________________ > lazarus mailing list > lazarus at lists.lazarus-ide.org > https://lists.lazarus-ide.org/listinfo/lazarus > > Perhaps this link gives you some useful hints: https://dev.mysql.com/doc/refman/8.4/en/windows-installation.html I never used mysql but for sqlite i learned : the *.dll have to be in the directory where your application *.exe exists Good luck John -------------- next part -------------- An HTML attachment was scrubbed... URL: From aurimenes at gmail.com Thu Jan 23 18:42:53 2025 From: aurimenes at gmail.com (Aurimenes Silva) Date: Thu, 23 Jan 2025 14:42:53 -0300 Subject: [Lazarus] libmysql.dll In-Reply-To: References: <5d662e5e-8986-58c9-4ff-b9d996cc37f6@freepascal.org>

Message-ID: <34d22837-77de-475e-bfa8-1bf80c9bfa4e@gmail.com> Take into consideration that both the exe and the dll should have the same architecture (both 32 or 64 bits). This is a common issue for a dll not being working. Place the Dll on your exe's folder or in a folder that is listed in the path and it will work. *Aurimenes Silva* Desenvolvedor de Software (81) 99935-9066 Em 23/01/2025 14:32, John Landmesser via lazarus escreveu: > Am 23.01.25 um 17:02 schrieb Larry Dalton via lazarus: >> I?ll try that. I have removed all instances of libmysql.dll from my >> laptop and it runs fine. However, my desktop doesn?t > -- O software antiv?rus Avast realizou uma checagem de v?rus neste e-mail. www.avast.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From the.tail.kinker at gmail.com Sun Jan 26 18:50:04 2025 From: the.tail.kinker at gmail.com (Timothy Groves) Date: Sun, 26 Jan 2025 12:50:04 -0500 Subject: [Lazarus] Bulk Renamer Message-ID: https://github.com/tailkinker/BulkRenamer A cheap little bulk renamer. From matthieugiroux at yahoo.fr Sun Jan 26 19:40:25 2025 From: matthieugiroux at yahoo.fr (Matthieu Giroux) Date: Sun, 26 Jan 2025 18:40:25 +0000 (UTC) Subject: [Lazarus] Bulk Renamer In-Reply-To: References: Message-ID: <1532801115.7776774.1737916825038@mail.yahoo.com> You can add your free software to the lazarus forum at third party index. Matthieu Giroux 13 Rue Fr Tanguy PRIGENT A.15 - 35000 RennesT?l : 09 61 37 01 82 - 06 44 733 008 http://www.liberlog.fr Le dimanche 26 janvier 2025 ? 18:50:22 UTC+1, Timothy Groves via lazarus a ?crit : https://github.com/tailkinker/BulkRenamer A cheap little bulk renamer. -- _______________________________________________ lazarus mailing list lazarus at lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus -------------- next part -------------- An HTML attachment was scrubbed... URL: From freedos.la at gmail.com Mon Jan 27 18:35:11 2025 From: freedos.la at gmail.com (Ralf Quint) Date: Mon, 27 Jan 2025 09:35:11 -0800 Subject: [Lazarus] Bulk Renamer In-Reply-To: References: Message-ID: <87084a4d-8f70-4562-857f-3c6defb17391@gmail.com> On 1/26/2025 9:50 AM, Timothy Groves via lazarus wrote: > https://github.com/tailkinker/BulkRenamer > > A cheap little bulk renamer. > It looks like this is Linux only, right? Would be nice to mention this in the readme file... :( Ralf From the.tail.kinker at gmail.com Mon Jan 27 21:31:45 2025 From: the.tail.kinker at gmail.com (Timothy Groves) Date: Mon, 27 Jan 2025 15:31:45 -0500 Subject: [Lazarus] Bulk Renamer In-Reply-To: <87084a4d-8f70-4562-857f-3c6defb17391@gmail.com> References: <87084a4d-8f70-4562-857f-3c6defb17391@gmail.com> Message-ID: The executable is Linux, but I don't see any reason why it couldn't be compiled under Windows. I just don't have a Windows box. On Mon., Jan. 27, 2025, 12:44 p.m. Ralf Quint via lazarus, < lazarus at lists.lazarus-ide.org> wrote: > On 1/26/2025 9:50 AM, Timothy Groves via lazarus wrote: > > https://github.com/tailkinker/BulkRenamer > > > > A cheap little bulk renamer. > > > It looks like this is Linux only, right? Would be nice to mention this > in the readme file... :( > > Ralf > > > -- > _______________________________________________ > lazarus mailing list > lazarus at lists.lazarus-ide.org > https://lists.lazarus-ide.org/listinfo/lazarus > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sarel at devnow.co.za Tue Jan 28 06:56:48 2025 From: sarel at devnow.co.za (Sarel Wessels (Devnow.co.za)) Date: Tue, 28 Jan 2025 07:56:48 +0200 Subject: [Lazarus] Bulk Renamer In-Reply-To: References: <87084a4d-8f70-4562-857f-3c6defb17391@gmail.com> Message-ID: <69ba5e52-b941-4d39-8a7f-cbc4b930d9da@devnow.co.za> Hey, do you need someone to compile it under windows for you each time? I would not mind. Regards, Sarel On 27/01/2025 22:31, Timothy Groves via lazarus wrote: > > The executable is Linux, but I don't see any reason why it couldn't be > compiled under Windows.? I just don't have a Windows box. > > > On Mon., Jan. 27, 2025, 12:44 p.m. Ralf Quint via lazarus, > wrote: > > On 1/26/2025 9:50 AM, Timothy Groves via lazarus wrote: > > https://github.com/tailkinker/BulkRenamer > > > > A cheap little bulk renamer. > > > It looks like this is Linux only, right? Would be nice to mention > this > in the readme file... :( > > Ralf > > > -- > _______________________________________________ > lazarus mailing list > lazarus at lists.lazarus-ide.org > https://lists.lazarus-ide.org/listinfo/lazarus > > -------------- next part -------------- An HTML attachment was scrubbed... URL: