I AM however, getting close to figuring this out... I will post what I know so far..
a .u3p file, is basically a .zip file that has been renamed to .u3p, and has the following directory structure in it...
data/
device/
Host/
manifest/
in the .u3p files I have found, the "data" and "device" directories have been empty. The "host" directory, contains the "exe" and all associated .cfm, .hlp, .ini, etc files.
the "manifest" directory contains 1 file called "Manifest.u3i"
which is basically an xml file, but that is all I know so far..
if anyone else has any information regarding this, please post.. The only thing I'm not so sure about at this point, is what is required in the xml file, and what isn't? for instance, what if the portable app doesn't come with an icon file,
under <icon></icon> do you leave that part out? or do you put the exe file in there? I am still confused about that yet, but I am in the process of experimenting with that to see if that directory structure will zip up and install or not without a u3 API being compiled in or not .
I also don't know about the application uuid, can you just make one up? I don't know yet....
anyone else willing to contribute to this please let me know