|
|
As an aside, some considerations I think we'd have to address
before even starting an IOS port
is the issue of "sandboxing" on the iphone.
FLTK does have some features that would probably be considered
unsafe; file browsers,
preference files (e.g. the Fl_Preferences stuff), and anything
that accesses the file system,
I'd imagine.
We'd have to be careful, I think, how we build the library for
IOS to prevent the app from accessing
system calls it shouldn't (like system(), fork()/exec()), and
may have to provide linking flags that disable
such features in the final compiled lib.
--
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/ca7e3dfe-5f4c-6d98-c2bb-9f873700e7c1%40seriss.com.
[ Direct Link to Message ] | |
|
| |