Hi I am a java guy myself. from what i know some famous java framework has adopted dojo as their default support for their client side tech. And the Struts2 used to include dojo as their native support, now as a plugin i think.
I an understand why your java guy is always mvc this mvc that. Its almost what we talk about when it comes to design. I think it really depends on why you need MVC on your javascript side. If your client side need to be run in different environment. for example, browser (online, offline with gears), or in AIR with the same code. Then MVC is probably what you have to consider. I am not too familiar with dojo, only used it for a while when i wasnt good at javascript, but hated the complicated API. I personally really like ExtJS's way of doing things, even though i use jQuery now.^^ I think the main reason(as far as i can think of) for doing MVC is when you are in a situation where your client side(javascript) does not know where your data is coming from and the format will change. ie. JSON, XML, or even plain text. here is just my opinion correct my if i am wrong on anything On Sun, Sep 13, 2009 at 9:59 AM, mattkime <mattk...@gmail.com> wrote: > > My new employer produces a web app which relies on Dojo. I haven't > been impressed with their use of Dojo and am hoping they'll let me > introduce them to jQuery. There is considerable resistance. The > project architect is java guy so it frequently seems like we're > talking two different languages when we discuss js frameworks. I'm all > "DOM this, and cross-browser that" and he's all "widget this and mvc > that" > > Which has me thinking - have any of you seen a reason to implement a > MVC layer in your js? > > Its my impression that MVC tries to solve a problem that js doesn't > particularly have. > > thanks, > matt > > p.s. sorry if this is a little off topic, but i wanted to get opinions > from fellow jQuery users.
