Ok, first, let me say, this is more a question of comparing two different approaches than of comparing two different frameworks. I don't know how many of you are aware of tntnet's existence, but it's a... competing? framework for using C++ in web design. The biggest difference between tntnet and witty, and the one I want to explore, is that it uses a template-based design (like PHP, Ruby on Rails, etc.) rather than the GUI-based approach of witty. The reason that I'm sending this message is that, as one more familiar with the tntnet approach than the Wt approach for web design purposes, I'm having trouble seeing the advantages of the GUI design. It seems to me that the template design is faster, for one who already knows HTML, than learning the Wt API. But, I've been reading some of the list archives, and I see a lot of you complain about the template design, but no one has (as far as I've seen) elaborated on WHY the template design is bad.
I do see one benefit to the GUI design - the ability to dynamically change the properties of a given widget using (for example) WWidget->setStyleClass(). I can definitely see the benefits of that, but I'd like to know more on the pros and cons of GUI-based design for web, as opposed to template design. And I want to know both "Why is GUI design good?" and "Why is template design bad?" For those who are unfamiliar with tntnet, the code is also pre-compiled, just as Wt's is, so there's no overhead involved in the parsing - or if there is overhead, it should exist only during the compile. I see a lot of good things that I like about Wt - the ability to deploy under Apache as a FastCGI script, for one. I'd like to continue exploring Wt as a possibility, but at current, I'm seeing the template design as an easier option that will shorten development time, and that alone is making me lean toward tntnet even though I see the capabilities, documentation, support, deployment options (I don't believe tntnet can be deployed on win32), community, reputation, history, amount of development, and so on, all seem to be better on Wt's end. So, basically, what I'm getting at is... convince me otherwise! I know everything I hear will be biased toward Wt, but that's a good thing, because I want to hear arguments in Wt's favor; I'd rather use Wt, if I can find a way to justify the perceived extra development time to my employer, or if I can be convinced that the development time would not, in fact, be that much longer. Thanks! Shadowcat ------------------------------------------------------------------------------ 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
