← Back to team overview

ubuntu-developer-manual team mailing list archive

Re: Developers' Manual Chapter Layout

 



On 01/05/2011 02:41 PM, Kyle Nitzsche wrote:
Hi

A few quick thoughts below.

Prologue
Part 1: Overview and Intro
Chapter 1: Introduction to the tools (currently called "Introduction to
Ubuntu Application Development")
Chapter 2: A fly though of building an app (currently $quickly tutorial)
Chapter 3: Python Language Crash Course (may be more suitable as an
appendix?)
I think Python Crash Course should be an appendix (or separated, maybe later) because: * it is not unique to Ubuntu app development *per se*, which this guide should be tightly focused on
 * many readers already know python

Part 2: Building an App
Chapter 4: Getting Started (Currently Creating an application with
Quickly, but with some meat added)
Chapter 5: Glade
etc...
I wonder if Getting Started and Glade are really so intertwined they should be one chapter. Or rather, if Building an App should be split into chapters that reflect that actual process & work flow of building an app. So this Part takes the user through building that sample app, with chapters in the natural order.
Chapter 9: Index of Common APIs
I'd put that (API index) in an appendix and reference it from content. Again, it is not unique to Ubuntu app dev.
Part 3: Collaborating and Sharing
Chapter 10: Using bzr for versioning and collaborating
Chapter 11: Using Launchpad to Manage Your Project
Is that really two different chapters? For some reason I tend to think of Bzr and LP as a single entity - even though I know they're not.


Canonical
belinda.lopez@xxxxxxxxxxxxx
dinda@xxxxxxxxxx
IRC: dinda
Office: Galveston, Texas
--
Ubuntu - Linux for Human Beings
http://www.ubuntu.com
http://www.edubuntu.org	
http://www.canonical.com
---------------------------




Follow ups

References