ComponentOne Studio, from software company GrapeCity in Pittsburgh, Pennsylvania, provides Visual Studio controls.
$1,495
Per Year Per User
React
Score 8.9 out of 10
N/A
React is a JavaScript library for building user interfaces. React enables users to create interactive UIs. Design simple views for each state in an application, and React will update and render just the right components when data changes. React is available free and open source under the MIT license.
C1 is great for creating custom reports. We have client apps where we've created some fairly complicated reports such as invoices and real estate inspections. We also use the True DBGrid in many of our apps since it is so customizable. Its grouping and filtering features are very nice and can provide summary counts and totals at the bottom or right side of the grid that are very handy.
React is a JavaScript user interface construction library that works well for:
Developing web apps with dynamic and complicated user interfaces.
creating reusable UI elements that may be used in other applications.
creating single-page applications with dynamic content updates that don't require a page reload.
The Virtual DOM's effective updating mechanism allows it to handle large volumes of data updates.
React, on the other hand, might be less suitable for:
Websites that are simple, stagnant, and have no interaction. Other libraries or simple HTML, CSS, and JavaScript may be a better fit in such circumstances.
Web sockets may be a better choice for applications that need real-time updates, such as chat or gaming apps.
When creating mobile apps, React Native is a better option.
Server side rendering only, as React is designed to run on the client side.
The True DBGrid control is nice for showing parent/child relationships and being able to drill down and show the child data. It also is nice for showing summary totals.
The report engine is great for building custom reports for Win Forms or web apps. It can do everything that Crystal Reports can do.
They have a good selection of controls that can do just about anything you can imagine.
React is fantastic for building performant user interfaces. Our web app is snappy and great for our customers.
React has the philosophy of doing one thing and doing it well which is the view layer of the application. This makes it incredibly intuitive and flexible for developers to use.
React has lead the way in being able to write modular and structured code. It is a drastic improvement since the days of spaghetti jQuery code.
React has an unmatched community. The amount of tools and libraries available is fantastic, and there plenty of solutions available online for common problems.
Debugging React is challenging. Bugs in react code generate stack traces internal to React and it is often totally unclear how it relates to the code you actually wrote.
Relating your React elements to corresponding DOM elements is difficult. The intentional separation of virtual and actual DOM also makes it difficult to map the elements to the structures in the DOM. This is partially ameliorated by the use of the React dev tool, which provides a DOM-like view of the React elements, but the tool still does not provide a direct correspondence with the DOM that is often necessary to figure out why something isn't right.
Because JSX is React-specific and not a language feature, a special compilation process is necessary to convert JSX code to normal JS. Coming from a C++ background, compiling things doesn't bother me, but many JS developers are used to a less structured development.
React is just a bit of a different animal. I was avoiding it for the longest time. I thought for sure I would land on Vue or something else with a more approachable and familiar appearance. But after taking an online course in React, I started realize what people were raving about (and complaining about) and decided to implement it at our office for one of our products.
Since it's open-source and very popular, the community support for React and related tools and libraries is excellent. There are a lot of people using the same tools, and so issues tend to get fixed quickly and "recipes" are easy to come by. And since it's backed by Facebook, they have a dedicated engineering team working on the progression of React.
We have been in business since 1992, so we have used many different products over the years. The two other products we've primary used that are similar to ComponentOne, are Infragistics and Crystal Reports. Infragistics has a vast array of controls similar to ComponentOne. We use both to be honest and I'm not sure which one I would pick over the other. I guess that would depend on what you're trying to accomplish and if one had some control or capability that the other didn't. ComponentOne does have the reporting capabilities, where Infragistics does not.
While this is a widely contested debate with various blog posts and benchmarks all over the place, its really a personal choice to determine what works for the team. Coming from a Angular 1.x background, I decided to try a new framework when Angular 2.x was announced and at that time React is gaining popularity and Vue hasn't taken off yet. Compared to Angular 1.x and Vue (hybrid of React and Angular) that split the logic from the html templates, I loved the way React breaks code into components using the jsx syntax. In my mind, this allows for cleaner components and easier maintenance
ComponentOne allows us to add additional features to our apps that wouldn't be found in apps written with just Visual Studio itself. That allows our clients to get more creative in their requirements, which in turn, means more work and billable hours for us!
Our apps appear more professional when using ComponentOne which helps us get projects for new clients.
ComponentOne also helps us to save clients some money since we are not having to develop things that it can do from scratch.
