dslinux/user/pixil/docs AUTHORS BUGS ChangeLog ChangeLog.historical LICENSE LICENSE.DUAL LICENSE.GPL LICENSE.LGPL README.ARM README.keyboard README.microwindows README.packages README.pixilDT README.platform README.x11 TODO

amadeus dslinux_amadeus at user.in-berlin.de
Tue Oct 3 13:24:46 CEST 2006


Update of /cvsroot/dslinux/dslinux/user/pixil/docs
In directory antilope:/tmp/cvs-serv11916/docs

Added Files:
	AUTHORS BUGS ChangeLog ChangeLog.historical LICENSE 
	LICENSE.DUAL LICENSE.GPL LICENSE.LGPL README.ARM 
	README.keyboard README.microwindows README.packages 
	README.pixilDT README.platform README.x11 TODO 
Log Message:
adding pristine copy of pixil to HEAD so I can branch from it

--- NEW FILE: README.keyboard ---
Overview
--------
This document describes the customization of the nxkeyboard application.



Quickstart Guide
----------------
Follow these instructions to quickly install and launch the nxkeyboard
application:

1) Create the '/usr/local/microwin/keymaps' directory if it doesn't
   already exist on your system.

2) Copy the keymap and image files for each keyboard you want to be able
   to use into the '/usr/local/microwin/keymaps' directory:

   Small (160x61) keyboard:          sml*.* (8 files total)
   Small (57x76) numeric keypad:     snum.* (2 files total)
   Compact (240x86) keyboard:        com*.* (14 files total)
   Medium (240x103) keyboard:        mid*.* (14 files total)
   Medium (65x86) numeric keypad:    mnum.* (2 files total)
   Large (480x200) keyboard:         big*.* (14 files total)
   Large (129x166) numeric keypad:   bnum.* (2 files total)

   These files will be found in the .../pixil/apps/nanox/nxkeyboard/keymaps
   directory.

3) Launch microwindows and the screentop as you normally would.

4) To display a keyboard, issue one or more of the following commands:

   Small keyboard:    ./nxkeyboard -d /usr/local/microwin/keymaps -m sml &
   Small keypad:      ./nxkeyboard -d /usr/local/microwin/keymaps -m snum &
   Compact keyboard:  ./nxkeyboard -d /usr/local/microwin/keymaps -m com &
   Medium keyboard:   ./nxkeyboard -d /usr/local/microwin/keymaps -m mid &
   Medium keypad  :   ./nxkeyboard -d /usr/local/microwin/keymaps -m mnum &
   Large keyboard:    ./nxkeyboard -d /usr/local/microwin/keymaps -m big &
   Large keypad:      ./nxkeyboard -d /usr/local/microwin/keymaps -m bnum &

   These commands will spawn a copy of the nxkeyboard application with the
   associated keyboard. More than one copy or size of a keyboard may be
   displayed at the same time.

   The -d parameter specifies the full path to the nxkeyboard keymap
   directory, and the -m parameter specifies which mapset to display.



Theory of Operation
-------------------



Creating Custom Keyboard Layouts
--------------------------------


--- NEW FILE: README.pixilDT ---
The PIXIL Desktop PIM Component
May 29, 2003

The PIXIL source distribution includes a set of PIM applications meant
to run on the PDA or embedded device, as well as a workstation PIM
application, known as the PIXIL Desktop.  The PIXIL Desktop can
be built to show PIM synchronization between the PDA applications
and the desktop.

The PIXIL Desktop currently requires an external FLTK library, which
allows building for X11 or Win32 (only X11 is currently tested).
Since PIXIL Desktop requires X11, PIXIL PDA must be built using
Microwindows on top of X11 in order to run both simultaneosly and
demonstrate synchronization.  See README.microwindows for more
information on setting up the PIXIL PDA build.

PIXIL Desktop has been tested using FLTK version 1.0.11,
available from http://www.fltk.org.  Currently, PIXIL Desktop
requires GCC version 2.96 or greater.

Building PIXIL Desktop (after building PIXIL PDA normally)

1.  If required, extract FLTK 1.0.11 into it's own directory,
    and build it:

	tar zxvf fltk-1.0.11-source.tar.gz
	cd fltk-1.0.11
	./configure
	make

2.  Edit the PIXIL config file and select the PIXIL Desktop build:
	CONFIG_PIXILDT=y

3.  Specify the external FLTK directory in the PIXIL config file:
	CONFIG_PIXILDT_FLTK=y
	CONFIG_PIXILDT_FLTKDIR="/usr2/fltk-1.0.11"

4.  (Re)make PIXIL
	Type "make".

7.  Install PIXIL:
	Type "make install".

	PIXIL Desktop will be installed into the $(INSTALL_DIR)/workstation
	directory, normally /usr/local/pixil/workstation.

8.  Run PIXIL PDA and Desktop:
	cd /usr/local/pixil
	./run_pda.sh
	./run_desktop.sh


Demonstrating Synchronization

Currently, sync is performed only for Address Book records, and
will only merge records that were created uniqely on either the
PDA or Desktop.  The sync is performed for demonstration using
TCP/IP localhost sockets.

To sync, start PIXIL PDA and Destkop, as described above.
Then start the PDA Sync application in the PIM group.
Select Address Book checkbox, and press synchronize.
The records should be copied across.  To view the records
on the desktop, shutdown the desktop application and restart.

--- NEW FILE: LICENSE.LGPL ---
		  GNU LIBRARY GENERAL PUBLIC LICENSE
			 Version 2, June 1991

	  Copyright (C) 1991 Free Software Foundation, Inc.
       59 Temple Place, Suite 330, Boston, MA  02111-1307  USA

     Everyone is permitted to copy and distribute verbatim copies
      of this license document, but changing it is not allowed.

    [This is the first released version of the library GPL.  It is
   numbered 2 because it goes with version 2 of the ordinary GPL.]

			       Preamble

  The licenses for most software are designed to take away your
freedom to share and change it.  By contrast, the GNU General Public
Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.

  This license, the Library General Public License, applies to some
specially designated Free Software Foundation software, and to any
other libraries whose authors decide to use it.  You can use it for
your libraries, too.

  When we speak of free software, we are referring to freedom, not
price.  Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.

  To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if
you distribute copies of the library, or if you modify it.

  For example, if you distribute copies of the library, whether gratis
or for a fee, you must give the recipients all the rights that we gave
you.  You must make sure that they, too, receive or can get the source
code.  If you link a program with the library, you must provide
complete object files to the recipients so that they can relink them
with the library, after making changes to the library and recompiling
it.  And you must show them these terms so they know their rights.

  Our method of protecting your rights has two steps: (1) copyright
the library, and (2) offer you this license which gives you legal
permission to copy, distribute and/or modify the library.

  Also, for each distributor's protection, we want to make certain
that everyone understands that there is no warranty for this free
library.  If the library is modified by someone else and passed on, we
want its recipients to know that what they have is not the original
version, so that any problems introduced by others will not reflect on
the original authors' reputations.

  Finally, any free program is threatened constantly by software
