Leaderboard

Wow. I can't wait to see how productive people are using all these AI tools built on infinite AI training feedback loops.

There goes another enshittification. And we all get to watch it live and in color.

I guess, whatever the real intention is, one can always make up a fake reason to do so.

The whole situation at Stack Overflow just made a drastic turn for the worse: https://meta.stackoverflow.com/questions/425162/we-are-seeking-functional-feedback-for-the-formatting-assistant and https://meta.stackoverflow.com/questions/425081/stack-overflow-will-be-experimenting-with-a-question-formatting-assistant-and-w It seems that whole reason behind tying the mods hands when it comes to detecting and moderating AI content is related to the brand new "AI Formatting Assistant" It is presented as something that would help people write better questions, but I guess that is just first step and second one would be expanding it to answers, too. Because such "formatted" posts would have typical AI signature, moderators would not be able to distinguish between AI generated and "merely formatted" posts. Additionally, the results of "formatting" go beyond mere formatting because AI completely rewrites the post including text and code adding its hallucinations on top. It is beyond horrible and harmful.

Some people found it helpful to manually uninstall all GetIt packages before the update and re-install them afterwards. The installer seems not to handle that very well by itself.

Check out TMS WEB Core. https://www.tmssoftware.com/site/tmswebcore.asp It lets you build your entire app in the Delphi IDE or VS Code -- both the front-end and back-end. It's awesome technology! They have a blog and Andrew Simard has written a bunch of detailed articles on how you can work with common javascript libraries to tailor the UI to work fully in HTML/CSS rather than use the default Delphi screen widgets. Said another way, this lets you use Delphi to build an entire app and then refine the UI using JS if you want. No python is needed, although you could use it (or anything else) for the back-end if you wanted.

It's like watching a slow-motion car crash. Pretty fascinating, really.

In order to provide a timeout for async methods, the component would need to include a timer, using an extra handle and resources. When you have 100 components running in parallel, that is very inefficient, thus the design where the application is responsible for timing out unresponsive components. Some server components do include a timer for that purpose, but rarely do applications need more than one server component. Angus

I found that hint also annoying, especially as some people tend to have no hints and warnings when building their projects. IMHO it would be sufficient to emit it only f.i. in DEBUG mode or even better controlled by a specific DEFINE. As a workaround you can pre-compile the component units and use only the DCUs for your projects. As you stated, you prefer not to change the code, you can as well go this way - it will even speed up compile time a bit. That doesn't hinder you to debug the sources as long as everything is set up properly.

Hi Carlo, hi all! After I saw this thread, we decided to try this SVG components and the results are really awesome! But there is one really annoying issue: someone seems to think that it is a really good idea, to include a "{$MESSAGE HINT 'Use Delphi native Image32 SVG-Engine for SVGIconImageList'}" to indicate the used engine. So, on every build this hint pops up - a hint should be a note to take a closer look at a specific code not a simple debug information. And I didn't find a place to turn this off. 😞 Are we doing anything wrong? How to get rid of this? Otherwise, because of this little thing, this library would be useless for us. (I know how I could change the code myself, but I would like to use the standard, otherwise we would have to change it with every update 🙂 ) We are using the version deployed via GetIt.

Hello alogrep, let me answer your 2nd question first: This dialog is somewhat misleading IMHO; read carefully. It tells you that the previous version will be uninstalled if you click "uninstall". The Yes/No-selection in the dialog is about removing stored data from the registry. "No" means "keep all settings", which includes library/search path, toolbar configuration, installed packages and much more. Which leads to your 1st question: No. If you decide to keep the registry settings by choosing "no" (see above), all your own and/or 3rd-party components will be availabel in V11.3. This because V11.2 and V11.3 are binary compatible. HTH

I'm sure getting an mp3 onto your iPhone is not going to be the challenge. I mostly see people using their email or their favourite instant messenger to send themselves a file they want to access from another device while Airdrop also seems to be common, at least for Apple people. Here are three other ways I would do it Copy the file(s) to my computers desktop, because my desktop is synced with iCloud and and always accessible from my phone. Doesn't have to be iCloud, works with OneDrive, Dropbox and whatever is out there. Granted, that hardly applies to everybody because not everybody uses cloud file storage. I can just copy the file on my computer, and then just select paste on my phone. That probably doesn't work with Windows computers, though. I just right-click the file, share, Airdrop and then select my phone. Only works for Apple. By the way, this is how my mom always does it 🙂 I dare to say that making a file accessible to a mobile device from a computer is more or less common, even for non tech-savvy people. Understanding how to "upload" or "post" the file to a web application is trickier, because this is not so common. I believe most people are probably familiar with the image picker that is native to the OS, but not so much with the file picker. Also, it's possible your users already forgot the location they just saved the file to, and are now lost. Basically, your phone app does exactly the same as you had planned for a computer. It's just that people that are only accustomed to a phone probably hardly use the file system.

I'm that one old-schooler. However I find myself using simple and cheap streaming services more and more, especially as "radio" of favorite genre at home or in the car. What such users want it to look like, I guess : they locate a song in streaming app, press "Share" and send it to your app. On your side: 1 - I'm not sure a web app can register itself as Share receiver. Okay, you can require them to copy URL and paste into your app 2 - Getting a song from a service. If it has API, it's lucky case. However user still will have to enter his login once again as I doubt a service gives its songs to anonymous connections - all that copyright stuff. 3 - bonus item - remember that you do not own these tracks even if you bought them in iTunes/GMusic, you're just renting them. No usage besides listening on your devices with official client apps is allowed. Streaming services are even worse - you just buy the temporary ability to listen tracks that finishes when you end subscription. 4 - Well, now it's time to estimate how strongly you want this feature.

I first used interfaces via exported DLL functions. This was better than using many individual DLL functions, but still not very flexible. So I thought about how to implement the whole thing in a more general way. The result is this project. With AppCentral you can register interfaces in the host application or a DLL and get them in the host application or another DLL. The DLL can thereby also be written in C#, which is very practical, because you can connect various .NET libraries very well with Delphi. Example: Register an interface in Delphi type IAppDialogs = interface ['{EA3B37D8-5603-42A9-AC5D-5AC9C70E165C}'] procedure ShowMessage(const AMessage: WideString); safecall; end; TAppDialogs = class(TInterfacedObject, IAppDialogs) public procedure ShowMessage(const AMessage: WideString); safecall; end; implementation { TAppDialogs } procedure TAppDialogs.ShowMessage(const AMessage: WideString); begin Vcl.Dialogs.ShowMessage(AMessage); end; initialization TAppCentral.Reg<IAppDialogs>(TAppDialogs.Create); finalization TAppCentral.Unreg<IAppDialogs>; Fetch the interface in the host application or a DLL TAppCentral.Get<IAppDialogs>.ShowMessage('This is a message!'); // fetch directly, an exception will occur, if the interface is not registered yet Or in C# if (AppCentral.TryGet<IAppDialogs>(out IAppDialogs Dialogs)) { Dialogs.ShowMessage("Message from DLL: C# DLL registered!"); } The project can be downloaded here: https://github.com/jaenicke/appcentral Demo applications are included in source and in compiled form. I'll add a quick start manual soon.