Holy crap, I intended to make a nice litte contribution this morning, and look what happend ...
Anyways, it looks like I don't fully get what you guys want with the pyjsbuild and the bootstrap_progress.js, this is all too much rocket for me. Or what? After lots of thinking I have decided to do what I intended and pushed some changes to the pyjs_site in the repo on SF. It's just a GIF file and some minor modification to index.html and pyjs.css, we can always undo it quickly. (I don't recommend reverting as I fixed some CSS and HTML flaws, I would manually remove what needs to go away.) > bootstrap file is responsible for getting the whole party started -- > it searches for pygwt:module meta tags, loads the corresponding Aha, now I know that it was _just good_ that I didn't remove the pygwt:module meta tag from index.html that the W3C validator complained about! ;-) > there is a module controller in that file that you can hook into, and > an empty function called __pygwt_earlyuser ... this function will be > called before anything else (essentially the very first thing done), > giving you a chance to use raw javascript to create a bootsplash/etc > ... whatever you want really. I see. But is there a real advantage compared to just adding an image and some CSS in the index.html document? Probably that there could be code used from the pyjamas framework itself, and so avoid reinventing the wheel (design/copy a spinner, add CSS code) for every web site / pyjamas application? > it was designed this way to avoid tons of options for minor changes -- > simply add the custom code you want to the early user routine -- it's > sort of like an initramfs in linux. Looks very much elaborated. But help me understand: Does that mean I have to go into the JavaScript file and add custom JavaScript code in the __pygwt_earlyUser() function? For a loading spinner or a progress bar? Tell me this is made with Python somewhere else, please. Please let me know how you like the startup progress bar on the pyjs_site. This indicator isn't actively hidden yet, it only works at the moment, because the generated website fully covers the indicator as soon at it appears. There is a "bootstrap-loader" DIV that needs to be hidden (or removed from the DOM) at the end of processing bootstrap.js (or boostrap_progress.js) if it should be clean and beautiful. The GIF has a "Created with ajaxload.info" comment built-in (you can see it in the binary and, e.g., with GIMP). That's what it came with. Dunno if everybody is happy with that, and how this affects the copyright file... Peter
