RE: Cookbook release

> Supporting multiple implementations is right up my research alley
> (and related to an adaptive hypermedia showcase site that's on my
> TODO list after my new PostgreSQL and HTTP libraries are ready).
> Sadly, a wealthy benefactor will probably have to materialize
> before I can afford to do this. :)

I'm all for finding a wealthy benefactor!  ;)

The simple ideas I've had can be summarized as follows (I think I've
mentioned this briefly before):

1.  Under TWiki, we already have many Scheme snippets stored in the Scm web.
We could create a separate web for each supported implementation, and use a
variable to specify which one to use for inclusion.  I haven't actually
tested this, but I believe it shouldn't be too difficult to make that work.

2.  Since Scheme code is already being formatted via a Scheme servlet, we
could easily hook whatever we like in at that level, without being reduced
to Perl hackery.

Neither of the above deals with the question of implementation-specific text
in the topics.  For that, we could just use a simple #ifdef-style approach,
which has an equivalent in TWiki syntax, iirc.  But, that could make the
source text quite unmanageable if many implementations are supported.  For
topics that have a lot of implementation-specific text, we could resort to
having a separate topic for each implementation, again selecting the
appropriate ones based on a variable (set via e.g. the user's preferences or
the URL).
Using separate topics isn't ideal (the cut-and-paste antipattern), but
perhaps better than nothing.

Anton



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click