Re: [Phpwiki-talk] Re: wiki with https

[<are...@nb...>]

> > This should be a simple fix, but what's the simplest? We can add another
> > config variable to let the admin decide between 'http' and 'https', but
> > there should be a way to let the Wiki decide this itself. Suggestions?
> 
> any way to use relative urls instead of absolute ones ?

Yes, but I'll have to track back and forth over my changes (which now number in
the thousands!) from the stock distro to find out what I did; I -think- I'm
using only relative URLs-- if not, I'm dynamically generating correct ones
using the environment variables that PHP has available.

If anyone wants to log in and steal the source code to NBTSWikiWiki, just email
me and I'll set up an account-- the server's welcome to logins from afar, so
don't be bashful. I keep meaning to clean up the code enough to check into an alternate CVS branch, so it's available, but I haven't gotten there yet.

Oh, by the way, I'll be checking in a new flatfile driver that's much happier
than the old one-- searches work and all that.

My biggest problem lately in keeping up with PhpWiki-release version is that I
prefer non-templating code; since the translation functions take well over five
seconds on this server for a long page, I prefer to be sending data to the
client for that whole time. (It has always seemed a shame to me to have a nice
language like PHP where the scripting is nicely embedded try as hard as it can
to make HTML separate again. I guess I prefer to have it there, and then give a
human editor the instructions "That's PHP; Don't touch it until you learn about
it. It's cool, though, so learn it..."); anyway, in the NBTSWikiWiki release is
some pretty slick code to flush output every 16 lines (since there's
expressions that can be applied to more than one line at a time for speed)...
the whole parser is -finally- beginning to be clean again, so maybe at some
date in the future, I'll check in an alternate module for wiki_transform, using
the (much more readable!) NBTSWiki markup.

(My goal in writing the markup was to have the markup make total sense in text
as well, using already-familiar conventions such as "-bold in  here-" and
/italic text like this/, and, of course, astrices as bullets.)

Anyway, this email is getting plenty long, and it's time for a break from wiki
code, seeing as I spent yesterday adding features and smoothing the parser
instead of working, so today, I write scripts for someone else!

g'day,
	Aredridel