You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Eelco Hillenius <ee...@gmail.com> on 2008/04/01 20:15:16 UTC
planning for Wicket 3.0
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
Re: planning for Wicket 3.0
Posted by David Pollak <fe...@gmail.com>.
On Tue, Apr 1, 2008 at 11:15 AM, Eelco Hillenius <ee...@gmail.com>
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.
I guess, given that lift's abandoning Scala, Wicket should move into the
space:
http://groups.google.com/group/liftweb/browse_thread/thread/90a3014bc96a5248
>
> * 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
>
--
Scala lift off unconference, May 10th 2008, San Francisco
http://scalaliftoff.com
lift, the secure, simple, powerful web framework http://liftweb.net
Collaborative Task Management http://much4.us
Re: planning for Wicket 3.0
Posted by Cristi Manole <cr...@gmail.com>.
I fell for it too...
I figured... this is THE best web framework... I saw it grow and put my
confidence into it...
And when I saw that you were ALL moving in all the wrong way... I was so so
sooo disappointed.... no more Java sources, no more regular HTMLs for web
designers to do their job while not interfering with mine... applet?!
Pheeeew... what a nightmare :))))))
Cristi Manole
On Thu, Apr 3, 2008 at 2:25 AM, TahitianGabriel <gl...@piti.pf> wrote:
>
> You really got me Eelco. I almost had a heart attack! I was really getting
> worried while reading your post.
>
> Keep Wicket the way it is, the best Java framework ever...
>
>
>
> Eelco Hillenius wrote:
> >
> > In case you didn't get it: april fools'! :-)
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/planning-for-Wicket-3.0-tp16430664p16453597.html
> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>
>
Re: planning for Wicket 3.0
Posted by TahitianGabriel <gl...@piti.pf>.
You really got me Eelco. I almost had a heart attack! I was really getting
worried while reading your post.
Keep Wicket the way it is, the best Java framework ever...
Eelco Hillenius wrote:
>
> In case you didn't get it: april fools'! :-)
>
>
--
View this message in context: http://www.nabble.com/planning-for-Wicket-3.0-tp16430664p16453597.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
Re: planning for Wicket 3.0
Posted by Johan Compagner <jc...@gmail.com>.
> How about letting it extend from JCompagner instead?
that would be soooo coool!
Re: planning for Wicket 3.0
Posted by Eelco Hillenius <ee...@gmail.com>.
On Wed, Apr 2, 2008 at 10:02 AM, Matej Knopp <ma...@gmail.com> wrote:
> A joke?! I already made Component extends JComponent! Does it mean I
> won't get to commit that?
How about letting it extend from JCompagner instead? It'll be closer
to the creative source.
Eelco
Re: planning for Wicket 3.0
Posted by Matej Knopp <ma...@gmail.com>.
A joke?! I already made Component extends JComponent! Does it mean I
won't get to commit that?
-Matej
On Wed, Apr 2, 2008 at 6:18 PM, Peter Ertl <pe...@gmx.net> wrote:
> What? This was a joke?! And I was so excited about Swing <--> Wicket
> interoperability *lol*
>
>
>
> Am 02.04.2008 um 18:07 schrieb Eelco Hillenius:
>
>
>
>
> >
> > > I thought the move to Scala was a pretty intriguing idea. It
> > > was the logic in markup and the integration with Swing that
> > > had me worried.
> > >
> >
> > Yeah, I like Scala, or at least parts of it. And the joke had to be
> > somewhat believable :-)
> >
> > Eelco
> >
>
>
--
Resizable and reorderable grid components.
http://www.inmethod.com
Re: planning for Wicket 3.0
Posted by Peter Ertl <pe...@gmx.net>.
What? This was a joke?! And I was so excited about Swing <--> Wicket
interoperability *lol*
Am 02.04.2008 um 18:07 schrieb Eelco Hillenius:
>> I thought the move to Scala was a pretty intriguing idea. It
>> was the logic in markup and the integration with Swing that
>> had me worried.
>
> Yeah, I like Scala, or at least parts of it. And the joke had to be
> somewhat believable :-)
>
> Eelco
Re: planning for Wicket 3.0
Posted by Eelco Hillenius <ee...@gmail.com>.
> I thought the move to Scala was a pretty intriguing idea. It
> was the logic in markup and the integration with Swing that
> had me worried.
Yeah, I like Scala, or at least parts of it. And the joke had to be
somewhat believable :-)
Eelco
RE: planning for Wicket 3.0
Posted by "Martijn C. Vos" <m....@onehippo.com>.
Nino Saturnino Martinez Vazquez Wael wrote:
> I got it:) Although I think I heard a discussion once on the
> wicket irc channel about scala..
I thought the move to Scala was a pretty intriguing idea. It
was the logic in markup and the integration with Swing that
had me worried.
mcv.
Re: planning for Wicket 3.0
Posted by Nino Saturnino Martinez Vazquez Wael <ni...@jayway.dk>.
I got it:) Although I think I heard a discussion once on the wicket irc
channel about scala..
I admit I can be a little naive sometimes.
regards Nino
Eelco Hillenius wrote:
> In case you didn't get it: april fools'! :-)
>
> On Tue, Apr 1, 2008 at 11:15 AM, Eelco Hillenius
> <ee...@gmail.com> 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
Re: planning for Wicket 3.0
Posted by Eelco Hillenius <ee...@gmail.com>.
In case you didn't get it: april fools'! :-)
On Tue, Apr 1, 2008 at 11:15 AM, Eelco Hillenius
<ee...@gmail.com> 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
>
Re: planning for Wicket 3.0
Posted by Gerolf Seitz <ge...@gmail.com>.
On Tue, Apr 1, 2008 at 8:15 PM, Eelco Hillenius <ee...@gmail.com>
wrote:
> * 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.
>
We actually talked about this in ##wicket recently.
I think it would be a great idea to have Component extend Applet
(or JApplet if you like), so it can provide a richer user experience.
I also suggest renaming Component into WApplet.
Let's kick some RIA ass ;)
Gerolf
Re: planning for Wicket 3.0
Posted by Peter Ertl <pe...@gmx.net>.
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 <jcompagner@gmail.com
>> > 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 <eelco.hillenius@gmail.com
>>> >
>>> 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
Re: planning for Wicket 3.0
Posted by Nino Saturnino Martinez Vazquez Wael <ni...@jayway.dk>.
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 <jc...@gmail.com> 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 <ee...@gmail.com>
>> 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
Re: planning for Wicket 3.0
Posted by James Carman <ja...@carmanconsulting.com>.
On Tue, Apr 1, 2008 at 4:10 PM, Maurice Marrink <ma...@gmail.com> wrote:
> Excellent idea, but it might be hard to convince apache to move to git
> so maybe we should consider leaving apache.
>
Nah, just let everyone have their own repository. Then, right before
release time, everyone emails their repositories to the release
manager and they just merge everything together and check it into SVN.
:)
Re: planning for Wicket 3.0
Posted by Maurice Marrink <ma...@gmail.com>.
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 <jc...@gmail.com> 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 <ee...@gmail.com>
> 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
> >
>
Re: planning for Wicket 3.0
Posted by Johan Compagner <jc...@gmail.com>.
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 <ee...@gmail.com>
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
>
Re: planning for Wicket 3.0
Posted by Martijn Dashorst <ma...@gmail.com>.
GWT!!!
(I hear that the W stands for Wicket... Google's Wicket Translator)
On 4/1/08, Johan Compagner <jc...@gmail.com> wrote:
> hmm
>
> we need a compiler that transforms wicket code directly to html and
> javascript so that we can run completely in the browser
>
>
> johan
>
>
>
> On Tue, Apr 1, 2008 at 8:15 PM, Eelco Hillenius <ee...@gmail.com>
> 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
> >
>
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.2 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.2
Re: planning for Wicket 3.0
Posted by Maurice Marrink <ma...@gmail.com>.
Another neat feature would be if we could use MS Visual Studio to
develop Wicket apps. VS ROCKS!
And Drag and Drop!
Maurice
On Tue, Apr 1, 2008 at 9:39 PM, Johan Compagner <jc...@gmail.com> wrote:
> hmm
>
> we need a compiler that transforms wicket code directly to html and
> javascript so that we can run completely in the browser
>
> johan
>
>
>
> On Tue, Apr 1, 2008 at 8:15 PM, Eelco Hillenius <ee...@gmail.com>
> 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
> >
>
Re: planning for Wicket 3.0
Posted by Johan Compagner <jc...@gmail.com>.
hmm
we need a compiler that transforms wicket code directly to html and
javascript so that we can run completely in the browser
johan
On Tue, Apr 1, 2008 at 8:15 PM, Eelco Hillenius <ee...@gmail.com>
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
>
Re: planning for Wicket 3.0
Posted by Matej Knopp <ma...@gmail.com>.
Thanks. You just gave me a headache...
-Matej
On Sun, Apr 27, 2008 at 5:17 PM, Jonathan Locke
<jo...@gmail.com> wrote:
>
>
> heh. brian (breadbox below) and i went to college together. besides his
> brainfuck page, brian also has written significant programs in "Intercal".
> i double dare you all to google that up. it makes my brain hurt just to
> think about it.
>
>
>
>
> Stefan Lindner wrote:
> >
> > Nino Saturnino Martinez Vazquez Wael wrote:
> >
> >>Argh! I like java and I like wicket, what boundarys are you guys
> > reaching that java cant solve? And I then the future in short will be
> > all about alternative languages in jvm, like jruby scala python etc. Why
> > not keep it safe a little longer, but I guess it does not matter if its
> > totally compatible with regular java (only thing that could be annoying
> > is when looking at the source).
> >
> > I think the final target for Wicket 5.0 is brainfuck
> > (http://www.muppetlabs.com/~breadbox/bf/). The Scala implementatioin is
> > just a step towards Brainfuck. But remember: just wicket itself will be
> > written in Scala and because Scala is fully compatible with Java, you
> > can continue to write your code with Java. You just jave to ensure that
> > your Apllication server (Tomcat, Weblogic, etc.) supports Scala.
> >
> > Keep on Wicket!
> >
> > Stefan
> >
> >
>
> --
> View this message in context: http://www.nabble.com/planning-for-Wicket-3.0-tp16430664p16924829.html
>
>
> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>
>
--
Resizable and reorderable grid components.
http://www.inmethod.com
RE: planning for Wicket 3.0
Posted by Jonathan Locke <jo...@gmail.com>.
heh. brian (breadbox below) and i went to college together. besides his
brainfuck page, brian also has written significant programs in "Intercal".
i double dare you all to google that up. it makes my brain hurt just to
think about it.
Stefan Lindner wrote:
>
> Nino Saturnino Martinez Vazquez Wael wrote:
>
>>Argh! I like java and I like wicket, what boundarys are you guys
> reaching that java cant solve? And I then the future in short will be
> all about alternative languages in jvm, like jruby scala python etc. Why
> not keep it safe a little longer, but I guess it does not matter if its
> totally compatible with regular java (only thing that could be annoying
> is when looking at the source).
>
> I think the final target for Wicket 5.0 is brainfuck
> (http://www.muppetlabs.com/~breadbox/bf/). The Scala implementatioin is
> just a step towards Brainfuck. But remember: just wicket itself will be
> written in Scala and because Scala is fully compatible with Java, you
> can continue to write your code with Java. You just jave to ensure that
> your Apllication server (Tomcat, Weblogic, etc.) supports Scala.
>
> Keep on Wicket!
>
> Stefan
>
>
--
View this message in context: http://www.nabble.com/planning-for-Wicket-3.0-tp16430664p16924829.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
Re: planning for Wicket 3.0
Posted by Igor Vaynberg <ig...@gmail.com>.
I have already ported Wicket to WhiteSpace[0], so I can help you port
it to Brainfuck since I have the experience.
[0] http://compsoc.dur.ac.uk/whitespace/
-igor
On Tue, Apr 1, 2008 at 12:28 PM, Stefan Lindner <li...@visionet.de> wrote:
> Nino Saturnino Martinez Vazquez Wael wrote:
>
> >Argh! I like java and I like wicket, what boundarys are you guys
> reaching that java cant solve? And I then the future in short will be
> all about alternative languages in jvm, like jruby scala python etc. Why
> not keep it safe a little longer, but I guess it does not matter if its
> totally compatible with regular java (only thing that could be annoying
> is when looking at the source).
>
> I think the final target for Wicket 5.0 is brainfuck
> (http://www.muppetlabs.com/~breadbox/bf/). The Scala implementatioin is
> just a step towards Brainfuck. But remember: just wicket itself will be
> written in Scala and because Scala is fully compatible with Java, you
> can continue to write your code with Java. You just jave to ensure that
> your Apllication server (Tomcat, Weblogic, etc.) supports Scala.
>
> Keep on Wicket!
>
> Stefan
>
RE: planning for Wicket 3.0
Posted by Stefan Lindner <li...@visionet.de>.
Nino Saturnino Martinez Vazquez Wael wrote:
>Argh! I like java and I like wicket, what boundarys are you guys
reaching that java cant solve? And I then the future in short will be
all about alternative languages in jvm, like jruby scala python etc. Why
not keep it safe a little longer, but I guess it does not matter if its
totally compatible with regular java (only thing that could be annoying
is when looking at the source).
I think the final target for Wicket 5.0 is brainfuck
(http://www.muppetlabs.com/~breadbox/bf/). The Scala implementatioin is
just a step towards Brainfuck. But remember: just wicket itself will be
written in Scala and because Scala is fully compatible with Java, you
can continue to write your code with Java. You just jave to ensure that
your Apllication server (Tomcat, Weblogic, etc.) supports Scala.
Keep on Wicket!
Stefan
Re: planning for Wicket 3.0
Posted by Nino Saturnino Martinez Vazquez Wael <ni...@jayway.dk>.
Eelco Hillenius 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.
>
>
Sounds like a good idea to avoid confusion.
> 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.
>
Argh! I like java and I like wicket, what boundarys are you guys
reaching that java cant solve? And I then the future in short will be
all about alternative languages in jvm, like jruby scala python etc. Why
not keep it safe a little longer, but I guess it does not matter if its
totally compatible with regular java (only thing that could be annoying
is when looking at the source).
> * 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.
>
Hmm, I actually like that you cant script. I tend to believe it keeps
the spaghetti out of the code. Keep code/logic in java and markup in
markup and a have clean cut.
> * 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.
>
Could be good.
> * 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.
>
>
Could also be good, but how would you handle the client server paradigm
in swing?
> WDYT? Comments/ suggestions?
>
This isnt aprilsfools?
> Cheers,
>
> Eelco
>
>
>
--
-Wicket for love
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
Re: planning for Wicket 3.0
Posted by Martijn Dashorst <ma...@gmail.com>.
Also, instead of naming things like they are some web concept, we
should name them to what they can do. Link is not a very good concept.
Instead of a Link we would have a Clickable. But that name is lame...
so I suggest prefixing all our interfaces with ImA. this would make a
clickable component implement ImAClickable
Martijn
On 4/1/08, Eelco Hillenius <ee...@gmail.com> 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
>
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.2 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.2