2:17 p.m.
Then there's the lovely version issue, when each lib depends on a different
jquery... oops; ) that one shouldn't happen too much, but Its worth
considering... might be easy just to say "you're on your own"
Lincoln Baxter III
http://ocpsoft.com
http://scrumshark.com
Keep it simple.
On Dec 23, 2009 3:09 PM, "Dan Allen" <dan.j.allen(a)gmail.com> wrote:
On Mon, Dec 21, 2009 at 4:12 AM, Werner Punz <werner.punz(a)gmail.com> wrote:
> a) The import part, ...
I just thought it would be
interesting if two components that requested
something like jQuery (even in different libraries) would recognize that
they are both asking for the same thing and just put one of them in the
head. I think that happens automatically if they happen to use the same
resource name. But if they are in different JAR files, then the resource
name won't be the same and a duplicate will be sent. So some sort of global
identifier much be nice for the most popular libraries.
-Dan
-- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #2...
2:22 p.m.
New subject: [jsr-314-open] An observation on where we should focus attention
On Wed, Dec 23, 2009 at 3:17 PM, Lincoln Baxter, III <
lincolnbaxter(a)gmail.com> wrote:
Then there's the lovely version issue, when each lib depends on a
different
jquery... oops; ) that one shouldn't happen too much, but Its worth
considering... might be easy just to say "you're on your own"
Well, in a sense it would be like a Maven dependency in that you have to
specify a version range of compatibility. If the the page attempts to load
different versions, where one is not in the range of accepted versions of
the other, it would throw some sort of compatibility exception (otherwise,
you just get unexpected behavior in the page). I'm speaking fairly high
level here, but certainly worth considering if the goal is the really make
sure we support mixing and matching components.
-Dan
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen
3:01 p.m.
New subject: [jsr-314-open] An observation on where we should focus attention
On 23.12.2009, at 21:22, Dan Allen wrote:
On Wed, Dec 23, 2009 at 3:17 PM, Lincoln Baxter, III
<lincolnbaxter(a)gmail.com
> wrote:
Then there's the lovely version issue, when each lib depends on a
different jquery... oops; ) that one shouldn't happen too much, but
Its worth considering... might be easy just to say "you're on your
own"
Well, in a sense it would be like a Maven dependency in that you
have to specify a version range of compatibility. If the the page
attempts to load different versions, where one is not in the range
of accepted versions of the other, it would throw some sort of
compatibility exception (otherwise, you just get unexpected behavior
in the page). I'm speaking fairly high level here, but certainly
worth considering if the goal is the really make sure we support
mixing and matching components.
While it would be great to have jsf automatically resolve duplicates/
versions, I think sometimes the developers has to get involved, so
first of all it should be possible to map resource-requests to other
resources, so that a user (=developer) could say (.*)jquery(.*).js
maps to lets say a jquery-min-1.2.13.js resource in some other jar or
war.
(This could even be used to replace images of components with one
line, if you allow for references from the matches on the source-
regexp in the target-exp)
While it is possible to do that on your own, I think that could be a
valuable addition to the specs.
Concerning version issues, I don't think we should come up with a
solution (which would probably involve versionnamespacing the included
scripts and the calls to it... ugly!) but as suggested just say
"you're on your own".
Imre
3:13 p.m.
New subject: [jsr-314-open] An observation on where we should focus attention
I like the mapping idea, perhaps with a hook for your minification tool of
choice? One of the ideas I've been rollicking around is: minifaces
:)
Lincoln Baxter III
http://ocpsoft.com
http://scrumshark.com
Keep it simple.
On Dec 23, 2009 4:01 PM, "Imre Osswald" <ioss(a)mx.jevelopers.com> wrote:
On 23.12.2009, at 21:22, Dan Allen wrote: > On Wed, Dec 23, 2009 at 3:17 PM,
Lincoln Baxter, III <l...
While it would be great to have jsf automatically resolve
duplicates/versions, I think sometimes the developers has to get involved,
so first of all it should be possible to map resource-requests to other
resources, so that a user (=developer) could say (.*)jquery(.*).js maps to
lets say a jquery-min-1.2.13.js resource in some other jar or war.
(This could even be used to replace images of components with one line, if
you allow for references from the matches on the source-regexp in the
target-exp)
While it is possible to do that on your own, I think that could be a
valuable addition to the specs.
Concerning version issues, I don't think we should come up with a solution
(which would probably involve versionnamespacing the included scripts and
the calls to it... ugly!) but as suggested just say "you're on your own".
Imre
5841
days inactive
5841
days old
jsr-314-open-mirror@lists.jboss.org
3 comments
3 participants
participants (3)
-
Dan Allen -
Imre Osswald -
Lincoln Baxter, III