Soluții | Page 60 of 194 | Dimensional Data

From the blog

May 14, 2022

How To Save Money On Cross-Platform Development Frameworks

Delphi

Are you considering developing a mobile application? Your thoughts immediately turn to native app development. Still, before you decide, it is critical to understand that native apps are designed for something like a specific platform, such as iOS or Android, with a different codebase. Cross-platform apps, on the other hand, can target multiple platforms with a single codebase. Here in this brief article, you will learn about how to save money on cross-platform development frameworks. Because of the numerous advantages of having apps which can work on multiple devices – both desktop and mobile, developers worldwide embrace cross-platform app development. Today, there’s a great choice of frameworks to allow developers to create apps for multiple platforms using shared code to reduce the amount of additional work needed to address the differences the devices may have. In this article we explore what we mean by the term cross platform development and how we go about creating apps that can work for our users no matter what their choice of target whether it be desktop or mobile. What is cross-platform development? Software that can run on multiple devices and operating systems can be an example of a cross-platform application. Moreover, as a developer, you can define cross-platform apps by building a cross-platform app out of the same source code without changing so much on the core. For instance, Delphi provides a cross-platform development ecosystem with its set of tools and libraries. The FireMonkey framework is the core tool for creating cross-platform and native applications using the same code. by Adding FMXLinux you can deploy to Linux powered platforms and also create Web Apps FireMonkey framework is one of the leading visual frameworks for creating cross-platform apps. Its architecture lets you create high-performance and secure applications. Screenshot of a Game built with Delphi – RAD Studio Do you really need to use a cross-platform development framework? Not all cross-platform development tools provide you with the best experience when creating it or a great user experience for the users. Because cross-platform applications utilize layers of abstraction to make the thing work and sometimes you might not get the true native app feeling. For instance, apps built with hybrid technology or web technologies do not provide security over your product. Furthermore, there may be a problem when accessing hardware functionalities. Nevertheless, Delphi, with its promising FireMonkey framework, is the solution for all. With FireMonkey visual framework and Delphi IDE, you can design GUI apps in no time and build/deploy them to Windows, macOS, Android, iOS and Linux devices quickly. Moreover, you can access any device or the operating system feature with built-in helper functions. Microsoft also has a new technology called MAUI, which is similar to FireMonkey’s architecture. However, it is still in preview, and as you can see, FireMonkey has been in active development for more than a decade and is the most stable cross-platform visual framework. Create Multi-Device Native Application using a Single Code Base Are cross-platform frameworks the future of app development? This is no secret that most companies, primarily startups, choose cross-platform development frameworks to target several markets easily. That’s why we may say that these cross-platform frameworks are in demand, and over the years, it has shown that cross-platform app development can help reduce cost and engineering time dramatically. We can […]

May 13, 2022

Expanding the robotics toolbox: Physics changes in Unity 2022.1

Noutați

Rigidbody uses both interpolation and extrapolation to give an impression of smooth motion while simulating at a comparatively low frequency. Internally, this is implemented by calculating the transform poses every update. In the case of interpolation, the last two simulated poses are used to calculate a new transform pose for this frame. In the case of extrapolation, the last simulated pose and velocity are used instead. Since it is designed to be lightweight, however, we don’t communicate these poses back to the physics engine. The poses are only presented to the systems outside of physics (e.g., graphics and animation). Because of that, for instance, a raycast won’t detect a body at the interpolated pose. To keep physics from noticing the transform changes, the mechanism was to have a Physics.SyncTransforms() call each update right before pose write, followed by an internal method call to clear all transform updates for physics. That caused two classes of problems: If a scene has at least one interpolated body, all the transform changes to all the physics components were synced with the physics engine each update (even though they’re mostly needed once per FixedUpdate); and If a change was made to a transform that had a Rigidbody component with interpolation on it, interpolation for this object broke because the user-made transform change was propagated to the physics engine and effectively changed the last simulated pose (the pose is not stored separately – it’s just the pose that the physics engine uses currently). To address these problems, we updated the interpolation code so that it doesn’t need to sync all transforms for each frame. This change also improves performance; the new interpolation code runs faster than before (depending on the scene complexity).

May 13, 2022

How we run Red Team operations remotely

Noutați

