zoolib-dev — Development list for the ZooLib cross-platform application framework

Re: [ZooLib-dev] Is ZooLib ready for real-world use?

[Andrew G. <ag...@em...>]

Hi Joshua,

On 22 May 2001 18:05:34 -0400, Joshua Juran wrote:
> First of all, I apologize for the slightly inflammatory subject line 
> -- I'm not here to rant about the issues I'm having with ZooLib, but 
> to solve them.  So I'm just trying to get some attention.  In case I 
> raised anyone's hackles, you may lower them now. :-)

I'd love it if you'd dive in and let rip with the issues :) Almost
everything that exists in ZooLib has already survived criticism and
debate with the people who use it, but that's been a fairly limited
group so far and additional insights or complaints are only going to
help.
Using this mailing list would be most valuable, rather than sending
directly to my email. I get the feeling that although there must be at
least 1000 people who've downloaded the source, most of them have not
been able to get into it because of the paucity of documentation and
sample code. A richer mailing list archive might be helpful, and could
seed a documentation effort (I can dream).

wrt cvs, my copy of ZooLib is managed out of a private cvs server that
supports the product development work of Learning in Motion and OISE.
Every month or so I post a package of source at
<http://www.zoolib.org/bleedingedge/>,
which I intended as an interim measure until I figured out how to handle
keeping the source in two cvs servers simultaneously. Unfortunately I
don't have any experience with that kind of setup -- in fact if I'm
doing anything other than a checkin or update I have to hit the cvs
manual to refresh my memory. If you (or anyone else reading this) has
any suggestions about how to handle this I'd love to hear from you.

Looking forward to hearing from you,
Andrew Green

[ZooLib-dev] Is ZooLib ready for real-world use?

[Joshua J. <ju...@nc...>]

Hello,

First of all, I apologize for the slightly inflammatory subject line 
-- I'm not here to rant about the issues I'm having with ZooLib, but 
to solve them.  So I'm just trying to get some attention.  In case I 
raised anyone's hackles, you may lower them now. :-)

I work for the National Center for Biotechnology Information (NCBI), 
part of the National Library of Medicine (NLM) at NIH (National 
Institutes of Health) near DC.  My branch writes the scientific 
software.  We use a cross-platform toolkit, and my job is to maintain 
and develop the Mac support.

The version of the toolkit currently in circulation is written in C 
and uses an app framework developed in-house called Vibrant, which is 
about eleven years old and shows it.  We're developing a new toolkit 
in C++, and are considering frameworks to use.  We will not port or 
rewrite Vibrant.  We had been considering only wxWindows, but I 
suggested that we also look at ZooLib, and so my current task is to 
try out both and make a recommendation.

I was already clear that ZooLib is the winner architecturally -- 
that's why I suggested it.  But here's where the 'real-world use' 
comes in:  We need to support Unix.  On the other hand, our C++ 
toolkit won't be ready to ship for a few more years.  So, while we're 
already using wxWindows for one of our apps, it may be feasible to 
switch to ZooLib later on (even if it means having to port that app 
myself, which I would willingly do to make better software).  So the 
race is on.

In the meantime, I would *really* like to get ZooLib from CVS.  For 
one thing, it makes it easier to make diffs, and it's also easier to 
incorporate them.  I'll import the source myself if you want.

Speaking of which, I have patches (addressing compile-time issues) to 
ZRefCount.h and ZUITextEngine_Mac.cpp, but I don't have a suitable 
diff-generator handy.

Thanks for your attention to this.

Joshua Juran

FW: [ZooLib-dev] Tab panels and splitters

[Mark W. <mr...@bi...>]

Mark,
To add a splitter you need to do the following:

1. Create in window constructor.

myWindow::myWindow(ZApp* inApp)
:    ZWindow(inApp, sCreateOSWindow(inApp))

..snip..
    fSplitter1 = ZUIFactory::sGet()->Make_Splitter( fToolbarPane, this );
    
    fSplitter1->GetPanes( fPanel1Pane, fPanel2Pane );
    fSplitter1->AddResponder(this);
..snip..

2. Make sure you size properly using the GetPaneSize method.

bool myWindow::GetPaneSize(ZSubPane* inPane, ZPoint& outSize)

..snip..
    if( inPane == fSplitter1 )
        {
        outSize = fToolbarPane->GetSize();
        outSize -= fToolbarPane->GetToolbarOffset();
        }

3. Make sure you set the location properly using the GetPaneLocation method.

bool myWindow::GetPaneLocation(ZSubPane* inPane, ZPoint& outLocation)

..snip..
    if( inPane == fSplitter1 )
        {
        outLocation = fToolbarPane->GetToolbarOffset();
        }
        
4. Make sure you support the pane properties using the GetPaneAttribute
method.

bool myWindow::GetPaneAttribute(ZSubPane* inPane, const string& inAttribute,
void* inParam, void* outResult)

..snip..
    if( inPane == fSplitter1 )
        {
        if( inAttribute == "ZUISplitter::Orientation" )
            {
            (*(bool*)outResult) = false;
            return( true );
            }
        else
        if( inAttribute == "ZUISplitter::SizePane1" )
            {
            (*(ZCoord*)outResult) = fPanel1PaneSize;
            return( true );
            }
        }

