New and not-so-advanced developers tend to adopt this bad style and start running into a direction that will end up in fatality. So, the basic concept that FireMonkey encourages is wrong.
FIREMONKEY VS VCL CODE
A good developer should have the inner urge to produce code at a certain minimum quality level and putting everything on the form is nothing that helps here. I'm not going to argue with anybody about decoupling, testability of code and all the other Clean Code aspects and concepts. but this is also already the point where it starts getting wrong.įireMonkey, by it's RAD approach, encourages the developer to click his user interface together, double-click on controls and put all the logic onto the form - where it doesn't belong.
FIREMONKEY VS VCL FOR MAC OS X
So the main idea is, that you design your forms with FireMonkey components and controls, double-click on buttons to add your business logic like Delphi developers did this for the last decades and then be able to compile the application for Windows, for Mac OS X and for iOS without changing it anymore.Īnd indeed, this works technically. FireMonkey is written for Delphi and can also be used from C++ within Embarcaderos C++ Builder. FireMonkey is a application development framework (or platform, as Embarcadero likes to call it) and contains components that should enable the developer to build cross-applications with a singe code base for Windows, Mac OS X, iOS and soon to come Android. So, let's start what FireMonkey is - or aims to be. NET focused, so let me get you all set with the required background information. I know the audience of my blog is mostly. It all started with the definition of 'native' or - even worse - 'true native', but let's start at the beginning. A short time ago I had a harsh twitter argument with Nick Hodges ( about the FireMonkey framework in Delphi XE4 (you may know that I had the start of my professional career with Delphi and started as a speaker at Delphi conferences).
0 kommentar(er)
