Django, What is it, Why is it cool?
•Télécharger en tant que PPT, PDF•
8 j'aime•6,425 vues
This text presentation attempts to hit on the highlight features and structure of Django and its ecco-system. It is intended as an introduction for those who are curious about , what is it?
![Why do I care? ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],http://oswco.com](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (6)
Similaire à Django, What is it, Why is it cool?
Similaire à Django, What is it, Why is it cool? (20)
Dernier
Dernier (20)
Django, What is it, Why is it cool?
- 1. Django, What is it, Why is it cool? 'Cause it is built on Python and has Pinax on top, and they are all Open Source http://oswco.com
- 3. Django Is a Python Framework Not just a Web framework What is Python? http://oswco.com
Notes de l'éditeur
- If I don't know what Python or Pinax is, why should I care? First slide needs to grab attention. Make a statement: "here's what Django can do for you!"
- What is a Modern Framework? HOw does that help me? Here's where a diagrem might help.
- something like this. I am sure this isn't accurate but a comparison would be great. Perhaps followed by a software diagram for both. How about a workflow showing the steps to building an application old school versus Django?
- Good, its important to name drop to establish credibilty and continuity.
- Does this mean the underpinings are already done? How does this improve my need to deploy and maintain a teller application? How does this lower the cost of your company's product? I like this, I think most CIO's would know what a MVC is. How about a contrast of MVC vs MVT?
- Again, I think a workflow diagram showing how a developer goes about developing with C++. Visual Basic, verus Python Django would be helpful. Also, a diagram showing the interdependence on Python, Django and Pinax.
- I think we need some kind of schematic of the hardware layout: where does the logic reside (local server, central servier, workstation). Is it browser based? Smart clent? Disaster recovery? Version control? Can I run two different versions at the same time (conversions)?
- Good, is this where object orientation or SOA resides? So, PInax are pre-assembled objects, DJango is the framework and Python is what? Can that be shown graphically, in some kind of picture?
- Again, this needs to be tied back to a CIO's needs: version control, central administration, security, agility, scalability, reliability. etc.