Re: [Wicket-user] wingS 2.0 v. wicket 1.1

2005-12-12 Thread Igor Vaynberg
why dont you post that to tss?-IgorOn 12/12/05, Martijn Dashorst <[EMAIL PROTECTED] > wrote:I think that not all markup on a page needs to be componentized. When I look at an administrative interface Topicus is currently developing,I think only 20% or even less of the markup tags has a wicket:idass

Re: [Wicket-user] wingS 2.0 v. wicket 1.1

2005-12-12 Thread Martijn Dashorst
I think that not all markup on a page needs to be componentized. When I look at an administrative interface Topicus is currently developing, I think only 20% or even less of the markup tags has a wicket:id assigned. The rest is supporting markup layout (divs, tables, non-internationalized text), or

Re: [Wicket-user] wingS 2.0 v. wicket 1.1

2005-12-12 Thread Eelco Hillenius
Agreed. I think it is still a one-man-only project and the statistics didn't look too impressive. Which doesn't say anything about the quality of the framework of course. But it helps to have an active community like the one that starts growing around Wicket now. Eelco > > 2. No one has heard of

Re: [Wicket-user] wingS 2.0 v. wicket 1.1

2005-12-12 Thread Andrew Berman
Well, I can tell you two disadvantages of using wingS:1. It uses Layout managers.  Why it needs these if it uses HTML is beyond me, but it uses the Swing layout managers.  I don't know how many here have used Swing, but coding those layout managers by hand is a horrendous experience, especially the

Re: [Wicket-user] wingS 2.0 v. wicket 1.1

2005-12-12 Thread Eelco Hillenius
I don't understand what you mean by duplication. Having things seperated (in this case markup from logic) is not a violation of DRY. It is just partitioning and seperation of concerns. And why we do this? To keep things neatly seperated. Same reason as that you don't want scriptlets in your JSP (at

Re: [Wicket-user] wingS 2.0 v. wicket 1.1

2005-12-12 Thread Christopher Gardner
I'm still cross posting to the ServerSide, as I'm trying to get the thoughts of wingS users. --- Some of the responses mention the separation of concerns: Web page designers can focus on the usability and beauty of the page, while Java developers can hook up that page to that application. I see ad

Re: [Wicket-user] wingS 2.0 v. wicket 1.1

2005-12-12 Thread Dorel Vaida
Michael Jouravlev wrote: On 12/11/05, Andrew Lombardi <[EMAIL PROTECTED]> wrote: Programmers work in Java, Designers work in HTML, wicket follows the separation of concerns fairly eloquently. This is a wrong principle. Modern-day web programming is not a CGI script + HTML 2.0. Web bro

Re: [Wicket-user] wingS 2.0 v. wicket 1.1

2005-12-12 Thread Dorel Vaida
Martijn Dashorst wrote: I think there are different types of designers... Our company design team (2 people) use photoshop to create the design, and one of them transforms that into HTML + CSS + JavaScript for a mockup website. Well, the first is the creative designer. This guys is drawing t

Re: [Wicket-user] wingS 2.0 v. wicket 1.1

2005-12-12 Thread Martijn Dashorst
I think there are different types of designers... Our company design team (2 people) use photoshop to create the design, and one of them transforms that into HTML + CSS + _javascript_ for a mockup website. This is then presented to our customer, and then turned over to the development team. We are

Re: [Wicket-user] wingS 2.0 v. wicket 1.1

2005-12-12 Thread Michael Jouravlev
On 12/11/05, Andrew Lombardi <[EMAIL PROTECTED]> wrote: > Programmers work in Java, Designers work in HTML, wicket follows the > separation of concerns fairly eloquently. This is a wrong principle. Modern-day web programming is not a CGI script + HTML 2.0. Web browsers are capable of Javascript, D

Re: [Wicket-user] wingS 2.0 v. wicket 1.1

2005-12-12 Thread Dorel Vaida
Christopher Gardner wrote: I posted this to the ServerSide in the recent article on wingS. How would you sell wicket, which requires a physical HTML page, over wingS, which I think does not? Well, I'm not quite familiar with wingS, it looks pretty interesting, but I really enjoy handing ove

Re: [Wicket-user] wingS 2.0 v. wicket 1.1

2005-12-11 Thread Andrew Lombardi
clarification below On Dec 11, 2005, at 9:11 PM, Andrew Lombardi wrote: Though I've not looked at WingS at all ... I am really enjoying working with wicket because it feels less like mucking around with tags (whether xml or xhtml), and more like actual bare-knuckles programming. That bei

Re: [Wicket-user] wingS 2.0 v. wicket 1.1

2005-12-11 Thread Andrew Lombardi
Though I've not looked at WingS at all ... I am really enjoying working with wicket because it feels less like mucking around with tags (whether xml or xhtml), and more like actual bare-knuckles programming. That being said, I don't really get a warm fuzzy about having *all* of my page re

[Wicket-user] wingS 2.0 v. wicket 1.1

2005-12-11 Thread Christopher Gardner
I posted this to the ServerSide in the recent article on wingS. How would you sell wicket, which requires a physical HTML page, over wingS, which I think does not? --- While I've looked at wicket 1.1 very closely, I've only read the documentation for wingS 2.0. Both intrigue me, and I'm trying to