2012/3/17 lkcl luke <[email protected]>: > On Sat, Mar 17, 2012 at 5:28 PM, lkcl luke <[email protected]> wrote: >> hey folks, >> >> ok you remember the cute idea of doing automatic parsing of the html >> loader file? well, um... when you try to install 2+ pyjs >> applications, guess what happens? only one of the loader files ends >> up with its HTML having the bootstrap loader tags added, because as >> far as the rest of the public/*.html files are concerned...
Can you explain what "install 2+ pyjs applications" means? Can you give a (real world) example? Can you describe the build / deployment process? >> i'm trying to think how to deal with this - i think it means treating >> public/* as "basically a blop of static html wot gets copied" and >> moving HTML loader files *out* of public/ That's correct: The <myapp>.html file is just one of the static html files with a special sematic meaning. As soon as that apploader file is called differently than the application itself the parsing fails (because that's no such file <myapp>.html then). Best example: the pyjs_site application. > ok i've added a "--apploader-file" parameter. Not sure whether that's the ultimate solution. You'll have to handcraft a index.html (or so) document. I'd like to free us from that burden. There must be a way of creating from template (or parsing a prepared) apploader file when you build the 2+ applications in one single process. We should also take into account that the developer might want to test every single application separately (or just have some of them combined) in the development process. Peter
