Martijn Dashorst schrieb:
The benefits of unix:
find jdk-1.4/wicket -name *.js | xargs grep -E rag|rop
delivers
jdk-1.4/wicket/src/main/java/org/apache/wicket/ajax/wicket-ajax.js
Martijn please don't hit me for this, or as a former college of mine
always says: grep is one of the most
And the best thing about these unix commands is that they are so obvious :)
Eelco
On 6/21/07, Martin Funk [EMAIL PROTECTED] wrote:
Martijn Dashorst schrieb:
The benefits of unix:
find jdk-1.4/wicket -name *.js | xargs grep -E rag|rop
delivers
That's were 'ctrl' + 'r' comes into play.
Figure it out once and your history never forgets:-)
And if it does beefing up 'export HISTSIZE=5000' might help.
mf
Eelco Hillenius schrieb:
And the best thing about these unix commands is that they are so
obvious :)
Eelco
On 6/21/07, Martin Funk
On 6/22/07, Martin Funk [EMAIL PROTECTED] wrote:
That's were 'ctrl' + 'r' comes into play.
Figure it out once and your history never forgets:-)
And if it does beefing up 'export HISTSIZE=5000' might help.
Indeed :) I also keep a document around with my favorite tricks.
Though I'll never be
hi,
just found the file mentioned in the subject and since the corresponding
.java file was deleted with rv. 459972 the .html file should be deleted too.
anyway, i was just wondering...
gerolf
Hi,
Why you have to implement a new PortletRequestCycle? Take a look at
PortletActionRequestCycle and PortletRenderRequestCycle, and the
default getDefaultRequestCycleFactory method from
PortletApplication. As you can access all the original portlet
Action/Render Request/Responses from
Gerolf Seitz wrote:
just found the file mentioned in the subject and since the corresponding
.java file was deleted with rv. 459972 the .html file should be deleted
too.
Heh. Done. Thanks.
Regards,
Al
--
Alastair Maw
Wicket-biased blog at http://herebebeasties.com
Hi
Im starting up a stuff project. Which are gonna be about input events,
mouse and key events.
I've been thinking about these features:
1. event triggering a component (forexample submitting a form)
2. chaining component events (selecting a radio and going to the next
component),
Why you have to implement a new PortletRequestCycle?
Because I do a custom-error-handling, as you can see in the following
fragment of the already-posted-snippet (onRuntimeException):
protected IRequestCycleFactory getDefaultRequestCycleFactory() {
...
public Page onRuntimeException(Page page,