phpwiki-talk

Re: [Phpwiki-talk] Page scoring.

[Reini U. <ru...@x-...>]

Steve Wainstead schrieb:
> Why 80 columns? Readability again. The reason magazines and newspapers
> print in columns is because the human brain can best read lines that are
> 6-8 words long. Anything shorter or longer slows down the reading process
> considerably.

well said! 
And I though I was the only one who knew this :) (but you worked for a
newspaper)

Layouters and fast-readers even count in eye-hops, where a hop is a word or 
a easy to identify group of words. You normally read in 3-5 hops and can 
train up to 5-6 hops.
80 chars for reading is a pretty large number for readers, but okay 
for programmers.

in my current php project people don't do any linebreaks, but my emacs does. 
so I don't care.

like:            <td align="right"><br><form name="search" <? echo 'action="'
. tep_href_link(FILENAME_ADMIN_USERS, tep_get_all_get_params(), 'NONSSL') .
'"'; ?> method="get"><?php echo
tep_span_class("smallText",'','&nbsp;'.HEADING_TITLE_SEARCH . '&nbsp;<input
type="text" name="search" value="'. $HTTP_GET_VARS['search'] . '"
size="8">&nbsp;' . tep_image_submit(DIR_WS_IMAGES . 'button_search.gif',
IMAGE_SEARCH)); ?></form></td>
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] New jeffshacks snapshot.

[Jeff D. <da...@da...>]

I've put a new jeffshacks snapshot up.

The new pgsql is working.
Deletion of old archived revisions is implemented.

I've been playing with the style sheets, so the look has changed
quite a bit.  I haven't tested my stylesheet hacks at all with IE yet 
(only
Netscape and Mozilla) so it could well be unreadable with IE at
this point.

A live demo is up at:
  http://phpwiki.sf.net/jeffs-hacks/wiki/

A tar-ball of the source code can be found at:
  http://phpwiki.sf.net/jeffs-hacks/files/

Jeff

Re: [Phpwiki-talk] tab-width

[Jeff D. <da...@da...>]

Just to clarify, the php-mode tab-width setting does not affect how
far blocks of code are indented (c-basic-offset controls that, and
I'm not suggesting changing that).

The tab-width setting (in combination with indent-tabs-mode (see below))
just controls how emacs achieves that indentation.  If tab-width is
set to 4 (as PEAR dictates), then emacs assumes that a tab character
in the text moves to the next multiple of 4 columns.    The problem with
this, is that most text file viewers assume that a tab moves to the
next multiple of 8 columns, so code which looks fine when viewed
with a tab-width setting of 4 can look severely mangled when viewed
with other programs.

> I actually rangled over this for some time with some programmer friends. I
> think I posted a link to this list that was something written by jwz about
> why you should not use tabs at all. It was pretty sound.

Yes, I agree.  Setting indent-tabs-mode to 'nil forces php-mode not to
use tabs at all, and just indent with spaces.  This is good.

The problem is that unless great care is taken to eliminate all tabs
in the source code, some tabs will remain.  When indentation is
achieved with a mixture of spaces and tabs, then things get particularly
badly munged when viewed by a viewer with a different idea of what the
tab-width is.


I think the intention of the PEAR standards is that indentation be 
achieved using only tabs.  This allows individuals to adjust
the displayed indentation just by changing the tab-width.
The problem is that even when tab-width == c-basic-offset, emacs
does not really guarantee that all indentation is achieved using
tabs rather than spaces.

If you use, e.g. 'less' to view the PEAR source code (at least
the version I've got) the problem will be immediately obvious.
In general, most blocks are indented 8 columns (since tabs were
used) --- that's ugly and hard to read as you point out, but at least
the indentation still properly shows the block structure.
However some lines in the PEAR code are indented with spaces.
Those lines only shift blocks over four columns.  The result
is that nothing lines up with anything.

Re: [Phpwiki-talk] PhpWiki does not survive a slashdot

[Steve W. <sw...@pa...>]

On Sat, 1 Sep 2001, Jon =C5slund wrote:

> My Shakespeare Programming Language web page (built using PhpWiki) did
> just get slashdotted. The web server died hard, very quickly. :)

yes, Wikis do not scale :-)

