Thanks Eelco, Frank,
1.3 it will be.
Regards,
Erik.
--
Erik van Oosten
http://day-to-day-stuff.blogspot.com/
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get
I am evaluating frameworks wrt a new project I will be working on.
The application requires a richish user interface (don't they all now!)
The 'richest' user case is
1) The user starts entering the name of a client into a text field.
2) After entering a few letters they enter a special
What comes close is Wicket's autocompletion field. It works just like
google's autocompletion. It is quite flexible and easy to use.
Regards,
Erik.
richard schmidt wrote:
I am evaluating frameworks wrt a new project I will be working on.
The application requires a richish user
looks not very complex -
base would be the Autocomplete Example
http://www.wicket-library.com/wicket-examples/ajax - Auto Complete...
rest is a bit CSS playing + Contentvalidating - only the point with the
keystroke would need add. ajax and seems odd to me as i dont know a secure
way to
* Igor Vaynberg:
On 3/26/07, Toscano [EMAIL PROTECTED] wrote:
I mean:
- The combo-option is treated as a new tag attribute, not as the name of
the
tag. Is there any way of maintain that - there?
what wicket version are you using? this might be a bug in our xml parser.
please open a
Hi.
I have a problem in that inside the constructor of a page(panel actually) i
invoke a stored procedure which needs to get the model for the panel. The
stored procedure may throw an error message. The error message should be
seen by the user, he can understand what he did wrong. So inside the
I'm a divorced Struts programmer the breakup took place when I found
Wicket. So I'm new to Wicket and I have a question about
Model/DropDownChoice/Domain Object updating.
Sorry about the long email.
Here is my question:
How do I update the Buyer object with a different Profile object if the
You component is not attached to a parent yet.
You could try doing that work in onAttach().
serban.balamaci wrote:
Hi.
I have a problem in that inside the constructor of a page(panel actually)
i invoke a stored procedure which needs to get the model for the panel.
The stored procedure
On 3/31/07, Kurt R. Hoehn [EMAIL PROTECTED] wrote:
Wicket 2.0-SNAPSHOT
Wicket-Spring 2.0-SNAPSHOT
wicket 2.0 has been discontinued for various reasons. you might want to
switch your project to the 1.x branch.
new DropDownChoiceProfile(form, profile,
If you're using Tomcat, try the persistent manager with the file or
JDBC based store.
http://tomcat.apache.org/tomcat-5.5-doc/config/manager.html
-Ryan
On Mar 30, 2007, at 8:55 AM, dukejansen wrote:
Does anyone have any good recommendations for how I get started
with second
level
That worked great! Thank you for the assistance and advice.
-kurt
On Sat, 2007-03-31 at 09:17 -0800, Igor Vaynberg wrote:
On 3/31/07, Kurt R. Hoehn [EMAIL PROTECTED] wrote:
Wicket 2.0-SNAPSHOT
Wicket-Spring 2.0-SNAPSHOT
wicket 2.0 has been discontinued for various
I complained the ajax modal window cannot show every time when i click the ajax
link ,after the updgading ,it can work well. but i get a new problem, I used a
modal winwo to input something, when i open the modal window first, it's ok,
but when i open it again , it will generate the bellow
NORTHWEST WIND 15 TO 25 MPH. NORTHWEST WIND TO 15 MPH. TO FORT CHAFFEE LINE BY
10 AM. FLOOD WATERS ARE USUALLY DEEPER THAN THEY APPEAR. PARTLY TO MOSTLY
CLOUDY SKIES WITH A FEW SNOW SHOWERS OR FLURRIES THIS MORNING.
MOST FLOOD DEATHS OCCUR IN AUTOMOBILES. THE COLD FRONT AND ASSOCIATED LINE OF
I've written up a new example document for workign with drop down
choice components, as they seem to be a source of confusion (should be
available any time soon when Apache syncs the servers)
http://incubator.apache.org/wicket/examples.html
Martijn
On 3/31/07, Kurt R. Hoehn [EMAIL PROTECTED]
Weird problem. Can you give us a stack trace please? I tried this:
Index:
/Users/eelcohillenius/Documents/workspace_wicket/wicket-1.x/jdk-1.5/wicket-examples/src/main/java/wicket/examples/helloworld/HelloWorld.java
===
---
it works fine because you are calling error on a page and not on a
component. errors are stored at page-level.
-igor
On 3/31/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
Weird problem. Can you give us a stack trace please? I tried this:
Index:
Ok, I see.
public final void error(final Serializable message)
{
getPage().getFeedbackMessages().error(this, message);
}
Why don't we fix this?
Eelco
On 3/31/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
it works fine because you are calling error on a
Is it the latest svn version? There have been several important
versioning fixes lately, i suggest you checking the latest from svn.
-Matej
On 3/31/07, tooy li(Gmail) [EMAIL PROTECTED] wrote:
I complained the ajax modal window cannot show every time when i click the
ajax link ,after the
Fix it like this:
Index:
/Users/eelcohillenius/Documents/workspace_wicket/wicket-1.x/jdk-1.4/wicket/src/main/java/wicket/Component.java
===
---
I don't like the addition of the 4 bytes to the component. Apparently
the usecase is pretty rare (only discovered after 2 years of
production use), and this will increase memory usage considerably for
a small benefit.
Isn't a message queue that isn't bound to a component but to the
current
Sure, sounds good. Can you make a proposal please? It's kind of where
we started in the first versions, but then again, much was different
and this time that can work.
Eelco
On 3/31/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
I don't like the addition of the 4 bytes to the component.
Apparently the usecase is pretty rare (only discovered after 2 years of
production use)
Well, you can't really know as you don't know how many people ever
bumped across this and decided to implement a workaround without
mentioning it to us. More importantly, I just don't think it is right
users
1.2.6
we no longer need bodycontainer in 1.3 because we have a much more elegant
system for handling such things
-igor
On 3/31/07, Chris Colman [EMAIL PROTECTED] wrote:
Java objects construct the way that they do and we use Java object
constructors because we like that simplicity.
yeah, threadlocal would work. it would also get rid of the need for
Session feedback messages. in some sense, i think the error is really
being registered for the request (thread) anyway, not any object.
so i like that idea. it can just be a threadlocal in the appropriate
class and
if you can wait, i think we're going to be fixing this so you don't have to
make any changes.
serban.balamaci wrote:
Thanks for the answer. Do you mean that instead of doing the loading of
the model in the constructor to do it onAttach() ?
Jonathan Locke wrote:
You component is
i am not so sure this is correct. we often deal with two page instances
inside the same request - the current one and the response page. this breaks
any kind of scoping as errors reported against current page will now make it
into response page?
dont know how likely the above usecase is, but
On 3/31/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
i am not so sure this is correct. we often deal with two page instances
inside the same request - the current one and the response page. this breaks
any kind of scoping as errors reported against current page will now make it
into response
Do feedbackmessages in the session really need to be synchronized with
CopyOnWriteArrayList? I'm in doubt whether synchronization helps that
much, but if it does, wouldn't it be more efficient to use a normal
synchronized one?
Eelco
On 3/31/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
On
Eelco Hillenius wrote:
About the session messages... well, they have a slightly different
meaning: display whenever there is a feedback component rendered on
any page. This is useful when writing generic software where you know
that a message should be displayed, but you just don't know
We chose that, yes. But would it be better to simply have all feedback
messages stored in the session? That would solve all our scoping problems
wouldn't it? Every feedback message would go into the session and then
feedback panels could pull them out when they're ready to. If a feedback
yeah, your patch would work, but i think we agree that the
session approach is better and cleaner (both functionally and
conceptually) for the long term even if it could at least
/conceivably/ break some especially odd code (which it
seems likely does not even exist).
the semantics are
Yeah, that does sound like overkill in a single-threaded environment.
What other thread would ever be accessing a session's feedback messages?
Eelco Hillenius wrote:
Do feedbackmessages in the session really need to be synchronized with
CopyOnWriteArrayList? I'm in doubt whether
Yeah, that does sound like overkill in a single-threaded environment.
What other thread would ever be accessing a session's feedback messages?
Furthermore, copy on write is efficient when there are lots of reads
and just a couple of writes, but that's not the case I think. So
normal
copy on write has the advantage when it comes to iterating over the list.
the locking needs to be there because we lock on pagemaps and not on
session, so two pages in different pagemaps would need to be synced.
-igor
On 3/31/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
Yeah, that does
34 matches
Mail list logo
