Re: Can script determine if window.onload has already fired?
- From: beegee <bgulian@xxxxxxxxx>
- Date: Mon, 30 Nov 2009 06:50:56 -0800 (PST)
On Nov 29, 10:02 pm, David Mark <dmark.cins...@xxxxxxxxx> wrote:
On Nov 29, 8:47 pm, beegee <bgul...@xxxxxxxxx> wrote:
Mostly, again, what I've seen of the modular approach is the 10 pages
with the same decoration or worse, server-side generation of HTML.
You feel every page should have a different decor? Perhaps you are
subscribing to the belief that the background image, scripts, etc.
will be downloaded every time the user navigates? That's not true.
No, my point was that the web site is better served by having one page
that dynamically generates different display depending on downloaded
(via AJAX) content. In this way you can keep the same decord without
resorting to the braindead scheme of using ten different pages just
because your content changes.
And what is wrong with "server side generation of HTML"? That is
where most HTML is generated.
It shouldn't be, in my opinion. It is far easier to use server-side
generated *data* to generate html, client-side.
In fact, I think a
discussion of different "web patterns" would be really useful, like
MVC Server, MVC Client, Mixed html and server-side, client-side js
called web services.
No, client-side JS is not called Web services. I have seen attempts
to replace needed server side processing with pure client side script
in the name of using "Web services". That's how to turn something
simple that works for everyone on the planet into a dicey crap shoot
that works for some and does unexpected things for others. Somehow,
this is seen as a "cool" and progressive thing to do. But results
that developers don't expect won't lead to good experiences for users,
QA, support, etc. That's not cool at all (simply incompetent). ;)
Sorry, late at night for me. I meant "client-side js calling web
services." But no, now you're over-generalizing. Using web services to
retrieve data in order to generate UI elements and content is a very
nice way to separate business logic and UI.
I'm sure there's a pattern for on-demand
javascript.
I don't believe there's an atom of meaning in it.
Ok, you're being a little fuddy-duddy here. I hope in taking up the
anti-jQuery banner, I haven't sided with a bunch of arch-conservative
javascript programmers ;)
Bob
.
- References:
- Re: Can script determine if window.onload has already fired?
- From: Evertjan.
- Re: Can script determine if window.onload has already fired?
- From: wilq
- Re: Can script determine if window.onload has already fired?
- From: David Mark
- Re: Can script determine if window.onload has already fired?
- From: beegee
- Re: Can script determine if window.onload has already fired?
- From: Thomas 'PointedEars' Lahn
- Re: Can script determine if window.onload has already fired?
- From: beegee
- Re: Can script determine if window.onload has already fired?
- From: David Mark
- Re: Can script determine if window.onload has already fired?
- Prev by Date: Re: Can script determine if window.onload has already fired?
- Next by Date: Re: Can script determine if window.onload has already fired?
- Previous by thread: Re: Can script determine if window.onload has already fired?
- Next by thread: Re: Can script determine if window.onload has already fired?
- Index(es):
Relevant Pages
|