Build your properties files using you local (latin 2) encoding so that
you don't need to put any escaped characters in. Then, as part of the
build pocess run native2ascii on all of the properties files to get all
the extended characters correctly escaped.
regards,
Chris
Matej Knopp wrote:
I would have to agree very strongly with Eelco on this one. One of the
major problems with most frameworks are that they are too flexible. If
we work on the general average that there are around 10 average
programmers for each good/excellent one (something I have found to hold
true over many
I have no preference other than the colon makes my code look a bit neater!
Chris
Martijn Dashorst wrote:
I am in the 'want to use the component id as (limited) ognl
expression' camp. I think that the component seperator should be
either colon (:) or dollar sign ($). Visually I have a
I have just run the two examples through a profiler (YourKit Java
Profiler) and I can confirm that the Tapestry example is just over twice
as fast as the Wicket one. The amount of difference is variable, with
the biggest difference being for the page that renders the list view.
Taking a quick
logging and then I'll
try the profiling again.
regards,
Chris
Chris Turner wrote:
I have just run the two examples through a profiler (YourKit Java
Profiler) and I can confirm that the Tapestry example is just over
twice as fast as the Wicket one. The amount of difference is variable
(Begin render + this); which are very expensive because they
do a toString() on the object.
Any other thoughts?
regards,
Chris
Johan Compagner wrote:
if that really is the case then we should turn logging default off??
and supply a right properties file?
johan
Chris Turner wrote:
One word
.
It seems that I'm doing something wrong.
Thank you.
Chris Turner wrote:
I believe that all of the logging statements are currently surrounded
by the if check - I could not find any that were not. However, if you
don't provide a logging configuration then the call to
log.isDebugEnabled() always
The letters for the hangman application are dynamically generated. In
the Letter.java class there is a method that generates
DefaultButtonImageResource objects. Then in Guess.java the list view
iteration obtains the enabled and disabled images for each letter in
turn, either creating them (via
Oops, I never thought of that when I wrote the resource location code.
I'll make the change - shouldn't take me long. The search order will
then be:
1) Search properties for current component class
2) Recursively search properties for each super class of the current
component class
3)
Hi Stefan,
Glad that you like what we are doing. It's very encouraging to get so
much positive feedback.
I've tried to answer your questions as best as possible below.
Stefan Arentz wrote:
First of all. Wow. This stuff rocks. Wicket is my first experience
with a component based framework
Hi All,
I have added a couple of short how-to articles to the wiki
(http://wicket.sourceforge.net/wiki). One describes how to use borders
to create template site layouts. The second describes how to combine
borders and panels together to create templated reusable site elements.
Hope you find
liigo wrote:
Two things that I can't understand easily, just in the HelloWord
application.
With the HelloWord demo application code following:
package wicket.examples.helloworld;
import wicket.markup.html.WebPage;
import wicket.markup.html.basic.Label;
public class HelloWorld extends WebPage
{
+1 on break it into sections. I'm happy to write the ones on
localization and scalability/clustering (as my reference manual has made
little progress since I've been trying to solve the clustering issues)
regards,
Chris
Jonathan Locke wrote:
it might be helpful to break the user's guide up into
Hi All,
Having spent a couple of days investigating ajax (to meet some
requirements that we have in a struts application for one of my
customers) I decided to take a good look that the Echo2 stuff. Here are
my thoughts:
I'm not sure that the Echo2 stuff is actually targeting the right end
use
14 matches
Mail list logo