On Sat, 2 Jul 2016 09:30:30 +0200 Ch Lamprecht <ch.l.n...@online.de> wrote:
> With pp they don't even have to install, they click and it just runs > fine. I'm using pp now for 10 years to deliver an executable that > includes Postgres client libraries and Tk UI. It works fine on Linux > MacOS and Windows. pp is a great tool, and I'm very happy that its there. Once I worked out the tedious process of getting the necessary libraries included it produces functional binaries and that's just about all to ask for. Nevertheless why not try to get the best of both worlds. Cava Packager has some features that would make life easier for pp users too. For example, Cava Packager provides Cava::Packager, a license-free module (see http://www.cavapackager.com/appdocs/utilities.htm) that is very handy when developing programs that will be packaged. For example, the functions abstract out whether the application is running bare (unpackaged, e.g. during testing and development) or packaged. There are functions to get access to packaged data and so on. I have wrapped Cava::Packager in a custom App::Packager that also supports pp packaged applications. One of the most relevant functions is GetResource, which will provide the actual path name of a given resource no matter whether it is packaged by pp, Cava, or not at all. It seems to me that this would be a nice addition to pp, too. -- Johan
