Noutați

11 Ways to Fully Revamp Your Low Code Application Platform

In business, a low code application platform describes software that allows users to create or customize applications without writing code. Low Code Application Platform is becoming increasingly popular as companies strive to speed up application development and achieve digital transformation. However, simply using low code alone is not enough to guarantee success. This article will show you 11 ways to completely revamp your low code application platform and make it even more effective! The low code application platform has evolved significantly Over the last few years, there has been a significant shift in software development. Low code development platforms are becoming increasingly popular as they allow developers to create applications without writing large amounts of code. There are many reasons for this shift. Firstly, low code platforms are much faster to develop than traditional platforms. This is because developers can drag and drop various elements to create an application rather than having to write code from scratch. This means that applications can be completed in a fraction of the time they take on a traditional platform. Secondly, low code platforms are much more user-friendly than traditional platforms. This is because they don’t require developers to have a deep understanding of coding languages. This makes them ideal for businesses who want to create their own applications but don’t have the time or resources to invest in training their employees in programming languages and technologies. Finally, low code platforms are much more flexible than traditional platforms. This is because they allow businesses to customize their applications to suit their specific needs easily. This flexibility is critical for companies that want to adapt their applications as their business changes and grows. RAD Studio Over the Years – Get the latest version of RAD Studio 11.1 Alexandria right now! How to get the best out of a low code application platform 1. Out with the old If you’re looking to revamp your low code application platform completely, the first step is getting rid of the old. This means any outdated applications, hardware, or software are no longer used. Getting rid of these things will help declutter your system and make it easier to manage. 2. In with the new Once you’ve gotten rid of the old, it’s time to bring in the new. This includes new applications, hardware, and software that can help improve your system. Be sure to do your research and choose things that will work well with your existing system.  3. Keep it organized After making all of your changes, it’s essential to keep your system organized. This will help you keep track of everything and ensure nothing gets lost. Create a file system or use a project management tool to help you stay on top of things. 4. Test everything Test everything out before launching your new and improved low code application platform. This includes testing applications, hardware, and software to ensure they work together correctly. Once everything is up and running, you can enjoy your new system! Revamp your low code application platform and breathe life into your apps with minimal effort 1. In with the new If you want to revamp your low code application platform completely, the first step is to get rid of the old. That means any outdated software, hardware, or anything else that’s no […]

Read More

Everything You Need To Know About the New RAD Studio 11.1 Alexandria Update

Rad Studio 11.0 Alexandria was strategically released last September, just a month before the release of Windows 11. It provides a great number of features including the High DPI IDE support, VCL Styles in the Form Designer, and Android API 30 support to name a few. Interestingly, a new update was released a few months ago, providing many notable IDE improvements and other new functionalities that are absolutely beneficial to Windows application development. Coinciding the release of RAD Studio 11.1 is a launch webinar hosted by Jim McKeeth and other Embarcadero MVPs such as Marco Cantu, Kyle Wheeler, David Millington, and Stephen Ball. What’s new with RAD Studio 11.1 Alexandria? The primary focus of RAD Studio 11.1 is to enhance all the great features that are already present in the RAD Studio 11. The update also provides a focus on usability, performance, and stability improvements. It also includes some new functionalities, including new database drivers. RAD Studio 11.1 features many IDE Improvements including the extensive High DPI IDE quality and the improved use of the IDE with Remote Desktop. The update also provides improvements in toolbar font sizing, better scaling when dragging windows between different resolution monitors, and additional IDE fix pack integration. It also features improved high DPI designers for both VCL, FireMonkey, and the styled VCL form designer. There are also notable GetIt Library Manager enhancements and other new IDE features such as the Messages View, New Items and Compile Dialog boxes and more. Another significant quality focus area of RAD Studio 11.1 is Code Insight for both languages, Delphi and C++ Builder. There is also a big performance improvement in Delphi LSP Engine. The new update also provides notable improvements with Delphi and C++ Builder’s Compilers and debuggers. It includes additional support for ASLR and an introduction to new Delphi debugging technology based on LLDB. Delphi RTL also had several optimizations and quality improvements in the new RAD Studio update. Additionally, the RAD Studio 11.1 release offers official support to operating systems released after 11.0 shipped: Windows 11, macOS 12 Monterey, iOS 15, and Android 12. In case you missed the recently held RAD Studio 11.1 Alexandria Launch Webinar, feel free to watch the video below.   