The only viable solution I see is to generate the Wiki as flat files
(HTML) for browsing. (Even being slashdotted will kill a flat file server
though). PhpWiki+MySQL being slashdotted? fuhgettaboutit!

cheers
~swain

>

---
                  http://www.panix.com/~swain/
"Without music to decorate it, time is just a bunch of boring
production deadlines or dates by which bills must be paid."
                     -- Frank Zappa
http://pgp.document_type.org:11371/pks/lookup?op=3Dget&search=3D0xF7323BAC

Re: [Phpwiki-talk] Page scoring.

[Steve W. <sw...@pa...>]

Finally getting around to this thread... :-)

On Sun, 2 Sep 2001, Jeff Dairiki wrote:

> Anyhow, as I said, I never use the "5 best incoming/outgoing links".
> Does anyone?

I don't, though occasionally it's interesting to look at. I think this
info should be moved off to some kind of "meta" page, or perhaps something
in the Info link.

It's always refreshing to go back to c2.com and see how clean and simple
the interface is; personally the only thing I'd change clicking on the
title search to find all pages linking to the one you're looking at, since
it's not intuitive, but that's a small thing.

>
> PS:  Anybody have any preferences on the tab-width=4 vs tab-width=8
> issue?  If no one says anything I'm going to start using tab-width=8,
> 'cause thats my preference....

I actually rangled over this for some time with some programmer friends. I
think I posted a link to this list that was something written by jwz about
why you should not use tabs at all. It was pretty sound.

I don't have the greatest eyesight in the world. I use a font size of 12
in Emacs on a 19" monitor, and I can read quite well. With indents of 8
spaces, the code will quite often wrap around and will look like a total
mess. I could go to an 8 pt font, but I will get eye strain.

Originally I went for 2 or 3 spaces indenting. 4 seems too much to me :-)
Also, I don't think code should extend beyond 80 columns, which is why you
always see me doing crap like:

$query = "select foo from bar "     .
         "where blah='blippy' and " .
         "bar=42 sort by ascending";

Why 80 columns? Readability again. The reason magazines and newspapers
print in columns is because the human brain can best read lines that are
6-8 words long. Anything shorter or longer slows down the reading process
considerably.

My 2 cents. I think the PEAR guidelines are good ones.

cheers
~swain

---
                  http://www.panix.com/~swain/
"Without music to decorate it, time is just a bunch of boring
production deadlines or dates by which bills must be paid."
                     -- Frank Zappa
http://pgp.document_type.org:11371/pks/lookup?op=get&search=0xF7323BAC

[Phpwiki-talk] hey (fwd)

[Steve W. <sw...@pa...>]

Just sharing some nice words from a user...

~swain

---
                  http://www.panix.com/~swain/
"Without music to decorate it, time is just a bunch of boring
production deadlines or dates by which bills must be paid."
                     -- Frank Zappa
http://pgp.document_type.org:11371/pks/lookup?op=get&search=0xF7323BAC
---------- Forwarded message ----------
Date: Sat, 08 Sep 2001 13:50:55 -0500
From: ~CG~ <con...@ex...>
To: Steve Wainstead <sw...@pa...>
Subject: hey

I *know* you're like, "Good Lord, what is she emailing me about now!"

However, I wanted to drop you a line to see what we're up to with PHPWiki...

http://www.exit-23.net/hunters/
http://www.exit-23.net/amongus/auwiki/index.php
http://www.exit-23.net/mutanthigh/mhwiki/phpwiki/index.php

