http://www.deltics.co.nz/blog/?p=936
David Intersimone "David I" on August 1, 2012 at 09:06
The team is working to surface native controls for FireMonkey on each platform. Then developers will have the choice to use vector drawn components in their projects across all platforms – or to choose to have native controls on each specific platform. More to come when additional FireMonkey capabilities are completed.

On 8/1/12 8:40 AM, vikosh maha wrote:
  (snip)

I think until i can use native iOS viewControllers that firemonkey wi
  
  
  

lets try that again lol.
    I think until i can use native iOS viewControllers that firemonkey will
    be useless to me on iOS.
    
    

vikosh maha wrote:
  (snip)

This existed in the original VGScene library under the name
  TNonVGLayout. You placed this layout on your form and connected a VCL
  component to it. It would then rotate, scale, etc., just like a native
  VG component (IIRC).

(snip)

Personally (others may differ of course), but I'd like what was released for XE2 to be rewritten to a better standard first, with native API hooks added VCL-style as appropriate (e.g., TCanvas exposing a Handle property typed to CGContextRef on OS X, etc.).
  That said, having recently had the misfortune to use a dog of a QT application on the Mac, I hope 'native controls' isn't a codeword for 'son-of-CLX'...
  
  
  

(snip)

+1, building on shaky foundations is only asking for trouble later on.
    (snip)
Apparently it's not, they seem to be aiming for repeatedly copying the
    surface of hidden native controls so they can be made visible in the FMX
    scene-graph. If so, this would be more of a dirty hack and a recipe for
    performance troubles and graphical glitches in the long run IMHO.

"Dominique Willems" skrev i meddelelsen
    news:✉forums.embarcadero.com...
    (snip)

Its not exactly the same I suspect.
    The NonVGLayout thingy constantly copied the graphical surface of the
    component, to be able to rotate etc. The original component still floated

Am 01.08.2012 14:40, schrieb vikosh maha:
  (snip)

One less argument for Joanna...
  
  
  

Joanna,
  (snip)

Squeaky wheel gets the grease.
  --
  Q
  08/01/2012 10:52:15

Le 01/08/12 17:47, Markus Humm a écrit :
    (snip)
Maybe my "complaining" finally struck home that there was something
    missing in the original approach?
    After all, it was my comments on Simon Choi's excellent efforts that earned me a reprimand from Embarcadero.
    Joanna

Quentin Correll wrote:
    (snip)

And just because they lop your head off for saying something doesn't
    mean they don't recognize that you were right. :^)
    --
    Cheers,

Le 01/08/12 20:00, Van Swofford a écrit :
  (snip)

How does that song go?
  "Wide-eyed and headless, I've gone and done it again…"
  ;-)
  Joanna

(snip)

Original approach was good, but in some cases native controls are better choice.
  I like being able to choose what best fits my needs in any particular case, but
  I do hope that the whole thing will be less buggy. Also, I do hope that FM will not
  be abandoned.
  Dalija Prasnikar

wrote in message news:✉forums.embarcadero.com...
    (snip)

"working to surface native controls for FireMonkey on each platform. Then
    developers will have the choice..."
    doesn't sound to me like abandonment...
    

Van,
  (snip)


  --
  Q
  08/01/2012 12:38:27

Joanna Carter (Team OOAD) wrote:
    (snip)

Hmm, don't recognize that one. Was it from the Beatles Butcher Album?
    Or maybe from the Legend of Sleepy Hollow? :^)
    --
    Cheers,

Quentin Correll wrote:
    (snip)

Or maybe spit out like a watermelon seed.
    --
    nhoJ
    

Mike Margerum wrote:
  (snip)

Don't know about iOS, but you can use native OS X ViewControllers on OS
  X. I'd think the same should be possible with iOS too, right now.
  --
  Rudy Velthuis

(snip)

Somehow I missed that part.
  Dalija Prasnikar
  
  
  

(snip)

I hope that is not their way.
  Dalija Prasnikar
  
  
  

Hello,
  Eric Grange wrote:
  (snip)

ugh. Where did you take this from?
  --
  Moritz

Moritz Beutel wrote:
    (snip)
He is assuming, I think, they will be using the existing TNonVGLayout
    component that already existed in the original KSDev library, back in
    2010.
    

(snip)
From the hints that they would be surfaced as FMX components, and that
    it's what the old VGScene component for that or "NakeyMonkey" do.
    If you want to make native controls part of the FMX scene graph, ie.
    allow them to be rotated or overlayed by other FMX components f.i., it
    means they have to be rendered as textures, which in turns drastically