At GitLab, our Red Team conducts security exercises that emulate real-world threats. This gives us an opportunity to assess and improve our ability to deal with cyber attacks. These types of exercises require a lot of planning, which is traditionally done by getting folks from multiple departments into the same room at the same time to discuss hypothetical scenarios and expected outcomes. Then, actually conducting the attacks and validating the detection/response capabilities is, once again, traditionally done by people who are physically sitting in the same space. Like many things at GitLab, we are not quite so traditional. Each member of our Red Team is separated from the others by a literal ocean, with about eight hours difference in local time between us. Our entire organization works remotely, and the various groups we need to involve in these exercises are spread across the world. We understand our approach is unique. However, more of the workforce is moving to remote work models, so we recently spent some time writing down what works for us when doing these types of complex exercises asynchronously across time zones. Keep reading to see what we came up with and how you can use it yourself. Take our 2022 DevSecOps survey and get a $10 gift card. Have your voice count! Defining an asynchronous workflow If there is one thing we’ve learned about working remotely, it’s that you need to write things down. In a traditional office, it’s possible to have a back-and-forth conversation in a matter of minutes. Conversations across time zones and departments, however, can take days when you’re not co-located. This is why we use our public handbook as a single source of truth for how we run the company and why we decided to use this same spot to document how our Red Team will work to propose, plan and execute operations. Purple Team process As you can see, we’ve broken down the process of “Purple Teaming” into nine unique stages. Each of these stages is supported with a GitLab issue template that clearly explains what must be completed in order to move to the next stage. At GitLab, we use the term “Purple Teaming” to describe an exercise where emulated attacks are done in the open: Everyone involved knows what the attack is, when it is coming, and exactly what techniques will be involved. When we perform more traditional “Red Team” exercises where stealth is involved, we use roughly the same process; only with less active participants. When we begin planning an operation, we open a new epic on gitlab.com. Inside that epic, we open nine new issues using the templates linked above. Everyone involved in the operation will have access to these issues, and everyone can clearly see what has been completed and what comes next. New Red Team issue While it may seem like a lot of stuffy process, this level of clarity and transparency gives us the freedom to focus more on the interesting work and less on figuring out who should be doing what next. Even better, the process is open source: Anyone with an idea for improvement can simply open a merge request to discuss. This includes you: We would love to hear from the community to continually improve this process. Dive deeper into our workflows […]

May 13, 2022

Biden administration accelerates software supply chain security expectations a year into Executive Order

Noutați

President Joe Biden last year on May 12th signed Executive Order 14028 “Improving the Nation’s Cybersecurity”, which called on public and private sector organizations to improve the nation’s cybersecurity with “bold change” and “significant investments”. “Incremental improvements will not give us the security we need,” the EO states. Since then, the administration has only increased the pressure on agencies, forcing them to take a hard look at their software supply chains and justify their application development decisions, including how they use open source code, test their code, and grant permissions. “The federal government has accelerated its expectations for software supply chain security compliance, yet some organizations are still trying to understand how to broadly and proactively protect their software development,” says Joel Krooswyk, Senior Manager of Solutions Architecture at GitLab. “Agencies and their vendors have been focused on policy management and role-based access, but the federal government wants to go deeper and know where code is coming from and how to better secure it. They are quickly moving down the supply chain.” The interest in the origins of software code stems from the complexity of cyberattacks such as that carried out on SolarWinds, as well as the ongoing log4j and Spring4Shell vulnerabilities. “Intentionally malicious contributions can inject code that is literally opening the doors to hackers,” Krooswyk says. “However, agencies and vendors can’t just stop utilizing open source software and microservices. They need the ingenuity of the open source community.” GitLab is a proponent of open source and believes everyone can contribute. The Biden administration, through its frameworks and mandates, is simply saying, ‘we have to keep a better eye on that,’ especially as more organizations assume a cloud-first posture, according to Krooswyk. For example, earlier this year, the National Institute of Standards and Technology (NIST) published the Software Security Development Framework (SSDF) 1.1, which offers guidance on how to create tighter controls throughout the software development lifecycle. The SSDF 1.1 framework recommends: organizations should be prepared by reviewing permissions all components of software should be safe from tampering and unauthorized access software should be produced with minimal security vulnerabilities in its releases organizations should be able to quickly and sufficiently respond to vulnerabilities Take our 2022 DevSecOps survey and get a $10 gift card. Have your voice count! Code sourcing The next phase in the federal government’s move to secure the software supply chain will be to require reporting and/or attestation. “Agencies and their vendors are being asked if their software is justifiably built using properly sourced code. As a result, organizations may have to explain why they chose to use code from non-mainline repositories,” Krooswyk says. For instance, if a DevOps team chooses code from a non-mainline repository originating in China, they will have to attest to why they did that over sourcing from a mainline repository. The same idea applies to pulling clean containers and not repeatedly using those plagued with existing vulnerabilities, according to Krooswyk. He believes these questions will all be rolled up into a Cybersecurity & Infrastructure Software Agency (CISA) mandate for a software bill of materials (SBOM), which is a list of ingredients that make up software components. “The SBOM will show the list of contributors, known vulnerabilities, results of dependency scans on open source, and more,” he says. “The Biden administration, NIST, […]

