On 08/20/2013 11:58 AM, Koen Deforche wrote: > Hey Muhammed, > >> 1. RAD toolkit for editing the interfaces (GUI designer preferred): >> While GWT has exciting GUI designer Wt hasn't so when I tried to >> write my first application (addressbook) it took me a full day to >> build the interfaces while GWT took 10min, so I wonder is there any >> suggestion or solution to make interfaces designing much developer >> friendly? > We don't have a designer; we usually start from HTML templates. We > find that this becomes very effective once you start modifying and > adding things, although there is indeed a learning curve involved. Hmm, I didn't notice any mentioning for HTML templates even when I tried to use Wt examples! if that so, I've to design the interfaces by HTML editor (ex. Kompozer or DreamWeaver) then start working with Witty... does it?
> >> 2. Report designer: While GWT can easily integrate to JasperReports >> engine & iReport, Wt hasn't any report designer to be integrated >> although I found OpenRPT which works fine with Qt but it doesn't >> support server mode unlike JasperReports, so do you've any >> suggestion or idea about this point? > Wt includes Wt::Render which is an HTML/CSS to PDF renderer. This is > (in our experience) brilliant for reporting since you can reuse much > of the HTML/CSS that use for displaying the same information on the > user's screen. > > We've expanded this renderer alot within the scope of the current > imminent release. Actually Qt guys say same thing but practically I never find it effective because report engines and their designers make life so easy. > I don't believe they are still using GWT > themselves in their own product development. I don't think that so because Google groups and translate toolkit still have new releases base on GWT. > On a technical side, here are some advantages of using Wt : no need > for implementing client/server protocol with security risks and > performance issues (not too many requests!), no need to artificially > trying to break application in smaller downloads using a complicated > strategy to have faster startup times ... This is very strong point indeed but the main reason of posting this thread was the short period of producing my first application in GWT (As I mentioned before) by comparing to Witty which made me suspicious about Witty although C++/Qt flows in my blood. One of my friends said to me: "speed of producing is relative matter because if we compared ASP.net to PHP we will find PHP absolutely lose but in real life PHP wins so don't care about this speed because when you'll accustomed to Wt your production will increase just like you're using fancy GUI designer"... do you agree with this saying? -- Best Regards, Muhammad Bashir Al-Noimi ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ witty-interest mailing list witty-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/witty-interest
