|
RE: Case Study: XMLC vs. Velocity: msg#00102java.enhydra.xmlc
> According to the rumor, doesn't Barracuda has even higher learning > curve then XMLC? ;) Oh yeah, of course. Its definitely only for "real programmers" ;-) (ok, ok, I'm just kidding in case someone didn't understand my sarcasm!!!) Barracuda _does_ have a steeper learning curve, but the payoff is amazing, both in terms of time-to-implement and in terms of maintainability. The initial phases of the project were always focused on getting it architecturally right, rather than trying to just make it really easy right up front. We've spent the last year and a half here at ATMReports actually using Barracuda to build production apps, and I wish I could show you some of the things we are doing...I think they are impressive in that they provide a very sophisticated web interface (all reports are sortable, filterable, customizable, cross-browser, can be downloaded as Excel files, etc), and yet at the same time the code is extremely maintainable. In short, the app architecture scales very well. At any rate...all this to say that we've been learning an awful lot about how to make Barracuda easy (for our own developers to implement). I hope to eventually put together a sample app that would provide a very good starting point for others to look at, but it probably won't happen until the current project winds down (end of the year). Once all this is done, I'd like to investigate creating an IDE plugin on top of all that...but that's probably a ways down the road still ;-) Christian ---------------------------------------------- Christian Cryder Internet Architect, ATMReports.com Project Chair, BarracudaMVC - http://barracudamvc.org ---------------------------------------------- "Coffee? I could quit anytime, just not today" > -----Original Message----- > From: xmlc-admin@xxxxxxxxxxx [mailto:xmlc-admin@xxxxxxxxxxx]On Behalf Of > David Li > Sent: Wednesday, September 17, 2003 10:06 AM > To: xmlc@xxxxxxxxxxx > Subject: Re: Xmlc: Case Study: XMLC vs. Velocity > > > > >> I wonder if we should try to work on a higher level API over the DOM > >> based approach and try to reduce the high initial learning curve and > >> also the tedious low level DOM manipulation. > > > > Barracuda, my friends! :-) > > According to the rumor, doesn't Barracuda has even higher learning > curve then XMLC? ;) > > OK, kidding aside, I am not thinking about framework level. Not with > all the event and component abstraction. Just some nicer ways to deal > with DOM tree and make XMLC easier to integrate with other framework. > > David Li > > _______________________________________________ > XMLC mailing list > XMLC@xxxxxxxxxxx > http://www.enhydra.org/mailman/listinfo.cgi/xmlc
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | RE: Case Study: XMLC vs. Velocity, Christian Cryder |
|---|---|
| Next by Date: | Re: XMLC 2.2.1 release, Jacob Kjome |
| Previous by Thread: | Re: Case Study: XMLC vs. Velocity, David Li |
| Next by Thread: | Re: [news] Case Study: XMLC vs. Velocity, Douglas Harris |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |