John Spackman-3 wrote > During development, put the whole tree in your website but after you’ve > created a “build" version that build version is self contained - so you > don’t need to deploy the qooxdoo package to your live server > > John
Well, I found out, (until now this seems to work), that you need the tool, framework and component folders along with all the root files. So, it seems (and is logical) that you can omit the application and documentation folders. I asked this question as I share my development folder with Dropbox, and Dropbox goes crazy if you add a lot of files, but even worse, renaming the root folder of those files will also result in huge network traffic. Effectively this setup enables me to do my tooling on the host machine (os x) and the website (via iis) on the guest VM. The backend is written in F#, that's why IIS is preferred. -- View this message in context: http://qooxdoo.678.n2.nabble.com/Which-dirs-files-are-needed-to-use-the-framework-tp7586544p7586546.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
