Guys i would like to use Django as my backend framework and qooxdoo as the frontend framework.
伙计们我想用Django作为我的后端框架,qooxdoo作为前端框架。
Is it practical to do this?
这样做是否切实可行?
Has anyone tried to do this?
有没有人试过这样做?
How did they do it?
他们是如何做到的呢?
Links and pointers would nice.
链接和指针会很好。
Gath
1 个解决方案
#1
5
I have no direct experience using Django and qooxdoo, but the general answer to the question "Is it practical?" is: yes :). Although Django's default rendering behaviour is to produce HTML (which is unsuitable for a single page application like the ones you build with qooxdoo), it's easy to switch to returning e.g. Json on requests, which is a common format for the client-server communication between a qooxdoo frontend and a server. They just exchange data.
我没有使用Django和qooxdoo的直接经验,但对“这是否实用?”这一问题的一般回答。是是的 :)。虽然Django的默认渲染行为是生成HTML(不适合像qooxdoo那样构建的单页应用程序),但很容易切换到返回例如:请求Json,这是qooxdoo前端和服务器之间客户端 - 服务器通信的通用格式。他们只是交换数据。
Has anyone tried to do this? - Yes, but they don't give much information on how, other than the before mentioned Json data exchange, implementing a Json RPC server in Django using RPC4Django.
有没有人试过这样做? - 是的,但他们没有提供太多信息,除了前面提到的Json数据交换之外,如何使用RPC4Django在Django中实现Json RPC服务器。
AFAIK, there is no deeper Django integration, e.g. interfacing qooxdoo with Django views on the server (like dojango).
AFAIK,没有更深层次的Django集成,例如:在服务器上连接qooxdoo和Django视图(如dojango)。
Hope this helps.
希望这可以帮助。
Update:
- There is one elaborate product, Sava, using qooxdoo for the frontend and Django for the backend. There is a short overview, but I think it's closed-source so it only testifies to the "practicality" of using this technology stack. You probably won't learn in detail how it is realized.
- There is also enre, a qooxdoo-based GUI for Django. But I'm not familiar with it, and couldn't find any documentation on first glance, so I'm not sure what this really means.
有一个精心制作的产品,Sava,前端使用qooxdoo,后端使用Django。有一个简短的概述,但我认为它是封闭源,所以它只能证明使用这种技术堆栈的“实用性”。您可能不会详细了解它是如何实现的。
还有一个基于qooxdoo的Django GUI。但我不熟悉它,乍一看也找不到任何文档,所以我不确定这是什么意思。
#1
5
I have no direct experience using Django and qooxdoo, but the general answer to the question "Is it practical?" is: yes :). Although Django's default rendering behaviour is to produce HTML (which is unsuitable for a single page application like the ones you build with qooxdoo), it's easy to switch to returning e.g. Json on requests, which is a common format for the client-server communication between a qooxdoo frontend and a server. They just exchange data.
我没有使用Django和qooxdoo的直接经验,但对“这是否实用?”这一问题的一般回答。是是的 :)。虽然Django的默认渲染行为是生成HTML(不适合像qooxdoo那样构建的单页应用程序),但很容易切换到返回例如:请求Json,这是qooxdoo前端和服务器之间客户端 - 服务器通信的通用格式。他们只是交换数据。
Has anyone tried to do this? - Yes, but they don't give much information on how, other than the before mentioned Json data exchange, implementing a Json RPC server in Django using RPC4Django.
有没有人试过这样做? - 是的,但他们没有提供太多信息,除了前面提到的Json数据交换之外,如何使用RPC4Django在Django中实现Json RPC服务器。
AFAIK, there is no deeper Django integration, e.g. interfacing qooxdoo with Django views on the server (like dojango).
AFAIK,没有更深层次的Django集成,例如:在服务器上连接qooxdoo和Django视图(如dojango)。
Hope this helps.
希望这可以帮助。
Update:
- There is one elaborate product, Sava, using qooxdoo for the frontend and Django for the backend. There is a short overview, but I think it's closed-source so it only testifies to the "practicality" of using this technology stack. You probably won't learn in detail how it is realized.
- There is also enre, a qooxdoo-based GUI for Django. But I'm not familiar with it, and couldn't find any documentation on first glance, so I'm not sure what this really means.
有一个精心制作的产品,Sava,前端使用qooxdoo,后端使用Django。有一个简短的概述,但我认为它是封闭源,所以它只能证明使用这种技术堆栈的“实用性”。您可能不会详细了解它是如何实现的。
还有一个基于qooxdoo的Django GUI。但我不熟悉它,乍一看也找不到任何文档,所以我不确定这是什么意思。