Rollo62

Just try with GELATO to find out if its defined somewhere

Never say never. There are also a lot of local, free AI models around nowadays, keeping stuff private ....

Interesting approach. 👍 Don't you get then varying font sizes for each control, by differing MaxWidths? How do you control that there is a unique look-and-feel, do you use always the same width spaces for all components? Maybe you have some screenshots available, to get a better idea.

As explained above, define work top-down as compiletime, pretty much as the "defines" in C/C++. This is very useful since you can switch between certain code behaviour parts, include or not to compile, depending on a compiletime defined condition. //Can be used with DEFINED() in a more speaking, checkbox-like version {$DEFINE ___USE_THE_BO_VARIANT } {$DEFINE _X_USE_THE_MO_VARIANT } {$DEFINE ___USE_THE_ZO_VARIANT } FUNCTION DOTHERPORT; BEGIN {$ifDEF _X_USE_THE_BO_VARIANT} result :=DoCharges(true,-1,false,False,false,lg('CLOSE CHARGES'),'1',dm2.sysdate.fieldbyname('date').asdatetime) {$else} result := DoCharges(sender=Nil,-1,False,False,FALSE,lg(TDsFancyButton(Sender).Caption),'',0,dm2.sysdate.fieldbyname('date').asdatetime); {$endif} END; //Or maybe in mode complex scenarios, as switch/case-like option, like this FUNCTION DOTHERPORT2; BEGIN {$if DEFINED( _X_USE_THE_BO_VARIANT ) } result :=DoCharges(true,-1,false,False,false,lg('CLOSE CHARGES'),'1',dm2.sysdate.fieldbyname('date').asdatetime) {$elseif DEFINED( _X_USE_THE_MO_VARIANT ) } result := DoCharges(sender=Nil,-1,False,False,FALSE,lg(TDsFancyButton(Sender).Caption),'',0,dm2.sysdate.fieldbyname('date').asdatetime); {$elseif DEFINED( _X_USE_THE_ZO_VARIANT ) } result :=DoCharges(true,-1,false,False,false,lg('ZOOOO'),'1',dm2.sysdate.fieldbyname('date').asdatetime) {$else } result :=DoCharges(true,-1,false,False,false,lg('NOTHING ELSE MATTERS'),'1',dm2.sysdate.fieldbyname('date').asdatetime) {$endif} END;

I was curious how far you can get with the newer System.Net.HttpClient, System.Net.HttpClientComponent, System.Net.URLClient. It seems quite limited, perhaps the good old Indy might have more tricks up its sleeve. TNetHTTPClient TRESTClient and friends are not so verbose in regards of internal stream data. Perhaps a combination of both can get more insights about the underlying data streams? T526_RestDebug_002.zip

Have seen it, but never checked it out before. Its on my ToDo list now

Not that it solves your RestDebugger but, but there is also a nice tool Bruno, which might help to dig deeper. https://www.usebruno.com/

Nice demo. 👍 Perhaps you forgot to mention that its available on GetIt https://getitnow.embarcadero.com/delphi-yolo-onnx-runtime-wrapper/ and on GitHub https://github.com/SoftacomCompany/Delphi-YOLO-ONNX-RuntimeWrapper and Medium https://medium.com/@softacom.com/object-detection-in-delphi-with-onnx-runtime-2b1e28b0e1b3

I could think of maybe parsing and replacing somehow, or edit manually at least in an easier editing system than InDesign. Im not an InDesign user, but my impression is that using InDesign as-is is a pain-in-the-.... in the first place. Maybe I'm wrong, but its not something I would love to use on a daily base.

But thats not always what it is. It may be a signal word, it may be a warning sign, which is crucial to the user in user manuals. https://www.kothes.com/en/blog/creating-safety-and-warning-notices-with-the-safe-method Ok, those can be maybe set in their local language, but sometimes these icons were not repeated in each language. Thats hard to keep on track, if you have 8000 of those entries in hundrets of files. Our artwork department will be working on that alone for half a year, updating the current/older documents. I think the best way is to keep as-is and to provide a second channel of those documents, e.g. by HTML, where it will be possible to somehow auto-translate and fill those elements.

