gnustep/libs-gui
0
0
Fork 0
mirror of https://github.com/gnustep/libs-gui.git synced 2025-04-22 18:11:06 +00:00
Code Issues Projects Releases Packages Wiki Activity

Update

Browse source 
git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/libs/gui/trunk@9215 72102866-910b-0410-8b05-ffd578937521
This commit is contained in:
Adam Fedor 2001-02-23 04:13:00 +00:00
parent 9f69e63cb3
commit 94fe65783b
9 changed files with 136 additions and 410 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

42
ANNOUNCE
View file

@ -1,7 +1,7 @@
ANNOUNCE
********
This is version 0.6.6 of the GNUstep GUI library (`gnustep-gui').
This is version 0.6.7 of the GNUstep GUI library (`gnustep-gui').
What is the GNUstep GUI Library?
================================
@ -31,44 +31,34 @@ component like the GNUstep X/DPS GUI Backend.
What's new in this release?
===========================
The currently released version of the library is `0.6.6'.
The currently released version of the library is `0.6.7'.
Noteworthy changes in version `0.6.6'
Noteworthy changes in version `0.6.7'
=====================================
* Window hints for motif and generic window managers.
* App Icons can support documents dropped using DnD.
* Major improvements to the text handling classes (NSText,
NSTextView, etc)
* Added color conversions, working color picker and panel.
* Pasting of fonts and rulers.
* Almost complete rewrite of NSBezierPath
* Much better RTF handling
* Loads of improvements to Text classes.
* DnD for NSColorWell
* NSImage, NSButton, NSCell, etc, implemented many missing methods.
* Much improved NSSplitView
* ...and even more changes to the Text classes.
* New classes - NSColorPanel, NSTableView
* Starting implementation of printing.
* NSScreen rewritten with full support for all methods and functions.
* Scrollview fixes.
* Can use image reading routines from WindowMaker if available to
read a variety of image formats besides TIFF.
* Implemented deferred windows.
* Many fixes to get the AppKit to work better with WindowMaker.
* NSTableView implemented.
* Much better gmodel support (particularly with nibs translated from
NeXT or OPENSTEP 4.2).
* Implemented object value and formatter support in NSCell
* Muh improved font classes and font support.
In addition both the xgps and xdps backends have seen some large
efficiency improvements. Much better font support. The xdps backend
itself has seen speed improvements by at least a factor of 4. Note
however, that the xdps backend is still considered experimental and you
may have to deal with many problems in order to get it working. We
recommend sticking with the xgps backend (the default) for now.
* Support middle mouse button.
How can I get support for this software?
========================================
@ -82,7 +72,7 @@ the GNUstep Web Pages for more information regarding GNUstep resources
Where can you get it? How can you compile it?
==============================================
The gstep-gui-0.6.6.tar.gz distribution file has been placed on
The gstep-gui-0.6.7.tar.gz distribution file has been placed on
`ftp.gnustep.org' in `pub/gnustep/core'.
The program requires gcc 2.8.0 or higher.

45
BUGS
View file

@ -4,42 +4,10 @@ TODO
Bugs in the GUI library
=======================
Windows
-------
* Getting and releasing keyboard focus is still buggy. This is mostly
annoying for users trying to type in a GNUstep or non-GNUstep
window.
Texts
-----
* There have been a lot of improvements in the NSText code, but is
particularly complex. It is somewhat usable though. We hope to
keep improving it.
Matrices
--------
* Encoding/Decoding of matrices is unimplemented. There are some
minor known bugs with handling of mouse down in matrices.
Cells
-----
* Since NSText does only left alignment, when you select or edit text
in a cell it becomes automatically left aligned regardless of the
original alignment.
* Multi line texts are unsupported; isScrollable, wordWraps etc do
nothing. This restriction will hopefully be removed in next
releases.
Images anf Graphics
-------------------
* There are problems with alpha composing. To avoid these problems,
you may set manually the background color of your image when
displaying it.
@ -48,15 +16,6 @@ Images anf Graphics
limited degree.
Alert, Info Panels
------------------
* Multi line messages are generally unsupported due to the similar
restriction in the cells code.
Unimplemented Classes
---------------------
The following classes are currently unimplemented or unfinished to
such a degree to be unusable.
@ -64,13 +23,9 @@ such a degree to be unusable.
* NSHelpPanel
* NSLayoutManager
* NSPageLayout
* NSPrintPanel
* NSSecureTextField
* NSSpellChecker

6
ChangeLog
View file

@ -1,3 +1,9 @@
2001-02-22 Adam Fedor <fedor@gnu.org>
* Documentation/news.texi: Update
* Documentation/install.texi: Likewise.
* INSTALL, NEWS, etc, regenerate.
Wed Feb 21 11:30:48 2001 Nicola Pero <nicola@brainstorm.co.uk>
* Headers/gnustep/gui/AppKit.h: Commented out extra token after

193
Documentation/install.texi
View file

@ -1,169 +1,50 @@
@c -*- texinfo -*-
@chapter Installation
@ifset TEXT-ONLY
@node Top, Introduction, (dir), (dir)
@include version.texi
@end ifset
This file documents the installation of the GNUstep GUI
Library, @samp{gnustep-gui}. Copyright (C) 1996 Free Software
Foundation, Inc. You may copy, distribute, and modify it freely as long
as you preserve this copyright notice and permission notice.
@menu
* Introduction::
* Configuration::
* Compilation::
* Installing::
@end menu
This is version @value{GNUSTEP-GUI-VERSION} of the GNUstep GUI library.
@section Installing @samp{gnustep-gui}
@node Introduction, Configuration, Top, Top
@section Introduction
Here is a quick-and-dirty example of installation commands:
This file documents the installation of the GNUstep GUI Library,
@samp{gnustep-gui}. If you are installing this package as part of the
GNUstep core package, read the file GNUstep-HOWTO for more complete
instructions on how to install the entire GNUstep package (including
this library). GNUstep-HOWTO is located at @url{www.gnustep.org}
@node Configuration, Compilation, Introduction, Top
@section Configuration
Configuration is performed by running the @file{configure} program at a
shell prompt. You may want to use some of the optional arguments to the
@file{configure} program. Type @code{configure --help} for a list. GNUstep
specific options are at the end of this list (if any).
@node Compilation, Installing, Configuration, Top
@section Compilation
To compile this library, type make. After this is complete, type make
install (make sure you are the root user). Some additional options you
can use with make are @samp{debug=yes} to make a debugging version of
the library and @samp{shared=no} to make a static version of the
library. See the gstep-make package for more information on these options.
@node Installing, , Compilation, Top
@section Installing
To install, type
@example
./configure --prefix=/usr/GNUstep
make
make install
@end example
Here are more detailed instructions. Also read the @file{GNUstep-HOWTO}
for instructions on how to install the entire GNUstep system.
@enumerate
@item
Install @samp{gcc}. The library requires gcc version
@value{GNUSTEP-GUI-GCC} or later.
@item
Install the @samp{gnustep-base} library.
@item
Install the @samp{TIFF} library. This library requires the header files
in the TIFF library to compile; the TIFF library is used for the NSImage
and associated classes for reading, writing, and manipulating tiff files.
@item
Configure the package for your system. In the directory that this
file is in, type @file{./configure}. If you're using @file{csh} on an old
version of System V, you might need to type @samp{sh configure} instead
to prevent @samp{csh} from trying to execute @file{configure} itself.
The @file{configure} shell script attempts to guess correct values for
various system-dependent variables used during compilation, and
creates the Makefile(s) (one in each subdirectory of the source
directory). In some packages it creates a C header file
containing system-dependent definitions. It also creates a file
@file{config.status} that you can run in the future to recreate the
current configuration.
Running @file{configure} takes less than a minute or two. While it is
running, it prints some messages that tell what it is doing. If
you don't want to see the messages, run @file{configure} with its
standard output redirected to @file{/dev/null}; for example:
@smallexample
./configure >/dev/null
@end smallexample
To compile the package in a different directory from the one
containing the source code, you must use a version of make that
supports the VPATH variable, such as GNU make. @samp{cd} to the
directory where you want the object files and executables to go and
run @file{configure}. @file{configure} automatically checks for the
source code in the directory that @file{configure} is in and in
@file{..}. If for some reason @file{configure} is not in the source
code directory that you are configuring, then it will report that it
can't find the source code. In that case, run @file{configure} with
the option @samp{--srcdir=DIR}, where DIR is the directory that
contains the source code.
By default, @samp{make install} will install the package's files in
/usr/local/bin, /usr/local/lib, /usr/local/man, etc. You can specify
an installation prefix other than /usr/local by giving
@file{configure} the option @samp{--prefix=PATH}. Alternately, you
can do so by giving a value for the @samp{prefix} variable when you
run @samp{make}, e.g.,
@smallexample
make prefix=/usr/gnu
@end smallexample
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If
you give @file{configure} the option @samp{--exec_prefix=PATH} or set
the @samp{make} variable @samp{exec_prefix} to PATH, the package will
use PATH as the prefix for installing programs and libraries. Data
files and documentation will still use the regular prefix. Normally,
all files are installed using the regular prefix.
You can tell @file{configure} to figure out the configuration for your
system, and record it in @file{config.status}, without actually
configuring the package (creating Makefile(s) and perhaps a
configuration header file). To do this, give @file{configure} the
@samp{--no-create} option. Later, you can run @file{./config.status}
to actually configure the package. This option is useful mainly in
@file{Makefile} rules for updating @file{config.status} and
@file{Makefile}. You can also give @file{config.status} the
@samp{--recheck} option, which makes it re-run @file{configure} with
the same arguments you used before. This is useful if you change
@file{configure}.
@file{configure} ignores any other arguments that you give it.
If your system requires unusual options for compilation or linking
that @file{configure} doesn't know about, you can give
@file{configure} initial values for some variables by setting them in
the environment. In Bourne-compatible shells, you can do that on the
command line like this:
@smallexample
CC='gcc -traditional' DEFS=-D_POSIX_SOURCE ./configure
@end smallexample
The @samp{make} variables that you might want to override with
environment variables when running @file{configure} are:
(For these variables, any value given in the environment overrides
the value that `configure' would choose:)
@table @samp
@item CC
C compiler program. Default is @samp{cc}, or @samp{gcc} if @samp{gcc} is in
your PATH.
@item INSTALL
Program to use to install files. Default is @samp{install} if you
have it, @samp{install.sh} otherwise.
@end table
(For these variables, any value given in the environment is added
to the value that @file{configure} chooses:)
@table @samp
@item DEFS
Configuration options, in the form @samp{-Dfoo -Dbar ...}
@item LIBS
Libraries to link with, in the form @samp{-lfoo -lbar ...}
@end table
If you need to do unusual things to compile the package, we
encourage you to figure out how @file{configure.in} could check whether to
do them, and mail diffs or instructions to the address given in
the @file{README} so we can include them in the next release.
@item
Type @samp{make} to compile the package. If you want, you can override
the @samp{make} variables @samp{CFLAGS} and @samp{LDFLAGS} like this:
@smallexample
make CFLAGS=-O2 LDFLAGS=-s
@end smallexample
@item
Type @samp{make install} to install the library, data files, header
files, and documentation.
@item
You can remove the program binaries and object files from the
source directory by typing @samp{make clean}. To also remove the
Makefile(s), and @file{config.status} (all the files that @file{configure}
created), type @samp{make distclean}.
The file @file{configure.in} is used as a template to create
@file{configure} by a program called @file{autoconf}. You will only
need it if you want to regenerate @file{configure} using a newer
version of @file{autoconf}.
@end enumerate
@bye

25
Documentation/news.texi
View file

@ -9,6 +9,27 @@
The currently released version of the library is @samp{@value{GNUSTEP-GUI-VERSION}}.
@section Noteworthy changes in version @samp{0.6.7}
@itemize @bullet
@item App Icons can support documents dropped using DnD.
@item Added color conversions, working color picker and panel.
@item Almost complete rewrite of NSBezierPath
@item Loads of improvements to Text classes.
@item NSImage, NSButton, NSCell, etc, implemented many missing methods.
@item ...and even more changes to the Text classes.
@item Starting implementation of printing.
@item Scrollview fixes.
@item Implemented deferred windows.
@item NSTableView implemented.
@item Implemented object value and formatter support in NSCell
@item Support middle mouse button.
@end itemize
@c ====================================================================
@c Keep the next line just below the list of changes in most recent version.
@ifclear ANNOUNCE-ONLY
@section Noteworthy changes in version @samp{0.6.6}
@itemize @bullet
@ -35,10 +56,6 @@ backend is still considered experimental and you may have to deal with
many problems in order to get it working. We recommend sticking with the
xgps backend (the default) for now.
@c ====================================================================
@c Keep the next line just below the list of changes in most recent version.
@ifclear ANNOUNCE-ONLY
@section Noteworthy changes in version @samp{0.6.5}
Many of the basic GUI classes have been vastly improved or rewritten, thanks

44
Documentation/todo.texi
View file

@ -9,45 +9,12 @@
@section Bugs in the GUI library
@end ifclear
@subsection Windows
@itemize @bullet
@item Getting and releasing keyboard focus is still buggy. This is mostly
annoying for users trying to type in a GNUstep or non-GNUstep window.
@end itemize
@subsection Texts
@itemize @bullet
@item There have been a lot of improvements in the NSText code, but is
particularly complex. It is
somewhat usable though. We hope to keep improving it.
@end itemize
@subsection Matrices
@itemize @bullet
@item Encoding/Decoding of matrices is unimplemented. There are some minor
known bugs with handling of mouse down in matrices.
@end itemize
@subsection Cells
@itemize @bullet
@item Since NSText does only left alignment, when you select or edit text
in a cell it becomes automatically left aligned regardless of the original
alignment.
@item Multi line texts are unsupported; isScrollable, wordWraps etc do nothing.
This restriction will hopefully be removed in next releases.
@end itemize
@subsection Images anf Graphics
@itemize @bullet
@item There are problems with alpha composing. To avoid these problems,
you may set manually the background color of your image when displaying it.
@ -56,24 +23,13 @@ degree.
@end itemize
@subsection Alert, Info Panels
@itemize @bullet
@item Multi line messages are generally unsupported due to the similar
restriction in the cells code.
@end itemize
@subsection Unimplemented Classes
The following classes are currently unimplemented or unfinished
to such a degree to be unusable.
@itemize @bullet
@item NSDataLink
@item NSHelpPanel
@item NSLayoutManager
@item NSPageLayout
@item NSPrintPanel
@item NSSecureTextField
@item NSSpellChecker
@end itemize

160
INSTALL
View file

@ -1,142 +1,36 @@
Installation
************
This file documents the installation of the GNUstep GUI Library,
`gnustep-gui'. Copyright (C) 1996 Free Software Foundation, Inc. You
may copy, distribute, and modify it freely as long as you preserve this
copyright notice and permission notice.
Introduction
============
This is version 0.6.6 of the GNUstep GUI library.
This file documents the installation of the GNUstep GUI Library,
`gnustep-gui'. If you are installing this package as part of the
GNUstep core package, read the file GNUstep-HOWTO for more complete
instructions on how to install the entire GNUstep package (including
this library). GNUstep-HOWTO is located at <www.gnustep.org>
Installing `gnustep-gui'
========================
Configuration
=============
Here is a quick-and-dirty example of installation commands:
Configuration is performed by running the `configure' program at a
shell prompt. You may want to use some of the optional arguments to the
`configure' program. Type `configure --help' for a list. GNUstep
specific options are at the end of this list (if any).
Compilation
===========
To compile this library, type make. After this is complete, type make
install (make sure you are the root user). Some additional options you
can use with make are `debug=yes' to make a debugging version of the
library and `shared=no' to make a static version of the library. See
the gstep-make package for more information on these options.
Installing
==========
To install, type
./configure --prefix=/usr/GNUstep
make
make install
Here are more detailed instructions. Also read the `GNUstep-HOWTO'
for instructions on how to install the entire GNUstep system.
1. Install `gcc'. The library requires gcc version 2.8.0 or later.
2. Install `gnustep-base'. This library requires the classes the
GNUstep Base Library.
3. Install the `TIFF' library. This library requires the header files
in the TIFF library to compile; the TIFF library is used for the
NSImage and associated classes for reading, writing, and
manipulating tiff files.
4. Configure the package for your system. In the directory that this
file is in, type `./configure'. If you're using `csh' on an old
version of System V, you might need to type `sh configure' instead
to prevent `csh' from trying to execute `configure' itself.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation, and
creates the Makefile(s) (one in each subdirectory of the source
directory). In some packages it creates a C header file
containing system-dependent definitions. It also creates a file
`config.status' that you can run in the future to recreate the
current configuration.
Running `configure' takes less than a minute or two. While it is
running, it prints some messages that tell what it is doing. If
you don't want to see the messages, run `configure' with its
standard output redirected to `/dev/null'; for example:
./configure >/dev/null
To compile the package in a different directory from the one
containing the source code, you must use a version of make that
supports the VPATH variable, such as GNU make. `cd' to the
directory where you want the object files and executables to go and
run `configure'. `configure' automatically checks for the source
code in the directory that `configure' is in and in `..'. If for
some reason `configure' is not in the source code directory that
you are configuring, then it will report that it can't find the
source code. In that case, run `configure' with the option
`--srcdir=DIR', where DIR is the directory that contains the
source code.
By default, `make install' will install the package's files in
/usr/local/bin, /usr/local/lib, /usr/local/man, etc. You can
specify an installation prefix other than /usr/local by giving
`configure' the option `--prefix=PATH'. Alternately, you can do
so by giving a value for the `prefix' variable when you run
`make', e.g.,
make prefix=/usr/gnu
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If
you give `configure' the option `--exec_prefix=PATH' or set the
`make' variable `exec_prefix' to PATH, the package will use PATH
as the prefix for installing programs and libraries. Data files
and documentation will still use the regular prefix. Normally,
all files are installed using the regular prefix.
You can tell `configure' to figure out the configuration for your
system, and record it in `config.status', without actually
configuring the package (creating Makefile(s) and perhaps a
configuration header file). To do this, give `configure' the
`--no-create' option. Later, you can run `./config.status' to
actually configure the package. This option is useful mainly in
`Makefile' rules for updating `config.status' and `Makefile'. You
can also give `config.status' the `--recheck' option, which makes
it re-run `configure' with the same arguments you used before.
This is useful if you change `configure'.
`configure' ignores any other arguments that you give it.
If your system requires unusual options for compilation or linking
that `configure' doesn't know about, you can give `configure'
initial values for some variables by setting them in the
environment. In Bourne-compatible shells, you can do that on the
command line like this:
CC='gcc -traditional' DEFS=-D_POSIX_SOURCE ./configure
The `make' variables that you might want to override with
environment variables when running `configure' are:
(For these variables, any value given in the environment overrides
the value that `configure' would choose:)
`CC'
C compiler program. Default is `cc', or `gcc' if `gcc' is in
your PATH.
`INSTALL'
Program to use to install files. Default is `install' if you
have it, `install.sh' otherwise.
(For these variables, any value given in the environment is added
to the value that `configure' chooses:)
`DEFS'
Configuration options, in the form `-Dfoo -Dbar ...'
`LIBS'
Libraries to link with, in the form `-lfoo -lbar ...'
If you need to do unusual things to compile the package, we
encourage you to figure out how `configure.in' could check whether
to do them, and mail diffs or instructions to the address given in
the `README' so we can include them in the next release.
5. Type `make' to compile the package. If you want, you can override
the `make' variables `CFLAGS' and `LDFLAGS' like this:
make CFLAGS=-O2 LDFLAGS=-s
6. Type `make install' to install the library, data files, header
files, and documentation.
7. You can remove the program binaries and object files from the
source directory by typing `make clean'. To also remove the
Makefile(s), and `config.status' (all the files that `configure'
created), type `make distclean'.
The file `configure.in' is used as a template to create
`configure' by a program called `autoconf'. You will only need it
if you want to regenerate `configure' using a newer version of
`autoconf'.

29
NEWS
View file

@ -1,7 +1,34 @@
NEWS
****
The currently released version of the library is `0.6.6'.
The currently released version of the library is `0.6.7'.
Noteworthy changes in version `0.6.7'
=====================================
* App Icons can support documents dropped using DnD.
* Added color conversions, working color picker and panel.
* Almost complete rewrite of NSBezierPath
* Loads of improvements to Text classes.
* NSImage, NSButton, NSCell, etc, implemented many missing methods.
* ...and even more changes to the Text classes.
* Starting implementation of printing.
* Scrollview fixes.
* Implemented deferred windows.
* NSTableView implemented.
* Implemented object value and formatter support in NSCell
* Support middle mouse button.
Noteworthy changes in version `0.6.6'
=====================================

2
README
View file

@ -1,7 +1,7 @@
README
******
This is version 0.6.6 of the GNUstep GUI library (`gnustep-gui').
This is version 0.6.7 of the GNUstep GUI library (`gnustep-gui').
Here is some introductory info to get you started: