Is there another shortcut to create a new FMX-based Windows application, besides "Firemonkey Metropolis UI Application?" What if one just wants to use the FMX library, without any of the Metropolis stuff?

-
Is there another shortcut to create a new FMX-based Windows application, besides "Firemonkey Metropolis UI Application?" What if one just wants to use the FMX library, without any of the Metropolis stuff?
And why is FMX for Windows such a hidden option? I remember it being quite prominent in XE2.

Comments

  1. David MillingtonAugust 28, 2018 at 8:36 AM

    File > New Multidevice Application, and choose the Blank item in the next screenshown. That creates a blank empty single-empty-form FMX app.

    It shouldn't be hidden! If it is, please let me know, that's a bug...

    ReplyDelete
  2. Dominique WillemsAugust 28, 2018 at 8:39 AM

    David Millington Thanks. For a Windows-only application, I have to use "Multidevice Application." That makes sense. ;)

    ReplyDelete
  3. Scott PinkhamAugust 28, 2018 at 9:33 AM

    Dominique Willems FMX is multiplatform, so I think they do that to better distinguish it from VCL which is Windows only.

    ReplyDelete
  4. Dominique WillemsAugust 28, 2018 at 9:47 AM

    Scott Pinkham It's probably just a semantics discussion. FMX can be multiplatform, but it doesn't take much to make it run just on Windows. If a developer sets out with the concept of a Windows-only application, he won't be looking under "Multidevice" solutions. But I'm probably the last Windows-only developer out there, so it doesn't really matter.

    ReplyDelete
  5. Thomas Mueller (dummzeuch)August 28, 2018 at 10:30 AM

    Dominique Willems no, you're not.

    ReplyDelete
  6. Scott PinkhamAugust 28, 2018 at 10:53 AM

    Dominique Willems Totally agree. It would be interesting to discuss the pros/cons of using FMX when developing for Windows only. I use FMX for everything now because it seems to be a more modern, better-designed framework than VCL. FMX's ability to have any visual control contain another visual control(s) is something I use all the time and makes it hard to go back to VCL.

    ReplyDelete
  7. Dominique WillemsAugust 28, 2018 at 1:09 PM

    Scott Pinkham It's really refreshing to meet at least two others of my species! ;) When I discovered Eugene's VGScene, I never looked back at the VCL. But it was painful to watch it evolve so excruciatingly slowly, once it got swallowed by EMBT and used as a "multidevice" tool. It could have been a blisteringly fast and stable Windows GUI by now. Yet, it feels like it's devolving in certain respects, what Windows is concerned. Maybe I'll look at it in a more positive light at the end of this XE2 -> 10 conversion marathon. It looks like all of the FMX code I wrote was for a totally different framework.

    ReplyDelete
  8. Christen Blom-DahlAugust 28, 2018 at 1:34 PM

    Dominique Willems I’ve been a Firemonkey dev since XE2. There was a big change from XE2 to XE3. Since XE3, EMB has included many new features and quality improvements but code compatibility has been maintained.

    ReplyDelete
  9. Dominique WillemsAugust 28, 2018 at 1:57 PM

    Christen Blom-Dahl Yes, I guess the big sea change was from FMX1 to 2. I vent mostly because I'm losing time fixing broken code, instead of coding. Code-breaking changes are a pain.

    ReplyDelete

Post a Comment