I currently have plans to convert Exit-23 (http://www.exit-23.net)
completely over to wiki and also to start a knowlege base for the
roleplaying community there.

Thank you so much for your help and your genius!


~CG~
--------------------
http://www.exit-23.net
--------------------
"Mix in a little rectal surgery and it's my best day ever." -- Xander, BtVS

Re: [Phpwiki-talk] tab-width and new database API

[Jeff D. <da...@da...>]

Wups... I thought I sent this to phpwiki-talk, but apparently I sent it
only to Pablo...  Here it is:
======

On Sep 5, 2001, "Pablo Roca" said:
> Hum curious, why is needed a new template engine?

Well, in the process of munging my new database API into the rest of
the code PhpWiki I had to modify the browse.html and editpage.html
templates.  It bothered my again (it has always bothered me)
that template syntax was ugly and unnecessarily inflexible.

So I rewrote the template engine.  I wrote a real parser to deal with
the if blocks, with the idea of eventually adding some kind of loop
structure.  Added a way to automatically LinkExistingWikiWord,
so that "<a class="wikilink" href="###BROWSE###FindPage"><span 
class="wikiword">FindPage</span></a>" could be written more legibly.

Then, I discovered that PHP4 has this set of ob_* commands which allow
one to capture the "standard output" into a variable.  This is great,
I think, as it allows for templates to be regular php code.
So I tossed my new template engine and replaced it with a new one
which essentially just include()s the template, capturing it's output
to a variable using the ob_* stuff.  (All this refactoring explains
why the current version is, at this point, pretty ugly itself.
It's a mish-mash of the original GeneratePage code, code from my first
template engine, and the current one.  As I said, it still needs
refactored.)

> Let us know when this is available for seeing.

I'll do it now, sorry.  When it's up it'll be at
 http://phpwiki.sourceforge.net/jeffs-hacks/wiki/

> > A tar-ball can be found in:
> >   ftp://www.dairiki.org/phpwiki/
> 
> I can' connect to this server I get an error. ... :(

Yes, my virtual host seems to be unreachable.  Crap.

Try: http://phpwiki.sf.net/jeffs-hacks/files/

Cheers,
Jeff

RE: [Phpwiki-talk] tab-width and new database API

[Pablo R. <pr...@cl...>]

> * New database API.  See lib/WikiDB.php and

Cool

> * Plugins.  See pgsrc/WikiPlugin ...

Plugins? Oh, I can't wait to download the tarbal. :)

> * New template engine.

Hum curious, why is needed a new template engine?

> Perhaps I'll set up a demo wiki later tonight.

Let us know when this is available for seeing.

> A tar-ball can be found in:
>   ftp://www.dairiki.org/phpwiki/

I can' connect to this server I get an error. ... :(

Saludos,

Pablo Roca

Re: [Phpwiki-talk] tab-width and new database API

[Jeff D. <da...@da...>]

> Jeff Dairiki schrieb:
>
> Cannot wait to see it.

Okay.  Well.  I'm not done, but I'm ready to let you see it.  I've gone 
overboard
again, and I expect that not all of you are going to like it :-)

In anycase some highlights (also see pgsrc/ReleaseNotes):
* New database API.  See lib/WikiDB.php and lib/WikiDB/backend.php for 
what
documentation there is on that (so far).  Both the mysql and the dba 
backends
work for me.  I haven't put together a pgsql backend but that should be 
easy.

* Plugins.  See pgsrc/WikiPlugin for the beginnings of notes on that.

* New template engine.  Sorry, I couln't help it.  Currently it's still 
a mess,
so don't look to hard at it...

A tar-ball can be found in:
  ftp://www.dairiki.org/phpwiki/

There are too many new and deleted files for it to be worth making a new
branch in the CVS.  If the powers-that-be like my changes, I'll just 
check
them into the main branch.  (Otherwise, I'll keep the my hacks 
available
somewhere.)

Perhaps I'll set up a demo wiki later tonight.  Now I'm off to obedience
class (with the doggy.)

Awaiting all comments.

Jeff

