Thank you all for your responses. They've been very helpful. Things like the built-in browser compatibility, future-proofing, XSS immunity, smaller load requirements, etc, are the reason I asked this question; in that regard, Wt definitely has the advantage over tntnet. What I'm building definitely qualifies more as a "page-based" design, though, which is why the template-based design seems more natural to me in this situation. That said, I think I'll still try to take the Wt approach, just for the other advantages it offers, as I feel they are numerous enough to warrant changing my way of thinking a bit.
Thanks for all the help, Shadowcat Dushan Savich wrote: > Hi all, > > I second mobi and Wim . > For example. I don't know nothing about JavaScript( let alone AJAX ) , > and yet, I can make interactive web applications :) . > Unlike web sites , web applications are more like normal GUI apps, and > I like "attacking" the problem with GUI design . > > > Cheers! > Dushan > > > > ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