patents.  We wish to avoid the danger that companies distributing free
software will individually obtain patent licenses, thus in effect
transforming the program into proprietary software.  To prevent this,
we have made it clear that any patent must be licensed for everyone's
free use or not licensed at all.

  Most GNU software, including some libraries, is covered by the ordinary
GNU General Public License, which was designed for utility programs.  This
license, the GNU Library General Public License, applies to certain
designated libraries.  This license is quite different from the ordinary
one; be sure to read it in full, and don't assume that anything in it is
the same as in the ordinary license.

  The reason we have a separate public license for some libraries is that
they blur the distinction we usually make between modifying or adding to a
program and simply using it.  Linking a program with a library, without
changing the library, is in some sense simply using the library, and is
analogous to running a utility program or application program.  However, in
a textual and legal sense, the linked executable is a combined work, a
derivative of the original library, and the ordinary General Public License
treats it as such.

  Because of this blurred distinction, using the ordinary General
Public License for libraries did not effectively promote software
sharing, because most developers did not use the libraries.  We
concluded that weaker conditions might promote sharing better.

  However, unrestricted linking of non-free programs would deprive the
users of those programs of all benefit from the free status of the
libraries themselves.  This Library General Public License is intended to
permit developers of non-free programs to use free libraries, while
preserving your freedom as a user of such programs to change the free
libraries that are incorporated in them.  (We have not seen how to achieve
this as regards changes in header files, but we have achieved it as regards
changes in the actual functions of the Library.)  The hope is that this
will lead to faster development of free libraries.

  The precise terms and conditions for copying, distribution and
modification follow.  Pay close attention to the difference between a
"work based on the library" and a "work that uses the library".  The
former contains code derived from the library, while the latter only
works together with the library.

  Note that it is possible for a library to be covered by the ordinary
General Public License rather than by this special one.

		  GNU LIBRARY GENERAL PUBLIC LICENSE
   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

  0. This License Agreement applies to any software library which
contains a notice placed by the copyright holder or other authorized
party saying it may be distributed under the terms of this Library
General Public License (also called "this License").  Each licensee is
addressed as "you".

  A "library" means a collection of software functions and/or data
prepared so as to be conveniently linked with application programs
(which use some of those functions and data) to form executables.

  The "Library", below, refers to any such software library or work
which has been distributed under these terms.  A "work based on the
Library" means either the Library or any derivative work under
copyright law: that is to say, a work containing the Library or a
portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language.  (Hereinafter, translation is
included without limitation in the term "modification".)

  "Source code" for a work means the preferred form of the work for
making modifications to it.  For a library, complete source code means
all the source code for all modules it contains, plus any associated
interface definition files, plus the scripts used to control compilation
and installation of the library.

  Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope.  The act of
running a program using the Library is not restricted, and output from
such a program is covered only if its contents constitute a work based
on the Library (independent of the use of the Library in a tool for
writing it).  Whether that is true depends on what the Library does
and what the program that uses the Library does.

  1. You may copy and distribute verbatim copies of the Library's
complete source code as you receive it, in any medium, provided that
you conspicuously and appropriately publish on each copy an
appropriate copyright notice and disclaimer of warranty; keep intact
all the notices that refer to this License and to the absence of any
warranty; and distribute a copy of this License along with the
Library.

  You may charge a fee for the physical act of transferring a copy,
and you may at your option offer warranty protection in exchange for a
fee.

  2. You may modify your copy or copies of the Library or any portion
of it, thus forming a work based on the Library, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

    a) The modified work must itself be a software library.

    b) You must cause the files modified to carry prominent notices
    stating that you changed the files and the date of any change.

    c) You must cause the whole of the work to be licensed at no
    charge to all third parties under the terms of this License.

    d) If a facility in the modified Library refers to a function or a
    table of data to be supplied by an application program that uses
    the facility, other than as an argument passed when the facility
    is invoked, then you must make a good faith effort to ensure that,
    in the event an application does not supply such function or
    table, the facility still operates, and performs whatever part of
    its purpose remains meaningful.

    (For example, a function in a library to compute square roots has
    a purpose that is entirely well-defined independent of the
    application.  Therefore, Subsection 2d requires that any
    application-supplied function or table used by this function must
    be optional: if the application does not supply it, the square
    root function must still compute square roots.)

These requirements apply to the modified work as a whole.  If
identifiable sections of that work are not derived from the Library,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works.  But when you
distribute the same sections as part of a whole which is a work based
on the Library, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote
it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Library.

In addition, mere aggregation of another work not based on the Library
with the Library (or with a work based on the Library) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

  3. You may opt to apply the terms of the ordinary GNU General Public
License instead of this License to a given copy of the Library.  To do
this, you must alter all the notices that refer to this License, so
that they refer to the ordinary GNU General Public License, version 2,
instead of to this License.  (If a newer version than version 2 of the
ordinary GNU General Public License has appeared, then you can specify
that version instead if you wish.)  Do not make any other change in
these notices.

  Once this change is made in a given copy, it is irreversible for
that copy, so the ordinary GNU General Public License applies to all
subsequent copies and derivative works made from that copy.

  This option is useful when you wish to copy part of the code of
the Library into a program that is not a library.

  4. You may copy and distribute the Library (or a portion or
derivative of it, under Section 2) in object code or executable form
under the terms of Sections 1 and 2 above provided that you accompany
it with the complete corresponding machine-readable source code, which
must be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange.

  If distribution of object code is made by offering access to copy
from a designated place, then offering equivalent access to copy the
source code from the same place satisfies the requirement to
distribute the source code, even though third parties are not
compelled to copy the source along with the object code.

  5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library".  Such a
work, in isolation, is not a derivative work of the Library, and
therefore falls outside the scope of this License.

  However, linking a "work that uses the Library" with the Library
creates an executable that is a derivative of the Library (because it
contains portions of the Library), rather than a "work that uses the
library".  The executable is therefore covered by this License.
Section 6 states terms for distribution of such executables.

  When a "work that uses the Library" uses material from a header file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can be
linked without the Library, or if the work is itself a library.  The
threshold for this to be true is not precisely defined by law.

  If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the object
file is unrestricted, regardless of whether it is legally a derivative
work.  (Executables containing this object code plus portions of the
Library will still fall under Section 6.)

  Otherwise, if the work is a derivative of the Library, you may
distribute the object code for the work under the terms of Section 6.
Any executables containing that work also fall under Section 6,
whether or not they are linked directly with the Library itself.

  6. As an exception to the Sections above, you may also compile or
link a "work that uses the Library" with the Library to produce a
work containing portions of the Library, and distribute that work
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.

  You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered by