[Phpwiki-talk] re: questions PHP Wiki

[Steve W. <sw...@pa...>]

On Sat, 1 Sep 2001, Marzi, Agentur Smartie.de wrote:

> Hi Steve!
>
> I got several questions regarding your PHP Wiki:
>
> - I created a page, for example: "index.php?JackDaniels" - where is the
> content of that page saved? I was unable to locate the flat files where the
> content is saved in.

If you configured PhpWiki to save the pages as flat files (instead of in a
DBM file, or MySQL) they should be under the directory you set in
lib/config.php.

>
> -What about the built in full text engine? Is it able to search in thousands
> of documents without problems?

Thousands, perhaps. It just does an unbounded search on the page text
(i.e. "WHERE CONTENT LIKE '%foo%'") so eventually you will run into
performance problems...

> -What is the name of the file where I can add/modify the replacement
> strings?

$WikiNameRegexp is defined in lib/config.php. I think that's what you are
looking for.

> Great work you did, mr. diver!

Really, the credit goes to Jeff and Arno and the gang. I'm just a
secretary ;-)

> PS: You forgot to add the .com in your mailto: email link on your website.

Thanks, fixed that! :o)

cheers
~swain

---
                  http://www.panix.com/~swain/
"Without music to decorate it, time is just a bunch of boring
production deadlines or dates by which bills must be paid."
                     -- Frank Zappa
http://pgp.document_type.org:11371/pks/lookup?op=get&search=0xF7323BAC

Re: [Phpwiki-talk] Curious Behaviour of Wiki

[Steve W. <sw...@pa...>]

Hi Mickey!

That's odd. The field that was showing blank (created) is an INT. Quoting
it should just create more barf. Unless MySQL lets one quote INTs. Hmm. I
wonder why it comes out blank to begin with? Perhaps this the state after
the installation? I'll take a look.

~swain

On Sun, 2 Sep 2001, Mickey wrote:

>
> Hi,
>
> I just installed phpwiki, version 1.2, at my home
> computer: a debian potato.
>
> Everytime I modified the front page, I got an error.
> I searched and found that the error was due to the
> following SQL query:
> wiki (author, content, created, flags, lastmodified, pagename, refs,
> version) values ('', '____September 2, 2001 * [FrontPage]
> ([diff|phpwiki:?diff=FrontPage]) ..... 217.128.30.29 ', ,//
>  0, 999454843, 'RecentChanges', 'a:0:{}', )
>
> so I change the lib/mysql.php file:
>       $VALUES =  "'$pagehash[author]', '$pagehash[content]', " .
>                  "$pagehash[created], $pagehash[flags], " .
>                  "$pagehash[lastmodified], '$pagehash[pagename]', " .
>                  "'$pagehash[refs]', $pagehash[version]";
> became:
>       $VALUES =  "'$pagehash[author]', '$pagehash[content]', " .
>                  "'$pagehash[created]', '$pagehash[flags]', " .
>                  "'$pagehash[lastmodified]', '$pagehash[pagename]', " .
>                  "'$pagehash[refs]', '$pagehash[version]'";
>
> and now it works well.
>
>
> thanks you for this beautiful program,
>
> bye
>
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>

---
                  http://www.panix.com/~swain/
"Without music to decorate it, time is just a bunch of boring
production deadlines or dates by which bills must be paid."
                     -- Frank Zappa
http://pgp.document_type.org:11371/pks/lookup?op=get&search=0xF7323BAC

Re: [Phpwiki-talk] Page scoring.

[Adam S. <ad...@pe...>]

> How do you define the sidebar contents? Just textually?

yep, it's just a variable in moin_config.py.

> What would be nice (heh) would be to configure a sidebar and have a
> checkbutton when editing a page to "add to sidebar". The sidebar could
> build dynamically based on the pages selected, and the developer could
> choose what classifies as an important link or not.

