maybe wicket 2.0 can refactor the components hierarchy to use the bridge
pattern?
for example, i want a Calendar component that will be implemented with
jscalendar, yui calendar etc. making Calendar abstract and extending it with
YuiCalendar is not efficient if there are other implementations
Hi,
I've checkout the entire branch of WICKET_1_2 (wicket,
wicket-auth-roles, wicket-auth-roles-examples, ... etc) and it builds
fine. Probably because there is pom.xml in the branch folder.
I've also checkout just the wicket directory as separate project, tried
to build it and get the same
Eelco did that:do not set application settings automatically. 1) I don't agree with it, because this multi
window support is about more than just supporting the back button 2)
Even if we wanted to prevent that setting, it should check and throw an
exception if set, rather than quietly setting it
Sspitting out the javascript for SecondLevel model does make little sense.
So while I agree that changing application settings silently is not the
best practice, neither is doing nothing. Most of the user will not be
aware what multi window support does and that they should turn it off
with
Maybe you could be more explicit in what you mean?
The differences between those versions would primarily be in the
different javascript/ css dependencies they use, which is easy to
configure using header contributors. And they would need some
different initializations, which you could maybe do
everything is doable, the question is about design (not if i can make it work,
but if i can make it work reusing code, easy to change etc.)
say i have YuiButton and YuiMenu, both need to contribute the same js to the
header. now i want to reuse the code that adds this header contribution. I can
If you are not using the whole branch of WICKET_1_2 as your
development workspace for Wicket (shame on you!), but prefer to check
out individual projects, you will find it hard to get the parent pom.
This next subversion statement will get you the parent pom, which you
can then install into the
why dont we just publish it to sateh's mirror or our server and include that in the child poms as a mirror?-IgorOn 7/5/06, Martijn Dashorst
[EMAIL PROTECTED] wrote:
If you are not using the whole branch of WICKET_1_2 as yourdevelopment workspace for Wicket (shame on you!), but prefer to checkout
If that's what you want, why not do something simple like this?
public interface IComponentFactory {
Button createButton(MarkupContainer parent, String id);
}
class YuiComponentFactory implements IComponentFactory {
public Button createButton(MarkupContainer parent, String id) {
Eelco Hillenius wrote:
If that's what you want, why not do something simple like this?
public interface IComponentFactory {
Button createButton(MarkupContainer parent, String id);
}
class YuiComponentFactory implements IComponentFactory {
public Button
Hi All,
Did someone in this group hit the StringIndexOutOfBoundsException?
I am getting this exception when I change selection in a
DropDownChoise component that has
wantOnSelectionChangedNotifications set to true. It looks like it is
related to CryptedUrlWebRequestCodingStrategy and
Hi
There's a known problem with head contribution of components, that are
not rendered when the whole page is (are hidden or not even part of
hierarchy), but are additionally rendered using an AJAX call.
The problem is, that while the body of the component is placed in the
page, the head
We (on ##wicet, Frank coded an example) just did that, and that seems
to work fine.
Eelco
On 7/5/06, Johan Compagner [EMAIL PROTECTED] wrote:
if you add css or javascript to the head of the page at runtime in a dynamic
way
is it then seen in the browser??
We should first test that.
johan
Adding both javascript and stylesheets seems to work, at least for
non-inline javascript and css. Still have to test inline stuff.
-Matej
Johan Compagner wrote:
if you add css or javascript to the head of the page at runtime in a
dynamic way
is it then seen in the browser??
We should first
Matej Knopp wrote:
Adding both javascript and stylesheets seems to work, at least for
non-inline javascript and css. Still have to test inline stuff.
I tested inline javascript, works well. Inline styles work too, but in
IE you have to use document.createStyleSheet for it to work.
I tested
15 matches
Mail list logo
