dabodoc Commit
Revision 46
Date: 2007-05-22 09:00:31 -0700 (Tue, 22 May 2007)
Author: Nate
Trac: http://svn.dabodev.com/trac/dabodoc/changeset/46
Changed:
U trunk/book/DaboBook.tex
U trunk/book/Introduction/DaboInstallation.tex
U trunk/book/Introduction/WhatIsDabo.tex
U trunk/book/Preface.tex
Log:
Removed the annoying tags. The copyright on the bottom of every page didn't
quite look good so I commented it out.
Diff:
Modified: trunk/book/DaboBook.tex
===================================================================
--- trunk/book/DaboBook.tex 2007-05-22 06:59:26 UTC (rev 45)
+++ trunk/book/DaboBook.tex 2007-05-22 16:00:31 UTC (rev 46)
@@ -57,7 +57,7 @@
%Define variables
\renewcommand{\title}{The Dabo Book} %Title Goes Here
-\newcommand{\subtitle}{3-Tier Application Made Easy} %Subtitle Goes Here
+\newcommand{\subtitle}{3-Tier Applications Made Easy} %Subtitle Goes Here
\renewcommand{\author}{Paul McNett, Nathan Lowrie}
%Author Goes Here
\newcommand{\copyrightHolder}{Ed Leafe, Paul McNett, et. al.} %Copyright
Holder Goes Here
\newcommand{\subject}{3-tier desktop applications}
%Subject Goes Here
@@ -127,7 +127,7 @@
% as determined above---in non-upper
case in the header, to the left on even pages.
%Displays the
lower-level (section) information---as
% determined above---in the header,
to the right on odd pages.
-\fancyfoot[c]{\textcopyright\ 2004-2007 \copyrightHolder}
+% \fancyfoot[c]{\textcopyright\ 2004-2007 \copyrightHolder}
\fancyfoot[LE,RO]{\thepage}
\fancyfoot[LO,RE]{\today}
\renewcommand{\headrulewidth}{1.3pt} %Underlines the header. (Set to 0pt
if not required).
Modified: trunk/book/Introduction/DaboInstallation.tex
===================================================================
--- trunk/book/Introduction/DaboInstallation.tex 2007-05-22 06:59:26 UTC
(rev 45)
+++ trunk/book/Introduction/DaboInstallation.tex 2007-05-22 16:00:31 UTC
(rev 46)
@@ -2,7 +2,7 @@
\chapter{Installation of the Dabo Development Environment}
-This chapter details the process for getting your computer set up for
developing applications using Dabo. While these instructions would work for
your deployment targets as well, there are better ways to deploy applications
than by using the instructions here. Dabo has dependencies on a number of
external libraries, and while developing your applications you'll want to keep
all those libraries - and Dabo - as current as possible. For deployment, you
want better control over the versions in use. Deploying applications is covered
in <xref linkend="dabo-ap-b"/>.
+This chapter details the process for getting your computer set up for
developing applications using Dabo. While these instructions would work for
your deployment targets as well, there are better ways to deploy applications
than by using the instructions here. Dabo has dependencies on a number of
external libraries, and while developing your applications you'll want to keep
all those libraries - and Dabo - as current as possible. For deployment, you
want better control over the versions in use. Deploying applications is covered
in (need link).
\section{Downloading and Installing}
@@ -34,7 +34,7 @@
[GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-5)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>
-You are now inside Python's command interpreter. Test to make sure that
<application>MySQLdb</application>, <application>wxPython</application>, and
<application>dabo</application> load correctly. If there are no errors, they
are installed correctly.
+You are now inside Python's command interpreter. Test to make sure that
MySQLdb, wxPython, and Dabo load correctly. If there are no errors, they are
installed correctly.
>>> import MySQLdb
>>> import wx
@@ -42,4 +42,4 @@
Dabo Info Log: Thu Sep 9 19:16:23 2004: No default UI set. (DABO_DEFAULT_UI)
>>>
\end{verbatim}
-The message from <application>dabo</application> is normal, and no errors
happened during the import of the other packages, so everything is set up
correctly on my system.
\ No newline at end of file
+The message from Dabo is normal, and no errors happened during the import of
the other packages, so everything is set up correctly on my system.
\ No newline at end of file
Modified: trunk/book/Introduction/WhatIsDabo.tex
===================================================================
--- trunk/book/Introduction/WhatIsDabo.tex 2007-05-22 06:59:26 UTC (rev 45)
+++ trunk/book/Introduction/WhatIsDabo.tex 2007-05-22 16:00:31 UTC (rev 46)
@@ -14,12 +14,12 @@
\section{Flexible Database Support}
-Dabo supports all databases for which there is a Python wrapper that conforms
to the dbapi version 2. This includes all popular databases, as illustrated in
<xref linkend="fig-tier1-1"/>. <warning>Please note that this book is being
written for future benefit, and that as of this writing the only supported
databases are MySQL, Firebird, and Sqlite, and MySQL is the most
tested.</warning>
+Dabo supports all databases for which there is a Python wrapper that conforms
to the dbapi version 2. This includes all popular databases, as illustrated in
(need fig-tier1-1). Please note that this book is being written for future
benefit, and that as of this writing the only supported databases are MySQL,
Firebird, and Sqlite, and MySQL is the most tested.
\section{Flexible User Interface Support}
-After version 1.0, Dabo will support a selection of user-interface libraries,
as illustrated in <xref linkend="fig-tier3-1"/>. The support of multiple
libraries while allowing the Dabo developer to use a common API makes Dabo a
very flexible, powerful solution. Different toolkits have their pros and cons;
you can choose which one to deploy and not worry too much about that during
development. You could conceivably do all your development using one toolkit
and deploy with another. You may have one deployment using PyQt, and another
using wxPython, both using the same codebase. <warning>Please note that this
book is being written for future benefit, and that as of this writing the only
supported user interface is wxPython.</warning>
+After version 1.0, Dabo will support a selection of user-interface libraries,
as illustrated in (need fig-tier3-1). The support of multiple libraries while
allowing the Dabo developer to use a common API makes Dabo a very flexible,
powerful solution. Different toolkits have their pros and cons; you can choose
which one to deploy and not worry too much about that during development. You
could conceivably do all your development using one toolkit and deploy with
another. You may have one deployment using PyQt, and another using wxPython,
both using the same codebase. Please note that this book is being written for
future benefit, and that as of this writing the only supported user interface
is wxPython.
\section{Cross-platform Support}
-Dabo is truly multi-platform. Develop on any supported platform, and deploy
the same code base to any supported platform. The supported platforms are
Macintosh OS X (10.2 or higher), Linux, and Windows (98SE or higher). <xref
linkend="fig-multiplatform-lin"/>, <xref linkend="fig-multiplatform-osx"/>, and
<xref linkend="fig-multiplatform-win"/> show the same Dabo-developed
application running on all three platforms.
+Dabo is truly multi-platform. Develop on any supported platform, and deploy
the same code base to any supported platform. The supported platforms are
Macintosh OS X (10.2 or higher), Linux, and Windows (98SE or higher). (need
fig-multiplatform-lin), (need fig-multiplatform-osx), and (need
fig-multiplatform-win) show the same Dabo-developed application running on all
three platforms.
Modified: trunk/book/Preface.tex
===================================================================
--- trunk/book/Preface.tex 2007-05-22 06:59:26 UTC (rev 45)
+++ trunk/book/Preface.tex 2007-05-22 16:00:31 UTC (rev 46)
@@ -6,13 +6,13 @@
For over a decade, the situation was mutually beneficial: the large company
got to make billions off its operating system, and the developer got to make a
living selling solutions using low-priced development tools provided by that
same large company.
-Something started happening, however, late in the 1990's. At a time when
everyone thought Unix was uttering its final words, "Linux" became a household
term. A student's hobby in 1991 became a world-class enterprise operating
system by 1998, and since then Linux has made impressive gains in the user
application space: the desktop. At about the same time, Apple Computer released
Darwin - another Unix based operating system - to the open source world and
built a rock-solid user friendly interface on top of it, and today Apple's
successful future seems guaranteed: elegant, user-friendly applications built
on top of Darwin/OS X, such as <application>iTunes</application>,
<application>iPhoto</application>, <application>iDVD</application>, and
<application>iMovie</application> are reverberating among a growing user base.
+Something started happening, however, late in the 1990's. At a time when
everyone thought Unix was uttering its final words, "Linux" became a household
term. A student's hobby in 1991 became a world-class enterprise operating
system by 1998, and since then Linux has made impressive gains in the user
application space: the desktop. At about the same time, Apple Computer released
Darwin - another Unix based operating system - to the open source world and
built a rock-solid user friendly interface on top of it, and today Apple's
successful future seems guaranteed: elegant, user-friendly applications built
on top of Darwin/OS X, such as iTunes, iPhoto, iDVD, and iMovie are
reverberating among a growing user base.
-A sea change is underway. Up until now, and into 2006, the open source
community has been playing catch-up with Microsoft, trying to make applications
that do everything the typical Microsoft Windows user expects, in the same
ubiquitous fashion. As I type this (September 2004) I can say that the open
source community has almost caught up.
<application>OpenOffice.org</application> is approaching version 2.0, and can
already replace <application>Microsoft Office</application> for all but the
most complex <application>Word</application>,
<application>Powerpoint</application>, and <application>Excel</application>
documents. <application>Mozilla FireFox</application> and
<application>ThunderBird</application> are approaching 1.0, and already handle
browsing and emailing better than <application>Microsoft Internet
Explorer</application> and <application>Outlook</application>. The Gnome and
KDE Linux desktops, besides being fast and stable, now have all the goodies any
modern user would want. From now on, the catch-up phase is over, and real
innovation will begin to be defined not by one huge company, but by a
loosely-knit community of open source developers from all over the world. The
big company will have to become a part of that community - and play by its
rules - or risk being sucked into the undertow.
+A sea change is underway. Up until now, and into 2006, the open source
community has been playing catch-up with Microsoft, trying to make applications
that do everything the typical Microsoft Windows user expects, in the same
ubiquitous fashion. As I type this (September 2004) I can say that the open
source community has almost caught up. OpenOffice.org is approaching version
2.0, and can already replace Microsoft Office for all but the most complex
Word, Powerpoint, and Excel documents. Mozilla FireFox and ThunderBird are
approaching 1.0, and already handle browsing and emailing better than Microsoft
Internet Explorer and Outlook. The Gnome and KDE Linux desktops, besides being
fast and stable, now have all the goodies any modern user would want. From now
on, the catch-up phase is over, and real innovation will begin to be defined
not by one huge company, but by a loosely-knit community of open source
developers from all over the world. The big company will have to become a part
of that community - and play by its rules - or risk being sucked into the
undertow.
We aren't quite there yet. One very important missing piece for software
development on Linux or Mac is a comprehensive, easy-to-use, flexible
Integrated Development Environment (IDE), such as Microsoft Visual Basic, that
lets people develop powerful applications without necessarily having to know
how to write great code. An IDE is basically a collection of power tools, such
as a visual form designer, a graphical debugger, a project manager, and a help
system. Until such an application becomes available, the only people developing
open source applications will be people comfortable with the command line, make
files, and a c compiler.
-Enter Dabo, an open source, data aware, 3-tier development framework that
you can use to develop open source and/or proprietary applications for
distribution to your customers. Dabo aims to be easy to learn, fun to work
with, flexible, and powerful. You can program in Python by hand using any
editor, or you can use the Dabo IDE which centralizes all the files in your
project and offers all the power tools you need to create your databases, build
your user interface, write your business rules, and create your reports
(printouts or previews of your data, formatted the way you define).
+Enter Dabo, an open source, data aware, 3-tier development framework that you
can use to develop open source and/or proprietary applications for distribution
to your customers. Dabo aims to be easy to learn, fun to work with, flexible,
and powerful. You can program in Python by hand using any editor, or you can
use the Dabo IDE which centralizes all the files in your project and offers all
the power tools you need to create your databases, build your user interface,
write your business rules, and create your reports (printouts or previews of
your data, formatted the way you define).
%Not really sure what this is so I commented it out.
%Intro paragraph - first paragraph style
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/dabo-dev/[EMAIL PROTECTED]
