I did a lot of work on the Drupal 4.x releases way back in the day. It stood out from the rest of the PHP crowd back then because Dries cared so much about what the API would be like to use, both internally and externally. I think Wicket does a reasonable job of this, but we do have some consistency issues and suffer somewhat from there being a hundred different ways to do lots of things. On the other hand, Drupal's API is mostly quite low-level - it doesn't really solve the same problems when it comes to easily running projects across a team of tens of developers and building proper reusable components.
It's genuinely hard to compare the two - they solve different problems in different ways. Drupal tries to help you build modules and things for Drupal. Wicket tries to help you build pretty much anything you want on the web. It's almost like trying to compare sed and Java. They both let you do String manipulation, but... Regards, Al On 04/01/2008, Ahmed Al-Obaidy <[EMAIL PROTECTED]> wrote: > Thanks Martin, > > RAP is very interesting framework, but IMHO, it misses a lot of the charm of > the Web. It copies the Eclipse platform as it is to the Web, and maybe it is > not a great idea. > > > Hi Nino, I hope you are doing well, > > I prefer Drupal approach for these reasons, please correct me when I'm wrong: > > We don't need to write HTML page for each Web page, forms and views are > generated on runtime with the help of the theme engine. > Its something like task oriented framework rather than page oriented. I > mean you don't write pages. you write a part of page. and without markup. The > creation of page is done by the framework. > > There are a lot of other things, but I'm in hurry now :D > > cheers, > Ahmad > > > --------------------------------- > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it > now.
