Re: How barracuda explain about DOM problem?

At 04:27 PM 11/13/2003 +0700, you wrote:
>My friend discuss to me that barracuda use dom. It make barracuda use more 
>memory. What do you think? And he suggest me to use webwork2. but I still 
>love in barracuda model. It would be appreciated if you compare barracuda 
>to webwork2 .
>

I'm not very familiar with Webwork, so I can't say much of anything about 
it.  Keep in mind that Barracuda's component model uses the DOM.  Barracuda 
provides an event model and forms model that have nothing to do with the 
DOM.  As such, you should be able to use any presentation strategy that you 
want.  Of course, other frameworks I've seen have tended to combine the 
view strategy with the controller strategy (or even the 
model).  Barracuda's strength is that it keeps these separate.

It is true that the DOM takes up a bit of memory.  However, you gain the 
benefits of complete programmatic access to the entire presentation object 
rather than dealing with a bunch of strings.  This means you have no 
specific need for templating. Your HTML or XML object is your template (and 
your storyboard).  Of course, Barracuda also provides BTemplate, which uses 
a templating strategy that leaves the template as valid markup, rather than 
some proprietary embedded language which makes it invalid unless fully parsed.

What presentation strategy does Webwork2 use?  How does its controller 
work?  Is it based on Real events which are chainable like in Barracuda, or 
is it based on string matching in a config file?  It seems you like the way 
Baracuda works, so I won't try to sell it to your further.  I'll just 
suggest that you investigate the questions above and come to a conclusion 
of whether Barracuda or Webwork2 is the way to go.

Also, maybe you can provide a synopsis of Webwork2 so the rest of us can 
understand what it does.

Jake