Scott, I raised this issue first under the assumption that complex
applications load Trinidad scripts, Tomahawk scripts, their own scripts,
and so on.
If every library says "I need my scrips, thus I load them on my own",
that application ends up in overall loading scripts multiple times.
This affects performance AFAIK, so a centralized - independent script
loader would solve this issue for *all*. I guess Jaws covers exactly
this role.
Otherwise in the above scenario we would need at least three atomic
loadings, assuming private scripts are packed by Jaws.
-- Renzo
Scott O'Bryan wrote:
I think Matthias misunderstood. <trh:script> is a replacement for the
<script> tag in html. :) I believe you are asking why we don't have
an option to disable loading our scripts automatically.
I guess my answer to that question would be why? Wouldn't such an
option just cause errors unless people really knew what they were
doing? I mean the trinidad components REQUIRE the script to be
there. So make users even know about it? I'm also still questioning
why we would need Jawr to load our javascripts in the first place.
That said, I wouldn't mind supporting a plugable "script loader" in
Trinidad if people were really wanting to plug in Jawr, but we should
still ask what it gains us.
Scott
Jordi Hernandez wrote:
Well, actually I know nothing about Trinidad. Scott said "currently
there is
no way to
have trinidad NOT link to the common js". I imagined that it means
that some
files will be always linked automatically. So you could not link the
common
js with Jawr. Maybe I misunderstood?
Regards, Jordi.
Mathias Walter wrote:
Hi,
I hope I'm not too pretentious by saying this, but maybe Trinidad
should
offer an option to let users load the scripts themselves. Not
Indeed, Trinidad has such an option: <trh:script>
--
Kind regards,
Mathias
