Hey Muhammed, 2013/8/20 Muhammad Bashir Al-Noimi <mbno...@gmail.com>: >> 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?
I would rather suggest emacs or some sort of editor. >>> 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. But at least the HTML/CSS way doesn't require you to learn a new specialized tool, you can simply reuse your HTML/CSS skills. >> 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. I was rather implying that they are not basing any new work on GWT (or otherwise it's a bit odd to explain that they've abandoned it?) > 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. Generating UI's is quicker until you need start changing things or deviate from the paved standard path? Honestly, we also use Qt Designer when we need to create an occasional dialog in Qt which has a completely static layout. But most of our application are more complex than that. And maintaining generated code isn't a panacea either. > 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? You have good friends! Regards, koen ------------------------------------------------------------------------------ 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
