This blog post covers the Developer Skill Sprint which will air on Feb 17, 2015 entitled Promote Healthy Apps by Separating App Logic from the UI using Common Patterns
Explore the Flexibility of RAD Studio XE7
Live sessions every Tuesday January 20 - March 25, 2015 6AM San Francisco / 9AM New York / 2PM London / 3PM Milan 11AM San Francisco / 2PM New York / 7PM London / 8PM Milan 5PM San Francisco / Wed 10AM Tokyo / Wed 12PM Sydney
It's the new year and time for more Developer Skill Sprints! Join us for this 10-part series exploring some of the newest features of RAD Studio, Delphi and C++Builder XE7. We'll show you how to use the new revolutionary FireUI multi-device designer, utilize multi-core CPUs with the all new Parallel Programming Library, explore InterBase XE7 change views, and much more!
With the addition of cross-platform support to Delphi, and the coming Mobile Studio product, there is an increasing need to have device-specific User Interfaces. At the same time, you want to minimize the amount of code you have to rewrite for each platform. This session will look at Model-View-ViewModel, one technique that leverages LiveBindings to not only minimize the effort required to slide different UIs in front of your code, but also increases the maintainability and testability of your app as a bonus
Brian Alexakis is a Product Marketing Manager at Embarcadero Technologies. He is focused on leveraging the connected world of technology to build new experiences for the Internet of Things.
I remember that when I first started programming with Delphi 3 many years ago, I was very surprised to discover that "on" events become functions in the *form*. That's a sure-fire way to encourage poor separation between UI and functionality. Before I used Delphi, I was using CodeWarrior on Mac, and there events were started by the controls themselves, making it easy and natural to receive events in the event loop and make appropriate calls to functional code in well-separated units.
Please login first in order for you to submit comments
Page :
1
Check out more tips and tricks in this development video:
I remember that when I first started programming with Delphi 3 many years ago, I was very surprised to discover that "on" events become functions in the *form*. That's a sure-fire way to encourage poor separation between UI and functionality. Before I used Delphi, I was using CodeWarrior on Mac, and there events were started by the controls themselves, making it easy and natural to receive events in the event loop and make appropriate calls to functional code in well-separated units.