yep this is part of what i've been thinking about for a long time, the
marriage of wiki's with weblogs.  i want a weblog framework (ability to
register users, import rss feeds, run polls etc) but with the central part
being a wiki rather then a story engine.

drupal (drop.org) almost has this with their book module but it's too
structured for my taste.  by controlling gravity (drupals notion of karma)
you can even allow anonymous edits which is pretty cool, but because it
isn't really set up for that it has no backups etc.

> Organizing the sidebar into groups and having separators would be the
> next great step. It's not that hard to think up UI for this. Don't
> know about implementation :)

yeah ... i agree.  pikiepikie has some good features along this way but
it's missing a lot of other features as well.

adam.

Re: [Phpwiki-talk] Page scoring.

[Christian R. R. <ki...@as...>]

On Sun, 2 Sep 2001, Adam Shand wrote:

> i'm still running moinmoin but i had the same problem, especially with my
> site because i get a lot of visitors coming to specific pages and never
> really figuring out what the hell it's all about.  if anyone's curious i
> just built basic side bars and hacked them into the config file.

How do you define the sidebar contents? Just textually? What would be nice
(heh) would be to configure a sidebar and have a checkbutton when editing
a page to "add to sidebar". The sidebar could build dynamically based on
the pages selected, and the developer could choose what classifies as an
important link or not.

Organizing the sidebar into groups and having separators would be the next
great step. It's not that hard to think up UI for this. Don't know about
implementation :)

Take care,
--
Christian Reis, Senior Engineer, Async Open Source, Brazil.
http://async.com.br/~kiko/ | [+55 16] 272 3330 | NMFL

Re: [Phpwiki-talk] Page scoring.

[Adam S. <ad...@pe...>]

> Anyhow, as I said, I never use the "5 best incoming/outgoing links".
> Does anyone?

i never do on other peoples phpwiki's.

adam.

Re: [Phpwiki-talk] Page scoring.

[Adam S. <ad...@pe...>]

> Nope. Ripped it out when I made the templates. However, I sometime
> long for a site-wide "links" bar which provide navigation (the thing
> wikis are very bad at). I've hacked mine into the templates.

i'm still running moinmoin but i had the same problem, especially with my
site because i get a lot of visitors coming to specific pages and never
really figuring out what the hell it's all about.  if anyone's curious i
just built basic side bars and hacked them into the config file.

> PS: is CVS in a working state? Was wondering because I really need the
> table support. Thanks!

i'm waiting for revisions (something like KeptPages) and table markup.
moinmoin is great but i need the templating and i don't want to hack it
into the source for every upgrade.

the other thing i wish is that there was a standard wiki syntax cause it's
gonna suck retraining users.

adam.

[Phpwiki-talk] Curious Behaviour of Wiki

[Mickey <par...@pa...>]

Hi,

I just installed phpwiki, version 1.2, at my home 
computer: a debian potato.

Everytime I modified the front page, I got an error.
I searched and found that the error was due to the
following SQL query:
wiki (author, content, created, flags, lastmodified, pagename, refs,
version) values ('', '____September 2, 2001 * [FrontPage]
([diff|phpwiki:?diff=FrontPage]) ..... 217.128.30.29 ', ,//
 0, 999454843, 'RecentChanges', 'a:0:{}', )

so I change the lib/mysql.php file:
      $VALUES =  "'$pagehash[author]', '$pagehash[content]', " .
                 "$pagehash[created], $pagehash[flags], " .
                 "$pagehash[lastmodified], '$pagehash[pagename]', " .
                 "'$pagehash[refs]', $pagehash[version]";
became:
      $VALUES =  "'$pagehash[author]', '$pagehash[content]', " .
                 "'$pagehash[created]', '$pagehash[flags]', " .
                 "'$pagehash[lastmodified]', '$pagehash[pagename]', " .
                 "'$pagehash[refs]', '$pagehash[version]'";

and now it works well.


thanks you for this beautiful program,

bye

Re: [Phpwiki-talk] Page scoring.

