I vote for freemarker as the superior markup language (pure html feels
so 1992)
also the layout managers should be based on <table> layout (using code
generation) to ensure maximum browser performance.
Am 01.04.2008 um 22:21 schrieb Nino Saturnino Martinez Vazquez Wael:
Ahh, yes an then I'd like to suggest going for VB6, as I really
liked that. Especially their error handling and nice syntax. and use
the CPIP[1] to ensure more stability!
1=http://www.blug.linux.no/rfc1149/
Maurice Marrink wrote:
Excellent idea, but it might be hard to convince apache to move to
git
so maybe we should consider leaving apache.
Maurice
On Tue, Apr 1, 2008 at 10:06 PM, Johan Compagner <[EMAIL PROTECTED]
> wrote:
By the way,
before we do all that
i think we should really first deprecated subversion and go
straight to GIT.
that will make all this development a lot easier
johan
On Tue, Apr 1, 2008 at 8:15 PM, Eelco Hillenius <[EMAIL PROTECTED]
>
wrote:
Hi,
>
> Now that half of the team is getting ready to work on Wicket 1.4,
> which is all about supporting the Java 5 features, I think it is
time
> for the other half of the team to start talking about Wicket 3.0
(we
> skip 2.0 as we've used that for prototyping before), which is
> scheduled for 2009.
>
> We've had some offline talk about this with various team
members, and
> it seems that we have basic agreement on at least a couple of
things:
>
> * Wicket 3.0 source will be all Scala (http://www.scala-
lang.org/),
> which means quite a transition for our team, but we will still
> maintain compatibility with regular Java.
> * Relax our policy towards scripting in pages. We're just getting
> tired of people having a hard time to do simple things with
Wicket, so
> in the future we want to support loops, conditionals and property
> expressions directly in the markup on top of the facilities we
have
> now.
> * Introduce layout managers. While it is great to be able to
directly
> code markup with Wicket, we'd like to hide that a bit more and
> introduce layout managers as the preferential mechanism for
composing
> pages and components.
> * Swing compatibility. We want our future components to be able
to run
> directly in Swing, and Swing components to be run in Wicket
apps. Just
> like some of our competitors.
>
> WDYT? Comments/ suggestions?
>
> Cheers,
>
> Eelco
>
--
-Wicket for love
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
