Leaderboard

"Paying the piper" comes to mind. They cut R&D too deeply and will suffer the consequences. Sometimes you have to tell the money people NO. You always need someone on staff that has the cojonnes or influence to do the right thing versus the least expensive thing.

https://community.idera.com/developer-tools/b/blog/posts/august-2019-delphi-android-beta-plans-august-roadmap-update Here’s what’s planned for 10.3.3: Platform Enhancements iOS 13 & macOS Catalina Support RAD Server Deployment with Docker C++ Expand C++ libraries support Delphi Android 64-bit platform support User Experience Further IDE UI/UX Improvements New Downloads/Licensing Portal Quality Focus Areas App Tethering for VCL and FMX IDE Quality C++ Toolchain performance and quality improvements With the addition of 10.3.3 this fall, we’re now planning the 10.4 release for early in 2020. As outlined in our May 2019 PM roadmap commentary blog post, 10.4 is going to focus on improved code tooling, language enhancements, VCL High DPI styles, RAD Server enhancements, FireMonkey features and quality and more.

Update: I have now completed a massive set of minor changes, affecting over 1400 units. Removed all units from uses clauses which were not needed, and demoted from interface to implementation, where possible. The other change was to add a module to manage unit initialization, rather than leaving that to Delphi. All initialization and finalization clauses have been replaced by procedures. That should leave us less susceptible to sequence issues as we continue to resolve the coupling issues. In the process, also reduced by about 25% the unit dependency cycles identified by MMX. And in my VM on an SSD, the time for a first full build after loading the IDE dropped from nearly 4 minutes to about 40 seconds. Progress.

Here is the patch for 1435 revision: ics-CB2009-fix-1435-ALL.patch

https://community.idera.com/developer-tools/b/blog/posts/august-2019-delphi-android-beta-plans-august-roadmap-update As a follow-up to our 10.3.2 release that introduced macOS 64-bit support for Delphi, C++17 for Windows 64-bit, new RAD Server tooling, key quality enhancements (addressing 400 customer requests) and more, we are planning a 10.3.3 release, with Delphi Android 64-bit being the key new platform feature. We received many requests for Android 64-bit from our customers and a 10.3.3 release allows us to deliver this speedily and with full compatibility with apps and code developed in 10.3.2. Given there is no significant change to the Delphi language and the underlying memory management model in 10.3.3, our customers should be able to migrate their applications to Android 64-bit faster. The same is likely true for component vendors. While we still plan to transition the Delphi language for mobile, removing ARC memory management, this will happen at a later time. As 10.3.2 adoption is high, upgrading to 10.3.3 should be a faster option than migrating applications to 10.4. 10.3.3 will also include additional features and quality improvements to make 10.3.3 one of RAD Studio’s best versions. Please keep in mind that the Google Play Store extension for our Delphi and C++Builder customers is in effect for existing 32-bit applications. This allows our customers to provide updates to existing applications in the Google Play Store applications until August 2020, but only after an extension has been granted. 10.3.3 will remove this limitation for Delphi by including complete support for Android 64-bit apps. We’re planning on kicking off an NDA Beta for the 10.3.3 release, codenamed Sugarloaf, later this month. All customers on Update Subscription will be invited to participate in the Beta and will be able to start migrating their applications even earlier with Beta versions, which will include a specific Beta EULA waiver permitting Google Play Store deployment. Here’s what’s planned for 10.3.3: Platform Enhancements iOS 13 & macOS Catalina Support RAD Server Deployment with Docker C++ Expand C++ libraries support Delphi Android 64-bit platform support User Experience Further IDE UI/UX Improvements New Downloads/Licensing Portal Quality Focus Areas App Tethering for VCL and FMX IDE Quality C++ Toolchain performance and quality improvements With the addition of 10.3.3 this fall, we’re now planning the 10.4 release for early in 2020. As outlined in our May 2019 PM roadmap commentary blog post, 10.4 is going to focus on improved code tooling, language enhancements, VCL High DPI styles, RAD Server enhancements, FireMonkey features and quality and more.

I prefer regular Json as defined by Ecmascript ES5 / https://json.org When exchanging data, I prefer rigid formats over flexible formats.

Yeah, seems pointless. Use YAML if you want more readable files.

I update my code from uri := StrToJURI('file://' + AURI); to: LUri := TAndroidHelper.JFileToJURI(TJFile.JavaClass.init(StringToJString(AFileName))); and it works. Thanks Dave.

The list of known classes is built from parsing the project files (if checked) and the files opened in the editor (at least once when Persistent Module Information is checked). F.i. to add TInterfacedObjectEx to the known types list, the unit Spring.pas either has to be included in the project or opened in the editor so that MMX can parse the source. The parsed modules with the types declared are stored per IDE and MMX version in %LOCALAPPDATA%\Raabe Software\MMX Code Explorer\15.0\BDS20_known_modules.xml (for MMX15 in Delphi Rio). You can inspect that file for the missing type identifiers.

Indeed, that would be better.

This works for 10.3.x if you have some kind of PDF viewer installed on the device: uses Androidapi.JNI.GraphicsContentViewText, Androidapi.Helpers, Androidapi.JNI.Net; procedure OpenPDF(const AFileName: string); var LIntent: JIntent; LUri: Jnet_Uri; begin LUri := TAndroidHelper.JFileToJURI(TJFile.JavaClass.init(StringToJString(AFileName))); LIntent := TJIntent.JavaClass.init(TJIntent.JavaClass.ACTION_VIEW); LIntent.setDataAndType(LUri, StringToJString('application/pdf')); LIntent.setFlags(TJIntent.JavaClass.FLAG_GRANT_READ_URI_PERMISSION); TAndroidHelper.Activity.startActivity(LIntent); end;