Read More

Extend TMS WEB Core with JS Libraries with Andrew: CodeMirror

Do you want to display or edit code directly within your TMS WEB Core application? Then this is the post for you.  This time out, we’re diving head-first into CodeMirror 5, which describes itself as “a versatile text editor implemented in JavaScript for the browser.”  Which it certainly is.  Beyond just being a text editor, it is natively aware of more than 100 different programming languages.  Beyond that, it has numerous add-ons and configurable options to mimic the many styles and conventions of other editors you might already be familiar with, like Vim, Emacs, and so on. And using it in a TMS WEB Core project is just as easy as any of the other JS libraries we’ve covered so far. Motivation. Why do we need a code editor at all? The very first benefit of a code editor, as compared to a simple text editor or an editable TWebMemo field, for example, is that it typically comes with syntax-highlighting that is configured for the programming language that you’re editing. For Pascal, this means that begin and end are automatically shown in a different color, as well as any other Pascal-related reserved keywords.  This also typically means that the various kinds of brackets are shown in a way that makes it easy to find the matching pairs of brackets, or that comments show up in a different color or style.  Might not seem like much, but if you’ve ever tried writing code without this, it is a very different experience. Of course, you’re likely very familiar with this kind of thing, as the Delphi IDE does exactly this (and much, much more!) when editing code.   Sometimes it is even helpful to display other text using this kind of mechanism, if for no reason other than to make it a little nicer to look at.  If you have log files that are potentially visible to your users, for example, they can be setup so that they are viewed through CodeMirror.  Perhaps set to something like SQL (my personal preference) will make the log files a little easier to read, depending on how they’ve been formatted, with dates and numbers and other things displayed potentially in a different color.  Or perhaps you want to display text that has line numbers beside it.  Or perhaps the most common of all, you want to edit HTML source and have the tags shown in a different color.  We’ll be taking a look at both Summernote and SunEditor in an upcoming post, both of which use CodeMirror to provide their “edit HTML source” functionality. CodeMirror 5 vs. CodeMirror 6. Before we get any further, let’s quickly sort this out.  Normally I’m 100% all-in when it comes to using the leading (bleeding) edge of any particular JS Library, with the thought that it will likely have the best support for the latest browsers and the most active development efforts, as compared to older versions of the same library.  And this does indeed apply here as well.  However, they’re a little too far out on the leading edge at the moment.  So far out that CodeMirror 6 is really a collection of modules that cannot be directly (perhaps easily would be more accurate) loaded into a web application, as we’ve been doing.  Instead, the various modules and their […]

Read More

In the TMS lab with our students

Hello world!  You might have been used to see and read Stephanie in past posts, but today it’s time to introduce a new face! I’m Emmanuel, the internship Marketing and communication since 25th of January. My goal in this internship is to learn about the marketing side of development world, as well as creating video-, photo- and audio content for social media channels. In this blogpost we will discuss a new application that Stephanie created as internship project. The app in question is a navigation system that is based on FNC components. Before going further into it, I would like to discuss my journey within the development world as a Marketing student. It is quite important to know that I have little to no experience with coding, and that most of the components and code languages discussed in this video are mostly unknown to me. Which means that the experiences and point of view expressed could be different and less educated than most. My point of view, in some situations, is handful for having a full user perspective on the software that is being created. Sometimes a developer can create or design tools that might seem easy to them but isn’t really for the regular customer. It happens sometimes that I’m a first tester of a software that Stephanie creates. I, for example, helped her with the French language for the navigation software, as I am a native speaker. My first usage of the app also gave us path to new bugs, which were immediately patched. It feels good to know that even with no understanding of the coding world, one can still help in other ways.  My main task within the navigation app was to create a video for a quick demo of the finished application. There are a few steps to get done before starting with the video editing, which are: Introduction and learning of the software functionalities Agreement on what should be demoed Shooting and creating content + directing the present persons And afterwards starts the video-editing part, which isn’t a walk in the park! In the video, that was created in iMovie, you can also hear and see me for the French tutorial. Emmanuel Dernoncourt, Intern Marketing 