Yes, that is some messy stuff, the icons. What I do, to avoid getting even more messy: - I made a 1:1 copy of the original Embarcadero artwork from /bin/artwork/... into a local folder to my project - This ensure that I use the same filenames as Embarcadero did, if I forget one or some changes in new versions, there is always the fallback to the Emba Icon - Then I redirect the folders ( not the filenames ) of the Icons dialog, to link to my local folder ( this can be done by search/replace in *.dproj too, if you do carefully ). - Then you might change the icons accordingly to your design, keep all dimensions, file-names, file-formats, etc., just relace the image to your design - After that, your app takes the new images (perhaps you have to de-install/re-install) the app, to make it happen. That way you don't have to fumble around with deployment at all, if its only about the original Embarcadero App Icons. You just trick the IDE to replace the original artwork by your, without even add more and more messy filenames.

Even worse than that, I ask myself what happens with internationalizations? We have PDF with 27 languages in one file. How is internationalization regulated there, are there certain regulations and best practices? What I mean is, for example, an alternative text for images, for screen readers. https://www.w3.org/TR/WCAG20-TECHS/PDF1.html We sometimes have documents in 27 languages, usually with one image per language, which could be tagged internationally, which is an enourmous workload. However, there are always many images that apply directly to many languages, in the worst case for 27 languages, what measures should the alternative texts and tags be given there? It makes no sense at all to put 27 translations in one tag. Alternatively, it would be conceivable to only ever add EN as a fallback, but this would also contradict the fact that all documents should be available in all national languages in each EU country. Such EN fallback would not be OK according to WCAG 3.1.2 or EN 301 549. How could such cases be handled sensibly? Yes, the right answer is, re-structure the whole document, which also would blow up the size tremendously. Since the files are also for printed user manuals, it would mean we have to have much more size and paper waste. No matter what you do, you cannot meet all the EU regulations, because they were highly contradicing in so many single topics, best method, close your eyes and wait until you get sued Of course, the more you try to regulate, the more it gets into over-complexity and finally the opposite of the original intention. At least HTML has maybe solutions to that, even though not very easy to use: <picture><source srcset="banner-de.svg" lang="de"> … <img alt="Standort Berlin" …></picture> or you denfine, thats its a language neutral role, which would work in the least of all cases, IMHO. html <img src="check.svg" alt="" role="presentation"> My conclusion: You cannnot meet all requirements: A11y, L18n, EcoDesign( saving Paper), EUDR (do not de-forest), GPSR, User manual design (warning icons), etc. etc., but you can freely choose which regulation you would like to violate the most. Are there any other fresh ideas about these topics? I cannot believe that we are the only ones looking into this mess.

What I wanted to say is, that even for SameValue(Value), you have to consider the Epsilon. Only because its some kind of default, it doesn't make it better, you should better know it and deal with it. https://docwiki.embarcadero.com/Libraries/Athens/en/System.Math.SameValue What exactly is reasonable and whats not, depends on the use case, like you perfectly said. Thats why I would argue, that you always shall consider it (and better set it to make it visible to the outside too). I prefer to pre-set Epsilon always by myself, to the desired value, instead of any automatic and maybe unexpectedly changing behaviour from internal structures. This is only calling for unwanted sideeffects. All this might be true, but is very scientific. Unless I cannot see a real benefit, I will stay with my decimal Epsilon, perhaps only in deeper Physics we would need different perspectives than 10^-3, ... 10^-15 or so.

Yes, I completely get that point. Only I'm unsure in which cases this would really make sense. Usually I know my workroom, where I expect my variable to sit in. If you don't know that and you really want to switch tolerances, then I'm not really sure why. That would mean a 1^3 will get the tolerance of 1.0, a 1^6 might get a tolerance of 1000.0, for example. So what happens when you multiply two number, do you really want to re-calculate the tolerances too? Ok, in more complex calculations it should be enough to calculate the tolerance at the very end, according to the result value. Instead of putting such overhead to an "adaptive" functionality, I would rather put more overhead into statistics, to achive mean and std deviation, which are much more useful to me. I must confess, that I did such "adaptive" tolerance too, in some projects, but when using statistics for getting more insights of data, this was always much more useful to me. Nevertheless, maybe there are good reasons for adaptive tolerances too, only its already late today and I cannot find a real use case at the moment. 🤔 The only two reasons I could see for now, are for display clearance of the last digits, or if you want to convert the real numbers into integers then afterwards, to keep their last digits clean .

I think always in tolerances, when it comes to real numbers, because thats what the real numbers were all about, IMHO. Perhaps, I'm a little biased by handling with measurement technology too much ... Not sure what you mean by "adaptive" here, but what comes to my thought is statistics then, which directly follows the real numbers tolerances.