The most common complaint about installing Scripto is the Zend Framework dependency, in particular, determining the path to the ZF library. Removing this dependency would streamline the installation process, but using a custom HTTP client (which is the extent of ZF needed by Scripto) may be more trouble than it's worth.
An alternative would be to package the ZF library (or only the requisite ZF components) alongside the Scripto library. However, this would greatly, and perhaps unjustifiably, increase the size of Scripto downloads.
The most common complaint about installing Scripto is the Zend Framework dependency, in particular, determining the path to the ZF library. Removing this dependency would streamline the installation process, but using a custom HTTP client (which is the extent of ZF needed by Scripto) may be more trouble than it's worth.
An alternative would be to package the ZF library (or only the requisite ZF components) alongside the Scripto library. However, this would greatly, and perhaps unjustifiably, increase the size of Scripto downloads.
A related change would be to update to ZF 2.