Read More

TMS FNC Chart: update with Types, Appearance and CSV Loading

Version 2.0 of the TMS FNC Chart is available. This major release brings a lot of new features.Most of them are related to quickly get the chart that you want with just a couple lines of code. An overview of the features that were implemented: Chart type specific sub classes Appearance: with the color scheme and global font Load From CSV Load From Array Load From JSON Database Adapter Grid Adapter In this blogpost we will elaborate on the first three features mentioned in the list. The others will be addressed in a follow-up blogpost. Holger has created a great video, where he combines some of the new features in a simple application.With just one line of code, he loads a CSV file in a bar chart.  Chart Type Specific Sub Classes A lot of new components were added to the package, these are all instances of the TTMSFNCChart each with a different chart type set as default. This way you can immediately start working with a bar chart (or any other) without the need to change the type of the series. Appearance You can easily set the overall look of the chart with the new Appearance property. This property currently exist of two larger parts. The color scheme can be set with a list of predefined colors, you can use the default Excel colors or you can get different shades of a selected color. The other one is the GlobalFont. This property gives you the ability to set all the fonts of the chart with one setting.You can change the size, font name, color and/or style and you can keep the proportions of all the fonts and just scale them a little bigger or smaller. Load From CSV Different ways were added to load data from a file, stream or text. And those will be further explained in some upcoming blogposts.But now we will focus on the LoadFromCSV method.This method will take the indices of the different columns that you want to use. For some parameters these are arrays of integer, that way you can create multiple series in one call. Another new property in the chart is the DefaultLoadOptions, with this property you can choose how series will be added/updated when using some kind of data loading. If you want to deviate from the defaults for one csv you can add an instance of the TTMSFNCChartLoadOptions that you’ve created to the parameters of the LoadFromCSV call. This was added because we want to be as flexible as possible. And in that regard we’ve made three different ways to add different types of data. First you have the short method: TMSFNCChart.LoadFromCSVData(myFile.csv, [1,2], -1, 0); //Parameter 1: my file, stream or text variable. //Parameter 2: Array of Integer that are mapped on the y-values. A Series will be created for each value. //Parameter 3: The x-values that you can use, as this is -1 they are skipped while loading. //Parameter 4: The index for the column that uses the labels shown on the x-axis. If not set this is -1 and skipped. A more detailed procedure that takes the second or variable values: TMSFNCChart.LoadFromCSVDataEx(myCSVStream, myLoadOptions, [1,3], -1, 0, nil, [2,4]); //Parameter 1: my file, stream or text variable. //Parameter 2: Optional load options, if not define the DefaultLoadOptions are used. […]

Read More

Profiling in Unity 2021 LTS: What, when, and how

Profiling is like detective work, unraveling the mysteries of why performance in your application is lagging, or why code is allocating excess memory. Profiling tools ultimately help you understand what’s going on “under the hood” of your Unity project. But don’t wait for significant performance problems to start showing before digging into your detective toolbox. The best gains from profiling are made when you plan early on in your project’s development lifecycle, rather than just before you are about to ship your game. It’s an ongoing, proactive, and iterative process. By profiling early and often, you and your team can understand and establish a “performance signature” for the project. If performance takes a nosedive, for instance, you’ll be able to easily spot when things go wrong, and quickly remedy the issue. You can also make before-and-after performance comparisons in smaller chunks by using a simple three-point procedure: First, establish a baseline by profiling before you make major changes. Next, profile during the development to track performance and budgeting, and finally, profile after the changes have been implemented to verify whether they had the desired effect. You should aim to profile a development build of your game, rather than profiling it from within the Unity Editor. There are two reasons for this: The data on performance and memory usage from standalone development builds is much more accurate compared to results from profiling a game in-Editor. This is due to the Profiler window recording data from the Editor itself, which can skew the results. Some performance problems will only appear when the game is running on its target hardware or operating systems, which you’ll miss if you profile exclusively in-Editor.

