If anyone care there is problem with the portable foxit reader (and these forums).
1. if you just happen to click on check for updates in the foxit reader, a registry entry is left when exiting foxit.
2. there should be a report bugs forum or a direct link to report the bug.
3. back in the beginning opf the portable apps project, the source (nsi) was freely available for any particular app. Now it seems you are more intersted in forcing a return to this site for updates and/or problems.
I frankly have to wonder about the motives for some of the apps posted here. I know for a fact that many of the progs are ALREADY PORTABLE (for example XMPLAY). I then wonder why you have 'portablized' them. Why not publish what and why you have done. I for one do not give a flying whatever if the only change is to make the prog work with your launcher (if that is indeed why you have changed the app).
How about a little openess about just what you have done to make an app portable? Many of use (oldtimers) just want an app that runs cleanly.
This was a worthy project in the beginning, but I think you have lost your way.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Perhaps you should re-examine and research before making wild accusations. First of all, the source code is freely available for Foxit's launcher as well as the other apps you are thinking of. It's called the PortableApps.com Launcher and it lets developers and even end-users portablize apps without needing to write any code. The goal was to keep from having hundreds of different custom launchers that duplicate the same functionality (which is just plain silly) and make it much easier to portablize apps. And, of course, it's fully open source under the GPL.
Second, lots of so-called portable apps are only kinda portable and have things like most recently used files (nearly all), custom backgrounds (Opera and others), recent playlists, settings, local bookmarks or other things break as you move PCs. That's one reason. Most zip portable apps store their data in odd locations making it difficult to back just that up. Many can't be upgraded by just unzipping the new version over the old without losing settings. There are a lot of reasons and we detail them right here, a page which is linked from everywhere on the site.
Finally, if all you had was a minor bug report on Foxit, you could have simply said that without the assumptions and vitriol. We're the only fully open source portable software project that has all our portablization utilities based on 100% open source tools (Launcher uses NSIS, AppCompactor uses 7-Zip/UPX, Installer uses NSIS/7-Zip). We keep all our development discussions in public and all the rationale behind decisions like why using PA.c Format posted for all to see. In short, we're about as open as anyone can be, and I'm unsure why you'd think or assume otherwise.
Sometimes, the impossible can become possible, if you're awesome!
XMPlay does not handle drive letter changes that occur when taking a USB drive from computer to computer. This affects entries in the ini file and the library file. These issues are addressed by the PortableApps.com version found here. That's why XMPlay has been "portabilized".
neutron1132 (at) usa (dot) com