Thanks T. Any suggestions on how I would go about this?
The app I am building is a device UI. When we ship to customers, there are some customer specific themes that we package. Currently we build a separate image for each customer. This results in (# parts * # customer) js output files, which are a pain to manage I would like to be able to compile the themes separate from the app itself and then ship the app and the customer theme. So I changed it to compile the themes using parts and then dynamically load it at runtime depending on what a particular env. variable is set to. Everything works fine with the parts, but my problem as you can imagine is that I dont know which of the parts generated relate to a particular theme and I dont want to ship the theme for one customer to another :-) Hence my question. The only other way I can think to tackle this is to compile up the theme and UI as independent applications and launch the UI from within the main class of the theme app. This way I can compile multiple themes all accessing the same app. Am I on the right track? Thanks Jacob -- View this message in context: http://qooxdoo.678.n2.nabble.com/configure-file-name-for-parts-tp7583180p7583190.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