[Reini U. <ru...@x-...>]

Jeff Dairiki schrieb:
> Anyhow, as I said, I never use the "5 best incoming/outgoing links".
> Does anyone?

I do. But I got a lot of pages, so every navigation help is welcome.
outgoing is not that interesting as incoming, but it is similar to 
a summary of links.

> PS:  Anybody have any preferences on the tab-width=4 vs tab-width=8
> issue?  If no one says anything I'm going to start using tab-width=8,
> 'cause thats my preference....

tab-width=8
please set the emacs local var in the footer so it's no issue at all. 
it's only a problem for e.g. corman lisp where the author uses 4, 
but doesn't use emacs nor the local vars markup.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] Page scoring.

[Christian R. R. <ki...@as...>]

On Sun, 2 Sep 2001, Jeff Dairiki wrote:

> I think it might be more useful.  A high revscore indicates that a page
> is likely to be a good "index page" or starting point for exploration,
> since it links to lots of things...   These then are pages which you
> are likely to stumble upon if you randomly follow backlinks...

Agreed. Much better than incoming links. However, the incoming links do
provide a (flawed) navigation mechanism, in lack of something better.

> Anyhow, as I said, I never use the "5 best incoming/outgoing links".
> Does anyone?

Nope. Ripped it out when I made the templates. However, I sometime long
for a site-wide "links" bar which provide navigation (the thing wikis are
very bad at). I've hacked mine into the templates.

PS: is CVS in a working state? Was wondering because I really need the
table support. Thanks!

Take care,
--
Christian Reis, Senior Engineer, Async Open Source, Brazil.
http://async.com.br/~kiko/ | [+55 16] 272 3330 | NMFL

[Phpwiki-talk] Page scoring.

[Jeff D. <da...@da...>]

What's the concensus on the current page scoring scheme?

<ramble>

I haven't hacked it into my new database API yet, and I'm not sure
I want to.  Personally, I don't think it's particularly useful as it
is now.

Currently the "page score" is basically a count of how many pages link
to pages which link to the page.  (Not quite -- pages can be counted 
twice. i.e. in the following case, the score of C will be 2, not 1
--- A gets counted twice...)

   A--->B---->C
   |          ^ 
   +--->D-----+


Anyhow, the general idea is: the more links there are to a page, the 
higher
it's score....

Currently neighboring pages which high scores are listed at the bottom 
of
each page in the wiki.   I never use this feature --- never even look 
at it.

My take on the matter is:  if everyone links to a page (therefore giving
it a high score) I don't really need help finding it...  These are pages
that one is likely to stumble upon just by following random links in 
pages.

Actually, if the score were done in reverse,

  revscore of page A = how many different pages can I get to from A in 
n clicks

I think it might be more useful.  A high revscore indicates that a page
is likely to be a good "index page" or starting point for exploration,
since it links to lots of things...   These then are pages which you
are likely to stumble upon if you randomly follow backlinks...

</ramble>

Anyhow, as I said, I never use the "5 best incoming/outgoing links".
Does anyone?


Jeff

PS:  Anybody have any preferences on the tab-width=4 vs tab-width=8
issue?  If no one says anything I'm going to start using tab-width=8,
'cause thats my preference....

Re: [Phpwiki-talk] PhpWiki does not survive a slashdot

[Reini U. <ru...@x-...>]

Aredridel schrieb:
> > Jon =C5slund schrieb:
> > > My Shakespeare Programming Language web page (built using PhpWiki) did
> > > just get slashdotted. The web server died hard, very quickly. :)
> >
> > how exactly? any noises and symptoms? what hardware?
> >
> > I would temp. block with ipchains, as I did last month with code red.
> >   http://screaming-penguin.com/phorum/read.php?f=3D1&i=3D686&t=3D625
> >
> > I really have to write the dynamic robot blocking code now...
> > Every user has to be counted, php4 sessions would be the best.
> > for my php4 e-commerce project it works fine. (file sessions and mysql
> > sessions)
> 
> What I'm going to do (NBTSWikiWiki took a hit tonight from a search engine)
> is make robots.txt a script, and have it log the IP/useragent pair, and the
> wiki code just dump the raw wiki pages with only links linked instead of
> full rendering for anything with that IP/Useragent combinatiion that's hit
> robots in the last 24 hours.  Should be doable with a minimum of fuss,
> I think... about 25 lines of code, I'd think.