5. Make sure you support the SplitterChanged method.

void myWindow::SplitterChanged(ZUISplitter* inSplitter, ZCoord
inNewPane1Size, ZCoord inNewPane2Size)

..snip..
    if( inSplitter == fSplitter1 )
        {
        inSplitter->FramePreChange();
        fPanel1PaneSize = inNewPane1Size;
        inSplitter->FramePostChange();
        }
        



Hope this helps.

Mark Wrenn

        

[ZooLib-dev] Tab panels and splitters

[Mark A. <all...@la...>]

Hello All,

I'm having difficulty with ZoolLib tab panels and splitters. In the case of
tab panels, I can't get them to appear properly (tabs missing on MacOS and
tabs drawn as buttons on Windows).  Further, I can't get the tab buttons to
respond to mouse clicks on Windows.  In the case of splitter, when I click
on the divider it is highlighted but moving the mouse does not mive the
divider.

Thanks for the help

Cheers
-Mark

---------------------------------------------------------------------
Mark Alldritt                         Late Night Software Ltd.
Phone: 250-380-1725                   333 Moss Street
FAX:   250-383-3204                   Victoria, B.C.
WEB:   http://www.latenightsw.com/    CANADA  V8V-4M9

[ZooLib-dev] Re: ZooLib-dev -- confirmation of subscription -- request 520720

[Ruslan Z. <sun...@pu...>]

confirm 520720

Re: [ZooLib-dev] re: ZooLib on Open Source Directory

[David J. <da...@us...>]

On Saturday April 07 2001 05:15 pm, Michael D. Crawford wrote:

> It's a new site, and a little rough around the edges. 

It's very new. I think I had the first submission, and it was even rougher 
then. The maintainers are overworked, but nice people. If you're missing 
categories and stuff, just drop them a line.

-- 
David Johnson
___________________
http://www.usermode.org

[ZooLib-dev] re: ZooLib on Open Source Directory

[Michael D. C. <cra...@go...>]

(Keypress error sent it early... this time for sure)

Somebody has started a directory of mature, stable open source products called

http://www.opensourcedirectory.org/

It uses the SourceForge source code, but it is different from SourceForge - it
doesn't host software development or store any files, it just classifies them.

