Yes, CDATA should work. The following works in Flex:
http://ns.adobe.com/mxml/2009;
xmlns:mx="library://ns.adobe.com/flex/mx">
The only thing you have to escape in CDATA is "]]>". (You would replace
it with
Yes, and it probably is. You can run the MXML file through an XML validator to
check.
But then the data in the CDATA gets handed to the compiler, and I don't
remember our rules for string-based properties. Either you have to escape them
to also be Java-compiler-compatible, or the MXML parser
Shouldn't CDATA be ignored by compiler ? At least what is inside of it ?
czw., 12 maj 2022 o 17:37 Piotr Zarzycki
napisał(a):
> Hi guys,
>
> I'm fighting with problem of displaying text inside component in MXML. I
> have following text and a lot of similar one:
>
> "for machine in $(pfexec
Hi guys,
I'm fighting with problem of displaying text inside component in MXML. I
have following text and a lot of similar one:
"for machine in $(pfexec VBoxManage list runningvms | cut -f 1 -d ' ' | sed
's///g'); do pfexec VBoxManage showvminfo $machine | grep
Memory size: | sed 's/^.*
