You are using 1.2.x? To me it sounds like a bug that WicketTester or
MockWebApplication does not look into the application properties file
as a normal Application does. We should simply look at the config of
normal application and copy the one line of config into WicketTester.
Juergen
On 3/7/07,
Ok, thank you.
Hmm... I want to embedd into my HTML template some svg graphics. This is
just only for Firefox, or IE users with the adobe plugin. That means, I need
that Firefox turns on its XML parser, so I would need to use XHTML, because
if the file has the file extension html it doesnt
Ok, I've figured it out!
using xml as Markup Type will do everything I need!
Thank you for the tips!
Martin.
Martin Dames wrote:
Ok, thank you.
Hmm... I want to embedd into my HTML template some svg graphics. This is
just only for Firefox, or IE users with the adobe plugin. That
Martin Dames wrote:
Hmm... I want to embedd into my HTML template some svg graphics. This is
just only for Firefox, or IE users with the adobe plugin. That means, I need
that Firefox turns on its XML parser, so I would need to use XHTML, because
if the file has the file extension html it
Hi,
I'm using wicket1.2.jar
Recently I noticed that giving no type attribute inside input tag of a
Wicket Button
results in the Button being displayed as textfield.
The same is true for textfields, but it doesnt really matter in that case
:).
I guess this could be corrected in java code so
No, that would mean magic from the Wicket side, which we try to
minimize as much as possible. Wicket doesn't know your intentions with
the markup or the designers intentions. If you look at the html file
in a browser directly you would see the same thing. This
previewability would be lost if we
Hey,
yes I know, but Firefox 1.5 and better 2.0 can do svg quite good. 3.0 even
better. I tried that out, much faster. All non-firefox users are simply not
my problem! Sounds arrogant? Hehe.. its just a study project!
Martin.
Al Maw wrote:
Martin Dames wrote:
Hmm... I want to embedd into
On Mar 6, 2007, at 2:12 PM, Eelco Hillenius wrote:
1) Who uses 2.0 for serious projects?
We're using 1.2.x for now.
2) What do you think of the constructor change? Do you prefer 1.3's
add style or 2.0's style of passing in the parent construction time.
Absolutely prefer the 1.3/1.2 style.
I have tried to use dropdown menu in one of my projects. NavMenu has been
broken in that time (and I didn't figure out how to patch it) and my effort
in integrating TigraMenu wasn't succesfull either. Finally I have used the
approach which uses a pure CSS menu which is based on the :hover class.
On Mar 7, 2007, at 7:31 AM, Ryan Sonnek wrote:
Just my 2 cents, but considering the *massive* API changes in other
opensource projects when releasing a major version, i don't think
providing users with an easy upgrade path is that important.
Look at struts for example. version 2.0 is a
I know this is very low-tech, but I just arrange my links into a nav-looking
structure. Since they will auto-disable if they link to self (same page),
they form a kind of menu where you can see where you are. This has been
good enough for most of what I do, without hardly any coding (as a
Hello,
We're running into a problem that is probably not in wicket itself, but
perhaps someone here has also run into it.
We have a form with a TextField which has a validator. When the user
leaves the field, the validation is of the field is called though AJAX.
On our development/testing
* Eelco Hillenius:
going the other way 2.0-1.x should be trivial
This is true. At least it should be a lot easier.
I wouldn't be so confident. In 1.x very often we need to refrain
doing things in the constructor, and have to override onAttach()
to access the parent. So it's not
FWIW there is a JIRA issue for this already:
http://issues.apache.org/jira/browse/WICKET-346
Nathan Hamblen's suggestion to have a fallback font is good:
font-family: 'Lucida Sans', 'Helvetica', 'Sans-serif', 'sans';
Where shall we change that?
--
Jean-Baptiste Quenot
aka John Banana
Same here, having rolled out a 1.2.3 project with no need for updating,
and currently in the final stages of a 1.2.5 project, which will
eventually update to 1.3 if it comes out. Never did any tests beyond 1.2.
Regarding the constructor change:
the 1.x way of compiling the hierarchie via add()
I don't care about (understand) the pros and cons regarding the
constructor change. What Wicket needs is parameterized models
(generics). I think you should do what ever it takes to support this in
a released version as soon as possible.
/Anders
Gabor Szokoli wrote:
On 3/7/07, Korbinian
Yes, that's the problem! But it looks even worse on my computer... I think I
have installed a bad font or something..
On my laptop it looks fine (yesterday I told it didn't but after I checked
again it really did!) so I will compare the font list tonight and let you know.
The problem was
... and having two active development branches seems like a really bad
idea. /Anders
Anders Peterson wrote:
I don't care about (understand) the pros and cons regarding the
constructor change. What Wicket needs is parameterized models
(generics). I think you should do what ever it takes to
Hi,
I'm trying to get working a panel containing a TextField and a Label.
The label contains the hex value for the TextField content. The
TextField is Ajaxed so that it updates the label on each key press.
Unfortunalty, I cannot retrieve the value from the TextField, it always
returns a null.
I had also hoped that the new Constructor in 2.0 would have been useful.
But, I have been using the following solution in 1.2 / 1.3 to overcome not
having the parent at Component construction time. Then, all of my Panels
extend this Panel instead of the core Panel. It has been working for me
How about a hybrid system?
Is there a clear-cut way to know up-front which components have an
immutable parent versus others that might require it to change during
rendering time? If so, couldn't you require the use of constructors that
take a parent for components whose parents
I have an HTML document where I want to conditionally include (or exclude)
based on the type of user. For example, I might have a span that contains a
link to an administrator page that I only want shown of the user is an
administrator user. Is there a convenient way to only include the span
Hi,
In my form,
I have provided radio choices r1,r2,r3,etc based on whose selection I have to
change a panel's(id is p1) model object and display the panel corresponding to
that in UI.
I have used components RadioGroup, Radio to implement this.
I need to do this using Ajax.
Taking hint from,
On Thursday, 08 March 2007 01:23 am, Eelco Hillenius escreveu:
The big question there is whether you know all items beforehand or
not. If yes, integrating with any javascript library is easy. If not,
you need a tree, and probably can best look at that component or
navmenu
On Thursday, 08 March 2007 01:24 am, Eelco Hillenius escreveu:
Did you look at the examples project? Plenty of examples on repeaters.
Yes, but I don't see one that changes the column style that uses
PropertyColumn. That doesn't mean there isn't one, I just haven't seen one.
I think
is there a way to tell a markup to not go into the MarkupCache. I'm
overloading newMarkupResourceStream which will change on every page but it
is being put in the cache and never getting run again. There is
MarkupCache.clear() but that seems to much just to remove one
markupcontainer. can i
override the last modified time of the IREsourceStream you make
and return always the System.currentMillis()
johan
On 3/8/07, Scott Lusebrink [EMAIL PROTECTED] wrote:
is there a way to tell a markup to not go into the MarkupCache. I'm
overloading newMarkupResourceStream which will change
This only works in 1.3/ 2.0, but let your component implement
IMarkupResourceStreamProvider and IMarkupCacheKeyProvider. Then, let's
getCacheKey return null and your markup will never be cached.
Eelco
On 3/8/07, Scott Lusebrink [EMAIL PROTECTED] wrote:
is there a way to tell a markup to not go
How about a hybrid system?
Is there a clear-cut way to know up-front which components have an
immutable parent versus others that might require it to change during
rendering time? If so, couldn't you require the use of constructors that
take a parent for components whose
Hey all,
I've got a custom component (drop down of AjaxLinks) which extends
Panel. I would like for this component to be able to use an ajax
indicator. How can I do this? Can I just have that component implement
IAjaxIndicatorAware? When I use the indicatorAppender as part of this,
it does
going the other way 2.0-1.x should be trivial
This is true. At least it should be a lot easier.
I wouldn't be so confident. In 1.x very often we need to refrain
doing things in the constructor, and have to override onAttach()
to access the parent. So it's not just about
Alternatively:
1) Components are POJOs. Users can define whatever constructor they want.
2) Users always use add() to associate a parent with a component but you
move the component wiring out of the constructor and into a onWire()
method. Now, whenever the hierarchy/parent changes
When selecting a item from the autocomplete drop down, the onchange event
handler on the input is not called. The wicket-autocomplete.js needs to be
modified to call the onchange function explicitly. the changes should include:
case KEY_ENTER:
if(selected-1){
To summarize this: it's really only the constructor change that is in
question here. Whatever happens, the other features including generics
support will be in a version of Wicket, whether we call that 1.4 or
again 2.0.
The constructor change is the main reason why it is difficult to
maintain the
havent looked at your code but here is how i would do it
class mypanel extends panel {
private String value;
//getter+setter
public mypanel() {
TextField tf=new TextField(tf, new PropertyModel(this, value));
Label l=new Label(l, new propertyModel(this, value));
Try something like
startDate.getModelObject()
or address the form's model
vacationForm.getModelobject.getTextfield's property name
Stefan LIndner
winmail.dat-
Take Surveys. Earn Cash. Influence the Future of
Hey all,
I've got a custom component (drop down of AjaxLinks) which extends
Panel. I would like for this component to be able to use an ajax
indicator. How can I do this? Can I just have that component implement
IAjaxIndicatorAware? When I use the indicatorAppender as part of this,
it does
WebMarkupContainer adminSpan=new WebMarkupContainer(admin-span) {
public boolean isVisible() { return getsesion().getuser().isadmin(); }}
if you have a lot of components in that span and you dont want the overhead
of creating them make the span a panel or a fragment and add it or an empty
how about a jira issue with a patch? :)
-igor
On 3/8/07, David Robison [EMAIL PROTECTED] wrote:
When selecting a item from the autocomplete drop down, the onchange event
handler on the input is not called. The wicket-autocomplete.js needs to be
modified to call the onchange function
this wont work.
-igor
On 3/8/07, cowwoc [EMAIL PROTECTED] wrote:
How about a hybrid system?
Is there a clear-cut way to know up-front which components have an
immutable parent versus others that might require it to change during
rendering time? If so, couldn't you require
the advantage is that the error points you to the place in java code where
the problem is instead of a place in markup.
-igor
On 3/8/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
I have been using 1.2.4 for some days. I think the current construct
works
well. If there is no overwhelming
We've gathered a lot of opinions by now (more are still welcome
though!) and I think we should let this sink in for a bit.
There are a couple of projects being built on 2.0 (see the replies in
this thread, but also
http://www.mail-archive.com/general@lists.ops4j.org/msg00240.html),
but so far,
Well, the model never actually gets changed. I must be missing something,
the new value of the field never gets back to the server. Anyone know why
this would be or if there's a better way to do this?
Jason
On 3/8/07, Stefan Lindner [EMAIL PROTECTED] wrote:
Try something like
see AjaxFormComponentUpdatingBehavior
AjaxEventBehavior doesnt send over the value of the form component, just
triggers a roundtrip
-igor
On 3/8/07, Jason Roelofs [EMAIL PROTECTED] wrote:
Well, the model never actually gets changed. I must be missing something,
the new value of the field
Who will build the first vote engine using wicket so we will not have to
vote in the mailling list directly? :)
On 3/8/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
We've gathered a lot of opinions by now (more are still welcome
though!) and I think we should let this sink in for a bit.
There
the behavior checks if it or the component it is attached to implement
IAjaxIndicatorAware. what it then does is display:; to show whatever dom
element has the id returned by IAjaxIndicatorAware when the ajax request is
initiated, and then display:none; when the ajax request is finished.
also
All things equal I prefer the 1.x add() syntax, however I don't have a
good feel for the advantages/disadvantages that add() vs. new provide.
What I really want is generics/models.
Scott
-
Take Surveys. Earn Cash. Influence
Ok, that did it. Thanks again Igor.
Jason
On 3/8/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
see AjaxFormComponentUpdatingBehavior
AjaxEventBehavior doesnt send over the value of the form component, just
triggers a roundtrip
-igor
On 3/8/07, Jason Roelofs [EMAIL PROTECTED] wrote:
Well,
youre welcome
-igor
On 3/8/07, Jason Roelofs [EMAIL PROTECTED] wrote:
Ok, that did it. Thanks again Igor.
Jason
On 3/8/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
see AjaxFormComponentUpdatingBehavior
AjaxEventBehavior doesnt send over the value of the form component, just
triggers a
In Wicket 2 thete is a thing called AjaxFormComponentUpdatingBehavior
A behavior that updates the hosting FormComponent via ajax when an event it is
attached to is triggered. This behavior encapsulates the entire form-processing
workflow as relevant only to this component so if validation is
Speaking of, is AjaxFormSubmitBehavior broken in the current 1.x
snapshot, or is it just me?
Nathan
Igor Vaynberg wrote:
see AjaxFormComponentUpdatingBehavior
AjaxEventBehavior doesnt send over the value of the form component, just
triggers a roundtrip
Just dropping into the conversation (sorry, if its off topic): if you
need to get the value of a single cell, you can use (a variation of) the
code attached to https://issues.apache.org/jira/browse/WICKET-176. I use
it to validate just one field.
Regards,
Erik.
Nathan Hamblen wrote:
or do you need to have each tab have it's own form?
And if each tab has it's own form, does the user need to save their data
before switching tabs?
Would the submit button be on each form, on each tab, or outside the tabs
entirely?
Thanks.
That's why I used the terminology onWire() as opposed to onAdd(). My
point was that you should shift the burden of isInitialized() away from
the end-user over to Wicket. When a component's ancestors (all the way
up to the top-most component) are connected the first time or changed at
some
what happens when you move the component to another parent? will onWire be
called again? and if not can we have a method that will please? and then
another method if the component's hierarchy changes - a components ancestor
is moved.
point being only a small percentage of wicket components care
It looks like quite a few people, more than I expected in fact,
weren't that crazy about the constructor refactor in the first place,
though some people like it better in general (me being one of them
though I see disadvantages as well, but also
Hi!
Two design questions for experienced wicket users... Mail is a bit long.
I apologise for this, but I wanted to explain the situation well.
We have been using wicket now for a while, and I think it's time to try
to finally clean up our code a little. With that in mind, I have two
questions
here are my short answers :) ask more if you need something explained in
detail
On 3/8/07, David Leangen [EMAIL PROTECTED] wrote:
First Question: Controller Logic
The idea sounds good, but I'm wondering if this is even necessary. It
was suggested to me that
Using Wicket 1.2.5 / Spring 2.0.2
Is it possible (or reasonable) to inject Page model implementations with the
@SpringBean annotation? I've tried this with prototype-scoped beans. The
problem is that if I submit a form with an injected model object and leave
the page, then come back later, the
prototype beans are not supported just yet, there is a patch for that and a
vote to apply to 1.2.x
-igor
On 3/8/07, Jonathan Cone [EMAIL PROTECTED] wrote:
Using Wicket 1.2.5 / Spring 2.0.2
Is it possible (or reasonable) to inject Page model implementations with
the
@SpringBean annotation?
Great! Thanks for this. Very helpful!
This does give a lot of ideas, indeed. If my understanding is correct,
this would indeed provide a very elegant solution to what we're trying
to do.
One precision:
you have to decide what is clearly business logic vs ui logic. the
business logic should
The point *was* that onWire should get called whenever the parent
changes (i.e. when moving a component to another parent). If one wishes
to listen for hierarchy changes one could implement some event listener
mechanism to that effect by overriding onWire() of the ancestor nodes
and have
my point is that we are a framework and we already provide what is needed to
make this and the entire superset of these kinds of things possible. our job
is to provide functionality needed for 90% of usecases and leave the other
10% possible. this falls into the 10%.
-igor
On 3/8/07, cowwoc
-- before voting we should compare them by given usecases and construct it
with 1.x and 2.x constructors.
I prefer
1 rich internet application
2 highly personalized user interfaces for portal
3 CMS
to be our usecases.
Eelco Hillenius wrote:
We've gathered a lot of opinions by now (more are
feel free to go ahead and do that. looking forward to your analysis.
-igor
On 3/8/07, aozster [EMAIL PROTECTED] wrote:
-- before voting we should compare them by given usecases and construct
it
with 1.x and 2.x constructors.
I prefer
1 rich internet application
2 highly personalized user
I know how to do it with 1.x (actually already done some of them in previous
project) , but I don't know how to do it with 2.x constructors, can you give
me a clue if I want to create something like that?.
igor.vaynberg wrote:
feel free to go ahead and do that. looking forward to your
On 3/8/07, David Leangen [EMAIL PROTECTED] wrote:
This is actually something I'm kinda struggling with.
In our model, the biz logic is the query. So, for instance, if I have
two radios and a group of checkboxes:
( ) Any colour
( ) Choose colours
[ ] Blue
[ ] Red
...
If
Hi all
As said earlier, I'm beginning with Spring and I find it a bit hard to
know how to design my application with it.
Let me give an example : in order for the end user to register, I've a
registration form. Up to now, I've a registrationBean which isn't
managed by Spring. On the form submit,
Hello ZedroS,
You ask very difficult questions which are not easy to answer. The
ability to answer comes with years of practice and learning. I can
recommend reading some books on design patterns.
I /can/ provide some very rough guidelines:
- put similar things in the same place (do not
Hi ZedroS,
you could check out the wicket pastebin at
http://developer.berlios.de/projects/wicketpastebin/ which uses wicket
and spring.
I personally think using only the interfaces in your code is usually a
good idea. If you want to avoid XML and don't mind dabbling with
experimental code then
70 matches
Mail list logo
