Leaderboard

That is beside the point of this topic. Remember what the OP has actually asked.

Found the reason: GX_GrepSearchExpert in '..\..\source\Grep\GX_GrepSearchExpert.pas', is missing from the dpr files for most Delphi versions except 2007. After adding this unit, Grep Search is available again. Schönen 2. Advent!

No Bruce, ZeosLib as an OpenSource DAC(Database access component) and it's definitelly not for FireDac. We may call it "a source of inspiration for Dimitry's FireDac/AnyDac". ZeosLib is much better maintained than dbGo. So don't hassitate to use OpenSource! Regards, Michael

You can only load one pythonxy.dll in the Delphi process, hence you can only have one PythonEngine in an application. Look at Demo33 on how to use threads and/or multiple sub-interpreters without blocking the main thread. But also note that you cannot bypass the python famous GIL (Global Interpreter Lock), so that only one python thread can be executing at the same time. Under Tutorials/Webinar II look at PyVizSVG.dproj on how to generate svg files in python scripts and how to display them in Delphi, The only way to really use multiple cores to generate the graphs is to use external processes. (there is the mutliprocessing unit in python, but it would be easier just to start multiple python processes from Delphi).

You'll get no complaint from me on that.

I disagree - this is exactly the mindset that we got trained all these years because we did not know any better - the world moved on - heck there are people working on programming tools based on ML so it can suggest refactorings based on refactorings you have done in the past! And yet here we are mostly doing yolo driven development - "if it aint break it might be ok" (ok, I am exaggerating here). If the tooling can point out possible optimizations because they understand what you are doing that can just be good regardless of how much of a measurable improvement that will make. And if its just for some junior coders at Embarcadero slapping together some ... ahem ... non ideal code that never gets properly reviewed because lack of time. It took them years and an actual change of the FreeAndNil function to find bugs in their code that static code analysis could have found ages ago.

I brought the ICS TWSocketServer component page up to date, and the TWSocketServer.IcsHosts properties page, since those two components are the basis of all the servers, and I extended the capability a lot so you don't need TSslContext which is probably the component you want documented. And I'm slowly adding new components that don't need TSslContext either, already done HTTP, FTP and SMTP, to make SSL easier to use. I used Document Insight to create a 20MB CHM file, it has various other formats, But it really needs a large amount of XML added to the source files to be useful, which is many weeks or months of work. The file is on the wiki site but I'm not publishing the URL here since it's not useful in it's present form. Angus

The ICS FAQ pages already have a lot of SSL/TLS documentation for major subjects, and some of the server components have almost up to data documentation for properties and methods. But proper documentation takes weeks and no-one will pay for it, so I spend more time writing new components. http://wiki.overbyte.eu/wiki/index.php/Main_Page I have created a complete help file of all ICS components, properties, methods and events, but it would take weeks to make it useful with actual text on what they do. Some developers give up at that point and just leave a skeleton help file. Angus

I can understand the request to do so. I have already written in the project description that this would be a task one could/should do. As I'm busy enough with my other open source project (DEC - Delphi Encryption Compendium) I will accept such translations and update the code with them but won't invest the time in those at this time. As user Dummzeuch (a German by the way! ;-) ) stated: maybe somebody could contribute them. I guess there are enough Delphi developers out there who didn't contribute code etc. yet but only consumed so far what others contributed. That could be a start to give something back. As we're talking about contributing and my next topic is related to F. Piette: is there an easy way to write a Delphi source code parser (maybe using Delphi AST which I only know by name) to parse the source of ICS and generate output in the Wikipedia syntax so that for the still undocumented SSL ICS code the Wiki sceleton could be generated at least as a starting point to finally get documentation started? While I value the library and its many demos, a written documentation about the individual properties and methods is also worth quite something!