yes. I already wrote this.
http://xarch.tu-graz.ac.at/home/rurban/acadwiki-1.3.6pre/viewsrc.php?show=lib/robots.php#src

I'm constantly hit by search engines. some behave okay, some get nested in 
edit and diff links. I blocked these statically.
search engines and specific misbehaving agents are very easy to block 
(see the robot blocking code) 
the technical problem is dynamic blocking which can take a site down.

thttpd for example does this on the server side. apache is too stupid.
(bandwidth limiting)
mod_php4 should work for thttpd also, but php compilation is that tricky 
that I wouldn't try that out just for fun. I just broke a german phpwiki 
of mine just because of a new php binary (gettext issues).
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] PhpWiki does not survive a slashdot

[Reini U. <ru...@x-...>]

Jon =C5slund schrieb:
> My Shakespeare Programming Language web page (built using PhpWiki) did
> just get slashdotted. The web server died hard, very quickly. :)

how exactly? any noises and symptoms? what hardware?

I would temp. block with ipchains, as I did last month with code red.
  http://screaming-penguin.com/phorum/read.php?f=3D1&i=3D686&t=3D625

I really have to write the dynamic robot blocking code now...
Every user has to be counted, php4 sessions would be the best.=20
for my php4 e-commerce project it works fine. (file sessions and mysql
sessions)

What do you think? optional or with php3 workarounds? (phplib)
How is ward doing this? logfile analysis or sessions?
--=20
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] PhpWiki does not survive a slashdot

[Jon <d9...@na...>]

My Shakespeare Programming Language web page (built using PhpWiki) did
just get slashdotted. The web server died hard, very quickly. :)

--=20
___\ Jon =C5slund

Re: [Phpwiki-talk] tab-width and new database API

[Reini U. <ru...@x-...>]

Jeff Dairiki schrieb:
> On Aug 30, 2001, Reini Urban said:
> > Does it allow subpages then?
> 
> Err.... no.
> But I'm not sure that's a back-end issue (at least not too much.)
> Not that I'm all that interested in sub-pages.
> 
> I'm thinking, if you want sub-pages, you let '/'s (or whatever) in
> the page names denote sub-pagination --- the back-end doesn't really
> care, I don't think --- it's more of a mark-up issue.
> Or is there something I'm not thinking of?

you are right. it's merely a navigational (search,...) issue.
just take care that '/' is a valid pagename.

for preprocessing subpages (a special subpage -> page relation) it 
would be a db issue, but not for the backend. 
for < 5000 pages a seperate grouping table for subpages is academic.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] tab-width and new database API

[Jeff D. <da...@da...>]

On Aug 30, 2001, Reini Urban said:
> Does it allow subpages then?

Err.... no.
But I'm not sure that's a back-end issue (at least not too much.)
Not that I'm all that interested in sub-pages.

I'm thinking, if you want sub-pages, you let '/'s (or whatever) in
the page names denote sub-pagination --- the back-end doesn't really
care, I don't think --- it's more of a mark-up issue.
Or is there something I'm not thinking of?

Re: [Phpwiki-talk] tab-width and new database API

[Reini U. <ru...@x-...>]

Jeff Dairiki schrieb:
> As these are major changes, I think I'll check them into a new
> branch ('Jeff_Hacks_Again_Branch' ?) to give you all a chance to veto
> the changes if you don't like them before they're dropped into
> the main branch.

Cannot wait to see it.

Does it allow subpages then?
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/