It locates files on other servers, but it is different from FreshMeat 
(http://freshmeat.net).  FreshMeat lists a lot of open source stuff, but it
also lists a lot of closed-source stuff which runs on Linux.  The Open Source
Directory is just for stuff that is open source, and appears to intend to be
inclusive of other platforms besides Linux.  It's been featured on a number of
open source news sites the last couple days like newsforge and slashdot.

I've registered zoolib there at:

https://www.opensourcedirectory.org/projects/zoolib/

It's a new site, and a little rough around the edges.  For example, I could
only provide three operating systems for ZooLib's trove categorization.  I
picked OS Independent, Linux and Windows.  ZooLib isn't OS Independent
exactly, it would be more appropriate to list the separate OSes that it has
been ported to, but that's what is available.  Also there was no trove
categorization available for libraries or application frameworks, so I just
picked Software Development.

Regards,

Mike
-- 
Michael D. Crawford
GoingWare Inc. - Expert Software Development and Consulting
http://www.goingware.com/
cra...@go...

   Tilting at Windmills for a Better Tomorrow.

[ZooLib-dev] ZooLib on Open Source Directory

[Michael D. C. <cra...@go...>]

Somebody has started a directory of mature, stable open source products called

http://www.opensourcedirectory.org/

It uses the SourceForge source code, but it is different from SourceForge - it
doesn't host software development or store any files, it just classifies them.

It locates files on other servers, but it is different from FreshMeat 
(http://freshmeat.net).  FreshMeat lists a lot of open source stuff, but it
also lists a lot of closed-source stuff which runs on Linux.  The Open Source
Directory is just for stuff that is open source.

I've registered zoolib there at:

-- 
Michael D. Crawford
GoingWare Inc. - Expert Software Development and Consulting
http://www.goingware.com/
cra...@go...

   Tilting at Windmills for a Better Tomorrow.

Re: [ZooLib-dev] zoolib/foundation/ZAtomic.cpp ZAtomic_Add segfault sparc

[Andrew G. <ag...@em...>]

> We also have problems with the inline assembler on BeOS powerpc.  What I'm
> going to do there is write a regular (non-inline) assembler file for BeOS
> powerpc, and have a zconfig.h option for not using inline assembler when one
> makes a build

The problem Mike's referring to is simply CodeWarrior for BeOS's limitations
with inline assembler. We've got PPC assembler for the more recent versions
of CodeWarrior targetting MacOS, and of course for gcc (Chris Teplovs built
and successfully checked it out on LinuxPPC). If anyone knows how to get PPC
assembler, or even just explicit hex opcodes, to compile under CW for BeOS
please let us know. Alternatively we can have, as Mike suggests, a .S file
with pure assembly, and have ZAtomic.h's functions forward to the
implementations therein.

A
__________________________________________________________________
Andrew Green                                  mailto:ag...@zo...
ZooLib Guy                                   http://www.zoolib.org
350 25th Avenue, Suite #1                   Vox: +1 (415) 831 2471
San Francisco, CA 94121-1912                Fax: +1 (415) 831 2472

Re: [ZooLib-dev] zoolib/foundation/ZAtomic.cpp ZAtomic_Add segfault sparc

[Andrew G. <ag...@em...>]

James wrote:
> I downloaded Zoolib yesterday and compiled the demos on Linux 2.4.2
> (Intel) and Solaris 8 (UltraSPARC). The demos run (ostensibly) fine
> under Linux but crash (Segmentation fault) under Solaris. The problem
> seems to be when ZAtomic_Add tries to acquire the sMutexNR lock: the
> acquisition routine calls ZAtomic_Add...infinite recursion. It would
> seem that when compiled on an Intel platform the ASM is used and is
> correct (so the Linux build worked) but the C++ for non-PPC and
> non-Intel platforms is incorrect (so the Solaris build failed).


Hi James,

Mike's protestations (and associated complement):
>I would strongly disagree with you that there are logical errors in the C++
notwithstanding, you are correct that in the 0.8 source archive the 'dumb'
version of the atomic operators is incorrect. It was something I put
together as a placeholder as much as anything -- I didn't have a platform
that actually needed it, so I never actually ran it. On a subsequent
re-reading of the code my brain engaged: the implementation of sMutexNR is a
benaphore, relying on atomic add to shortcircuit non-contested non-recursive
mutex allocation. A fix is in place.
The most recent code  that I feel is in reasonable shape lives in
<http://www.zoolib.org/bleedingedge/>
I have not been posting announcements of updates to that directory, but in
looking back over it, I've been updating it about once a month.

Apps based on ZooLib have been built and run on Solaris, but it's been a
while and the full suite of atomic ops has grown up since then (about two
years ago). The atomic operations are fairly straightforward to port,
although sparc is probably the most awkward target architecture. I'd love to
work with you to get them in place.

I really appreciate the time you, and everyone, have taken to grab the
source and try it out. I encourage you all to post your findings to the
list. I can't promise to fix every problem that's found, but I'll do my best
to help out.

A
__________________________________________________________________
Andrew Green                                  mailto:ag...@zo...
ZooLib Guy                                   http://www.zoolib.org
350 25th Avenue, Suite #1                   Vox: +1 (415) 831 2471
San Francisco, CA 94121-1912                Fax: +1 (415) 831 2472

Re: [ZooLib-dev] zoolib/foundation/ZAtomic.cpp ZAtomic_Add segfault spa rc

[Michael D. C. <cra...@go...>]

> Oh. I thought ZooLib was portable.

ZooLib is portable, but it depends on the presence of atomic math, which is
not something that is typically provided in high-level languages.  If the
ZAtomic stuff compiles at all without the use of assembler, it is simply
incorrect, as you cannot do that sort of thing from C++.

Some operating systems, like the BeOS, provide library routines with access to
atomic math but ZooLib's author Andy Green says he has been unable to form a
complete set of atomic operations from even the routines provided by the BeOS.
 Hence there is a small amount of assembly code for each supported platform.

I would strongly disagree with you that there are logical errors in the C++; I
have yet to meet a programmer who pays more slavish attention to detail and
correctness of C++ code than ZooLib's author.  I don't doubt that there may be
some, but _I_ certainly have not had the pleasure of meeting them.

You will find that there are only a few platform-specific files in the whole
of ZooLib, and some of the classes have platform-specific members as
implementation details that are not publicly visible.  For example, there is
ZOSWindow_Mac, there is the ZAtomic inline assembler, and there are the
different kinds of platform-dependent bitmaps hidden inside a ZDCPixmap.

ZooLib _is_ portable but that does not mean it has been _ported_ to every
platform; because both threaded code and graphical user interface code are
highly platform specific, effort is required to port to a new platform, it
doesn't just compile out of the box.

Imagine, if you will, implementing the ZAtomic and ZThread classes and
operations on top of Solaris threads - you can certainly do that, and there
would likely be advantages to you on your platform if you did.  But you
couldn't expect to do so without having to write some code which was native to
the Solaris operating system.

Mike
-- 
Michael D. Crawford
GoingWare Inc. - Expert Software Development and Consulting
http://www.goingware.com/
cra...@go...

   Tilting at Windmills for a Better Tomorrow.

Re: [ZooLib-dev] zoolib/foundation/ZAtomic.cpp ZAtomic_Add segfault sparc

[Michael D. C. <cra...@go...>]

Hi,

We're very pleased you're trying it on Sparc, but none of those involved in
writing ZooLib have had Sparc machines available to them.

It won't be right away, but I expect I'll get a Sparc machine later in the year.

Sometime soon I'm going to get another hard drive and I'll be adding BSD and
Solaris x86 to one of my Pentium III machines.  Can one cross-compile for
Sparc on Solaris x86?

Isn't there a compile farm at SourceForge?  How does one set up a project to
use it?  I could write some command-line test tools in ZooLib that we could
run on the compile farm, if they have Solaris.

Or you could give me a login on your machine ;-)

We also have problems with the inline assembler on BeOS powerpc.  What I'm
going to do there is write a regular (non-inline) assembler file for BeOS
powerpc, and have a zconfig.h option for not using inline assembler when one
makes a build.  When that is set up (this should be fairly soon), it should be
straightforward for someone to write the equivalent assembly code file for
Sparc or other architectures using PowerPC or x86 as a model.  There's only a
few routines that need to be implemented.

Andy's been making source drops available from his own webserver that aren't
on sourceforge, that have some updated code.  The stuff I do for BeOS powerpc
will go into there when I get it ready, so others can test it before we
release it to the world.  Would you be into writing the Sparc assembler needed
to do the atomic operations?  It won't have to be a lot of code but it _does_
have to be absolutely bug-free or your ZooLib application will be pretty brain damaged.
-- 
Michael D. Crawford
GoingWare Inc. - Expert Software Development and Consulting
http://www.goingware.com/
cra...@go...

   Tilting at Windmills for a Better Tomorrow.

[ZooLib-dev] zoolib/foundation/ZAtomic.cpp ZAtomic_Add segfault sparc

[James D. <j-d...@us...>]

Hi,

I downloaded Zoolib yesterday and compiled the demos on Linux 2.4.2
(Intel) and Solaris 8 (UltraSPARC). The demos run (ostensibly) fine
under Linux but crash (Segmentation fault) under Solaris. The problem
seems to be when ZAtomic_Add tries to acquire the sMutexNR lock: the
acquisition routine calls ZAtomic_Add...infinite recursion. It would
seem that when compiled on an Intel platform the ASM is used and is
correct (so the Linux build worked) but the C++ for non-PPC and
non-Intel platforms is incorrect (so the Solaris build failed).

[ZooLib-dev] ZooLib listed on BeBits tonight

[Michael D. C. <cra...@go...>]

I don't know how I could have overlooked this before, but things have been
hectic the last few months.  I'm getting more time these days.

I just listed ZooLib on BeBits, which is the main BeOS software download site.
They supply both freeware and they sell software now that BeDepot is closed.

http://www.bebits.com/

You'll find the ZooLib entry at:

http://www.bebits.com/app/2098

please pardon the confusing order in which the different items are laid out on
the page.  I listed the ZooLib source, ZHelloWorld executable, ButtonMessage
executable, and demo source code in that order, but BeBits laid them out
alphabetically, so the first thing you see in the download section of the page
is ButtonMessage and the ZooLib source is buried at the third item!  

I sent a mail to ask them to let us control the order of presentation.

Mike
-- 
Michael D. Crawford
GoingWare Inc. - Expert Software Development and Consulting
http://www.goingware.com/
cra...@go...

   Tilting at Windmills for a Better Tomorrow.

[ZooLib-dev] Let's talk about sample code & documentation

[Michael D. C. <cra...@go...>]

Many of you know that I'm supposed to be writing the documentation for ZooLib.
 

I'd like to write more sample code, and then I want to write tutorials on each
piece of sample code.  I'd like you all to discuss ideas for sample programs
with me, and I'll save up my email and use it when I write the sample code and tutorials.

It would help a lot of any of you folks would contribute sample code too.  It
doesn't have to be big, complex or take a long time to write; in fact the
simpler the better.  ButtonMessage is just a few source files.  One should
take care to write clean, proper code and do things right rather than in a
hurry or using skanky techniques.  I've seen some really bad, buggy sample
code on the Apple Developer Technical Support CDs.

We want to write the documentation in DocBook (http://www.docbook.org) - there
are many advantages to it; among them it can be readily rendered into
different formats such as Postscript, PDF and HTML for printed or online
viewing.  The Linux Documentation Project has standardized on DocBook.

On thing that's held me up is that it's complicated to get it working, but I
seem to have found good instructions for building and using a DocBook
toolchain on Linux.  Another good thing is that I've finally got my laptop
repaired and, while it boots Windows and BeOS also, I've decided to leave it
running in Linux most of the day so I can use it as a Samba and netatalk
fileserver (!) for my Mac and Desktop PC.  This means I won't have to go tear
my wife away from Windows 98 and reboot the PC to use Linux.

Writing a proper programmer's reference manual for the whole of ZooLib will be
a massive job.  It will also be of somewhat limited use in telling new users
_how_ to accomplish something in ZooLib.  

Andy's done some work with generating Doxygen files from ZooLib, and we can
provide tar or zip files of the generated HTML that people can download and
also have it on the web for people to casually browse, for example when they
want to just check something out quick.

Doxygen is like Javadoc for C++, but does a little more than javadoc.  For an
example, see the Doxygen output for Whisper, another fine cross-platform
application framework:

http://magnes.augsburg.edu/Whisper/html/

Doxygen's at http://www.doxygen.org

Andy's starting to put in the doxygen comment metacharacters so it will
extract a C++ comment and use it for the API reference in a Doxygen file.

What I think will get the most results for a moderate amount of effort is if
we write more sample code and then I write articles about each one.  

We should try to cover a wide range of ZooLib's functionality in, say, a dozen
programs but try to have each sample program focus on one component of ZooLib
so that a novice programmer can read and comprehend just a few source files in
one sitting.  Once enough sample programs have been written, a programmer
could work through each sample program one at a time and have a good overall
grasp of ZooLib.

Ideas I have for sample code include:

- a TCP echo client and server

- a simple ZDatabase server and query client.  You can enter an integer and a
string into edit fields in the client.  The string is stored in the database
with the integer as the key.  If you just send the key it will send back the
stored string or a "not found" indicator, and if you try to store an item
whose key already exists then it is replaced.

- Examples of doing various kinds of pane layout, and how to handle resizable
windows and also properly updating things when the pane size could change
after its data is modified.

I found layout the hardest part of ZooLib to grasp, but also one of the most
powerful tools it provides.  Andy and I have lots of ideas for utility classes
to make layout much easier to handle, so that one can write up a new window or
dialog with a minimum of fiddling.

- Examples of ZDCPixmap processing, both using GetPixel and SetPixel, and also
by directly accessing the pixel data via pointers offset from the base
address.  I'm starting to think about writing some iterators that will allow
the efficiency of direct memory access with nearly the ease and portability of GetPixel/SetPixel.

- Using streams and doing filters by chaining them.  One can illustrate a lot
of things just streaming in and out of a memory block, you don't have to touch
a file or network connection.  Of course there should be examples of file and
network streaming too.

- Reading and writing files, and using file open and save panels.

For the most part all of the sample code should be fully functional on all the
platforms.  At this stage this means we shouldn't use menus unless we really
have to, because menus won't work on XWindows.  Separate example code should
be written that does various interesting things with menus, and the people on
Mac, Windows and BeOS can use that.  When we have XWindows menus then we can
update all the sample code for a more natural UI.

(You don't have to get it to build on all the platforms yourself if you write
some sample programs, if you just make a reasonable effort to keep your code
platform-independent I can complete the job as I run all the platforms ZooLib
presently supports - any three at one time and as soon as I can afford one
more PC I can run all simultaneously without having to reboot.)

- It would also be useful to have sample code that fully exploited some
platform-specific feature on each of the supported platforms, for example one
could write a ZooLib application that used the BeOS media kit.  

This would illustrate that while being cross-platform is generally an
advantage it doesn't cripple one by requiring lowest-common-denominator
programs like SOME cross-platform approaches, and that using ZooLib to write
platform-specific code may be a more pleasing alternative to the more popular
application frameworks and native APIs because of its quality architecture.

I will generate Doxygen HTML files for each sample program, and post them online.

Then I will write DocBook tutorials on each sample program.  I'll do this for
my samples as well as any you write, unless you'd like to learn how to write
DocBook XML yourself.  

Having Doxygen-formatted comments in the sample code will go a long ways in
itself, but having the DocBook would be a better format for discussing the
motivations for doing things a certain way at greater length and in a more
pleasing-to-read format than the Doxygen.

I started writing an article for ZHelloWorld last year and called it the first
chapter of "The ZooLib Cookbook" but then I ran into problems because I wasn't
using an editor that would keep my document valid to the docbook DTD.

One thing I did find in this early effort is that it's not actually very hard
to learn to write DocBook source files by hand.  There are only a few tags one
needs to use to write most of one's text.  DocBook can get tricky   

Probably the most annoying thing is that one needs to convert "<" and ">" into
"&lt;" and "&gt;" respectively - these are called "entities" and are needed so
C++ template code won't confuse the XML parser.  But there are text-to-HTML
conversion utilities that are readily available so that rather than
laboriously hand-correcting my code snippets for the doc I can just filter them.

So what ideas do you have about sample code?  Do you have any samples you
think you could write based on what you know, or could you tell me what
samples you either might find useful now or would have found useful when you
first started?  What would you see as the philosophically or practically best
way to approach any particular aspect of ZooLib programming?

Mike
-- 
Michael D. Crawford
GoingWare Inc. - Expert Software Development and Consulting
http://www.goingware.com/
cra...@go...

   Tilting at Windmills for a Better Tomorrow.

[ZooLib-dev] Creating an Explorer type button with Zoolib

[Mark W. <mr...@bi...>]

I'm creating an Explorer type button - similar to the buttons on Outlook
Express, etc.  I have it limping along but I'm not sure how to handle
mouseovers.  The button normally blends with the background until the mouse
moves over it then the outline of the button appears.
 
How should this be structured so I can capture mouse movement?

Re: Debian compilation (was: Re: [ZooLib-dev] Linux compilation)

[David J. <da...@us...>]

On Tuesday 20 February 2001 01:43 am, Andrew Green wrote:

> Automatically determining the compiler is possible, cv gnu autoconf,
> although what I'm leaning toward is a clean up and extension of the
> existing mechanism, and taking a few lessons from the QT approach.

The Qt approach is very nice and very clean. Unfortunately, it chokes on 
non-standard installations. I would prefer something between autoconf and 
tmake. It would output human readable Makefiles like tmake, but actually go 
and check for the existance of libraries and headers like autoconf. 

-- 
David Johnson
___________________
http://www.usermode.org

Re: Debian compilation (was: Re: [ZooLib-dev] Linux compilation)

[Andrew G. <ag...@em...>]

> After some checking, I worked out that the makefile was looking for 
> it in /usr/X11/lib/ which didn't exist on my distro.  I changed the
> makefile to point at /usr/X11R6/lib/ and that fixed it.
>
> Is there any way to get these directories and commands from the
> OS instead of hardcoding them into the makefile?  (I don't have
> enough experience with 'nix to know.)  If there is, it could save
> some effort.

In wrapping up work on preliminary resource support I'm addressing the
makefile situation too. The reason it's currently pretty fragile is simply
that the user base has been small and homogenous enough for it not to be a
issue up till now. Clearly that's changing.

Automatically determining the compiler is possible, cv gnu autoconf,
although what I'm leaning toward is a clean up and extension of the existing
mechanism, and taking a few lessons from the QT approach.

The X11 libraries are really X11R6 nowadays, the makefile should not be
referring to /usr/X11/... that's just my mistake.


Andrew Green

Debian compilation (was: Re: [ZooLib-dev] Linux compilation)

[Mike M. <zo...@je...>]

Hi Bob, and everyone.

I did some checking and worked out that the makefile is calling 
gcc, which (at least on my Debian distro) is the C compiler as you 
guessed.  I changed the compile command to g++ and that fixed it.

After that I had some library problems, most of which went away 
when I upgraded various packages.  Notably though, it still couldn't 
find the x11 library.

After some checking, I worked out that the makefile was looking for 
it in /usr/X11/lib/ which didn't exist on my distro.  I changed the 
makefile to point at /usr/X11R6/lib/ and that fixed it.

Is there any way to get these directories and commands from the 
OS instead of hardcoding them into the makefile?  (I don't have 
enough experience with 'nix to know.)  If there is, it could save 
some effort.

Thanks for your help.
Mike.

Bob McLean <rm...@oi...> wrote:

> Sounds to me like you're using a C compiler rather than a C++ compiler.
> 
> There is lots of experience with zoolib and *nix systems; our shop has
> worked with it on Solaris and RedHat linux. 
> 
> vector and map are fundamental types in the C++ language; I think you'll
> find them in most books on C++. A good explanation is in the C++ Primer
> by Lippman and Lajoie, published by Addison Wesley.
> 
> Good luck,
> 
> Bob
> 
> Mike McGavin wrote:
> > 
> > Hello, zoolib elite.
> > 
> > I heard of zoolib a while ago when it was mentioned on the abiword
> > development list, and I've just now begun to look at zoolib 0.8.1.  It
> > sounds great.
> > 
> > I was wondering if anyone has any experience compiling it in linux,
> > or any unix-type system for that matter.  I'm running a debian
> > distribution with various packages ranging between the 2.0 and the
> > 2.4 releases.
> > 
> > I don't have enough experience developing in a unix environment to
> > know what libraries I might need for some of this, but if anyone can
> > give me a list of any dependencies that zoolib relies on for me to
> > hunt down, I'd appreciate it.
> > 
> > I followed the posix compilation instructions for compiling the
> > HelloWorld sample program from the command line, but got some
> > errors regarding missing files that are included from some of the
> > zoolib files.  I've cut down the compiler output since most of it isn't
> > relevant, but summarised, it's complaining about the following:
> > 
> > =====
> > 
> > ../../zoolib/foundation/ZTypes.h:30: cstdio: No such file or directory
> > 
> > ../../zoolib/graphics/ZDCFont.h:39: string: No such file or directory
> > 
> > ../../zoolib/foundation/ZCompat_algorithm.h:32: algorithm: No such
> > file or directory
> > 
> > ../../zoolib/threads/ZThread.h:29: stdexcept: No such file or
> > directory
> > 
> > ../../zoolib/threads/ZThread.h:30: vector: No such file or directory
> > 
> > ../../zoolib/graphics/ZDCPoly.h:31: vector: No such file or directory
> > 
> > ../../zoolib/graphics/ZDCRgn.h:31: vector: No such file or directory
> > 
> > ../../zoolib/foundation/ZTuple.h:33: string: No such file or directory
> > 
> > ../../zoolib/uicore/ZMenu.h:36: vector: No such file or directory
> > 
> > ../../zoolib/foundation/ZInterest.h:31: vector: No such file or directory
> > 
> > ../../zoolib/foundation/ZString.h:29: string: No such file or directory
> > 
> > ../../zoolib/uicore/ZUIFactory.h:30: map: No such file or directory
> > 
> > I noticed that every one of the included files that it can't find is
> > missing a ".h" extention.  I managed to work around a couple by
> > changing "csdio" to "stdio.h" and "string" to "string.h".  Some of
> > the others aren't as obvious, though.  I'm not aware of any standard
> > vector or map headers.
> > 
> > I'd appreciate any help or feedback about this.  Is it a known
> > problem on 'nix systems, or am I missing something standard?  If
> > anyone would like further information, let me know and I'll dig it up.
> > 
> > Thanks for any help.
> > Mike.
> > 
> > Public key (PGP) available at
> > http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0xB708EA39
> >  --Please check with me before giving my email address to any commercial entities
> > 
> > _______________________________________________
> > ZooLib-dev mailing list
> > Zoo...@li...
> > http://lists.sourceforge.net/lists/listinfo/zoolib-dev
> 
>  Email: RM...@oi...
> 



Public key (PGP) available at
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0xB708EA39
 --Please check with me before giving my email address to any commercial entities

Re: [ZooLib-dev] Linux compilation

[Bob M. <rm...@oi...>]

Sounds to me like you're using a C compiler rather than a C++ compiler.

There is lots of experience with zoolib and *nix systems; our shop has
worked with it on Solaris and RedHat linux. 

vector and map are fundamental types in the C++ language; I think you'll
find them in most books on C++. A good explanation is in the C++ Primer
by Lippman and Lajoie, published by Addison Wesley.

Good luck,

Bob

Mike McGavin wrote:
> 
> Hello, zoolib elite.
> 
> I heard of zoolib a while ago when it was mentioned on the abiword
> development list, and I've just now begun to look at zoolib 0.8.1.  It
> sounds great.
> 
> I was wondering if anyone has any experience compiling it in linux,
> or any unix-type system for that matter.  I'm running a debian
> distribution with various packages ranging between the 2.0 and the
> 2.4 releases.
> 
> I don't have enough experience developing in a unix environment to
> know what libraries I might need for some of this, but if anyone can
> give me a list of any dependencies that zoolib relies on for me to
> hunt down, I'd appreciate it.
> 
> I followed the posix compilation instructions for compiling the
> HelloWorld sample program from the command line, but got some
> errors regarding missing files that are included from some of the
> zoolib files.  I've cut down the compiler output since most of it isn't
> relevant, but summarised, it's complaining about the following:
> 
> =====
> 
> ../../zoolib/foundation/ZTypes.h:30: cstdio: No such file or directory
> 
> ../../zoolib/graphics/ZDCFont.h:39: string: No such file or directory
> 
> ../../zoolib/foundation/ZCompat_algorithm.h:32: algorithm: No such
> file or directory
> 
> ../../zoolib/threads/ZThread.h:29: stdexcept: No such file or
> directory
> 
> ../../zoolib/threads/ZThread.h:30: vector: No such file or directory
> 
> ../../zoolib/graphics/ZDCPoly.h:31: vector: No such file or directory
> 
> ../../zoolib/graphics/ZDCRgn.h:31: vector: No such file or directory
> 
> ../../zoolib/foundation/ZTuple.h:33: string: No such file or directory
> 
> ../../zoolib/uicore/ZMenu.h:36: vector: No such file or directory
> 
> ../../zoolib/foundation/ZInterest.h:31: vector: No such file or directory
> 
> ../../zoolib/foundation/ZString.h:29: string: No such file or directory
> 
> ../../zoolib/uicore/ZUIFactory.h:30: map: No such file or directory
> 
> I noticed that every one of the included files that it can't find is
> missing a ".h" extention.  I managed to work around a couple by
> changing "csdio" to "stdio.h" and "string" to "string.h".  Some of
> the others aren't as obvious, though.  I'm not aware of any standard
> vector or map headers.
> 
> I'd appreciate any help or feedback about this.  Is it a known
> problem on 'nix systems, or am I missing something standard?  If
> anyone would like further information, let me know and I'll dig it up.
> 
> Thanks for any help.
> Mike.
> 
> Public key (PGP) available at
> http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0xB708EA39
>  --Please check with me before giving my email address to any commercial entities
> 
> _______________________________________________
> ZooLib-dev mailing list
> Zoo...@li...
> http://lists.sourceforge.net/lists/listinfo/zoolib-dev

 Email: RM...@oi...

[ZooLib-dev] Linux compilation

[Mike M. <zo...@je...>]

Hello, zoolib elite.

I heard of zoolib a while ago when it was mentioned on the abiword 
development list, and I've just now begun to look at zoolib 0.8.1.  It 
sounds great.

I was wondering if anyone has any experience compiling it in linux, 
or any unix-type system for that matter.  I'm running a debian 
distribution with various packages ranging between the 2.0 and the 
2.4 releases.

I don't have enough experience developing in a unix environment to 
know what libraries I might need for some of this, but if anyone can 
give me a list of any dependencies that zoolib relies on for me to 
hunt down, I'd appreciate it.

I followed the posix compilation instructions for compiling the 
HelloWorld sample program from the command line, but got some 
errors regarding missing files that are included from some of the 
zoolib files.  I've cut down the compiler output since most of it isn't 
relevant, but summarised, it's complaining about the following:

=====

../../zoolib/foundation/ZTypes.h:30: cstdio: No such file or directory

../../zoolib/graphics/ZDCFont.h:39: string: No such file or directory

../../zoolib/foundation/ZCompat_algorithm.h:32: algorithm: No such 
file or directory

../../zoolib/threads/ZThread.h:29: stdexcept: No such file or 
directory

../../zoolib/threads/ZThread.h:30: vector: No such file or directory

../../zoolib/graphics/ZDCPoly.h:31: vector: No such file or directory

../../zoolib/graphics/ZDCRgn.h:31: vector: No such file or directory

../../zoolib/foundation/ZTuple.h:33: string: No such file or directory

../../zoolib/uicore/ZMenu.h:36: vector: No such file or directory

../../zoolib/foundation/ZInterest.h:31: vector: No such file or directory

../../zoolib/foundation/ZString.h:29: string: No such file or directory

../../zoolib/uicore/ZUIFactory.h:30: map: No such file or directory


I noticed that every one of the included files that it can't find is 
missing a ".h" extention.  I managed to work around a couple by 
changing "csdio" to "stdio.h" and "string" to "string.h".  Some of 
the others aren't as obvious, though.  I'm not aware of any standard 
vector or map headers.


I'd appreciate any help or feedback about this.  Is it a known 
problem on 'nix systems, or am I missing something standard?  If 
anyone would like further information, let me know and I'll dig it up.

Thanks for any help.
Mike.


Public key (PGP) available at
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0xB708EA39
 --Please check with me before giving my email address to any commercial entities

[ZooLib-dev] Added Instant Makeover to app list

[Michael D. C. <cra...@go...>]

Friends,

I added BeautyRiot's Instant Makeover to the ZooLib application list at:

http://zoolib.sourceforge.net/doc/applications.html

They're now shipping the windows version.  If you wonder why they're not 
shipping the Mac version, it probably has something to do with them 
terminating my contract when they stiffed me out of a lot of money after 
I slaved for nearly a year to write the product for them. 

I usually delivered Mac and Windows builds simultaneously from the same 
source base, but I guess they weren't able to find a Mac programmer to 
work on the cheap to ship the product.

Well, one small consolation is that I can now list Instant Makeover on 
ZooLib's app list and the products list on my resume.

Best,

Michael D. Crawford
GoingWare Inc. - Expert Software Development and Consulting
http://www.goingware.com/
cra...@go...

  Tilting at Windmills for a Better Tomorrow.

Re: [ZooLib-dev] CW Pro 6 & Visual C++

[Michael D. C. <cra...@go...>]

Hi,

I will definitely make a proper release when we have some loose ends tied up. 
We'll probably have a "0.9.0" development branch for a while.  There are
problems with getting it into sourceforge CVS, because the original developers
(Andy Green & Learning in Motion) have their own private CVS which has some
extra stuff for their own commercial application that will need to be dealt with
so they can continue their original work once it's in public CVS.

What I'm concentrating on right now is getting it to build on BeOS PowerPC. 
Apparently inline assembler is not supported for mwcc on beos so I'll be
implementing the atomic math using Be-supplied library routines and maybe a
little traditional (non-inline) assembler called via a subroutine call.

The work I do for _that_ will make it easier to get ZooLib up on platforms that
we do not know the atomic assembly for or whose compilers don't support inline
assembly.

I have Visual C++ but I don't have it installed due to a lack of disk space.  NT
only installs on a maximum of 8 GB hard drive, and while you can use a larger
drive and grow the partitions afterwards, you cannot then use the emergency
rescue disk.  So with NT, Win 98 on Linux on a 9 GB disk I literally don't have
room for Visual C++!

Pretty soon here I'll be adding a much bigger second drive to the machine and
installing BeOS intel on it as well as Windows 2000 so I can not only support
Visual C++ but also Win2k.  I'll also be trying at least one of the BSD
distributions.

Mike
-- 
Michael D. Crawford
GoingWare Inc. - Expert Software Development and Consulting
http://www.goingware.com/
cra...@go...

   Tilting at Windmills for a Better Tomorrow.

Re: [ZooLib-dev] CW Pro 6 & Visual C++

[Andrew G. <ag...@em...>]

Andreas,

> I've tried to compile the zoolib helloworld example with your new zoolib
> (from 13.2.2001), but unfortunately I've no success. I think it is an
> configuration problem, but I don't know. To many errors.

<http://www.zoolib.org/bleedingedge/> is there so that anyone who wants to
see where ZooLib is going can do so, and so that if patches are submitted
they can be taken advantage of quickly. It's not suitable for everyone. If
you're having problems with the demo source and the bleeding edge ZooLib
source then I would recommend dropping back to the 0.8.1 ZooLib sources, and
back to CW Pro 5 if necessary. The stuff in bleedingedge is a snapshot
straight off my hard drive, and is not guaranteed to work even for the apps
I'm working on, let alone for anyone else.

Unfortunately it is very time consuming to do a full build and test of the
demos on all platforms and compilers, and then to package it all for all
platforms. It's not something I'm planning on doing very often. Mike
Crawford did almost all of the 0.8.x packaging work (as well as the web
pages and actually writing the demo apps), and I have no doubt he'll put
together revised versions of the apps sometime soon-ish.

In the meantime, if you post the build errors you're seeing to the list, it
might turn out to be something trivial that I or someone else will be able
to do something about. Or it might not, in which case the demo apps will get
fixed just as soon as we can find time, but it might take a while.

Regards,
A

[ZooLib-dev] CW Pro 6 & Visual C++

[Andrew G. <ag...@em...>]

Drop me a line if you're interested in building with CW Pro 6 or Visual C++
(which the 0.8.x sources don't handle) and I can point you to a more recent
set of sources.

I'd obviously like to have the development tree available to anyone who
needs it, but as it is under development it is usually broken in at least
_some_ sense on at least _some_ platform. As I don't want to scare off
potential users with seemingly flakey code we have not yet set up a public
repository to provide access to it.

If you think it would be helpful to have access to the absolute latest set
of sources, please let me know. Any advice on how to handle the process of
releasing non-stable sources would also be appreciated.

A
__________________________________________________________________
Andrew Green                                  mailto:ag...@zo...
ZooLib Guy                                   http://www.zoolib.org
350 25th Avenue, Suite #1                   Vox: +1 (415) 831 2471
San Francisco, CA 94121-1912                Fax: +1 (415) 831 2472