corneliusdavid

@Dave Nottage, thanks for the clarification. It's been the rule of thumb I've used for the little bits of Apple dev I've done but I didn't consider older versions of Delphi or CE.

Always use the most recent version of XCode.

For me, I use AI with Delphi sparingly. But in two cases, it's helped quite a bit: 1) recalling seldom-used functions when I can't remember the right keyword but can describe the problem; and 2) writing unit tests. For web stuff, yes, it's great! The overall consensus, though is that it's not replacing our jobs any time soon: Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity

I've got Claude Code installed on WSL2 (Claude helped me get there--it was quite a chore) but probably won't be using it much for Delphi. I support some web sites using the Hugo static generator so plan on getting my feet wet with that.

There are no server settings to set--it's a client-only action and uses whatever MAPI-enabled email client you have installed. If Outlook, then yes, it uses Outlook. On my system, I use eM Client, so a quick sample app pulled up a new email message using that program.

That was my impression, too.

You can create a CGI application as a VCL Program that listens for web requests as if it was running under IIS--makes it very easy to debug (see attached image). Maybe this will help: https://github.com/corneliusdavid/AutoGetIt

This will help get you started on writing components.

I was going to say that this often indicates RAD Server is not yet started but you said the version page shows correctly, so your guess that it's a port configuration is a next guess. I've only used RAD Server on Windows; when I run RSConsole.exe (a windows program in the RAD Server folder, it wants to start the server on a port other than the public one, i.e. 8080 instead of 80 or 443. That's so you can isolate the console for secure management, like only within your local network. All this should be configured in the emsserver.ini file, including (as @Uwe Raabe said) the location of the database.

Try exiting Delphi, removing temp files like .dsk, .ddp, .dcu, and others, then restart Delphi and do a build-all. I've found that helps the source/debug line alignments. As for the function value return warning--I dunno!

Well, that's a different problem. I assume you've restarted Delphi?

I was re-reading your original post and I've encountered this before with a perfectly fine package that has all source. If this is the first time you've compiled/installed a custom package in this instance of Delphi, first check the Package Output Directory (in Tools > Options > Language > Delphi > Library), then make sure that path is listed in your Library Path (same options page):

Are you trying to install a Design-time package that relies on a XE2-compiled runtime package? That won't work, of course. What are are the required the packages of this Delphi project? Can you share the DPK of the package you're compiling/installing?

I've found it to be helpful as well in many situations. Just this morning, I was updating an old Delphi XE program that needed to get a list of available drives and forgot what the procedure was called. Sure, I could've looked it up but Claude reminded me of GetLogicalDriveStrings much quicker. Earlier this week, I wanted to try out Claude Code on my Windows machine. I learned it required Linux and didn't work on my currently installed WSL version 1. (The web-based) Claude helped me figure out which version of WSL I had, install WSL 2, then even though it was installed, WSL 1 was still the default so it helped me change that. Then, I had to go through a similar process with nodejs and npm. I learned several new "wsl" commands and got it up and running. It would've taken me many hours hunting down forums and blog posts to put all those pieces together--I probably would've given up. It's not great at writing whole programs or untangling a huge library of code but it can sure save time in many instances.

Perhaps this was a re-type error but that line with "{$IFNDEF GELATI" is missing the closing curly brace: {$IFNDEF GELATI} // <-- need to close with } Otherwise, it's dimming/not-dimming as I would expect. If GELATI is not defined, then code in a "{$IFNDEF GELATI}" would execute and therefore not be dimmed--because {$IFNDEF} = if the symbol is NOT DEFINED.