(It would be grander if qooxdoo supported extending its runtime into separate browser window instances but unfortunately that's currently impossible)
But I did get the build version served up once I figured that out and it has the same issue.
Ya,
qx.$$libraries in index.js is always not set.
Not sure if that's part of the problem?
The
transpiled dir works out because I'm serving the admin app's transpiled stuff from transpiled/admin:
router.PathPrefix("/transpiled/admin/").Handler(http.FileServer(http.Dir(settings.AdminUIRoot)))
@sknick you need to use a picture you actually use in your app, this was just an example from my own app. I get "https://example.com/myapp/../resource/qx/decoration/Modern/window/close-active.png"
icon/32/apps/utilities-text-editor.png
I think the way it works that you would have https://example.org/main and https://example.org/admin by just having a "main" and an "admin" app in your
compile.json
Qooxdoo is opinionated this way because of the way stuff is compiled.
Thanks guys!
For the default app a special index.html in the root is created.
So what you describe is by design
if you really want to have 2 different apps you need to copy them in 2 diffferent folders and write your own index.html in the root which do the redirection.
@sknick i hope I didn't forget a crucial detail before! Here’s what one of my startup pages looks like:
<script type="text/javascript">
(function(){
var src = “/path/to/output-directory/my-application-name/index.js";
if (window.qx === undefined)
window.qx = {};
qx.$$appRoot = "/path/to/output-directory/my-application-name/";
var elem = document.createElement('script');
elem.setAttribute('src', src);
var parent = document.getElementById("gw-app-container");
parent.appendChild(elem);
})();
</script>The page that this appears in is called something like /my-application-name.html - what happens is that in the loader for the Qooxdoo application, qx.$$appRoot becomes qx.$$resourceRoot, and qx.$$resourceRoot is used to prefix the resource paths
You should not need to set qx.$$appRoot because it should be calculated correctly from tthe path to the script source (ie <script src="/path/to/output-directory/my-application-name/index.js”> is all that the loader should need), but the reason that I specify it here is so that I can support older versions of IE (which I probably don’t need to support now, but the code’s not need to be changed)
i’ve got to go shortly but will try and check back in later
In your examples, your
/admin.html would have <script src="/path/to-output-directory/admin/index.js"> and your /userapp.html would have <script src="/path/to-output-directory/userapp/index.js"> - note that you have to place the entire build directory (or the result of qx deploy) in your web server as /path/to/output-directory
Great job, guys! Love this.
This is in a source build at least.
Is ECMA6 "new Map()" (or WeakMap) allowed in current qooxdoo?
event/Manager.js uses linear lookup like "for (var i=0, l=entryList.length; i<l; i++) {}"
As a Map key can be of type function pointer, porting would speed up functions like removeListener()
Currently the browser freezes for 45 seconds in our application which seems to be related to the linear search
event/Manager.js uses linear lookup like "for (var i=0, l=entryList.length; i<l; i++) {}"
As a Map key can be of type function pointer, porting would speed up functions like removeListener()
Currently the browser freezes for 45 seconds in our application which seems to be related to the linear search