Erik A. Onnen schrieb:
I had the same problem.The storage of Qooxdoo on my webserver is not in a standard location and cannot be for various reasons. My solution is a own Makefile with runtine-setting as shown below. generate-script-build: @$(GENERATE) \ --script-input $(FRAMEWORK)/source/class \ --generate-compiled-script \ --compiled-script-file qx/script/qx.js \ --copy-resource \ --resource-input $(FRAMEWORK)/source/resource \ --resource-output qx/resource \ --define-runtime-setting qx.theme.icon.CrystalSvgIconTheme.imageUri:/qooxdoo.resource/icon/crystalsvg \ --define-runtime-setting qx.theme.icon.NuvolaIconTheme.imageUri:/qooxdoo/resource/icon/nuvola \ --define-runtime-setting qx.theme.widget.WindowsWidgetTheme.imageUri:/qooxdoo/resource/widget/windows \ --define-runtime-setting qx.manager.object.ImageManager.staticUri:/qooxdoo/resource/static \ --cache-directory $(CACHE) The result is a qx.js with the given location (e.g. /qooxdoo/resource/...) for the themes. You don't have to set aliases then. But I am not happy about this, because for each new theme I have to change my Makefile. - Erich |
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