Read More

We’re back! Join us at the Annecy International Animation Festival 2022

Friday, June 17, 10:00–10:45 am XR for large-scale live events: A TED 2022 case study Sinan AlRubaye, Chief Experience Officer, ICVR Chris Swiatek, Chief of Product, ICVR Cassandra Rosenthal, cofounder and co-CEO, Kaleidoco Particle Ink: Speed of Dark is an immersive mixed reality experience combining street art, live performances, and XR technology. It transports the viewer into a living graphic novel using the Unity real-time 3D development platform with a mix of projection mapping and live broadcast.  Conceived by creatives from Cirque du Soleil, during the inaugural TED Talk of 2022, ICVR brought the live XR immersive experience to the 1,100-strong audience, each with one with synchronized iPads. Here, we will break down the tech behind Kaleidoco’s reveal of the Particle Ink world at the TED 2022 opening show, and discuss the future of live XR. 

Read More

Why Should You Spend More Time Thinking About Cross Platform Development?

In the last few years, cross platform development has taken the front seat. It lets developers write code once and implement it across all platforms.   Native app development requires different code for different platforms. It also requires Android Studio as an IDE and a suitable SDK. However, cross platform development frameworks need a single Codebase. It can compile builds for iOS and Android.  There is no need to develop applications from scratch for all platforms. Developers can save time with a low code platform. There are various tools for this purpose. These include RAD Studio, Delphi, and C++ Builder. These tools help you develop applications faster with one codebase. It works for Android, iOS, Windows, Linux, and macOS. What is cross platform Application development? The term cross platform development is also called hybrid app development. It’s an approach to building apps compatible with different platforms. Developers write code once and reuse it. It lets them release a product quickly.  For cross platform development, use intermediate programming languages. These include HTML, CSS, and JavaScript. These languages are not native to operating systems and devices. Developers package the applications into native containers. Then they integrate them into platforms. There are some fundamental strategies for using cross platform development. These include: Compiling different versions of the same program for different OS. Make a program abstract to accommodate different environments. Use of sub-tree files to fit the product to different operating systems. What is the difference between native and cross platform development? Native applications rely on native technologies. Developers can deploy native technologies to their native devices. Cross platform development offers multi-platform compatibility.  The hassle increased while using native app development. Because you need to build two separate apps for Android and iOS. However, these apps appear similar in functionality. But they need different codebases. It is required to accommodate the need for native app development.  What are the Advantages of using cross platform development? These are some advantages of using cross platform applications. 1. Cross platform development should allow you to reuse the code components Despite using new code for each platform, reuse the same code. It lets developers release products faster across all platforms. It also reduces the effort of doing repetitive tasks. You can develop features for Android and iOS with a single codebase. As a result, cross platform development optimizes efficiency. However, it’s not completely a new concept. But it’s been used in software development for years. The software industry gets benefits from reusing code with this technique. 2. A good cross platform development solution reduces overall cost Businesses are embracing different advanced strategies. But not everyone can afford to build native applications. Mobile apps help businesses deliver a personalized experience. Cross platform development helps businesses reduce the overall cost. They can build applications for distinct platforms efficiently. The approach works great for corporate products that are less profitable. Companies can save costs by developing a universal solution. 3. Implementation with the right apps builder software should be easy There are various tools like RAD Studio offering cross platform solutions. This makes it easier for developers to do adjustments. For instance, tools like RAD Studio offer a single-codebase framework. For instance, you can write code in HTML. And then modify it for different operating systems. It makes the implementation of […]

Read More