May 13, 2022

GitLab Heroes Unmasked: How I am elevating my company using GitLab

Noutați

A key to GitLab’s success is our vast community of advocates. Here at GitLab, we call these active contributors “GitLab Heroes”. Each hero contributes to GitLab in numerous ways, including elevating releases, sharing best practices, speaking at events, and more. The “GitLab Heroes Unmasked” series is dedicated to sharing their stories. Lee Tickett, director at IT development and support consultancy Tickett Enterprises Limited, is a GitLab hero and Core team member who continuously contributes to GitLab and provides exceptional feedback. In late 2020, he wrote a blog about how he came upon GitLab and began to use it as his company’s platform. At that point, his company was using GitLab in the following ways: for version control with a custom merge request approval process as a custom UI for streamlined/standardized project creation as an integration with our bespoke helpdesk platform as a Windows runner with fairly basic CI This blog picks up where that blog left off and gives insight into how Tickett Enterprises is making the most of GitLab’s One DevOps Platform for its helpdesk, CRM integration, CI/CD, and more. Migrating the helpdesk Quite some time ago, I decided to migrate from the bespoke helpdesk platform and use GitLab for issue tracking. Here’s an epic I created just over two years ago to start discussing my plans. I built a bespoke migration tool using C#, which connects directly to the existing helpdesk database and pushes the data into GitLab using the API. This includes: groups (each company in our helpdesk will become a group in GitLab with a single Helpdesk project) issues (every ticket in our helpdesk will become an issue in GitLab, estimates will be included and quotes converted to weights) notes attachments time logs labels (type, class, department, and “status” will be migrated to labels) Helpdesk workflow After discussing different approaches with the GitLab team and the community, we came up with the first iteration of our workflow process. The status of tickets in our helpdesk system becomes scoped labels in GitLab. It looks similar to the following: We have two relatively small teams so we can also leverage boards to distribute and manage work within the team: We will be leveraging the GitLab Triage RubyGem and Triage Ops project to handle reactive and scheduled automation, such as: opening pending issues once they reach their due date (this field has been slightly repurposed) nudging users when issues have been pended, but no due date has been assigned nudging the team when issues have not been triaged (labeled, estimates/quotes attached, etc.) GitLab triage will run as a scheduled pipeline from inside of GitLab, and Triage Ops (formerly known as Triage Serverless) will run as webhooks in AWS Lambda (triggered by webhooks). We may potentially transition some of our existing customizations from C# to GitLab Triage/Triage Ops, too. Building out CRM One of the biggest challenges moving our helpdesk over to GitLab was the inability to tie issues to Customers. So, roughly a year ago, I decided to start building out a Customer Relations Management (CRM) feature. You can see some of the work that has gone into the CRM so far: CRM Merged MRs. It’s surprising how much work is needed for what seems like a mostly simple feature. Despite careful planning, there were many surprises that caused […]

May 12, 2022

Run-time call-stack tracing with Delphi

TMS Software

