On Mon, Feb 27, 2012 at 8:16 AM, Peter Bittner <[email protected]> wrote:
> Yesssss,
>
>> however - i've got an idea. what about *removing* the requirement to
>> have bootstrap.js (entirely) from the public/ loader files, and having
>> the pyjs compiler actually go and parse the HTML and put it in, when
>> the file gets copied into the output/ folder??
>
> Exactly! If there is no bootstrap.js to be loaded with pyjd why should
> it be referenced in the html file! It must be injected by pyjs only.
how do you do that, when if it is removed, there *is* no way to load
the pyjs bootstrap?
pyjs *is* javascript. if there's no bootstrap loader, you can't do
*anything*. except rewrite the entire application as static (useless)
html.
> Only this way we separate the two worlds in a clean way.
.... but they're not separate, are they?
and you appear to have deleted and not acknowledged the point that i
made that having two separate and distinct html loader files is a
complete f*****g maintenance and development pain in the neck.
>> or perhaps having it commented-out <!-- <script .... --> and the
>> pyjsbuild process removing the comments when copying to output/ ?
>>
>> or perhaps having a comment-marker <!-- PYJSBOOTSTRAP -->
>>
>> the advantage of substitution is that in the case where
>> --progress-loader=blahblah it's done entirely from the command-line,
>> there's no need to go editing public/{loader}.html
>
> Actually, it would suffice to add the script tag at the end of the
> html file, just before the closing </body> tag. No comment marker
> needed.
>
> Ist the history iframe needed by pyjd?
strictly speaking, no - but you see what happened by *not* having it?
that recursive damage. i kinda always meant to rewrite the History
stuff _to_ use the history iframe.
> (sorry for my ignorance!) If
> not we could leeave it out and append it together with the bootstrap
> script, too.
actually it would be better if the initialisation (importing) of the
History module resulted in automatic creation and appending of the
history iframe using DOM.
> Et cetera, et cetera. Cleanly separate the two worlds. Completely.
that's not adviseable. i know what you mean, but pick your words
carefully. always think, "how can what i want to do be achieved in
*both* environments".
l.
