Rapid Development with Python, Django, and Google App Engine Guido van Rossum (Google) Learn how to create great web applications quickly on Google App Engine using the Django web framework and the Python language. Google App Engine lets you host complete, scalable web applications written in Python with minimal fuss. This tutorial assumes basic familiarity with Python but definitely no advanced Python knowlege; Django experience is optional. You will learn how to use the Django web framework with the datastore API provided by Google App Engine, and how to get the most mileage out of the combination. You will also see how to use Django best practices like unit testing when developing for Google App Engine.

Providing the complexity of web applications that can be developed with Django and Google App Engine, the need for Desktops remains present but we can question the need for virtual solutions in common applications such as Virtual Bridges.

Comments are open!

[VIDEO TUTORIAL] PHP & MySQL (Course 03 Configuring For Php).avi

9 min – 21-Feb-07

[VIDEO TUTORIAL] PHP & MySQL (Course 03 Configuring For Php).avi Read the rest of this entry »

Modeling Application Usage Visually
Google engEDU
37 min – Apr 24, 2006

Google TechTalks
April 24, 2006

Scott Barber
Scott Barber is the CTO of PerfTestPlus, Inc. and Co-Founder of the Workshop on Performance and Reliability (WOPR). Scott’s particular specialties are testing and analyzing performance for complex systems, developing customized testing methodologies, group facilitation and authoring instructional materials.

ABSTRACT
Modeling application usage is more than just parsing log files and calculating page frequencies. Whether we are analyzing navigation path effectiveness, planning for scenario testing, documenting performance test workload models or mapping services or objects to user activity having a single, intuitive picture to reference makes the job easier.

In this session, we’ll explore a highly adaptable method for visualizing application usage and how to use this model to improve cross-functional team communication without requiring team members to invest time learning some new fad of a modeling language that they’ll probably never use again. This method references UCMLâ„¢ which has been described as "what collaboration diagrams should have been." Read the rest of this entry »

Salesforce.com AppExchange Overview and Q&A
Google engEDU
1 hr 3 min – Aug 15, 2007

Google Tech Talks
August 18, 2007

ABSTRACT

Wondering why developers are talking about Salesforce.com and Appexchange?

What’s the big deal? Software for sales teams? Big whoop?

Salesforce.com has pioneered a business application development and delivery model and they have proven it to the tune of thousands of business customers of all sizes who swear by them.

And why do developers care?

Because Salesforce has opened up their infrastructure for developers to leverage in building their own applications. Bang! Instant scalability and reliability!

Wow! So developers save thousands by not having to build their own data center?

Ah, but there’s more! Salesforce has created a revolutionary platform for developers to market, sell, and distribute their applications!

All On-Demand, no infrastructure required!

Now that is a big deal!

Come hear the Salesforce developer relations team talk about how it all works…

Their pioneering distribution platform: the Appexchange Their On-Demand developer platform: Apex Their developer network: Apexdeveloper network Read the rest of this entry »

Ruby Sig: How To Design A Domain Specific Language
Google engEDU
1 hr 3 min – Oct 5, 2006

Google Tech Talks
October 5, 2006

David Pollak has been developing commercial software for 28 years. He founded Athena Design and wrote Mesa, the first real-time spreadsheet. David wrote Integer, the first online, collaborative spreadsheet. Since 2000, David has been developing domain specific languages for security and general web development.

ABSTRACT
David will describe a framework for developing DSLs which includes:

* Identifying the constituents in a development project;
* Determining the costs and benefits of a DSL for a particular constituency vs. hand-coding functionality for that constituency based on interviews and specs;
* Identifying the ‘thought leader’ in a given constituency and interviewing him or her to determine the semantics of the domain;
* Determining syntax of the DSL;
* Mocking up the DSL and ‘test driving’ it with the thought leader;
* Finding appropriate integration points for the DSL into the application;
* Defining the process by with the Domain Experts will update code in the DSL (e.g., they have a web page where they can change tax calculation rules vs. they make a change to particular Ruby files as part of a development/staging/production cycle.); and
* Iterate over the semantics, syntax, and process to fully integrate Domain Experts into the development process. Read the rest of this entry »