We are used to inspect a call-stack when something goes wrong in our application and it crashes. Delphi has excellent add-on tools that log detailed call-stack information when an application crashes. But it is not always when an application crashes that call-stack information can be useful. We experience ourselves from time to time that having detailed call-stack information during a regular running application could help us trace undesired situations. Recently, it happened that in rare cases, a component property ended up with an unexpected value. In the application where the component was used, it was from many parts of the code and VCL framework itself that this property was set and it was mostly a matter of knowing from where exactly the unexpected value was set. Once we knew, we could understand and address the problem. The ability to just take at runtime a snapshot of the call-stack when a specific value was set was sufficient to find the culprit. So, while this capability saved us already for several cases an enormous amount of time, we thought it was interesting to make it also available to you in TMS MemInsight. While TMS MemInsight will also give you at run-time insight into the call-stack when exceptions occur, now there is a simple method GetCallStack(sl: TStrings) that you can call from anywhere and as many times as you want and it will return detailed call-stack information. Only requirement is that you link your application with a detailed map information (see Linker options under Project options) How it works? Imagine there is a class TMyClass with a property Text: TMyClass = class(TPersistent) protected procedure SetText(const Value: string); public property Text: string read FText write SetText; end; Now, we want to know from where exactly in our application, this class Text property would be set with an empty string value. We can write the property setter in the following way: uses TMS.MI.Core; interface type TMyClass = class(TPersistent) protected procedure SetText(const Value: string); public property Text: string read FText write SetText; end; implementation proceduer TMyClass.SetText(const Value: string); var sl: TStringList; begin FText := Value; if FText = ” then begin sl := TStringList.Create; try GetCallStack(sl); sl.SaveToFile(‘c:tempcallstack.log’); finally sl.Free; end; end; end; Now, at application level we can use this class for example like: MyClass.Text := Edit1.Text; and when the text property is being set with an empty string, we’ll get a nice stack-trace report giving us the information we wanted. For this example, we create at TForm class level the method to set the myClass.Text via: TForm1 = class(TForm) private { Private declarations } procedure SetClassText(s: string); end; implementation procedure TForm1.SetClassText(s: string); begin myclass.Text := s; end; and when we call this from both the an edit control’s OnChange event and a form button OnClick event: procedure TForm1.Button1Click(Sender: TObject); begin SetClassText(Edit1.Text); end; procedure TForm1.Edit1Change(Sender: TObject); begin SetClassText(Edit1.Text); end; Now, we get a nice stack trace log when the class Text property is set with an empty string value: TMyClass.SetText (57)TForm1.SetClassText (77)TForm1.Button1Click (43)TControl.Click (7443)TWinControl.WndProc (10162)TButtonControl.WndProc (2617)…. […]

May 12, 2022

8 releases of TMS VCL UI Pack for Delphi so far in 2022

TMS Software

TMS VCL UI Pack is our flag-ship VCL product comprising over 600 VCL components to help you create more feature-rich VCL Windows applications faster. Today, we have released TMS VCL UI Pack v10.7.7.0 that is the 8th release so far in this year 2022. We actually lost count on the number of releases since the inception of TMS VCL UI Pack (formerly named TMS Component Pack in 1998). With TMS VCL UI Pack we not only want to enable you to include very powerful features fast in your VCL applications, we also want to deliver fixes, improvements as well as your wishes for new features fast. After all, we are in a fast moving world and software developers want to roll-out updates to their customers also fast. All this inspired by the famous words of Mark Twain: “Continuous improvement is better than delayed perfection”. So, today, we have released TMS VCL UI Pack 10.7.7.0, release number 8 this year. This is a shortlist of new features & improvements that already went into TMS VCL UI Pack just in 2022: 10.7.7.0 New : VCL styles support added in TAdvMoneyEdit New : Support to persist keyboards with unicode characters in TAdvTouchKeyboard New : Support for use of TVirtualImageList for use in high-DPI scenarios for TDBAdvGlowNavigator New : Support for drawing overlapped events added in TPlannerCalendar TPlannerCalendarGroup New : Setting SelectionColor SelectionTextColor = clNone allows to always use specified custom color in TAdvDBLookupComboBox New : CalculatorLook.BorderColor added in TAdvMoneyEdit New : Binary identifier setting in syntax styler to highlight also binary formatted numbers in TAdvMemo New : AutoShowCalculator property added in TAdvMoneyEdit Improved : cblChrome close button appearance in high DPI in TAdvOfficeTabSet Improved : LabelFont handling in connection with ParentFont in controls with attached label Improved : Alignment preserve when entering new line in TAdvRichEditor 10.7.6.0 New : Visible property to show or hide the extra needles in TAdvSmoothGauge New : VCL Style enabled cell checkbox drawing in TAdvStringGrid New : OnItemClick and OnItemDblClick events in TAdvKanbanBoard New : Added wpSftpList support in TWebCopy New : Added support for use of TVirtualImageList in TPlannerMonthView Improved : Error handling when invalid time was entered in TAdvTimePickerDropDown Improved : Dropdown control sizing in Delphi 11 for high DPI in TAdvControlDropDown Improved : Closed button look in high DPI scenarios in TAdvOfficeTabSet Improved : ButtonWidth handling with high DPI in TAdvEditBtn Improved : Added Key in TAdvSmoothListBoxItem.CopySettings() 10.7.5.0 New : Property FindText added to control whether the node is looked up or not in TAdvTreeComboBox New : BeginUpdate/EndUpdate methods added in TAdvWordCloud Improved : High DPI drawing of sys icons and per monitor DPI handling in TDirectoryListBoxEx TFileListBoxEx Improved : Exposed Font and Align properties for TAdvGradientDirectionSelector 10.7.4.1 Improved : telephone type specifier adding in export in TvCard Improved : Label font size initialization at design-time for high DPI in TAdvSpinEdit TAdvComboBox TAdvDropDown … Improved : Exception handling for opening unsupported files from TAdvRichEditorEditToolBar 10.7.4.0 New : TVirtualImageList support added in TInspectorBar New : TAdvOfficePage.TextAlignmentTAdvOfficePage.TextVerticalAlignment added Improved : THTMLStatusBar high DPI support for Delphi 11 Improved : Stop editing by setting Key = #0 in OnKeyPress() in TAdvStringGrid Improved : RowHeight updating via Zoom() in high DPI / Delphi 11 in TAdvStringGrid Improved : Popup toolbar behavior in high in TAdvRichEditor Improved : Performance in […]

