I have spend about 100 hours in creating a Wicket 1.3 port. Because half of
Wicket consists of anonymous classes it is near impossible. I had to add about
1000 new subclasses to get the core to work. When it compiled and actually
wanted to start and bind to a port I was unable to get the pages
Ohh crap. :( thats bad. The worst part are it being closed source. For me
it would mean changing jobs. Theres just too many things. Build server unit
testing version control etc are a whole new thing. Just in those things a
huge investment buying licenses (afaik all are $/commercial in ms land) .
I don't suppose anyone has ported Wicket to .NET?
What, and lose all the non-designable ASP.Net or Razor goodness? :)
- Tor Iver
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail:
I know it is overly simplistic but you can almost think of the .aspx and the
.aspx.c code-behind file as the .html and the .java file in Wicket if it will
make you feel any better. It is not that simple but it is quick way that our
junior .NET developers can relate to what the Java folks do in
http://www.ikvm.net/
Good luck :-)
On Tue, Feb 7, 2012 at 9:57 PM, shetc sh...@bellsouth.net wrote:
Well friends, it's happened -- the company I work for has been bought by a
larger competitor. Sadly, the new bosses prefer to work with .NET
I don't suppose anyone has ported Wicket to .NET?
