Trying to navigate the world of Cappuccino here. Looking for feedback from colleagues at StackOverview on the structure outlined below - the goal being to leverage the unique advantages of Django and Cappuccino without duplicating efforts...
When a 'friendly' URL is requested by the web browser (e.g., /, /articles, etc):
- Catching this request, DJango's urls.py identifies a view.
- Rather than following DJango's usual process of populating a template with the locals dict,
the view returns the concise HTML snippet used in a Cappuccino app directly. - The client fetches the Cappuccino HTML.
- Subsequently, the client seeks out the Objective J JS URLs referenced in the HTML snippet.
- The end-user app materializes and gets displayed on the browser.
A functioning app is now available in the browser. When the user initiates an action that requires server interaction:
- The browser dispatches an XMLHTTPRequest to a specific URL.
- DJango's URLs.py directs this request to a corresponding view.
- The view carries out its tasks, potentially engaging with the DB model. However, instead of serving a template, Django replies with JSON data.
- The client receives the JSON content and performs necessary actions accordingly.
Does this approach seem logical? We maintain the advantage of user-friendly URLs and benefit from the database setup done automatically for our coding needs. Rather than relying on templates, we offer Cappuccino stub pages and JSON responses to deliver a more app-like experience to users rather than an HTML templating system.
Is there a better alternative method? What are the preferences of other Python programmers? Appreciate any insights you can provide. Thank you!