May 12, 2022

Is WebAssembly really faster than JavaScript? A hands-on experiment!

TMS Software

WebAssembly is a low-level language with a compact binary format that runs with near-native performance. Free Pascal offers, since some time, a way to compile Pascal to WebAssembly and integrate these modules inside your web applications. So, of course we had to experiment with it, to see if it lives up to the hype. It is important to know that, while WebAssembly is fast and very compact, it is very low level. WebAssembly has no direct connection to the browser DOM and communication between JavaScript and WebAssembly is limited to arrays of bytes, integer and float values. Fortunately, you can allocate memory for the WebAssembly module and use this to read/write more complex data. But all the interfacing that is needed for this (and for accessing the DOM) is something that you’ll need to write yourself. Image Processing For our experiment we’ve created an image processing application as this typically involves heavy data processing. You can watch a live demo of the application here. You can upload an image and use different filters on it. You can use the toggle switch to choose between pure JavaScript or WebAssembly to process the image and see for yourself how much faster WebAssembly is. The first test only took the processing of the image in account, and not the reading & writing of data. As you can see in the graph, in this test, WebAssembly is about 3 times as fast. For the second test, we timed the full function. This included writing and reading from WebAssembly. And even then, WebAssembly is about 1.5 times faster than JavaScript. Conclusion JavaScript is much slower than WebAssembly when processing of large amounts of data is involved. For small tasks, JavaScript might still be the way to go, as the difference is neglectable. For resource-intensive tasks, like video editing and advanced image processing, WebAssembly is the way to go. These tasks require a lot of computing and that is where WebAssembly shines, performing at near native speed. Source code You can download the demo project source code here. This includes the TMS WEB Core web client application as well as the source code of the Pascal based image processing to be compiled to a WebAssembly module. We have shipped a pre-compiled WebAssembly file in the project so that you don’t have to compile it yourself. But if you want to compile or write your own WebAssembly modules you’ll need to install the FPC team Object Pascal to WebAssembly compiler. You can find the installation guide for the compiler here.

May 12, 2022

Create React App: It’s Not As Difficult As You Think

Sencha