this License.  You must supply a copy of this License.  If the work
during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License.  Also, you must do one
of these things:

    a) Accompany the work with the complete corresponding
    machine-readable source code for the Library including whatever
    changes were used in the work (which must be distributed under
    Sections 1 and 2 above); and, if the work is an executable linked
    with the Library, with the complete machine-readable "work that
    uses the Library", as object code and/or source code, so that the
    user can modify the Library and then relink to produce a modified
    executable containing the modified Library.  (It is understood
    that the user who changes the contents of definitions files in the
    Library will not necessarily be able to recompile the application
    to use the modified definitions.)

    b) Accompany the work with a written offer, valid for at
    least three years, to give the same user the materials
    specified in Subsection 6a, above, for a charge no more
    than the cost of performing this distribution.

    c) If distribution of the work is made by offering access to copy
    from a designated place, offer equivalent access to copy the above
    specified materials from the same place.

    d) Verify that the user has already received a copy of these
    materials or that you have already sent this user a copy.

  For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it.  However, as a special exception,
the source code distributed need not include anything that is normally
distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on
which the executable runs, unless that component itself accompanies
the executable.

  It may happen that this requirement contradicts the license
restrictions of other proprietary libraries that do not normally
accompany the operating system.  Such a contradiction means you cannot
use both them and the Library together in an executable that you
distribute.

  7. You may place library facilities that are a work based on the
Library side-by-side in a single library together with other library
facilities not covered by this License, and distribute such a combined
library, provided that the separate distribution of the work based on
the Library and of the other library facilities is otherwise
permitted, and provided that you do these two things:

    a) Accompany the combined library with a copy of the same work
    based on the Library, uncombined with any other library
    facilities.  This must be distributed under the terms of the
    Sections above.

    b) Give prominent notice with the combined library of the fact
    that part of it is a work based on the Library, and explaining
    where to find the accompanying uncombined form of the same work.

  8. You may not copy, modify, sublicense, link with, or distribute
the Library except as expressly provided under this License.  Any
attempt otherwise to copy, modify, sublicense, link with, or
distribute the Library is void, and will automatically terminate your
rights under this License.  However, parties who have received copies,
or rights, from you under this License will not have their licenses
terminated so long as such parties remain in full compliance.

  9. You are not required to accept this License, since you have not
signed it.  However, nothing else grants you permission to modify or
distribute the Library or its derivative works.  These actions are
prohibited by law if you do not accept this License.  Therefore, by
modifying or distributing the Library (or any work based on the
Library), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Library or works based on it.

  10. Each time you redistribute the Library (or any work based on the
Library), the recipient automatically receives a license from the
original licensor to copy, distribute, link with or modify the Library
subject to these terms and conditions.  You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.

  11. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License.  If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Library at all.  For example, if a patent
license would not permit royalty-free redistribution of the Library by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Library.

If any portion of this section is held invalid or unenforceable under any
particular circumstance, the balance of the section is intended to apply,
and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices.  Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

  12. If the distribution and/or use of the Library is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Library under this License may add
an explicit geographical distribution limitation excluding those countries,
so that distribution is permitted only in or among countries not thus
excluded.  In such case, this License incorporates the limitation as if
written in the body of this License.

  13. The Free Software Foundation may publish revised and/or new
versions of the Library General Public License from time to time.
Such new versions will be similar in spirit to the present version,
but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number.  If the Library
specifies a version number of this License which applies to it and
"any later version", you have the option of following the terms and
conditions either of that version or of any later version published by
the Free Software Foundation.  If the Library does not specify a
license version number, you may choose any version ever published by
the Free Software Foundation.

  14. If you wish to incorporate parts of the Library into other free
programs whose distribution conditions are incompatible with these,
write to the author to ask for permission.  For software which is
copyrighted by the Free Software Foundation, write to the Free
Software Foundation; we sometimes make exceptions for this.  Our
decision will be guided by the two goals of preserving the free status
of all derivatives of our free software and of promoting the sharing
and reuse of software generally.

			    NO WARRANTY

  15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
LIBRARY IS WITH YOU.  SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

  16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.

		     END OF TERMS AND CONDITIONS

     Appendix: How to Apply These Terms to Your New Libraries

  If you develop a new library, and you want it to be of the greatest
possible use to the public, we recommend making it free software that
everyone can redistribute and change.  You can do so by permitting
redistribution under these terms (or, alternatively, under the terms of the
ordinary General Public License).

  To apply these terms, attach the following notices to the library.  It is
safest to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.

    <one line to give the library's name and a brief idea of what it does.>
    Copyright (C) <year>  <name of author>

    This library is free software; you can redistribute it and/or
    modify it under the terms of the GNU Library General Public
    License as published by the Free Software Foundation; either
    version 2 of the License, or (at your option) any later version.

    This library is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
    Library General Public License for more details.

    You should have received a copy of the GNU Library General Public
    License along with this library; if not, write to the Free
    Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.

Also add information on how to contact you by electronic and paper mail.

