I want to bring this conversation public that Ed, Scott, and I have been having about assets for the upcoming simple widget, which will allow users to build a Cesium app with one line of code. I am, of course, really excited about this since this will significantly reduce the barrier to entry.
Scott has proposed adding a build step to copy “Source/Assets” to “Build/Assets”. We could also then have either a global (CESIUM_BASE_URL) or a script-tag attribute (data-cesium-base) that lets Cesium.js find “Build/Assets” and the worker scripts.
With this addition, I think the simple-widget branch could be brought up to date and readied for pull-requesting.
With Scott’s proposal, can we provide a default for the Cesium url attribute (I’d call it “assets” not “cesium-base”) that assumes the most common case, perhaps that assets is a directory at the same level as Cesium.js? However, Cesium knowing a directory structure like assets doesn’t feel right to me. Are more fine-grained urls, again with good defaults, better? Maybe that is worse - seems messy.
Any other, perhaps completely different, ideas?