Developers often find creating React apps difficult due to a vast array of build tools along with a ton of configuration files and dependencies. React is a JavaScript library established by Facebook that is frequently referred to as a frontend JavaScript framework. In addition to this, it is a tool for creating user interface components. It is fascinating because instead of directly altering the browser’s DOM, React constructs a virtual DOM in memory and performs all necessary manipulations there before modifying the browser DOM. However, one disadvantage of working with React is that it lacks pre-built components. As a result, React developers must either create these components from scratch or rely on the community. One of the hassle-free ways to deal with the issues underlying React is to use Facebook’s command-line tool: create React app. But if you are in the search of a perfect solution to all of React’s problems, you are in the right place. Sencha’s GRUI is a revolutionary tool that features high performance bundled with 100+ data grid features that ensure faster creation of data-intensive web applications. Whether you are a complete newbie or a seasoned developer, GRUI by Sencha is going to be the only tool you’ll ever need to succeed in creating React apps. Read on to find out more about create React app, GRUI by Sencha, and what makes it the ideal companion for React developers. What is Create React App? Setting up build tools like Babel and Webpack is required while creating a React application. Because React’s JSX syntax is a language that the browser doesn’t comprehend, certain build tools are necessary. That’s where create React app comes in, it helps you create applications that are compliant and supported by React framework. The beauty of this tool lies in the fact that it allows you to focus all of your energy on building apps rather than on building configurations. This results in increased productivity and saves developers from needless hassle. How to Get Started with Building Your GRUI App? Building apps on GRUI by Sencha is a breeze. There is no need for additional plugins and Sencha’s GRUI integrates seamlessly within your existing framework. This process can be easily categorized into 5 small steps. npx create-react-app –template minimal my-app Run cd my-app Run npm add @sencha/sencha-grid Building your own component by loading up the pre-generated app component and replacing its app source with: import React from “react”;import { SenchaGrid, Column } from “@sencha/sencha-grid”;import “@sencha/sencha-grid/dist/themes/grui.css”; export default class App extends React.Component {render() {const data = [{ col1: “value1”, col2: “data1”, col3: 1.01 },{ col1: “value2”, col2: “data2”, col3: 1.02 },{ col1: “value3”, col2: “data3”, col3: 1.03 },]; return ();}} Initiating the app by running: npm startSetting license by visiting GRUI and finally adding:SenchaGrid.setLicense(“”) How Convenient is It to Create a Column Editor in Sencha’s GRUI? Sencha’s GRUI is a high-performance react grid for react applications that makes it dead easy to create a column editor. In addition to this, it features extensive documentation which makes it a child’s play to diagnose and troubleshoot problems during installation or integration. In order to create a column editor you have to type in the following React typescript: /*** 1. Define the imports*/import React, { Component } from “react”;import EditorProps from “../EditorProps”;import IEditor from “./IEditor”; /*** 2. […]

May 12, 2022

Enterprise Ready React Data Grid | GRUI by Sencha

Sencha

React is a popular open-source JavaScript library that allows you to build complex UIs using a component model. Those components are expressed using JSX, a React extension to JavaScript language syntax that helps structure component rendering using a familiar syntax. Fig. 1 Example Sencha grid using JSX Figure 1 is an example of a Sencha Grid for React being defined using JSX on the left.On the right, you see the rendered output of that JSX. It is a complex data grid that includes several columns, groupings, filtering, sorting, and various other features. Let us try and understand them in more detail. 1. What is Sencha’s Grid for React (GRUI)? What is new in the 1.1 release? In 2021, Sencha released version 1.0 of “Sencha Grid for React” (also called GRUI). It has all the power and capabilities of Sencha’s Ext Grid but has been rebuilt from the ground up. GRUI’s modernized code base is optimized for a very small footprint so that applications load quickly and seamlessly fit in with the rest of the npm React ecosystem; essentially, you install and get going. The idea was to make it as easy as possible to integrate Grid into your React applications. No other plugins or configuration were to be required. In the short amount of time since GRUI’s initial release, a lot of feedback has come in from our customers and early adopters. Hence, we released the second version of GRUI (version 1.1) with additional features. This release includes Tree Grid, a powerful grid capability that allows you to display hierarchical data. GRUI 1.1 can handle grouping, sorting, and filtering and has all the other Tree Grid capabilities that you have come to expect from the Ext version of the Sencha Grid. GRUI 1.1 also includes: locking grid, spreadsheet selection model, multi-level grouping, and several other filters and features. Additionally, an out-of-the-box Dark Theme is available with GRUI 1.1. 2. What is a typical React application with GRUI? Let’s learn more about GRUI by building a realistic React application. This simple example uses: Material UI, a very popular open-source component library for React FusionCharts, a commercial enterprise charting library GRUI, a commercial enterprise-grade data grid Fig.2 Example Sencha GRUI for REACT As shown in the above figure (Fig. 2), on the left-hand side we have the “VS” code, and on the right-hand side we have the sample application running in the browser. The stack used for building this application is: React 18 Material UI 5 FusionCharts and GRUI Grid 1.1 Fig. 3 – Example of FusionCharts integration to sample React Application Fig. 4 – Example of Tree Grid’s integration to sample React application 3. How can I recreate the sample? To briefly introduce the sample application, we created a simplified layout using Material UI with a tab panel. This includes: Big Data – a big-data grid from a Storybook example FusionCharts – example of a standard FusionCharts visualization Tree Grid + FusionCharts – Tree Grid integrated with FusionCharts and having them interact with each other Grid Flow Graph – a simpler grid with an interesting custom-column component that has a simple chart for each row Get access to an on-demand video for a step-by-step guide on how to create a complex React application here:SenchaCon 2022: Sencha’s Grid for Enterprise React Applications […]

Abonează-te la noutăți