The injecting flag is used only by the new yuiloader functionality,
which will resolve and load library dependencies. Before this, you
would need to specify each dep by hand. For some reason, the yui event
prefers to use document.write to create the script node over
document.createElement if not
of the script. Otherwise it will be filtered by URL. So if
you have the contribution twice with same javascript url, it will be
filtered.
-Matej
On 7/19/07, James McLaughlin [EMAIL PROTECTED] wrote:
The injecting flag is used only by the new yuiloader functionality,
which will resolve and load library
what do you mean? that 2.2 didn't use document.write()?
No, I was merely puzzling over why they would use document.write, and
the only place YAHOO_config.injecting is checked is in a condition
that decides whether to use document.createElement or document.write.
Must be some kind of IE quirk.
Done https://issues.apache.org/jira/browse/WICKET-771
thanks,
jim
On 7/19/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
On 7/19/07, Matej Knopp [EMAIL PROTECTED] wrote:
Well, actually, there is none. The reference is filtered only by URL.
You can submit a feature request for adding an ID to
a little clicking around revealed this:
http://wicketstuff.org/confluence/administrators.action
best,
jim
On 6/2/07, Johan Compagner [EMAIL PROTECTED] wrote:
not me. i didn't do anything with confluence on the wicket server
i think igor?
johan
On 6/2/07, Eelco Hillenius [EMAIL PROTECTED]
Great news. Congrats, jbq!
I particularly enjoyed this factoid about bananaman:
the muscles of 20 men, and the brains of 20 mussels.
But I have no doubt that you well exceed the mussel count of your
noble ancestor. I mean, at least double :).
On 5/30/07, Johannes Fahrenkrug [EMAIL
I'm a wicket fanboy, so no apologies if this seems over the top :) :
Wicket is an Open Source project that represents a radical rethinking
of web app development frameworks. Designed from the ground up to
allow the developer to exploit the full expressive power of OOP,
Wicket excels at component
radical (usually is a showstopper word
for the Suitsfraction that often stops new technologies for business
reasons).
Any comments?
-Ursprüngliche Nachricht-
Von: James McLaughlin [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 23. Mai 2007 17:43
An: wicket-dev@incubator.apache.org
it as a attachement in our jira.
That is mostly easier.
johan
On 5/7/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
On 5/7/07, James McLaughlin [EMAIL PROTECTED] wrote:
Jim, if you're reading with us, would you be ok
with granting us official permission?
Certainly, for this code
I prefer this style of programming too, but I think making it mandatory is
probably not a good idea. If someone isn't careful, they can too easily
create leakage passing the panel between pages. I would vote for an
AbstractVelocityPanel as above, and a VelocityPanel as before. This way we
can get
Jim, if you're reading with us, would you be ok
with granting us official permission?
Certainly, for this code and for any other snipplets i may have
contributed :)
best,
jim
fwiw, i've occasionally wanted an onRemove callback in the component (and
now behavior :) ) hierarchy so the object can undo some of its damage when
replaced. If we had this, then we could leave that issue to the developer's
discretion. I've had to use the two phase init pattern occassionally, so
Sweet! Thanks guys for all your hard work.
jim
On 5/2/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
The Apache Wicket team is proud to announce Wicket's first Apache
Incubator release. This release is officially approved by the
Incubator PMC [1].
In this announcement:
- Apache Wicket
- This
fwiw, i would love to see this too.
best,
jim
On 3/28/07, Joe Toth [EMAIL PROTECTED] wrote:
Is this on the radar to be implemented in an upcoming version?
https://issues.apache.org/jira/browse/WICKET-18
Thanks
9 weeks is definitley too long for current 2.0 users to wait before. We all
know that 1 week in developer terms is 2 or 3 human weeks, so this really
leaves us high and dry with no viable codebase for a long period of time.
I'm sure for most of us that means backporting to 1.3, then
On 3/8/07, Jean-Baptiste Quenot [EMAIL PROTECTED] wrote:
* James McLaughlin:
9 weeks is definitley too long for current 2.0 users to wait
before. We all know that 1 week in developer terms is 2 or 3
human weeks, so this really leaves us high and dry with no
viable codebase
It might be worthwhile to keep wicket-stuff-develop so that when it
comes time to coordinate a release or encourage
wicket-stuff-developers to make some changes (like mavenizing their
projects) we won't pollute wicket-user. But for this to work, we would
need to make sure all the project
No doubt that would be great for making announcements regarding
project releases and what not, but for coordinating work I think we
would need more back and forth than an rss feed could provide. I'm
cool with it either way, though.
On 2/7/07, Al Maw [EMAIL PROTECTED] wrote:
James McLaughlin
Agreed. +1
I only brought this up becuase some of us have been reluctant to
create noise on the mailing lists, to the degree that we have
contacted each other off list.
jim
On 2/7/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
but for coordinating work I think we
would need more back and
I ran into this issue a while back and proposed an IOnLoadContributor
interface that kind of mirrors all the good work of IHeaderContributor, but
for script that is inserted anywhere below /head, such as onload, or
script blocks in the actual body.
the html has been rendered. we were discussing about
implementing that as part of wicket to have nice serverside api support
for
it, but havent had the time yet. matej?
-igor
On 1/23/07, James McLaughlin [EMAIL PROTECTED] wrote:
I ran into this issue a while back and proposed
javascript into ajax request target during ajax render
void onRendered() {
if (isajaxrequest()) {
AjaxRequestTarget t=RequestCycle.get().getRequestTarget();
t.appendjavascript(javascript.getobject());
}
}
}
-igor
On 1/23/07, James McLaughlin [EMAIL PROTECTED
Hello,
I have a need for an interface that is a twin to IHeaderContributor, but
which will contribute javascript to be executed after the html has been
rendered on the client. I realize all the hooks are there with
WebPage.getBodyContainer().addOnLoadModifier(), and
23 matches
Mail list logo
