I am new to Wicket framework, I have seen many good reviews on this framework.
I would like to know how is the adoption rate for Wicket compared to other frameworks (like GWT, JSF etc..).
Here is a nice post: http://www.thebuzzmedia.com/which-is-the-hottest-java-web-framework-or-maybe-not-java/
Related
I'm getting into Scala, I find the object-oriented & functional paradigm combination really interesting.
So, I've read some tutorials about basic Scala, but now I want to get deeper into Scala as for web applications.
Anyone have tutorials, links, blogs or any kind of useful information?
definitely checkout play. its syntax is pretty sleek, has dynamic loading of classes (no restart of JVM when you make changes) and the APIs are pretty well thought.
Try Lift: http://liftweb.net/getting_started
I also recommend having a look at Lift since it uses Scala's strength very well. For example there's the embedded SiteMap DSL for structuring your site and an actor-based Comet implementation.
In this Interview with David Pollak he explains his reasons to start this project and (in short) Lift's benefits compared to Rails, Wicket, the Smalltalk web framework Seaside and Struts.
There are several Books about it (Lift in Action, The Definitive Guide to Lift: A Scala-based Web Framework), including two beeing available for free (Simply Lift by David Pollak, Exploring Lift including a very interesting chapter about Lift's internals).
When you are from a MVC background, you should read why Lift uses a different "View First" architecture for web apps. But there's a MVC Helper, too. See also chapter 13 in Simply Lift about that.
For a short look at different interesting code snippets I recommend the Seven Things Demo Application, but there also is another offical demo.
When you read some example view code you will probably encounter tags like <lift:surround with="default" at="content">. You would have to import the xml namespace to pass (x)html validators with such tags. Since this is not very designer-friendly a newer way to embed lift semantics in views is using the class attribute of a regular html element: <div id="main" class="lift:surround?with=default;at=content">
I am in the process of migrating to a new PHP Framework. I have been involved in heavy development using the CodeIgniter Framework, but I am finding it a little too lightweight for my needs now.
I have boiled my choices down to either Zend Framework or Symfony. I know the learning curve for both is relatively high. However, I just wanted to get a rough idea of which will be worth getting stuck into (as I will be spending quite a lot of time getting familiar with the chosen framework).
If it helps narrow the answer down a little. I am not looking to build a simple blog or anything like that. I am in need for something that will support full-fledged development of e-commerce systems, customer relationship managers and content management systems.
Personally i have been working with ZF since it was in version 1.6, and i am pretty happy with it , I had seen very good improvement since 1.6 , but i think ZF missing some ideas :
1- ORM and later on very great implementation between ZF + Doctrine 1.2 has taken very popularity
and i honestly depend on ZF + Doctrine in many projects
and these days we can see great integration between ZF + Doctrine2
2- the symfony's bundle is completely forgotten in ZF
Do you think Zend framework misses the Symfony's Bundle principle ?
and i think its really indeed to see it soon (hopefully in ZF 2 )
3- i had many good points about symfony 1
- doctrine built in support
- bundle principle
- admin generators which can save a lot of time
- symfony plugins is very popular
- symfony documentation is really good
finally , i had took a deep look at symfony 1 but i am really taken by the buzz of symfony2 in the late of 2010 and till today its public preview http://symfony.com/download
and i am trying to spend some time learning it .
wish me luck :)
update
I don't want my answer to imply that ZF isn't good or symfony is better than ZF , ZF IMO very powerful library and being ZF developer === advanced + powerful PHP OOP programmer .
I had to make this choice about 1.5 years ago. I first looked at ZF and read up on it as much as possible, but at the end of the day I never really felt comfortable with it. It felt over-engineered, and I found myself getting lost in the code pretty often. I then checked out Symfony with Doctrine. I was able to come to grips with the code base much quicker than ZF. I've since used Symfony on 30+ projects, everything ranging from small sites to pretty large applications and I couldn't be happier. Their admin generator tools have cut down the time I spend building CMS's by a ridiculous amount, and I'm constantly adding my own additions so that future projects take even less time. On top of that, their routing framework, forms framework, and plugin architecture are very well built and very useful. (And Doctrine is a God-send, but you can use that with ZF as well, it's just nice that Symfony uses it by default and has some tighter integration with it.)
Luckily, both ZF and Symfony are highly extensible, so whichever you choose, you'll be better off than using CodeIgniter.
Personally I would rather invest my time in learning the Zend framework. I've played with symfony in the past, and it does have its merits, but I like the Zend framework better. For me Symfony (1.x) has that "things patched together with duct tape" feel around it. There's a lot of different plugins, with varying code quality. ZF tries to raise the bar and feels like a more professional, and well thought out framework (and on top of that ZF is very flexible). Symfony might be better suited for prototyping though because of the admin generator.
I haven't looked at Zend, but I did look at a couple of other frameworks before deciding on symfony.
For me it was the quality of the documentation - which for Symfony is excellent.
The thing with frameworks is that if you cannot use features because they are not well documented then they are not features at all.
It really boils down to your own requirements and how each feels - as you know the whole point of a framework is to work with it, if you are always adding extra code or exceptions then that framework is not right for you.
I am searching GWT Design to setup project. I could use MVP(GWTP) or JBoss Errai.
I haven't decided yet. Is there anyone who experienced in one of these?
You can give advantages and disadvantages of these frameworks.
Errai by far the best for a complete set of tools.
GWT dispatch can be used just by itself if not using Errai or GWTP .
JBoss Errai is quite "mature" now I think, and I am using it for my commercial projects.
Basically, one of the best features of Errai now (as of this moment) is that it allows really good templating with GWT.
Errai features:
Errai UI, too easy to learn.
Errai UI again, the CSS use is native, just in special cases you have to set a CSS style in code.
LESS Suport.
JPA on browser.
CDI through Weld, you can use Seam over spring.
You can have page navigation (Errai navigation).
Don't have to declare two interfaces to have interaction with the server.
Communication with the server in the form of messages, events, or through REST or RPC.
GWT vanilla features:
UI Binder. What?! more tags to learn? oh come on!
CSS through Java code.
Does not have LESS support.
Does not support CDI injection of services natively.
Does not support page navigation natively (activities and places works just in one page).
Does not have any support of client-side persistence.
You have to declare two interfaces to have interaction with the server (yeah, you can have an assistant that makes the code for you, but is boilerplate code that you have to maintain).
GWT interaction just by RPC mechanism.
So, IMHO if you can add Errai in your GWT projects your developments will be more comfortable :-)
Cheers!
Sorry could not work about how to add a reply :( any way yes you are right . But Errai bus and for messaging and workspace for UI are good enough and quite mature and you Iam happily using them in a project with is not due to next 8 months . If however I wanted to go live today Errai would still not be a concern it is quite stable .
If you've written UIs in both Apache Wicket and ICEFaces, how do they compare?
My cursory look at ICEFaces suggests it provides more "out of the box", but perhaps it is more difficult to extend.
Which one leads to cleaner code and separation of concerns?
Is either faster to prototype in, or easier to code?
What are the advantages and disadvantages of each?
ICEFaces is a component library for JSF, you really should compare JSF to Wicket.
Wicket also has component libraries, check WiQuery for example.
Some pointers:
Reasons to choose Wicket over JSF and Spring MVC
JSF, Icefaces and custom components experiences
I was currently looking at S#arp Architecture. It seems to be still too young to develop anything on top of it.
Is there any alternative to S#arp that include support for NHibernate (fluent a plus), testing and MVC?
I would strongly advice you to just pick up ASP.NET MVC and use fluent nhibernate as your repository. Though Sharp architecture is pretty cool as well.