You did kinda answer the question. It's good to know that others are going through this too. I was looking for confirmation that this was actually a problem.
The spaghetti code, I definitely see that too. Because of the glob of junk that you have to deal my projects end up being a lot of glue and duct tape with a little bit of actual stuff in it. Thanks for sharing. On Apr 8, 2:43 pm, Scott Newman <snewma...@gmail.com> wrote: > > I've been looking at a couple of RIA frameworks, namely Sproutcore and > > Cappuccino. The feel a bit too heavy for me. Sproutcore does not > > integrate well with Django > > The reason I'm posting is to ask the community if they have know of > > anything that is at a higher level than jQuery + jQuery UI and a lower > > level than Sproutcore/Cappuccino. I'd like to find something that has > > this kind of stuff in it: > > - Client-side Javascript MVC implementation (Both Sproutcore and > > Cappuccino have controllers and view) > > - Easy layouts (I really > > likehttp://cappuccino.org/learn/tutorials/automatic-layout/) > > - Data bindings (Step 4 > > onhttp://www.sproutcore.com/documentation/hello-world-tutorial-2-your-f...) > > When I looked into some of the heavier JavaScript application > frameworks such as SproutCore, Cappucino, and ExtJS, the biggest > hurdle I faced was my own approach. > > These frameworks are designed to build complete web applications, not > to be sprinkled within Django template files the way I might do with > jQuery. After talking with Erich from the SproutCore project, I > decided the best approach was to build the entire front-end > application in static HTML, CSS, and JavaScript, relying on ajax calls > to Django URLs for backend data. (I use Apache to serve my static HTML/ > JS/CSS files and don't even process them with Django to save the > overhead) > > Even with my jQuery projects, my initial results were a morass of > spaghetti code because I was approaching my client-side projects as a > web developer, relying on my experience with what I'd call "request > and response" thinking. I had to study the practices of traditional > stateful, event-driven desktop application development before my > attempts at these projects went more smoothly. (and I'm still > learning!) > > If you settle on a client-side MVC framework, you'll probably want to > keep the frontend and backend completely separate and use Django for > web services calls to send and receive data to the frontend. The > client-side controllers will handle the data calls and binding to the > UI controls in the view. If instead you want a site that's mostly > driven by Django but has some extra functionality, I'd probably stick > with something lighter like jQuery. > > I know this isn't the answer to your question, but since I've faced > the same issues, I thought I'd share. Hope this helps. > > -- Scott --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
