Pronto! loads its modules from server skins, which is far from convenient if you're developing a module. In that case you have to upload each and every version you want to try inside server skin.
Test versions of Pronto! can be executed locally with the help of debugconfig.xml file, which should be placed near pronto.swf on your hard drive.
debugconfig.xml is intended to simplify the process of module development and makes it possible to run web version of Pronto! on developer's computer. It allows setting the server Pronto! should use, adding local modules and configuring remote modules to be loaded from local folders.
A typical debugconfig.xml file:
<debug> <!-- defaults: port="8100" secure="no" --> <server host="localhost" port="8100" secure="no" /> <modules> <!-- Load .swf, and icons for module, already existing on server, from local path --> <module id="com.myCompany.releasedModule" basePath="com/myCompany/releasedModule" /> <!-- Load .def, swf and icons for module that is not on server yet --> <module src="C:/Workspace/newmodule/bin-debug/newmodule.def" basePath="C:/Workspace/newmodule/bin-debug" /> </modules> </debug>
Root node should contain server and can contain modules nodes.