He is a core dev - just listen to him :P
ok, simple treeNode would be:
wicket:panel
IM A NODE
div wicket:id=content-/div
/wicket:pane
and Java:
class TreeNode extends Panel {
public TreeNode(String id, AnyOtherPossibleThingsYouNeed o) {
Thanks for that man... well I was able to get something to work from
that.however I will give a full throttle try tomorrow...will be heading
towards the forums again incase i get any problems
vishy
Korbinian Bachl - privat wrote:
He is a core dev - just listen to him :P
ok,
Nevermind I was able to get it to work
vishy
[EMAIL PROTECTED] wrote:
Hi,
with newNodeComponent in the BaseTree class i can specify a different
component for my treenode, but this is the same for all node. Is it
possible
setting different treenode component for added a different type
Can you point me to an example or explain a little more about this
Thanks
Vishy
Martijn Dashorst wrote:
iirc using a page instead of a panel works better and has less
bugs/quirks.
Martijn
On Fri, Aug 1, 2008 at 10:22 AM, steviezz [EMAIL PROTECTED]
wrote:
As you can see from
package wicketapp;
import org.apache.wicket.markup.html.link.Link;
import org.apache.wicket.markup.html.panel.Panel;
/**
*
* @author alearchlinux
*/
public class LogoutPanel extends Panel {
public void LogoutPanel(String id) {
super(id);
.
}
}
I filled a bug: https://issues.apache.org/jira/browse/WICKET-1768
-- Lars
On Wed, Jul 30, 2008 at 5:52 PM, Igor Vaynberg [EMAIL PROTECTED] wrote:
yep, file a jira issue
-igor
On Wed, Jul 30, 2008 at 1:53 AM, lars vonk [EMAIL PROTECTED] wrote:
Hi,
I have the following simplified
remove the void before your constructor
On 8/2/08, alex2008 [EMAIL PROTECTED] wrote:
package wicketapp;
import org.apache.wicket.markup.html.link.Link;
import org.apache.wicket.markup.html.panel.Panel;
/**
*
* @author alearchlinux
*/
public class LogoutPanel extends Panel {
insom wrote:
new DropDownChoice(period,
new PropertyModel(myObject, period),
periods,
new ChoiceRenderer() {
public String getDisplayValue(Object object) {
int period = ((Integer) object).intValue();
switch (period) {
case 1: return Day;
...
default:
Use AjaxPagingNavigator. You cannot use normal (non-ajax) links inside
a ModalWindow (like standard PagingNavigator does) because then the
whole page is refreshed.
--
Daniel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Or use a Page inside the modalwindow instead of a panel. Then it uses
an iframe, and that does work with normal links iirc.
Martijn
On Sat, Aug 2, 2008 at 12:51 PM, Daniel Stoch [EMAIL PROTECTED] wrote:
Use AjaxPagingNavigator. You cannot use normal (non-ajax) links inside
a ModalWindow (like
You can do without the ChoiceRenderer if you put your terms in a
property file next to your panel/page:
A.java
new DropDownChoice(period, ...) {
protected boolean localizeDisplayValues() {
return true;
}
}
A.html
select
Many Thanks!!! :handshake:
Martijn Dashorst wrote:
remove the void before your constructor
On 8/2/08, alex2008 [EMAIL PROTECTED] wrote:
package wicketapp;
import org.apache.wicket.markup.html.link.Link;
import org.apache.wicket.markup.html.panel.Panel;
/**
*
* @author
Thanks Vishy ,
this is i am already doing , issue is my ajax code is not firing , it only
fire when i click the check box. i didn't understand why it is not firing on
uncheck.
rit
vishy_sb wrote:
Well you need to put the component (say component) which you want to make
invisible into
Yes the code that you are putting in is for an onUpdate() method which means
that whenever the state of the checkbox gets changed only then the code will
be executed. So if you check it, something should happen and when you
uncheck it then again something should happen.
Also did u try to use the
Go Here
http://www.wicket-library.com/wicket-examples/ajax/modal-window.3
Look at Modal window example with Page.
vishy_sb wrote:
Can you point me to an example or explain a little more about this
Thanks
Vishy
Martijn Dashorst wrote:
iirc using a page instead of a panel
Martijn Dashorst wrote:
WIth regards to the TinyMCE editor, why didn't you maintain it on the
wicketstuff repo? That is the place where people expect the component
to be. Having an unmaintained component and an invisible one elsewhere
doesn't sound like a good way to move the TinyMCE
16 matches
Mail list logo