You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the library, if
necessary.  Here is a sample; alter the names:

  Yoyodyne, Inc., hereby disclaims all copyright interest in the
  library `Frob' (a library for tweaking knobs) written by James Random Hacker.

  <signature of Ty Coon>, 1 April 1990
  Ty Coon, President of Vice

That's all there is to it!

--- NEW FILE: ChangeLog ---
1.2.3 September 11, 2003 Greg Haerr <greg at censoft.com>
	* first public release of eval, commercial and GPL versions
	* tidy up "make clean" for cvs diff
1.2.3-rc1 September 10, 2003 Greg Haerr <greg at censoft.com>
	(Jason)
	* Added config.ARM for default ARM compilation
	* Changed config to build PixilDT for x86 desktop builds
	* Added README for ARM compilation (pixil/docs/README.ARM)
	* Updated many of the configuration files from Jordan's patch
	* added dvdview-1.1.0d(1.2.0pre), flash-0.4.10a, nxdoom-src packages
	* added 1.2.2-rc2 modifications to dvdview, flash, nxdoom (Greg)
	* added dvdview -U fullscreen option
	(Jordan)
	* Added packaging support for viewml, nxdoom, dvdview, and flash
	* Changed compilation order for the above projects
	* Cleaned up the Makefile for FLNX, fixed for cross-compilation
	* General ARM cross-compilation fixes
	* Updated header files to show licensing and URL information

1.2.2 May 30, 2003 Greg Haerr <greg at censoft.com> (pixil-1.2.2.tar.gz)
	* updated documentation, added license files
	* added USE_CACHE=1 for fast builds
	* built default config pixilDT uses external fltk-1.0.11
	* removed libwwwzip.a requirement (libwww 5.3.2 or 5.4.0)

1.2.2-rc2 May 14, 2003 jordanc <jordan at cosmicpenguin.net>
	* scripts/platforms/x86-demo/defaults.xml.in: Changed the nxdoom
		icon and fixed the sync so that only address is used
	* apps/nanox/Config.in: Added CONFIG_FLASH_RGB555
	* docs/README.sync: More SYNC documentation
	* Rules.make: Removed the native libraries during a clean
	* docs/config.pixil: Added config.pixil example
	* docs/README.x11: New readme information for X11 builds
	* scripts/platforms/x86-demo/Makefile: Fixed the install script so
		that a run_pda.sh file doesn't get created for X11 builds
	* libs/pim/nxmenuwindow.cxx: #ifdefed a section for X11 builds
	* libs/flnx/src/Fl_Slider.cxx: Fixed a slight slider drawing issue.
	* include/sync/coder.h: Status() conflicted with something under
		X11, so I removed it for X11 builds
	* docs/README.microwindows: More README changes for MW builds
	* docs/README: Small README changes
	* apps/viewml/src/Makefile: -D_NANOX should only be used when
		CONFIG_NANOX=y
	* apps/fltk/sysconfig/clock/nxsunclock.cxx: Removed useless
		nano-X.h
	* apps/fltk/netconfig/: dns_setup.cxx, ip_setup.cxx,
		net_config.cxx, ppp_modem.cxx: Removed unneeded n_x.h and nano-X.h
		from all files
	* apps/fltk/find/nxfindapp.cxx: #ifdefed a screentop action only
		allowable under Nano-X
	* apps/fltk/find/Makefile: Moved -lwm under ifdef CONFIG_NANOX
	* apps/fltk/Config.in: X11 build fix - MP3 player and Network
		config do not work under X11
	* docs/ChangeLog-1.2.2-rc1: Changelog for 1.2.2-rc1

1.2.2-rc1 May 13, 2003 jordanc <jordan at cosmicpenguin.net>
	* apps/fltk/sysconfig/backlite/backlite.cxx: Fixed Greg's backlight
		slider
	* Rules.make: Added a clean target for the par database stuff in
		the platforms dir
	* apps/nanox/misc/Makefile: added clean target to get rid of the
		evidence
	* libs/flnx/src/fl_font.cxx: Added the pda3x6.fnt
	* sys/syncagent/src/main.c: Handle IPC and network errors more
		gracefully
	* sys/pixilwm/screensaver.c: Add backlight changes regardless of PM
		status
	* sys/pixilwm/Makefile: Always build in -lpixil for the window
		manager
	* sys/par/lib/par_api.c: fixed par_getApplication to be less
		restrictive
	* scripts/platforms/x86-demo/run_pixil.sh.in: Added the MWFONTDIR
		flag
	* pixilDT/syncapp/Makefile: Changed the name of syncapp to
		dtsyncapp
	* pixilDT/src/Sync.cpp: Fixed the flags issue FIxed the extra field
		on the Address Book record removed bugs fixed the segfault issue
		removed debugging info
	* pixilDT/src/PixilDTApp.cpp: Fixed the CloseSync() so that it
		actually closes the sync app
	* pixilDT/src/NxDbRow.cpp: Removed debug noise and fixed the record
		flags
	* pixilDT/src/NxDbAccess.cpp: Removed some debug noise
	* pixilDT/src/Makefile: Removed the -efence library from the
		desktop
	* pixilDT/run_desktop.sh.in: Added the path for the dtsyncapp
	* libs/pixlib/Makefile: Tuxscreen now has its own set of functions
	* libs/pixlib/platform/tuxscreen/: backlight.c, calibrate.c,
		powermgmt.c, sound_dsp.c, sysinfo.c, tuxscreen.c: Added tuxscreen
		specific functions
	* libs/pim/nxapp.cxx: Several slight fixes regarding the sync
	* apps/fltk/sync/sync_ui.cxx: Removed the slider and fixed
		everything for a 1 button release
	* apps/games/minesweep/minesweep.c: Added <nxcolors.h>
	* scripts/platforms/x86-demo/Makefile: Fixed sample file copies
	* sys/par/tools/Makefile: Buildroot fixes
	* sys/par/lib/Makefile: Buildroot fixes
	* scripts/platforms/tuxscreen/nxstart.sh: Set the script to
		executable, and automatically kill the nano-X and clserver mods
		when the user Ctrl-Cs out of the pixilwm
	* scripts/platforms/: ipaq/Makefile, tuxscreen/Makefile,
		zaurus/Makefile: Slight changes for the ARM devices
	* libs/xml/Makefile: Build changes - much cleaner
	* scripts/platforms/x86-demo/defaults.xml.in: Added the syncagent
		capability

1.2.2-pre10 (c. May 10, 2003)
	* Added Zaurus support
	* Added Tuxscreen support
	* Continued sync support - two way sync enabled between DT and PDA
	* Made PM support optional
	* Added screensaver support to PixilWM
	* Added better power management suport to PixiWM
	* Added applet support to PixilWM
	* Fixed APM parsing in pixilb
	* Removed mandatory gettext support from PixilDT
	* Added checks for older compilers
	* Renamed several entries in the database
	* Added a sample DVD view mpeg
	* Added a real test MP3
	* Fixed drawing issues in sysconfig/power managment
	* Changed default target for .cc files
	* Fixed image support in NxBill
	* fixed nxTerm issues
	* Updated all platform scripts to use nxcal

1.2.2-pre9 (c. May 7, 2003)
        * Added Ipaq support
	* Added Ipaq power management support 
	* Added support for grabbing the SUSPEND key in the window manager
	* Added dvdview to the build
	* Added -L landscape support to dvdview
	* Added flash player
	* Various size optimizations
	* Added sync agent for PDA
	* added sync agent for Desktop - forked and piped to the desktop
	* added sync infrastructure to the Desktop (very alpha)
	
1.2.2-pre8 (c. April 4, 2003)

1.2.2-pre7 (c. March 21, 2003)
	* Fixed many bugs
	* Added sample data to most of the PIMs, the MP3 player and
	  the browser
	* Added Doom and the world clock
	* Added PixilDT to the master build and install
	* Changed the install scheme to be more orgainized for a demo
	
1.2.2-pre6
	* Fixed Truetype drawing issues, and rearranged some of the 
	* build options.
	* Added ViewML

1.2.2-pre5 (c. Mar 14, 2003)
	* Fixed PAR segfault when it tried to add new blocks
	* Fixed PAR error when no data was available (in nodes)
	* Fixed IPC loop on a SIGPIPE
	* Fixed font issues in nxmenubutton.c and other places
	* Fixed color and formatting in the sysconfig applets
	* Added individual config options for the sysconfig applets
	* Modified the default path to /usr/local/pixil
	
1.2.2-pre4
	* New build system (based on the kernel config)
	* Moved Pixil specific FLNX into the distro

1.2.2-pre3
	* Colosseum now removes the named socket when it exists
	* Sysconfig has been totally revamped to use a plugin
	  scheme.  
	* Other bug fixes and useless messages removed

1.2.2-pre2 February 21, 2003
	* added PixilDT to the tree (see pixilDT/ChangeLog for info)
	* Added color support to the Terminal Emulator
	* Updated the Nano-X games to better versions
	* More bug fixes
	* Cleaned up the code slightly

1.2.2-pre1 Feburary 18, 2003
	* Fixes to the build system
	* Added a default MP3 path to the MP3 player
	* Changed the look of the CPU load monitor
	* Removed debug messages throughout
	* Bug fixes to work in an RPM situation
        * Retag with the CCL/GPL 
	
1.2.1 "Phoenix" January 10, 2003
        * Initial build with the new build system
	* Features:
		Nano-X window manager
		Nano-X utilities: clock, load monitor, terminal, keyboard, 
		scribble
		Nano-X games:  minesweeper, snake, nxBill
		IPC server (Colosseum)
		application registry database (PAR)
		PIM Suites:  address, scheduler, todo, notepad, e-mail client
		Utilities:  calculator, system config, network config
		Multimedia:  MP3 player

1.2.0 October 31, 2002 Pixil v1.2 final (pixil-1.20.tar.gz)
1.1.0 ?
1.0.0 October 23, 2001 Pixil Operating Enironment first release (pixil_oe-1.0.tar.gz)

--- NEW FILE: README.ARM ---
PIXIL ARM Cross-Compilation Instructions
September 10, 2003

This README describes the procedure for compiling PIXIL for an ARM target 
platform on an x86 Linux host. To complete this procedure, you'll need to 
perform the following steps.

1. Download ARM Toolchain
----------------------------------

PIXIL is known to compile and work properly with the compiler supplied
with Century Software's PIXIL Developer's License (see
http://www.pixil.org/products.php for more information).

This compiler should work with any modern x86 Linux system. There are other 
compiler toolchains available, such as the ones distributed by the OpenZaurus 
project, http://www.openzaurus.org. Some have had success with these 
toolchains, but a good many people have not. If using one of these compilers, 
watch for segmentation faults during compilation, which is a sure sign that 
your toolchain has something incorrect about it. 


2. Install ARM Toolchain
----------------------------------

If you've downloaded the recommended toolchain included with the PIXIL
Developers License, all you need to do to install it is:

   a. As root, untar the gcc-arm-2.95.2.tar.gz file into the root of your 
filesystem. This will result in a new top-level directory called /skiff being 
created. It is important that the tar file is placed into the correct location, 
as the toolchain won't function with it in another place in the filesystem.

   b. For users wanting to use the compiler, add /skiff/local/bin to the 
user's path. This will allow the running of the compiler tools, arm-linux-*.


3. Unpack PIXIL Source
----------------------------------

Since you're reading this file, you've probably already done this step. If 
not, get the source from http://www.pixil.org and untar it into the directory 
of your choice.


4. Setup PIXIL Source for Cross-Compilation
----------------------------------

In the PIXIL top level directory, copy the file config.ARM to config 
(overwrite anything that you may be there.) This file is pre-configured to 
work with the cross-compiler that should be in your path.

After copying this file, edit it as you normally would, changing the 
INSTALL_PATH and other variables that are important to your particular 
environment. Please see the other PIXIL READMEs and documentation for more 
information on this topic.


5. Build the source
----------------------------------

Type make at the top level to build PIXIL. After the build complete, type 
"make install" to create a small ready-for-copying tree that is pre-configured 
for use on your ARM device. This is installed in the place that is specified 
in the top-level config using the INSTALL_PATH setting.


libwww Problems
----------------------------------

A common problem is the mishandling of libwww-config, a small utility script 
that is used to determine the proper location and configuration of libraries 
for the w3c-lib, used for viewml. When cross-compiling, you must make sure 
that you don't have another libwww-config program in your path that will cause 
an linking error when building ViewML. If ViewML fails to build, check this 
first. You can safely temporarily move the libwww-config program our of the 
way until your compilation is complete to remedy this situation.


--- NEW FILE: README.x11 ---
Using PIXIL with X11 (not Microwindows on X11)
May 29, 2003

The PIXIL Operating Environment and Applications were initially
designed to work within the Microwindows graphical windowing
environment, for an extremely small footprint.  The Microwindows
environment can be setup to run directly on framebuffer, or, for 
demonstration, on top of the X11 desktop environment, for people
without a working framebuffer system.  In addition, a subset
of PIXIL can be built that runs directly on X11, without using
Microwindows.

If you want to run the standard PIXIL build using Microwindows
running on top of X11 desktop for a full demonstration, see
README.microwindows.  This is the recommended method for 
running PIXIL with X11.

The PIXIL Operating Environment can be setup to run directly
on top of X11, without using Microwindows.  Currently, there is
no support for the PIXIL Screentop Window Manager, as well as
other applications dependent on the Nano-X API.  This support
is for portability of the PIM and other FLTK-based applications
to an X11-only operating environment.

To build PIXIL for X11 directly, edit the PIXIL configuration
file, config, and set

	CONFIG_NANOX=n
	CONFIG_X11=y

The PixilWM, Nano-X applications, and games will not be built, as they require
Microwindows to run.  The MP3 frontend is also constructed using some 
Microwindows components, so that will have to wait until somebody writes the
same components for X11.

Currently, some of the object files in libwm.so requires Microwindows, so
that library is *not* built under X11.  Because of this, the netconfig 
application is not built for X11.

So to recap, under X11 directly the following applications cannot be built:

* pixilwm
* nxterm
* nxloadmon
* world clock
* dvdview
* flash player
* Nano-X soft keyboard and scribble
* nxBill
* nxDoom
* Minesweeper
* Snake
* MP3 player
* Network Configurator

The ImLib image libraries are required for X11, since Microwindows
normally handles image decoding.

The Matchbox window manager is recommended for small X11-based
devices: http://handhelds.org/~mallum/matchbox/

--- NEW FILE: LICENSE ---
PIXIL v1.2.3 Operating Environment License Agreement
September 10, 2003

The files comprising the PIXIL Operating Environment fall under
three license categories, dependent upon the original origin of
the software component.  These three categories and license
documents are:

LICENSE.DUAL: Dual-licensed GPL and Century Commercial License (CCL).
LICENSE.GPL:  GPL only (GPL)
LICENSE.LGPL: LGPL only (LGPL)

See the above named files for descriptions of these licenses.

PIXIL is dual-licensed under the GPL license (see docs/LICENSE.GPL),
as well as Century Software's commercial CCL license (see docs/LICENSE.DUAL).
If your application is open source and fully GPL, then you are
able to use PIXIL under the GPL-only license.  Otherwise, a more commercial
oriented license is available from Century Software, Inc.
See http://www.pixil.org/license.html or
email cetsales at centurysoftware.com for more information.

The PIXIL open source site is http://www.pixil.org
The Century Software embedded site is http://embedded.censoft.com

Following is a breakdown of the components used in PIXIL and their
individual licensing.  All code originally written by Century Software,
Inc., is licensed under the dual-licensed GPL/CCL arrangement.

Component			License			Version
apps/fltk/address		DUAL GPL/CCL
apps/fltk/alarm			DUAL GPL/CCL
apps/fltk/calc			GPL
apps/fltk/find			DUAL GPL/CCL
apps/fltk/mail			DUAL GPL/CCL 
apps/fltk/mp3/frontend		DUAL GPL/CCL 
apps/fltk/mp3/mpegplay		LGPL
apps/fltk/netconfig		DUAL GPL/CCL
apps/fltk/notepad		DUAL GPL/CCL
apps/fltk/schedule		DUAL GPL/CCL
apps/fltk/sync			DUAL GPL/CCL
apps/fltk/sysconfig		DUAL GPL/CCL
apps/fltk/todo			DUAL GPL/CCL
apps/games/minesweep		DUAL GPL/CCL
apps/games/nxbill		GPL
apps/games/snake		DUAL GPL/CCL
apps/nanox/keyboard		DUAL GPL/CCL
apps/nanox/scribble		GPL
apps/nanox/wclock		DUAL GPL/CCL
apps/nanox/misc/nxclock		DUAL GPL/CCL
apps/nanox/misc/nxloadmon	DUAL GPL/CCL
apps/nanox/misc/nxterm		DUAL GPL/CCL
packages/dvdview		GPL			1.1.0e
packages/flash			GPL			0.4.10b
packages/nxdoom			DOOMLIC.TXT		1.0.0a
packages/viewml			GPL			0.23
libs/flek			LGPL			0.3
libs/flnx			LGPL			0.18
libs/pim			DUAL GPL/CCL
libs/pixlib			DUAL GPL/CCL
libs/sync			DUAL GPL/CCL
libs/wm				DUAL GPL/CCL
libs/xml			DUAL GPL/CCL
pixilDT				DUAL GPL/CCL
sys/ipc				DUAL GPL/CCL
sys/par				DUAL GPL/CCL
sys/pixilwm			DUAL GPL/CCL

Other libraries
microwindows			DUAL MPL/GPL		0.90
w3c-libwww			W3C			5.2.8+
fltk				LGPL			1.0.11

--- NEW FILE: AUTHORS ---
PIXIL Operating Environment and Applications Suite Authors

Unless otherwise noted in the code, the PIXIL code was developed 
entirely in-house at Century Software starting in 2000 by the PIXIL
development team: 

Programmers:
Greg Haerr
Dave Burkheart
Jordan Crouse
Truman Lackey
Jason Kingan
Shaun Kruger
Jeff Mollmer
Dave Tubbs
Jeff Webb

Artwork:  
Mike Davies

Documentation:  
Terry Jeffries

Project Management:
Roberto Elorega


--- NEW FILE: README.microwindows ---
Using PIXIL with Microwindows
May 29, 2003

The PIXIL Operating Environment and Applications were initially
designed to work within the Microwindows graphical windowing
environment, for an extremely small footprint.  The Microwindows
environment can be setup to run directly on framebuffer, or, for 
demonstration, on top of the X11 desktop environment, for people
without a working framebuffer system.

When PIXIL is configured to run using Microwindows, the determination
of whether to run on framebuffer or X11 is controlled solely through
the Microwindows configuration file, microwin/src/config.

The PIXIL Operating Environment can be setup to run directly
on top of X11, without using Microwindows.  Currently, there is
no support for the PIXIL Screentop Window Manager, as well as
other applications dependent on the Nano-X API.  For more
information, see README.X11.


To run PIXIL under the Microwindows graphical environment, 
you will need to download and build the Nano-X server.  PIXIL
requires Microwindows version 0.90 or later, available from
http://www.microwindows.org (microwindows-src-0.90.tar.gz)

To build Microwindows, do the following:
 
1.  Extract Microwindows into a directory:
	tar zxvf microwindows-src-0.90.tar.gz

2.  Change to the Microwindows source directory:
	cd microwindows-0.90/src

3.  Select your desired configuration:
	There are some premade configuration files located
	in the Configs directory.  Choose one that you want
	and copy it to 'config'. Following are some
	useful configurations:

	Configs/config.pixil	Required PIXIL options for framebuffer operation
	Configs/config.x11	Microwindows on X11 desktop demonstration
	Configs/config.ipaq	Microwindows on iPAQ

	Make sure that you HAVE_FNT_SUPPORT=Y set,
	as the Scheduler PIM application uses loadable fonts.
	Additional image decoders (from the minimal requirements in
	config.pixil) can be selected for the ViewML browser, if desired.

4.  Build Microwindows:
	Type "make".  The Nano-X server will reside in the
	microwindows-0.90/src/bin directory, the libraries in
	microwindows-0.90/src/lib, and the headers in 
	microwindows-0.90/src/include.  These will be automatically
	used when pointed to by the PIXIL configuration file (see below).

5.  Edit the PIXIL config file (config):
	cd <pixil source dir>

	A. Set MW_PREFIX to the Microwindows src directory:
		MW_PREFIX="/usr2/microwindows-0.90/src"
	Edit the config file and change the location of the Microwindows
	prefix MW_PREFIX (in Build Options) to point at your new distro.  Make
	sure you specify the /src directory at the end of the path, e.g.
	if Microwindows was extracted into /usr2/microwindows-0.90, then
	MW_PREFIX="/usr2/microwindows-0.90/src".

	B. Set CONFIG_NANOX=y
	This specifies Microwindows to be used as the graphical windowing
	system.

	C. To build the PIXIL Desktop (the workstation component of
	the PDA PIM suite), set CONFIG_PIXILDT=y.  Note that currently,
	this requires an external FLTK library which runs directly on
	top of X11.  Thus Microwindows must be built using config.x11
	if it is desired to run both the PDA and Desktop simultaneously
	for demonsration of syncing, etc.  See README.pixilDT for
	more information.

	D. Select the installation directory (default /usr/local/pixil):
		INSTALL_PREFIX="/usr/local/pixil"

6.  Make PIXIL:
	Type "make".

	If the make fails, it's likely due to insidious GCC compiler
	version incompatibilities.  For instance, currently
	the MPEG viewer (CONFIG_DVDVIEW) won't compile using
	"gcc 2.96 Red Hat 7.0", although it will using
	"gcc 2.96 Red Hat 7.3 (2.96-113)".  In this case, set CONFIG_DVDVIEW=n
	and remake. Note that CONFIG_PIXILDT requires GCC 2.96 or
	greater (see README.pixilDT).

7.  Install PIXIL:
	Type "make install".

	Currently, PIXIL must be installed in order to automatically
	put together the directory structure normally compiled for.
	This process will move the PIXIL binaries (not Microwindows)
	into the install directory (normally /usr/local/pixil).

8.  Run PIXIL:
	cd /usr/local/pixil
	./run_pda.sh

9.  Have fun!

--- NEW FILE: BUGS ---
make menuconfig build fails on 2.91.66 RH 6.2 system
some startup issues when Colosseum isn't around (what?)
we have some ugly default colors when PAR isn't enabled.  
remove template code to allow pixilDT build with 2.91.66?

X11-only
No resize_notify event for FLTK.  We need to make a patch.
A few minor drawing issues

--- NEW FILE: ChangeLog.historical ---
2002-10-30 08:15  jordanc

	* colosseum/: client/client.c, include/colosseum.h: Reverted some
	bugs

2002-07-25 14:53  jordanc

	* colosseum/: client/client.c, include/colosseum.h,
	server/message.c, server/network.c: Changes to the internal
	messaging system and the ClGetMessage() stucture :w

2002-06-17 14:00  jordanc

	* colosseum/: Makefile.in, client/client.c, include/colosseum.h,
	server/message.c, server/network.c: Added support for returning
	error when a message destination no longer exists

2002-04-30 10:56  jordanc

[...12793 lines suppressed...]
	packages/install.html, packages/dunix/fltk.key,
	packages/dunix/fltk.mi, packages/dunix/makedist.sh,
	packages/hpux/fltk.info, packages/hpux/makedist.sh,
	packages/irix/fltk.list, packages/irix/fltk.spec,
	packages/irix/fltk5x.list, packages/irix/makedist.sh,
	packages/linux/fltk.spec, packages/linux/makedist.sh,
	packages/solaris-intel/fltk.pkginfo,
	packages/solaris-intel/fltk.prototype,
	packages/solaris-intel/makedist.sh,
	packages/solaris-sparc/fltk.pkginfo,
	packages/solaris-sparc/fltk.prototype,
	packages/solaris-sparc/makedist.sh, visualc/ask.dsp,
	visualc/buttons.dsp, visualc/checkers.dsp, visualc/clock.dsp,
	visualc/cursor.dsp, visualc/demo.dsp, visualc/doublebuffer.dsp,
	visualc/editor.dsp, visualc/fltk.dsw, visualc/fractals.dsp,
	visualc/gl_overlay.dsp, visualc/iconize.dsp, visualc/inactive.dsp,
	visualc/mandelbrot.dsp, visualc/menubar.dsp, visualc/overlay.dsp,
	visualc/pack.dsp, visualc/shiny.dsp, visualc/symbols.dsp,
	visualc/valuators.dsp: [no log message]


--- NEW FILE: LICENSE.GPL ---
		    GNU GENERAL PUBLIC LICENSE
		       Version 2, June 1991

 Copyright (C) 1989, 1991 Free Software Foundation, Inc.
                          59 Temple Place - Suite 330, Boston, MA 02111 USA
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.

			    Preamble

  The licenses for most software are designed to take away your
freedom to share and change it.  By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users.  This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it.  (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.)  You can apply it to
your programs, too.

  When we speak of free software, we are referring to freedom, not
price.  Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.

  To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.

  For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have.  You must make sure that they, too, receive or can get the
source code.  And you must show them these terms so they know their
rights.

  We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.

  Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software.  If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.

  Finally, any free program is threatened constantly by software
patents.  We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary.  To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.

  The precise terms and conditions for copying, distribution and
modification follow.

		    GNU GENERAL PUBLIC LICENSE
   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

  0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License.  The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language.  (Hereinafter, translation is included without limitation in
the term "modification".)  Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope.  The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.

  1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.

You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.

  2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

    a) You must cause the modified files to carry prominent notices
    stating that you changed the files and the date of any change.

    b) You must cause any work that you distribute or publish, that in
    whole or in part contains or is derived from the Program or any
    part thereof, to be licensed as a whole at no charge to all third
    parties under the terms of this License.

    c) If the modified program normally reads commands interactively
    when run, you must cause it, when started running for such
    interactive use in the most ordinary way, to print or display an
    announcement including an appropriate copyright notice and a
    notice that there is no warranty (or else, saying that you provide
    a warranty) and that users may redistribute the program under
    these conditions, and telling the user how to view a copy of this
    License.  (Exception: if the Program itself is interactive but
    does not normally print such an announcement, your work based on
    the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole.  If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works.  But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.

In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

  3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:

    a) Accompany it with the complete corresponding machine-readable
    source code, which must be distributed under the terms of Sections
    1 and 2 above on a medium customarily used for software interchange; or,

    b) Accompany it with a written offer, valid for at least three
    years, to give any third party, for a charge no more than your
    cost of physically performing source distribution, a complete
    machine-readable copy of the corresponding source code, to be
    distributed under the terms of Sections 1 and 2 above on a medium
    customarily used for software interchange; or,

    c) Accompany it with the information you received as to the offer
    to distribute corresponding source code.  (This alternative is
    allowed only for noncommercial distribution and only if you
    received the program in object code or executable form with such
    an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for
making modifications to it.  For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable.  However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.

If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.

  4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License.  Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.

  5. You are not required to accept this License, since you have not
signed it.  However, nothing else grants you permission to modify or
distribute the Program or its derivative works.  These actions are
prohibited by law if you do not accept this License.  Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.

  6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions.  You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.

  7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License.  If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all.  For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices.  Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

  8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded.  In such case, this License incorporates
the limitation as if written in the body of this License.

  9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time.  Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.

Each version is given a distinguishing version number.  If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation.  If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.

  10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission.  For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this.  Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.

			    NO WARRANTY

  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.

  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

		     END OF TERMS AND CONDITIONS

	Appendix: How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

  To do so, attach the following notices to the program.  It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

    <one line to give the program's name and a brief idea of what it does.>
    Copyright (C) 19yy  <name of author>

    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation; either version 2 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License
    along with this program; if not, write to the Free Software
    Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111 USA

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:

    Gnomovision version 69, Copyright (C) 19yy name of author
    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
    This is free software, and you are welcome to redistribute it
    under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License.  Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary.  Here is a sample; alter the names:

  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
  `Gnomovision' (which makes passes at compilers) written by James Hacker.

  <signature of Ty Coon>, 1 April 1989
  Ty Coon, President of Vice

