Delivered: our first set of FireMonkey components


It's with much excitement that we release today our first set of controls for the FireMonkey framework: 
TMS Instrumentation Workshop for FireMonkey.

What is it?
A more or less equivalent set of controls, TMS Instrumentation Workshop for VCL has existed for years but the new TMS Instrumentation Workshop for FireMonkey has been designed from the ground-up. The components have been entirely designed in the spirit of the FireMonkey framework, meaning, extensive use of styles has been made where applicable. Use of styles not only means that you can customize the colors, gradients, textures, strokes of the controls at a very detailed level, it also means that the layout, elements within controls can be changed. The end result is ultra customizable controls. At the same time, we have tried to make the default look and feel of the components ready to use. In other words, the ultra customizability comes as an option but it's not needed to make use of the components. In this respect, the components offer the same "R for rapid" as VCL offers RAD.

Cross-platform
Of course the TMS Instrumentation Workshop for FireMonkey is fully ready for cross-platform development. Applications can be built with the controls for Win32, Win64, Mac OS-X and iOS! We provide a package "TMS Instrumentation Workshop for FireMonkey HD" and a package "TMS Instrumentation Workshop for FireMonkey iOS" that gives you access to the controls in FireMonkey HD, FireMonkey 3D and FireMonkey iOS project types. TMS Instrumentation Workshop for FireMonkey Sources can be deployed to compile with xCode/FPC to iPhone, iPad, iPod.

And now?
We're extremely curious to see how the controls will be used. We look forward to all your feedback, comments and requests for new features, new capabilities, new components within the TMS Instrumentation Workshop for FireMonkey control set. We're meanwhile also already exploring other components for FireMonkey. The TMS Instrumentation Workshop for FireMonkey control set was for us also a necessary first step to lay a solid foundation for component design for this new framework. The medium complexity of these controls was an ideal way to familiarize with an entirely new way for creating components. It was crucial for us to design the components to really fit in the FireMonkey framework, i.e. make extensive use of styles. We believe that in the long term, no one will benefit from quick ports of VCL components that do not fit in the design philosophy of FireMonkey. After the past months of learning a lot of new things, fighting with the initial quirks of this brand new framework and working very hard, we believe we now have a more solid foundation and are ready to tackle the next challenges. As the interest in these components and the market will justify, we'll build up a wider range of components for the FireMonkey framework.

VCL vs FireMonkey?
VCL has a history of over 15 years now. It is an extremely rich framework for Windows application development with a huge array of components that have over all these years become rock-solid and very feature-rich. By its nature, the VCL framework will always optimally and closely integrate with Windows. The VCL framework is perfectly suited to create first-class Windows applications. By using the native Windows controls in the VCL combined with custom controls, it is possible to create Windows applications that consistently and perfectly integrate in the overall look & feel and way the Windows operating system works and access the Windows operating system resources in every possible way.
On the other side, FireMonkey offers exciting new capabilities like 3D, cross-platform deployment, styling. With the design choices that have been made in the FireMonkey framework, comes the disadvantage that it is not using native operating system controls. This will in the best scenario always mean chasing a moving target to make applications that have a user interface that is 100% consistent in appearance and behavior with the operating system. Certainly, the advantages FireMonkey brings will in several scenarios justify living with its disadvantages.

A "+" story
It's always funny that many software developers always like to flipflop between life and death. That HTML5 is very much alive today means for many developers that native applications or even Silverlight are dead. If you look back, there was a time that when .NET was freshly released, many developers claimed that native application development was dead. We believe that in life things are not black or white, there are colors! Blues, greens, reds, a big palette to choose from. We see the VCL versus FireMonkey not as a life or death situation but rather a "+" situation. As Delphi developers, we're now fortunate enough to have one more option to choose from today. We can choose VCL to create the best possible fast native Win32 and Win64 applications, we can choose IntraWeb to create web applications in a RAD way, we can choose FireMonkey to create applications for iOS with our beloved language or cross-platform applications for Windows and Mac. We have never had more choices as Delphi developers and then, even more choices are on the way! VCL remains as ever, a very important choice for Windows application development and we're feverishly continuing to work on new offerings for VCL and extend and improve existing VCL components. IntraWeb remains a very productive way to create web applications for desktop and mobile browsers and we're working very hard to offer components that allow you to take advantage of HTML5, mobile browsers, ultrafast asynchronous updates etc.. And now there is the new kid on the block called FireMonkey that allows us to go Apple and we're also trying to offer added-value for Delphi developers in this area. It is in other words a VCL + IntraWeb + FireMonkey story. Let's work together to make the sum of this 1 + 1 + 1 story more than 3! 
Kind regards,TMS software team

Related Discussions
  • HOW TO RUN DATABASE APPLICATION ON THE INTERNET (2017-06-09 10:54:22)
    Well, in design I think there is already an issue. Backend is more then just a database with which you connect. There should be a complete layer...
  • REPEATING FUNCTIONS (2001-01-04 11:46:34)
    The OnIdle event is not hardware dependent. It is called when the program has idle time. The OnIdle event is in TApplication and is a warpper...
  • HOW TO MAKE MASTRE/DETAIL TABLES LIKE THIS ? (2001-01-04 11:14:14)
    You will need to add a TDataSource for Table 1 & 2 and connect to the respective tables. In the Table2 object set the "Table2.MasterSource =...
  • TELEPHONE BASED APPLICATION (2001-01-08 12:29:39)
    I did something like this. I wrote a fully operative phone- based banking applciation in two days using VisualVoice and Dialogic cards. However,...
  • EXES CONTAINING MORE THAN ONE ICON RESOURCE ... (2001-01-05 11:25:58)
    Just draw your icons with the Borland Image Editor (Delivered with Delphi). It allows to save different icons in one ico file as well.
  • HOW TO LOAD/SAVE FROM/TO INI FILES WITHOUT COMPONENTS? (2001-01-05 13:55:47)
    Thx...:)
  • DELPHI WITH INTERNET.. (2001-01-05 21:35:50)
    http://www.matlus.com/scripts/website.dll This site is 100% Delphi built and 100% dynamic. All the content you see here is "database driven" and a...
  • PRINTING A PDF FORM (2001-01-07 05:57:11)
    Hello Tom, If you find a delphi solution to bypass the acrobat Printer i am very interrested. Actually i am printing a lot of invoice to the...
  • MODBC MTABLE.POST - WHY DOESN'T WORK? (2001-01-07 11:32:50)
    Thanks for help :) I use Access database, and my 'ID' field is the standard unique field generated by Access. I've tried to set the field type...
  • EDIT BOX (2001-01-08 00:31:19)
    the first answere solves the problem but just in case you need something else then instead of checkbox1.checked you can say if ord(key) = 13 then...
Latest News
Submit News Form Past News
Latest Forum Entries