The Pros And Cons Of Low Code App Development Platforms

You know a lot about low code app development if you follow us. The beginner’s guide was the initial tutorial/article about low-code platforms. In that article, we have explored and learnt new things about no-code platforms in certain ways. If you have not read that article, here you can see what you can learn from it: No-Code Movement Differences between Low-Code Platforms Why Low-Code Tools Matter? When Should You Not Utilize Low-Code Developer Tools? Low-Code and Traditional Engineering Just check out the article here: Additionally, this article called 20 Fun Facts About The Best Low Code Platforms is helpful to really understand what is happening in the low code app development industry and other facts, for instance: Future of the Low-code Market? How and Where to Apply Low-Code Platforms Facts with Numbers related to Low-Code Industry Top Tech Companies’ Approach to Low-Code Tools and more Here go check out the article here: Now you have the resources to learn about all the necessary things, and directly we can be fully involved in the pros and cons of low-code app development platforms. As per Gartner, the clamour for application development is expanding five times faster than IT’s ability to meet it. Business owners request more web applications, and IT departments struggle to keep up. Since developing apps and software services from the ground up to take time and demands higher engineering, which also costs money, business owners are handing these problems to low-code developers. Low-code app development is fast and pretty much cheaper than traditional software development.  Moreover, Low-code development tools do not require deep coding or complex problem-solving abilities from the developer. These platforms provide you with dozens or hundreds of built-in components and functionalities that you can build service by building blocks. But using low-code or no-code platforms do have its drawbacks. Does low code mean low security? If you apply low-code development tools without IT’s knowledge, you do not know about security-first software. When you create apps with low-code platforms, you do not see any code, and you cannot alter the source code to make the process or transaction more secure. Additionally, you do not know how the source code is produced while you are developing by putting blocks of functions together. Of course, there is always a better ecosystem to develop secure and cross-platform native applications. For instance, Delphi with FireMonkey framework provides traditional and low code software development. The best thing is to mix those and create compelling applications in no time and target multiple platforms with a single code base.  FireMonkey framework is one of the best cross-platform and stable frameworks for any use: Business Apps Game Development 2D & 3D Development Utility applications to talk with hardware-specific functionalities Mobile, Web, and Desktop, all you need is here Huge third-party component pool to optimize the development process Thousands of hours of official workshops by experts to learn It doesn’t matter how stunning the looks are if the user experience is sluggish or unresponsive. On PCs, tablets, and mobile devices, FireMonkey-powered applications take full advantage of today’s hardware with native CPU performance and GPU-powered visuals. Do low code platforms produce solutions more quickly than other alternatives? As we said earlier, a low-code platform provides you with all the available building blocks for you, and you need […]

Read More

Terraform as part of the software supply chain, Part 1 – Modules and Providers

