How do we persist our packages and other dynamic information?
Actually this isn't very important as whatever we use is only internal to eXe, eXe will always have to transform the data into other formats, which will include XHTML from which XSLT transforms can also me made.
Loooking for something fast, easy to use, interoperable (between different computers-O/Ss and CPUs), transferable, flexible,
elp File Format
- zip up
- all resources used
- except for those which are generically available.
- all resources used
Security Concerns
- If a elp package includes executable content (iDevices and Styles) what protects the user from malicious code?
- Should users have the ability to disable iDevice plugins?