Your reply message has not been sent.
Your post was successful
On 04-05-12 19:15, Etienne B. Roesch wrote:
> So, have you made a decision about the way to go for your application?
for the spots where we need it (we'll use backbone to clean up on part
of the UI).
> I like the idea of using two different systems from the backend and theAnd... with django's staticfiles handling you can even bundle
> frontend. I am new to django (a month+), but I don't think there was
> ever a doubt in mind that my frontend would be .js based, and I liked
> that django dev let /static to be dealt with by say plain Apache,
> instead of enforcing python for that too.
js/css/images per app and Django'll combine it all together. Works great.
> As I said, I am new to django, but I have done some experiments (wroteDjango has always been frontend-agnostic. There's only the admin
> my own little hello world app, moved on to deploying mezzanine to
> dotcloud), and as I understand django is meant to be a flexible system
> to handle data, and was never meant to be a flexible frontend, right?
interface, for the rest you have to build everything yourself.
> Now, even though I do like the proper tools for the proper jobs, theWell, if the separation is clean enough, it is fine. Just make sure you
> perspective of maintaining two systems built on different technologies
> raises red flags. What do people think?
don't tie them together too much.
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.