Re: [Plib-devel] PLIB 'Neat stuff' library

[Steve B. <sjb...@ai...>]

Dave McClurg wrote:

> i kind of like how SDL manages games, apps, demos, and libraries that have
> been created around their *core* library.  they have each in a seperate
> download. this keeps the *core* plib very low level and clean.
> 
> http://www.libsdl.org/libraries.html
> http://www.libsdl.org/demos.html
> http://www.libsdl.org/apps.html
> http://www.libsdl.org/games.html

Well - yes - but I find SDL to be one of the WORST libraries to keep
track of.  I'm forever trying to build applications that demand
SDLmixer version x.y.z and SDL version p.q.r - I just can't keep track
of all the minor revision numbers of all the stoopid little components - some
of which in turn only work with some specific version of the base package.

There have been MANY SDL-based packages that I just can't keep running
together because they all demand mutually exclusive versions of one
sub-library or another.  SDL is a nice enough package - but the way it's
distributed SUCKS - IMHO.

I just wish they'd release ONE bundle with everything self-consistantly
up to date - even if that means that SDLMixer 1.2.3 is actually identical
to 1.3.0.

The thing that I like about our present approach with PLIB is that all
the component libraries are released together - you install it and you
have everything you need at that same revision.

> right now, http://plib.sourceforge.net has a few links to the more
> prominent projects that use plib.  it would be interesting and useful
> to see more in a format like http://www.libsdl.org/games.html.  i
> would certainly be interested in adding my own project there.

Hmmm - cute.

If you'd like to me to add something you are working on - I'd be very
happy to do so.  I'd like a small logo/icon to use with it also.

We should certainly think about doing something like the SDL list though.
 
> as for directory structure in cvs, i think the following might work:

> plib - core library
> apps/ssg_viewer
> apps/ssg_converter
> apps/mod_player
> demos/tux_example
> demos/fnt_example
> libs/ssg_sky
> libs/keyflier
> libs/particle_engine

Yes - although changing the present structure is a pain because CVS won't
let you delete directories.

Hence we are somewhat stuck with 'src' for the PLIB sources and 'examples' and
'doc' for the examples and documentation.  I don't have a problem with
adding 'apps' and 'auxlibs' for the applications and auxiliary libraries.

Perhaps 'tools' would be better than 'apps' if we are talking about viewers,
players, convertors and such like.

When we come to make a release though - I'd like to bundle the aux libraries
in with the main PLIB libraries so that people who just want to install PLIB
in order to get a game running don't have to download and install a dozen
separate components.

Minimising dependencies is VERY important.

Examples and tools/applications that are not going to be needed by 'Joe Public'
should be distributed separately to keep the file size to a minimum though. Only
developers ever need those things - and developers are increasingly becoming a
minority as PLIB gets more popular.

> other, *large* projects like ppe and tux_kart, of course, would have
> their own cvs source repositories like now.

CERTAINLY!

-- 
Steve Baker   HomeEmail: <sjb...@ai...>
              WorkEmail: <sj...@li...>
              HomePage : http://web2.airmail.net/sjbaker1
              Projects : http://plib.sourceforge.net
                         http://tuxaqfh.sourceforge.net
                         http://tuxkart.sourceforge.net
                         http://prettypoly.sourceforge.net