On 8/24/05, Anders Peterson <[EMAIL PROTECTED]> wrote:
> Isn't that strict checking something that should be done when compiling
> (someone has the time to code a wicket builder for eclipse) and not at
> runtime?
> 

1) you suggest to compare java code and markup at compile time?
2) than you need to support JBuilder, Netbeans, Idea, ...

IMO as long as such development time tools are not available, we
should keep the runtime check

> At runtime I'd like the ability to disable components that are not in a
> working state because they are currently not used/displayed.
>

you are. There is just the restriction that a model has to exist.
 
> As Gili said: Wicket is wasting resources rendering stuff that will not
> be displayed.
> 

though this is true, IMO is not a strong enough argument to disable
it. I'd rather prefer to discuss solutions on how to meet both our
requirements, compared to who has the better arguments pro and con the
current implementation.

Juergen


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to