When talking about Terraform security, there are many resources covering the security aspects of the infrastructure surrounding certain Terraform configurations. Looking at the security of Terraform itself and the things which could go wrong when running it, however, have very little coverage so far. Some previously published work I’m aware of includes: “Terraform providers and modules used in your Terraform configuration will have full access to the variables and Terraform state within a workspace. Terraform Cloud cannot prevent malicious providers and modules from exfiltrating this sensitive data. We recommend only using trusted modules and providers within your Terraform configuration.” The blog post you’re reading is part one of a three-part series examining the supply chain aspects of Terraform and aims to look at malicious Terraform modules and providers. I’ll also give recommendations on securing the process of running Terraform against modules and providers gone rogue. The next two blogs in the series will build upon these findings and cover more in-depth topics and vulnerabilities. Provider security Providers in Terraform are executable binaries, so if a provider turns malicious it’s certainly “game over” in the sense that it can do whatever the host OS it runs on allows. Providers need to have a signature which gets validated by Terraform upon installation of the Provider. Version 0.14 Terraform creates a dependency lock file which records checksums of the used providers in two different formats. zh and h1 checksums The first format, zh, is simply a SHA256 hash of the zip file which contains a provider for a specific OS/hardware platform combination. The h1 hash is a so-called “dirhash” of the provider’s directory. So if we look at the following lock file .terraform.lock.hcl we can observe the two different types of hashes: # This file is maintained automatically by “terraform init”. # Manual edits may be lost in future updates. provider “registry.terraform.io/hashicorp/aws” {  version = “4.11.0”  hashes = [    “h1:JTgGUEVVuuv82X0ePjDM73f+ZM+NfLwb/GGNAOM0CdE=”,    “zh:3e4634f4babcef402160ffb97f9f37e3e781313ceb7b7858fe4b7fc0e2e33e99”,    “zh:3ff647aa88e71419480e3f51a4b40e3b0e2d66482bea97c0b4e75f37aa5ad1f1”,    “zh:4680d16fbb85663034dc3677b402e9e78ab1d4040dd80603052817a96ec08911”,    “zh:5190d03f43f7ad56dae0a7f0441a0f5b2590f42f6e07a724fe11dd50c42a12e4”,    “zh:622426fcdbb927e7c198fe4b890a01a5aa312e462cd82ae1e302186eeac1d071”,    “zh:9b12af85486a96aedd8d7984b0ff811a4b42e3d88dad1a3fb4c0b580d04fa425”,    “zh:b0b766a835c79f8dd58b93d25df8f37749f33cca2297ac088d402d718baddd9c”,    “zh:b293cf26a02992b2167ed3f63711dc01221c4a5e2984b6c7c0c04a6155ab0526”,    “zh:ca8e1f5c58fc838edb5fe7528aec3f2fcbaeabf808add0f401aee5073b61f17f”,    “zh:e0d2ad2767c0134841d52394d180f8f3315c238949c8d11be39a214630e8d50e”,    “zh:ece0d11c35a8537b662287e00af4d27a27eb9558353b133674af90ec11c818d3”,    “zh:f7e1cd07ae883d3be01942dc2b0d516b9736a74e6037287ab19f616725c8f7e8”,  ] } The zh entries can also be found in the provider’s v.4.11.0 release within the SHA256SUMS file. To understand the single h1 dirhash entry we need to have a look at the provider’s directory. In our Terraform project it is constructed like this: $ ls .terraform/providers/registry.terraform.io/hashicorp/aws/4.11.0/linux_amd64/                                    terraform-provider-aws_v4.11.0_x5 $ cd .terraform/providers/registry.terraform.io/hashicorp/aws/4.11.0/linux_amd64/ $ sha256sum terraform-provider-aws_v4.11.0_x5 34c03613d15861d492c2d826c251580c58de232be6e50066cb0a0bb8c87b48de  terraform-provider-aws_v4.11.0_x5 $ sha256sum terraform-provider-aws_v4.11.0_x5 > /tmp/dirhash $ sha256sum /tmp/dirhash   253806504555baebfcd97d1e3e30ccef77fe64cf8d7cbc1bfc618d00e33409d1  /tmp/dirhash $ echo 253806504555baebfcd97d1e3e30ccef77fe64cf8d7cbc1bfc618d00e33409d1 | ruby -rbase64 -e ‘puts Base64.encode64 [STDIN.read.chomp].pack(“H*”)’ JTgGUEVVuuv82X0ePjDM73f+ZM+NfLwb/GGNAOM0CdE= The dirhash, called h1 in the lock file, is created from an alphabetical list of sha256sum filename. Once this list is sha256sum ed again, the resulting hash is taken in binary representation and then converted to Base64. From an attacker’s perspective, the interesting part about the lock file is that it can contain multiple zh and h1 hashes per provider. It is also noteworthy that those two types don’t have to have any relationship. If we modify a downloaded provider’s content on disk, we can simply place the corresponding h1 hash next to any other h1 in the lock file. As there can be multiple entries we would not break any legitimate installation and just allow-list a modified provider directory on-disk on top of what’s already allowed. Lessons learned here Put your .terraform.lock.hcl under version control (Terraform even suggests this on the […]

Read More