🚀 go-pugleaf

In article <C0JyrD.Jwx@ccsun.strath.ac.uk> clar27@ccsun.strath.ac.uk
("j.forssell") writes:
[...]
>Do you know John why Geoworks is reluctant to supply information like this
>electronically? Is it just because they don't want it to 'float around' and
>get in to wrong hands or is it a way to make sure that only the people with
>enough interest (to pay) will use it?

I talked with various Powers-That-Be at GeoWorks and they put it on *their*
list of things to look into.  There lists are longer than mine.  :-)  They
have yet to get back to this issue as there are plenty of things that are
more critical to the success of the company (obviously :-).

>About the cost for the SDK documentation, is that charged by GeoWorks to
>cover for their printing costs? I can`t see a reason for earning money on
>a thing like that.

Isn't this mentioned in the developers part of the FAQ?  If you purchase
the BETA SDK documentation you get over 3500 pages (in 5+ volumes) that
document the system *AND* each of the subsequent SDK BETA documentation
releases.  Do you have any idea how much limited runs of that many pages in
that many volumes costs?  It's a LOT.  GeoWorks is most likely losing a
good chunck of money but this is felt to be a very important part of the
process of making as much information available as possible.

>How about Macrosoft and IBM, do they supply similar manuals elecronically?

Microsoft distributes some things on CD-ROM because then they don't have
the cost of printing to worry about so they can get higher margins out of
their development packages and get people to buy more of their books
(because people want the printed manuals even if they have them online).

Hope this helps,
	John
	johnm@cory.Berkeley.EDu

P.S.	I speak for my self.  GeoWorks speaks for itself.