Alex Objelean wrote:
>The logic is simple: if you check a node - the checked Role is added to
> the list of selected Roles, otherwise it is removed from the list. At the
> same time, if you check a child - all the ancestors changes theirs state to
> intermediate (if their current state is unche
Johan Compagner wrote:
> for others not in ##wicket:
>
> the pagemap in the bookmarkable url can be get through the
> RequestCycle.urlFor(PageMap,Class,Params) method call
> give a pagemap there and the url will contain the pagemap param that
> will be used to hold the page in when it is clicked.
t the same component in whose markup the
fragment is defined ( the page )
does that make any sense?
-Igor
On 5/9/06, JasonB
<[EMAIL PROTECTED]>
wrote:
Juergen
Donnerstag wrote:
> you need to register it. It is not yet activated by default
> applicatio
Juergen Donnerstag wrote:
you need to register it. It is not yet activated by default
application.getPageSettings().addComponentResolver(new
FragmentResolver());
Strangely enough I just used fragments over the weekend and didn't have
to set this setting. What confused me was not having to add
If I guessed right as to what you are asking... Basically, when your
drop down has a value, you want to 'un-hide' another part of the page.
In your case a form. The most conventional way I know of is to override
the 'isVisible' method for the component you want to hide & unhide. In
the code sni
Jonathan Locke wrote:
makes me wonder if Java couldn't use a reflection notation
I have always thought this would be a great feature. (As a side note,
how hard would it be to write an eclipse plugin that would perform
compile-time checking, but would pass a string to the compiler? Aka: new
Johan wrote an answer earlier that you should use a regular expression
validator.
I believe he was referring to the following class:
wicket.markup.html.form.validation.PatternValidator
What problems are you having with this class and/or solution?
- Jason B.
ketan gote wrote:
hi
i want to v
2. Do the constructor change in a seperate release (Wicket 1.3) and
put Java 5 in the next (Wicket 2.0)
The constructor change is a major change. Would you rather support an
old and different version (1.2), or an old version that is much closer
in a major way to the 'current' version?
I vot
As Jesse referenced, once we move to Java 1.5 we can still release Java
1.4 versions via tools such as Retroweaver... assuming that the tool
works as advertised. Has anyone had more experience in these types of
tools?
- Jason B.
Jesse Sightler wrote:
I'm completely in favor of jumping to
The WebWork mailing list is integrated with their online forums via
"Jive Forums". Basically, if someone posts via the webforms, the email
contains the following blurb:
-
Posted via Jive Forums
http://forums.opensymphony.com/t
Whatever you want to call it, I'm advocating that something "like DataView" be packaged officially with Wicket. If we can
agree on that, it's a start.
Sure, if its hard for people to find or if it will improve newbie
experience, then maybe it should be packaged with wicket.
11 matches
Mail list logo
