Sorry to say that I regret about my Scripter purchase. I mean, I regret that I didn't purchase it before ;-)
I implemented the routine I needed in my application in less than 4 hours, thanks to the excellent examples in documentation and available features.
I'm even "scared" because everything worked in the very first time and every time this happens there is something really wrong "hidden" that only shows up when the application is running at the customer (one of the Murphy's Law).
Congratulations.
- Natali Junior Samuel
FixInsight brought us an immediate gain in code quality by highlighting possible problems that went undetected until now.
We included it in the static code analysis on our buildserver, so every commit by a developer is also checked with FixInsight. It is a tool that really helps you to make your codebase more solid and also improves readability by reminding developers to stick to conventions.
One should not forget to mention that Romans support is great.
- Lübbe Onken
We have built several windows (both .NET and Delphi) solutions using FlexCel and we have experienced the good evolution of the product. We like it mainly for the three following reasons: Value for the money: There is no need for any other component to have a full reporting solution. Performance: From the real experience we have performed, FlexCel is very well engineered and the performance you can obtain with it is impressive! The source code is available, and it's very important if you are involved in the development of competitive solutions and products.
- Luis del Ser
It's now very easy to build a report with the new Flexcel + Aurelius integration. It was so easy that I really thought I was doing something wrong. I will never go back to a report generator, Flexcel is way cooler and easier for reports.
- Eduardo Elias
I work with Delphi since the first version, and searching for components is a hard work (I think you know). I've tested tons of components, even the "best-sellers", in my eyes, there are two things importants to look for a component: the "look" (for visual components of course), and the most important:
It need to be easy to understand, to programming, and to find information when it is needed (help/manual/demos)
In all of these points your job is really good! Congratulations for you and your team.