This General Public License does not permit incorporating your program into
proprietary programs.  If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library.  If this is what you want to do, use the GNU Library General
Public License instead of this License.

--- NEW FILE: README.packages ---
PIXIL Packages Documentation
----------------------------

This file describes the methods used to add a new package to the
pixil/packages subsystem and  add it to the menu configuration system.

There are three main steps to adding a package to PIXIL: 

1. Create a new pixil/pakages/<package>  directory that contains an unpacked
   copy of your source.

2. Create Config.in and Makefiles for your new package in the
   pixil/packages/<package> directory.

3. Add your new config entries into the menu configuration system and to the
   default config files.

For the purpose of these instructions, we'll be working with the fictional
package "Snoop", a network sniffer.


Create a New Package Directory
-------------------------------

Under the pixil/packages directory, create a new subdirectory using the name
of your package. For instance, snoop. Within this directory, untar your
package sources, so that another directory is created underneath. When
completed, it should look something like this:

pixil/packages/snoop/snoop-1.0.4

The reason for the extra directory (instead of say, putting everything in
pixil/packages/snoop-1.0.4) is to allow for the creation of the
PIXIL-compatible Makefiles and Config.in for the menu configuration
system.

Creating Config.in and Your New Makefile
-----------------------------------------

  A. Config.in

The Config.in file contains information about your project that is used for the
menu configuration system of PIXIL. This includes such things as
an English description of the package, whether it is turned on by default, etc.

For Snoop, we'll keep it simple by creating Config.in in the
pixil/packages/snoop directory, and placing the following contents in it:

config CONFIG_SNOOP
        bool "Snoop the Network Sniffer (Shhhh!)"
        default n

Note the name of the config entry. This name must be chosen when adding the
packages. This is the same name that ends up the config files looking like
one of the following:

CONFIG_SNOOP=y

or

# CONFIG_SNOOP is not set

The text description is self-explanatory, and the default is either y or n
depending on whethere or not your package should be turned on by default or
not.

There are a multitude of other options for the Config.in entries that this 
document can't hope to cover. For some real-life examples, see the Config.in
files in the pixil/packages/viewml and pixil/packages/flash for additional
options such as package dependencies and optional settings.

When your Config.in is complete, you need to add an entry in the Config.in
located in pixil/packages. You can place your entry in any of the menus
present in the PIXIL system. By default, pixil/packages/Config.in contains
entries for Applications and Games (as you'll see when you edit the files.)
For other categories, look at the other Config.in files, particularly in the 
pixil/apps subdirectory. 

For Snoop, we'll add a like like the following under "Nano-X Applications":

source packages/snoop/Config.in

And finally, in the pixil/packages/pkg.conf file, we add a line like the
following:

CONFIG_SNOOP snoop

Where CONFIG_SNOOP is the previously chosen configuration option ( in
pixil/packages/snoop/Config.in) and snoop is the subdirectory containing
your package.

  B. Makefile

We need to add a new PIXIL-compatible makefile as the interface between your
new package (which probably does things differently) and the PIXIL build
system.

This new Makefile should have three main targets: all, clean, and install.

The all target should configure (if needed) your package, and then proceed
to perform all build steps. This of course, will call your existing 
package configuration and use your existing Makefiles.

The clean target should actually perform what is normally called a distclean.
That is, it should remove and configurations, auto-generated makefiles,
etc., as well as binary targets, libraries and object files. A good guideline
for this is that after a clean, a configuration step should be performed again
during the next make all.

The install target should take any binaries present and install them into the
appropriate locations, along with any support files. Keep in mind that this
will typically happen multiple times, so support for overwriting files 
should be included. 

The bestway to get started is to copy an existing Makefile and modify it
for your package. The Makefile located in pixil/packages/nxdoom is a good
place to start, as it contains very basic targets, as well as the most 
important make variables.

The following lists some of the more common make variables and their meaning:

TARGET_CROSS		If you're building a using a cross-compiler, this
			will be set to something like "arm-linux-". This
			is commonly used to set the toolchain variables
			(CC, CXX, etc.) that are passed to configuration 
			scripts and whatnot.

INSTALL_DIR		This is the location of the installation directory.
			This is what was set in the config file as
			INSTALL_PREFIX

SYS			The target system prefix. For ARM, this will be 
			arm-linux, for x86, something like i386-linux or
			i686-linux. Useful for passing as the --host 
			parameter to standard configure scripts.

BUILD_SYS		The system on which you are building. For x86 systems,
			this will be something like i386-linux or i686-linux.
			Useful for passing as the --build parameter to
			standard configure scripts.

Menu Configuration and Default Config Files
--------------------------------------------

At this point, running make menuconfig at the top level of pixil will display
the standard menus for configuration, and under the packages subtree will
be your new entry, in the menu name that you specified. In addition, it should
be selected if you set your default to "y" in your Config.in, or off otherwise.

Writing your config file upon exit from make menuconfig will cause your new entry
to be written to the config file.

The last step is to add an appropriate entry to the default configuration files
located in pixil/scripts/sysdep. The files are called 
defconfig* and are pretty self-explanatory. They are the same format as the top
level config files and can be hand-edited. Just add your CONFIG_SNOOP=y to
the same place as it was put in your top level config file.

--- NEW FILE: README.platform ---
This README details the status of PIXIL on the various platforms.

---------------------------------------------
PLATFORM:  Compaq Ipaq 3x00
STATUS:  Running

BUGS:
APM returns the wrong values for the battery life
The battery widget freaks out the server
Network setup is broken
Backlight is always at 100% brightness

TODO:

---------------------------------------------
PLATFORM:  Sharp Zaurus SL5500
STATUS:  Running

BUGS:
APM returns the wrong values for the battery life
The battery widget freaks out the server
Network setup is broken
Some of the keyboard isn't mapped yet

TODO:
Backlight control not ready yet
No way to suspend the device
Power management timer fires during use
Timezones not set up correctly

---------------------------------------------
PLATFORM:  Tuxscreen
STATUS:  Running

BUGS:

TODO:
ViewML isn't installed (may not fit)
World Clock isn't installed (may not fit)

--- NEW FILE: TODO ---
ccache fixes for g++ compiles
configure changes for dvdview for X11
make global find work
replace original copyright headers in calc, scribble, mail?
check pixil-1.20/microwindows diffs for nanowm fixes to flnx
replace database with SQL version

add tcp/ip connect facility for sync

--- NEW FILE: LICENSE.DUAL ---
/*                                                                       
 * Copyright (c) 2003 Century Software, Inc.   All Rights Reserved.     
 *                                                                       
 * This file is part of the PIXIL Operating Environment                 
 *                                                                       
 * The use, copying and distribution of this file is governed by one    
 * of two licenses, the PIXIL Commercial License, or the GNU General    
 * Public License, version 2.                                           
 *                                                                       
 * Licensees holding a valid PIXIL Commercial License may use this file 
 * in accordance with the PIXIL Commercial License Agreement provided   
 * with the Software. Others are governed under the terms of the GNU   
 * General Public License version 2.                                    
 *                                                                       
 * This file may be distributed and/or modified under the terms of the  
 * GNU General Public License version 2 as published by the Free        
 * Software Foundation and appearing in the file LICENSE.GPL included   
 * in the packaging of this file.                                      
 *                                                                       
 * This file is provided AS IS with NO WARRANTY OF ANY KIND, INCLUDING  
 * THE WARRANTY OF DESIGN, MERCHANTABILITY AND FITNESS FOR A            
 * PARTICULAR PURPOSE.                                                  
 *                                                                       
 * RESTRICTED RIGHTS LEGEND                                             
 *                                                                     
 * Use, duplication, or disclosure by the government is subject to      
 * restriction as set forth in paragraph (b)(3)(b) of the Rights in     
 * Technical Data and Computer Software clause in DAR 7-104.9(a).       
 *                                                                      
 * See http://www.pixil.org/gpl/ for GPL licensing       
 * information.                                                         
 *                                                                      
 * See http://www.pixil.org/license.html or              
 * email cetsales at centurysoftware.com for information about the PIXIL   
 * Commercial License Agreement, or if any conditions of this licensing 
 * are not clear to you.                                                
 */




More information about the dslinux-commit mailing list